Product Updates

Hello everyone,In this release, we have added support for Windows authentication, multi-row deletion, grouping tasks, and advanced sorting in cubes. We have also extended the HTML editor pop-up with more options and improved the breadcrumbs to show the location of your most recent action. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.12 (release candidate)For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.3.12 (release candidate) hereThis is a release candidate that you can use to test the new features. It is not suitable for use in a production environment. The full release will be available next week. ContentsDemo Universal GUI version 2024.3.12 (release candidate) New and changed Support for Windows authentication Support for multi-row deletion Support for grouping tasks Support for advanced sorting in cubes Support for HTML forms in Preview More options in the HTML editor pop-up Context-sensitive breadcrumbs Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedSupport for Windows authenticationnewThe Universal GUI now supports Windows authentication.For a smooth login experience, the Universal GUI now redirects users to the Indicium login page when Windows authentication is enabled for Indicium (menu Authorization > Users > tab Form > group Authentication). The login page of Indicium allows users to log in without re-typing their domain account credentials.For more information, see Windows authentication. Support for multi-row deletionnewIn the Universal GUI, you can now delete multiple selected records at once in a grid. Note: it is not yet possible to delete records across pages when pagination is enabled.In the GIF below, you can see how multiple records are deleted. In this example, "Slow 4G" network throttling is used to show the progress indicator. This progress indicator is not shown if deletion is completed within 200 milliseconds.Deleting multiple records in a grid Support for grouping tasksnewWe have added support for grouping tasks. Between two different groups, a divider will be displayed. Support for advanced sorting in cubesnewWe have added support for advanced sorting in cubes:Sorting a cube view on a domain with elements now follows the setting Sort order of elements, (Translation or Order no) in the menu Data > Domains > tab Form > tab Domains. In the tab Elements, this setting is available as Sequence no. You can now sort a cube view dimension by a cube field that is not present in the cube view itself (menu User interface > Business Intelligence > tab Tables > tab Cube views > tab Cube view fields > tab Form > tab Cube view field > setting Sort by cube field). Support for HTML forms in PreviewnewPreviously, HTML forms embedded inside a webpage that used the Preview screen component were not allowed to be submitted. You could recognize this situation in the browser's developer tools by the message 'Blocked form submission to [your website]'.Now, it is possible to allow HTML forms to submit by setting the extended property UnsafePreviewAllowForms to true or yes.Enable this feature only when you trust the contents of all web pages you intend to embed. HTML forms lack the Cross-Origin Resource Sharing restriction that is otherwise standard for ways to perform web requests. This makes it possible to access external websites that normally disallow such requests. More options in the HTML editor pop-upnewWe have added more options to the HTML editor pop-up:Font size and font family Text style and alignment Table Links Image upload Context-sensitive breadcrumbschangePreviously, the breadcrumb in the top bar of an open document showed the selected record of the main subject or, in the case of a zoomed-in detail document, it also showed the path to the parent subject.We have extended the breadcrumbs with nested detail navigation. They now show the location of your most recent action. For example, if you are working in Project > detail: Subproject > detail: Activities, the breadcrumb now shows: V.C. Partners > Development phase 2.0 > Analysis.This enhancement is particularly useful when your parent subject is hidden in an inactive tab, as it helps you track the project and subproject on which you are currently working. Minor fixes and tasksGeneric:We have fixed an issue where the subject could get unresponsive after dragging a splitter to resize its components. Tooltips are now shown at the top end instead of the beginning. This change reduces the chance of overlap with previous elements.For grids and forms:The HTML control did not display pasted text if other text was already selected in the control. This issue has been fixed. Previously, when opening the lookup pop-up of an empty field, users would see the form with the details of the first item in the lookup table. Now, the list of lookup items is shown instead. This change prevents confusion by showing an unrelated item as if it were selected.For cubes:Domain elements were not translated in the x-axis and legend of a chart, and in the pivot grid. The displayed values were the raw database values instead of the translated ones. This issue has been fixed. We have improved the date/time notation in pivot grids and charts. All types are now formatted based on the browsers' local settings. When data in a category (row) contained a quote ', a bad request message was displayed when the category was expanded. This issue has been fixed. When a pivot grid was part of a nested subject, the deep link would try to use the parent subject as the domain, resulting in bad request errors. This issue has been fixed.For process flows:In some cases, the Activate detail tab process action did not work. Especially when it was located in nested component tabs or when jumping back to the first tab page. This has been fixed.For session expiration:Sometimes, switching to a different application when the session expired resulted in an application error. This has been fixed. When the session expired, multiple session-expired pop-ups were displayed instead of just one. This has been fixed. In some cases, when the session expired, an infinite loop was running in the background, triggering API requests. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:The styling update, starting with the menu and global frame of the application (we expect the styling update to take multiple sprints) Editable pivot grid Grid column reordering including saving this to User preferences Casing of tab header labels, to solve this community idea.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

This is an additional release for the Universal GUI version 2024.3.11. This release contains the following fixes for the lookup editor:A crash occurred when opening the dropdown if the lookup display column has a domain with elements. Furthermore, the representation would also be incorrect in this case. The translation was incorrect when the database value was 0. These issues were introduced in the 2024.3.10 release.The 2024.3.11.2 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2024.3.11. This release contains the following fixes: If the user was typing in an HTML input field, focused another application or browser tab, returned to the HTML field and typed some more, the second part that was typed would not be saved when saving the record. This is fixed now. When "Refresh after update" was set as "Row" and the user edited the row, the preview component would wrongly display just "No preview available". This has been fixed. The 2024.3.11.1 release is now available for download in TCP.

October 28, 2024:Full release 2024.3.11 (from release candidate 2024.3.11) Solved the following issues found in the release candidate: The date control flashed when choosing a different date from the one already set. This is fixed now. When updating the date, two PATCH requests were sent to Indicium. This is now a single request. Once a record was dropped into the grid, the records could not be dragged again. This is fixed now. In charts, Domain element translations were only shown for multi-series. Now also single-series are included. We improved tooltip behavior to hide it once the element is left by the mouse cursor. This way the user can't unexpectedly click a button by clicking its tooltip. We have fixed an issue where the subject could get unresponsive after dragging a splitter to resize its components.  Hello everyone,In this release, we made sure users are always working on the latest deployed version when the Universal GUI is started. Besides, we added support for the conditional layout setting 'Apply to' and for multi-record selection in the default editable grid. For the barcode control, we introduced the option to suppress the on-screen keyboard on mobile devices. We also improved the date input and added week numbers to the date calendar on desktop. Additionally, we resolved several minor issues and tasks. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.11For more information about setting up the Universal GUI, see the Universal GUI setup  guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.3.11 here  ContentsDemo Universal GUI version 2024.3.11 Breaking Support for Thinkwise Platform releases 2022.1 and 2022.2 has ended New and changed Now always using the latest version when loading Universal Date picker and date field changes Support for conditional layout setting 'Apply to' Support for multi-record selection in a default editable grid Support for the Between/Not Between operator in the Filter form component Button to open preview in a new tab Barcode control - Suppress on-screen keyboard Minor fixes and tasks What we will be working on next sprint Questions or suggestions? BreakingSupport for Thinkwise Platform releases 2022.1 and 2022.2 has endedIn accordance with our Lifecycle Policy , the Universal GUI support for Thinkwise Platform releases 2022.1 and 2022.2 has ended.Upgrade to at least the Thinkwise Platform release 2023.1. New and changedNow always using the latest version when loading UniversalchangeWe have made sure users are always working on the latest deployed version when the Universal GUI is started. This is a long-awaited feature on the community with a lot of upvotes (59!). This also fixes issues where it was not possible to log in to an application after a platform upgrade because the cache was not yet refreshed. The cache is now refreshed before the login page is shown.Going forward, a user should only get messages about a new version when the model is updated while the user is active in the application. Note that this solution is only applicable from this version onwards. Date picker and date field changeschangeOn desktop, we have replaced the date picker component (used for Date and DateTime controls). This fixes some issues and allows us to now show week numbers. This was a highly requested community idea with 37 upvotes. In addition, the keyboard input has improved using input masks. For example, typing the year as '24' will now become 2024 instead of the input becoming empty after leaving the field.Besides this, in some browsers, when using the calendar to pick a date in a Date or Datetime control, we have fixed the field value being updated immediately after a user selected a different month. This fixes prematurely triggering the layout and default logic.Week numbers in the calendar Support for conditional layout setting 'Apply to'newIn the Software Factory, you can specify to which components a conditional layout should apply. We have now added support for this setting in the Universal GUI. It is available in the Software Factory in the menu User interface > Subjects > tab Default/Variants > tab Data > tab Conditional layout > tab Form > tab Conditional layout > field Apply to. The following options are available:Grid, Form and Edit - The conditional layout is applied to grid and form, in both read and edit modes. Grid and Form - The conditional layout is applied to the grid and form, only in read mode Grid only - The conditional layout is applied to the grid, only in read mode Form only - The conditional layout is applied only the form, only in read modeAdditionally, we have solved a problem where using the same style for different conditional layouts would only apply to the last conditional layout. Support for multi-record selection in a default editable gridchangePreviously, it was only possible to execute a task or Excel export on a selection of records when the grid was not editable. In particular, in a default editable grid, these features excluded each other. Now, multi-record selection is available in a default editable grid as well. Support for the Between/Not Between operator in the Filter form componentnewUsers can now apply the Between/Not Between operator in the *FilterTo enable this, they must first select the Between/Not Between operator in the Filter pop-up from the toolbar and enter the desired values. You can also set the default operator to Between in the Software Factory menu User interface > Subjects > tab Data > tab Filter. Then, the chosen field in the inline Filter form will show two input fields that the user can adjust as needed. Button to open preview in a new tabnewDue to CORS and the way browsers work, the Universal GUI cannot always show URLs in preview components.For that reason, we have added a button to preview components to open the previewed content in a new tab. This button is also shown when the file can be shown, which has the advantage of showing it larger in a separate browser tab.Button to open preview in a new tab This is opt-in, so the button only appears if you add the Screen component property showPreviewOpenButton to the Preview component in the menu User interface > Screen types > tab Screen components > tab Screen component properties.Screen component properties Barcode control - Suppress on-screen keyboardnewYou can now suppress the on-screen keyboard for the barcode control on mobile devices by adding the extended property SuppressBarcodeKeyboard. Set the value to yes. This feature is useful when using a barcode scanner that automatically enters the barcode value into the control. Minor fixes and tasksFor cubes and charts:If a cube field was configured with a specific number of decimals, the chart would previously show only 2 decimals. Now, it respects the setting configured in the Software Factory. Domain elements were not translated in the x-axis and legend of a chart, and in the pivot grid. The displayed values were the raw database values instead of the translated ones. This has been fixed. Cells with NULL as a value in a pivot grid were displayed as 0.00. This has been fixed.For grids and forms:When a user used a task to add a record to a table detail, the badge for the detail would not update. The same issue occurred if the user refreshed the table with the Refresh button. This issue has been fixed. The Not equal to layout condition was incorrectly applied to cells that had no value. This has been fixed. The conditional layout is now only applied to cells that have a value.For grouping in grids:The rules for enabling grouping in grids were not applied correctly. The behavior has been adjusted to work like this: Non default editable grid: If not in edit mode, grouping is enabled If in edit mode and auto-save is enabled, grouping is enabled If in edit mode and auto-save is disabled, grouping is disabled. Default editable grid: If auto-save is enabled, grouping is enabled (regardless of whether the user has changed a record in the grid) If auto-save is disabled and no records have been changed, grouping is enabled If auto-save is disabled and a record has been changed, grouping is disabled Previously, when grouping by a column in the grid and changing the active record, the grouping would be removed. This issue has been fixed, and grouping now persists across row changes. Group columns were not always added to locked columns. This issue has been resolved, and group columns are now correctly displayed within the locked columns area.What we will be working on next sprintThe next sprint we will be working on:Finishing context-sensitive breadcrumbs Multi-record delete Editable pivot grid (we expect this to take multiple sprints) Pivot grid column widthQuestions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

September 30, 2024:Full release 2024.3.10 (from release candidate 2024.2.15) Solved the following issue found in the release candidate: Pivot grids with an axis based on a group interval like 'year(date)' would give a bad request error when the drill-down pop-up was opened by double-clicking. This has been fixed.  Hello everyone,In this release, the FormList component has been improved with support for comboboxes, more refresh options, and an active record that moves with the editor. We have also added support for the property Show grid header in the screen type modeler.The performance of editing and task/report execution has been further optimized. DemoAs always, we have made a demo for you; try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.10For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.3.10 (release candidate) hereThis is a release candidate that you can use to test the new features. It is not suitable for use in a production environment. The full release 2024.3.10 will be available next Monday. ContentsDemo Universal GUI version 2024.3.10 Contents New and changed FormList - Support for lookup comboboxes FormList - More refresh support FormList - Active record and breadcrumbs Performance - Editing and task/report execution Security update Support for Show grid header in screentype modeler Deep links to log files Row selection in grid Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedFormList - Support for lookup comboboxesnewIn a previous release, we added support for lookup editors in the FormList component.At that time, we chose not to support comboboxes because a combobox would load its list of items after the editor appeared on the screen. Since the FormList displays an editor for each record, this would trigger many list requests and load unnecessary data.Instead, the lookup editor was always presented as a suggestion control in which the user had to search for options. The disadvantage of this approach was that the user has to know what values to search for. Especially for a small list of options, a combobox is more user-friendly.We have improved the combobox to load options after it is opened for the first time. This means that the use of comboboxes in a FormList is now supported.Whether it becomes a suggestion control or a combobox depends on the selected control type on the lookup reference in the Software Factory. FormList - More refresh supportchangeWe have improved how data is refreshed after changing a field value in the FormList component. Previously, only refreshing a Subject was supported. Now, we have added support for refreshing a Document (from a detail subject) and a Row. You can find these options in the menu User interface > Subjects > tab Default > tab Settings > tab Performance > group Refresh > field After update.We recommend refreshing the subject only when necessary, as the FormList displays editors for every record in the set and re-renders the layout for each row. See also Refresh behavior in the Software Factory documentation. FormList - Active record and breadcrumbschangeIn the FormList component, the active record now moves with the editor on which a user focuses. Previously, the first record remained the active record no matter what a user did in the FormList. This offers new possibilities for combining the FormList with other components, such as a detail tab subject to present detail data of the active record. In addition, the breadcrumb now shows the active record, and you can delete the active record. Performance - Editing and task/report executionchangeWe have further improved the performance of the Universal GUI by combining and saving requests for editing and task/report execution.The actions for Add, Copy, and task/report execution now combine the staging request with getting the result of the layout and default application logic. A lookup editor previously made an extra "translation" request after editing started. As the display value is already known, these requests (one per editor) no longer occur. This saves a lot of requests, especially when the subject is default editable.Skipping these requests saves waiting and processing time, and server-side resources for Indicium. Security updatenewWe have fixed the following security advisory: GHSA-mmhx-hmjr-r674.This resolves a security issue affecting some areas where HTML is displayed in the Universal GUI, including:HTML control (view-only mode) Preview component displaying an HTML field Prefilter, task, and report button tooltips Column, report, and task column tooltips Tooltips for grid headers Maps marker popupsIf a malicious actor were to inject an HTML value into one of these areas, such as through the Indicium API, this vulnerability could be exploited. In such a case, if a user had one of these elements visible, the attacker's JavaScript payload could be executed. In the worst-case scenario, the attacker could execute Indicium requests using the victim's credentials.Thanks to Indicium's Content Security Policy, the risk of exploitation was low. In addition, we strongly recommend always configuring Security headers. Support for Show grid header in screentype modelernewWe have added support for the property Show grid header in the screen type modeler (menu User interface > Screen types > tab Design). If this setting is set to false, the grid header will be hidden in the Grid screen component.Show grid header in the screen type modeler Deep links to log filesnewDatabase and server error messages now include a deep link to the indicium log files. This feature is only available for users with the role developer.Requests that produce a database error message include a deep link to the database event log Requests that produce a server error include a deep link to the error logThis makes it easier to find the cause of the error and resolve it.An error snackbar with both deep links. Row selection in gridchangeA selected record in a grid can be no longer available because of several reasons, for example:A user deletes the record A user edits the record and the record no longer meets the filter criteria A user deletes a record with a task, or edits a record with a task and the record no longer meets the filter criteria A user adds or copies a record but the record does not meet the filter criteriaPreviously, the grid would refresh and the first row would be selected. Now, the next record after the one that was removed is selected, which is more consistent with the expected behavior. For an add or copy action, this is still the first row. Minor fixes and tasksFor pivot grid and chart When a pivot grid had a related parent subject without any records, the pivot grid would still show data. This has been fixed. We solved the following issues in the pivot field list editor, the pivot grid, and the chart when multiple cube fields had the same source field: When you configured a column as both a dimension and a value When you configured multiple group intervals, like year, month from the same date When you configured multiple aggregations, like sum and average, for the same columns This could lead to: Dimensions disappearing in the editor when re-ordering them Values disappearing after dropping them into the editor Categories changing when switching between the pivot and chart tabs Charts with no y-axis Date interval dimensions showing the wrong interval, for example, year when month was configured In some cases, actually crashing the GUI For form and gridWhen a user selected a grid cell and pressed CTRL+C to copy, the Universal GUI would copy the whole grid row to the clipboard. Now, it only copies the selected cell. We have fixed an issue where in some cases, dragging a row over a drag/drop grid, would not indicate the rows being dragged over. When you grouped columns that render images inside grids, the images were scaled up in the group column. This has been fixed. When switching between open documents, some forms in the screen would flicker briefly. This should no longer happen. When a default editable subject was saved using auto_commit, it would not return to edit mode automatically. This has been fixed. Default editable details would not always go into default edit mode, for example, when executing a Zoom detail process action for the second time. This has been fixed. Numeric input would remove the minus sign, for example, when a user entered -0.5. This has been fixed. Additionally, a user can no longer add negative numbers if the Min. value (menu Data > Domains) in the Software Factory is 0 or higher than 0.For tasksTask execution was not halted after user input was marked as invalid by domain input constraints. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Grid multi-select in edit mode (continued) Calendar component: We will begin fixing the issue where the calendar component fills in the date during navigation. (continued) Force Universal GUI update Context sensitive bread crumbs - Breadcrumbs showing navigation to detail subjects Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  

This is an additional release for the Universal GUI version 2024.2.14. This release contains the following fix: When clicking the barcode scanner icon to scan using the camera, the camera didn't work. This has been resolved. The 2024.2.14.1 release is now available for download in TCP.

September 2, 2024Full release 2024.2.14 Solved the following issues found in the release candidate: Pivot tables did not respond to certain filter actions, such as toggling prefilters. We allowed deep-linking to ourselves without starting a new browser tab. When the link explicitly was configured to jump to a new tab, this was ignored. After clicking on a card list HTML (deep)link, the page would occasionally remain stuck in a loading mode, requiring an additional refresh to load correctly. After modifying the browser URL to jump to a subject of an application that had not been visited before, a crash occurred. Attribute tree rows without a group had the wrong order compared to the 2024.2.13 release. Now: ' ' (one singular space) is also considered a valid group value. '' (empty text) is treated as no group, equivalent to null.  Hello everyone,In this release, we added many improvements to the grid, form, and other components.One of the more noticeable changes is the improved grid performance. We have optimized the way in which the grid handles requests, which results in a better user experience. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.2.14For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.2.14 here ContentsDemo Universal GUI version 2024.2.14 New and changed Improved grid performance More grid improvements Form improvements Improved HTML control with a deep link Cube improvements Badge improvements Bar screen component sizing What we will be working on next sprint Questions or suggestions? New and changedImproved grid performanceIn this release, we have improved the grid performance, especially when (default) editing.One way the grid's performance has been improved is by optimizing its request handling. This is done by canceling requests that are no longer needed, which can happen when the user switches between rows in the grid.Besides this, we have improved the speed with which the Universal GUI builds up the grid, also while (default) editing. More grid improvementsIn addition, we have made some other improvements to the grid:Sometimes, when a user switched rows while editing in the grid, focus would be lost. The user had to click to reapply focus before being able to continue editing. This has been changed so that focus is now retained when switching rows. When a grid had grouped labels and the user switched rows, the group labels would blink momentarily. In some cases, parts of the tree would blink when switching records in the tree. Now, the group labels and tree parts no longer blink. Previously, when clicking anywhere on a grid cell rendering a checkbox, the checkbox's value was toggled. The same applied to forms, where clicking anywhere on the slot rendering a checkbox toggled its value. For example, in the Pivot settings pop-up, clicking above or below the checkbox's label toggled the value. This behavior has been adjusted to prevent users from unintentionally changing checkbox values. Now, the checkbox's value will only be toggled under the following conditions: In grids, when clicking within 12 pixels of the checkbox. In forms, like the Pivot settings pop-up, when clicking the checkbox control (including its padding) or the label. When editing in a grid with Auto-save activated and pressing the up or down arrow keys, the user interface would previously scroll slightly towards the previous or next row. Now, it only scrolls when the previous or next row is partially or fully out of view. This change reduces distractions while editing. Form improvementsThe fields with a File upload or File link control are now the same size as other fields. After editing and saving a row in the grid or form, users would briefly see the previous value in the form. Now, after updating the row, the latest values are displayed when saving. When a numeric control received focus on a mobile device, the value would not be selected, and it would not always show the right format; for example, "16.00" would be shown as "16". Both issues have been solved. Improved HTML control with a deep linkIn the HTML control (menu Data > Domains), you can add plain HTML, including URLs, to trigger deep links or enable navigation within your application. For card lists and grids not in edit mode, clicking a link within an HTML control would open in the current browser tab instead of a new one. This has been altered.Now, for example, if an HTML control contains a link to trigger a process flow that opens a specific subject within your application, clicking that link will open the subject in a new browser tab.We have added support for the following routes along with the route that triggers a process flow (in the examples, origin refers to https://16098.thinkwise.app and https://16098.thinkwise.app):origin  Example: https://16098.thinkwise.app/  Takes the user to the root application origin + /application=:application  Example: https://16098.thinkwise.app/#application=1286 Takes the user to application 1286 origin + /application=:application/subject=:entityId  Example: https://16098.thinkwise.app/#application=1286/subject=car Takes the user to the subject car in application 1286 origin + /application=:application/processflow=:processFlowId  Example: https://16098.thinkwise.app/#application=1286/processflow=open_car_subject Takes the user to application 1286 and triggers the process flow open_car_subject  origin + /application=:application/subject=:entityId/subjectVariant=:entityVariantId  Example: https://16098.thinkwise.app/#application=929/subject=project/subjectVariant=project_start_empty Takes the user to the subject project in application 929 with the variant project_start_emptyThe origin is not required. Only the route can be specified as well. Cube improvementsClicking the name of a cube field will no longer remove it from the cube. When the user reordered the categories in the pivot table fields, sometimes all the category columns would be emptied. Bad request errors no longer occur when a pivot contains a numeric category that has been set to default Expand in the Software Factory (menu User interface > Business Intelligence > Tables > Cube views > Cube view fields > Form). Badge improvementsBadges would sometimes not be updated. This has been fixed. Bar screen component sizingWe have fixed an issue with bars sometimes not covering 100% of the available width.This issue occurred when multiple bars, such as an action bar, taskbar, prefilter bar, or report bar, were placed next to each other. What we will be working on next sprintGrid multi-select in edit mode Calendar component: We will begin fixing the issue where the calendar component fills in the date during navigation. This task is expected to take two sprints. Database error navigation: Enabling users to navigate directly to the database error from a snack bar message. Manage Personal Access Tokens: Adding management of personal access tokens to the profile menu. Pivot improvements High-priority tickets Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  

This is an additional release for the Universal GUI version 2024.2.13. This release contains three fixes: In 2024.2.12.2, switching between open documents and visited detail tabs became slower to ensure consistent performance when working within an open document. We have improved performance of switching between open documents and visited detail tabs again, without the drawback of Universal becoming slower with more open documents and visited detail tabs. We will work on improving switching between open documents and visited detail tabs further, for instance less flickering when reactivating. There were cases in which tooltips would wrongly stay shown even though the mouse cursor would be somewhere else on the screen. In some cases, tooltips would also only work the second time the mouse cursor went over the element with a tooltip. These problems have both been solved. Universal provides the useFormFieldBackgroundColor config.json option to switch off the filled background style in form fields. Since Universal 2024.2.11.0, this setting was being ignored by several form fields, resulting in them wrongly having a background color. This is now fixed.The 2024.2.13.1 release is now available for download in TCP.

August 12, 2024:Full release 2024.2.13Hello everyone,In this release, we added support for keyboard shortcuts regarding import/export, updated the tab navigation within the grid in edit-mode, and changed how we manage users leaving an editable subject with unsaved changes. We have also addressed several issues and tasks.Universal versions between 2024.2.11 and 2024.2.12.1 have performance stability issues when working with multiple open documents and details. We strongly advise upgrading to this version as it includes a fix for the beforementioned performance stability issue and solves a significant amount of issues in general.DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI.Universal GUI version 2024.2.13For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.2.13 hereContentsDemo Universal GUI version 2024.2.13 New and changed Keyboard shortcuts for import and export Grid tab navigation in grid using modern key binding Confirmation dialog for leaving an editable subject Fixes and tasks What we will be working on next sprint Questions or suggestions?New and changedKeyboard shortcuts for import and exportnewWe have added support for keyboard shortcuts when importing or exporting data:Import: Ctrl + Shift + I Export: Ctrl + Shift + EGrid tab navigation in grid using modern key bindingchangeWe have updated the tab navigation within the grid in edit-mode. The keyboard navigation is as follows:Classic key bindings: Tab navigates through all fields, Enter navigates through editable fields only. Modern key bindings: Tab navigates through editable fields only, Enter is not used in this key binding.Confirmation dialog for leaving an editable subjectchangeThe Universal GUI previously only blocked a user from leaving an editable subject with unsaved changes. Now, we have added a confirmation dialog. It gives a user the option to either continue closing (losing the open changes) or to go back to the changes.Fixes and tasksFixes for issues on startup:We have fixed an issue where the Universal GUI would not load after logging in, if the active menu was not set or not available due to rights. This has been solved. Now, an alternative menu is selected or a message is displayed to the user. Logging into the same model on different versions of Universal previously caused an infinite loader, especially when downgrading from a newer to an older version. Now, you will be automatically logged out and an error message will be displayed. We resolved an issue where deep links sometimes failed to work correctly for non-cached applications, especially after you cleared the cache. This could mean that you would not end up at the intended part of the application or that the correct filters were not applied.Fixes for filtering: Some time ago, while implementing group header filtering for lookup-type columns, we decided to hide process flow filters in filter forms due to technical reasons. However, you informed us that you wanted to see the filtered values again so users would know they exist. We have now restored this functionality. Filtered values are again shown in filter forms, and the filter indicator is displayed in the grid column headers. In some cases, it may still not show up: When the filtered value does not exist in the dataset. When the filter key has multiple representations and multiple are available to the user for filtering, such as an item per selected language. When using the filter in grids to modify an existing filter with the 'In' or 'Not in' operator, you might not have been able to select any values. This has now been fixed. A few releases ago, we introduced column filtering from grid headers. In the case of a lookup without a display column, the list with items to filter on was not filled successfully. Now, the list is filled with all available items in the subject's data set. Fixes for lookups:When you add a row in a lookup pop-up, you would get an erroneous error message "No context or record", despite the row being successfully saved. We fixed this, as this was misleading and gave the impression of an error where there was none. When adding a new row and opening a lookup pop-up on that row, any linked details in the lookup pop-up would not be loaded. This has been resolved. When editing a lookup with two options having the same translation, the options would be further duplicated under some circumstances. This has been fixed.Fixes in form, grid and cardlist:In a default editable grid, checkboxes were still editable even when updating the row was disabled by the application logic. The value was not saved, but the user interface made it look like it was. This issue has been improved. Now, on the active row, the checkbox is disabled. For inactive rows, the user is still allowed to select it. After the row is activated, the value is corrected when needed. The reason for this solution is to maintain high performance in case the checkboxes on other rows are not cleared. If you get a validation error in a detail screen, such as one caused by an empty mandatory field, a snackbar message showing this error would appear on each refresh. This would only occur if both auto-save and auto-refresh are enabled on the main subject. We solved this by pausing the refresh on the main subject whenever there are unsaved changes in any of its details at any level. Refreshing resumes once there are no longer unsaved changes. We resolved a situation where the Universal GUI could enter an infinite loop. This could occur if Indicium returned a 422 error on an auto-save for reasons unrelated to mandatory fields, or if it involved a mandatory hidden field. We fixed an issue where changing a checkbox value in a card list would not be applied, even after refreshing the subject. The value is now updated automatically. If you encounter a validation error while editing in a form, the application logic values from the server would not be applied until you resolved the error. In certain cases, new values from the server may help to resolve such a validation error. For example, when the logic fills an empty mandatory field for an address after you provide the postal code and house number. Now, we apply the new values again, so you cannot get stuck on saving/executing the changes. This not only applies to regular forms but also to task forms. When consecutively switching rows in a default editable grid, either by clicking or using the up/down arrow keys, the grid would occasionally exit the edit mode. This has been resolved. After changing a value in a lookup-type column of a default editable grid and leaving the row to save it, the previous value would flash briefly. Now, the newly selected value is shown consistently. Values coming from the default procedure would not be processed when modifying a date field. Furthermore, when navigating through a default editable grid without making changes, rows would erroneously be saved if a date field was focused. Both these issues have been fixed.Fixes for charts:When you selected the chart type Funnel, the chart type would not change. This has been fixed. When you configured 2d bar (stacked) as chart type in the Software Factory, a value would not be displayed for Chart type in the popup Chart settings. Furthermore, when trying to save the values as configured in the popup Chart Settings in this situation, the Universal GUI would crash. Both these issues has been resolved.Other fixes:When a task is set up with a default procedure, a parameter may be filled with an invalid value. If this is handled by sending a message using tsf_send_message with the abort parameter set to 1, the old value of the task parameter would not be restored. This has now been fixed. When clicking a detail tile, the process action Zoom detail did not work as a process flow starting point. It does now. When you selected the chart type Funnel, the chart type would not change. This has been fixed. Actions on a scheduler may have triggered unexpected error messages when the scheduler was bound to a subject variant (SF concept). This occurred due to differences in the available columns between the original subject and the variant. This has now been fixed. When "2d bar (stacked)" was configured as chart type in the Software Factory, Universal would not display a value for "Chart type" in the "Chart settings" popup. Furthermore, when trying to save the Chart Settings popup in this situation, Universal would crash. Both these issues has been resolved. Executing a task by using the Tab key in a barcode field that is the last visible task parameter did not work anymore. Furthermore, when you configured in the Software Factory to disable layouts for the task, the same functionality would sometimes not work. Both of these issues have been resolved. What we will be working on next sprintThe next sprint we will be working on:Grid default edit-mode improvements Universal performance improvements High priority ticketsQuestions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

This is an additional release for the Universal GUI version 2024.2.12. This release contains three fixes:A report now uses the configured "Report action" to determine the way the report is served to the user. With this fix, previewing a report works again, instead of the report always being downloaded. Note: when Indicium and Universal are on different domains, this fix doesn't work, due to browser strictness. We make a distinction between report action “PDF” and “Print preview”. Before, both options would result in a preview. Now the "PDF” option will result in a download. The latest Indicium release, 2024.2.12.2, is required in order for these fixes to work. Actions on a scheduler may have triggered unexpected error messages when the scheduler was bound to a subject variant. This occurred due to differences in the available columns between the original subject and the variant. This has now been fixed.The 2024.2.12.3 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2024.2.12.We have fixed Universal becoming slower when the user has multiple open documents.The more open documents and visited detail tabs, the more this performance issue was noticeable. This fix ensures working within an open document is faster and performance is consistent, but switching between open documents and detail tabs can take a bit more time.Universal versions 2024.2.11 and 2024.2.12 were impacted.We will be working on a best of both worlds implementation in the near future. The 2024.2.12.2 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2024.2.12. It contains change for detail subjects:We fixed an issue where detail subjects kept “loading” after selecting another parent record. We optimized performance by preventing inactive detail subjects from reloading data after selecting another parent record.The 2024.2.12.1 release is now available for download in TCP. 

July 8, 2024:Full release 2024.2.12 Hello everyone,In this release, we have improved the way cell data is copied from the grid, optimized performance in edit mode, and added support for report parameter properties action and Export path. We have also solved some minor issues and tasks. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.2.12For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.2.12 here ContentsDemo Universal GUI version 2024.2.12 Contents New and changed Improved the way cell data is copied from the grid Improved performance in edit mode Support for report parameter properties action and Export path Warning about HTTP Opt-out of Sentry crash reporting Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedImproved the way cell data is copied from the gridchangeIt was already possible to copy data from the grid to the clipboard by selecting the cell and using Ctrl + C. This feature has been improved in this release.Previously, when a user copied a cell from a grid with Ctrl + C, the inner grid data for the current row was copied instead of the displayed data, which in some cases can be different.Now, when a cell is copied with Ctrl + C, the data that will be copied is the displayed data. There are some exceptions, though. Some controls format the value before copying:Color: copies the color value without image. Checkbox: if selected, true will be copied; if cleared, then false will be copied; if indeterminate, then a blank space will be copied. Progress bar (read only): copies the percentage displayed within the progress bar.Some controls copy a blank space to the clipboard:File link File upload HTML HTML card Image combo Image link Image upload SignatureAll the other supported control types will be copied exactly as they are presented to the user in the grid.Whether users are allowed to copy data in a subject to the clipboard is determined by the Software Factory setting Copy to clipboard (menu User interface > Subjects > tab Columns). Improved performance in edit modechangeWe have improved the performance of the Universal GUI in default edit mode by reducing the number of requests made when entering edit mode and after changing a value.We will continue to optimize performance in future releases. Support for report parameter properties action and Export pathnewFor a report parameter with the property action, the Universal GUI now creates a dropdown editor that displays the available options. Users can choose the download type for the report from this dropdown: Excel, image, Word, HTML, etc. The default is a preview in PDF format.In addition to the action property, we have also added the Export path property. You can use this property to influence the name of the downloaded report file.You can set these properties in the Software Factory in the menu Processes > Reports > tab Report parameters. Warning about HTTPnewFor security and performance reasons, it is recommended to run the Universal GUI on HTTPS. Now, when running on HTTP, a warning message is shown to the user. Opt-out of Sentry crash reportingnewIt is now possible to opt-out of Sentry crash reporting by adding this to config.json:"disableErrorReporting": trueYou can use this, for example, for a web server without a connection to the outside world because of security reasons. We advise you to keep the Sentry crash reporting activated because its information helps us solve crashes. Minor fixes and tasksFixes for layout and styling:For subjects with auto-save enabled, if a user updated a record and then navigated to their profile menu and selected User preferences, a pop-up with untranslated warning messages was displayed. This has been fixed. Very rarely, the CRUD buttons would not show up on screen type breakpoints. This has been fixed.Fixes for issues on startup:Users would sometimes get the following snack bar error when starting the Universal GUI: "Request error: The object was not found. You may have insufficient rights or the object no longer exists." After this error, start objects would not be opened. This has been fixed.Fixes for slow connections:On a slow connection, if users clicked too fast for the network to process the requests, they were sometimes confronted with "Objects could not be found" errors. These errors looked bad to users but could be ignored most of the time. Now, the user no longer gets this message. You can still see the 404 status of the corresponding network request in your browser's DevTools.Fixes in form and grid:Drag-drop tasks would not work if used in tables without variants. This has been fixed now. Previously, if you tried to select multiple records at one time using the Shift key, it would not work as expected if this was the first action taken in the grid component. This has now been fixed. A read-only column was editable in the grid though it was set to read-only in the model. This has been fixed. This could happen for regular columns where the Type was set to Read-only for component types: - Any editor in the grid - Lookup editors in the form where the Select button in the pop-up was not disabled. The lookup editor can contain a past value that is no longer available in the dropdown. Previously, when a user started editing, the field became empty. This was not correct. The field should show the value until something else is selected. This has been fixed. Every time a row in an editable grid was switched, the data in the lookup columns would be reloaded, causing it to disappear and reappear. This has been fixed. Data in lookup columns are no longer reloaded if there are no changes.What we will be working on next sprintThe next sprint we will be working on:Grid default edit-mode improvements High priority ticketsQuestions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  

Now that customer success is the focus of the Universal GUI, we can prioritize User Experience too.This blog is the first step, introducing quick win UI Styling updates that require no Model changes or changes in User Experience. Later, we'll introduce and discuss Data Density improvements and more comprehensive UX & Universal Theme implementations.In the past years a lot of features have been added to the Universal GUI, but in the meantime the visual side of this interface hasn’t changed a lot. Comparing our Universal GUI to other enterprise applications, we do notice that our interface lacks a little conviction. We want to improve on this together with you, to ensure that our ideas support you and your users. So please, join in the conversation and let us know what you think.We took the Insights application as a benchmark.The Projects screen in the current Universal GUIThere is a lot going on in this screen, which means our users have a lot of elements to visually look through.We think we can do better.Based on the Material UI components and the 10 Usability Heuristics we altered the UI styling, bringing us to the following design:Styling update of the Universal GUIThis is the same Projects screen in the Insights application, with only visual alterations. Let us take you through it, so you know what is going on.Styling update with subject indicators Menu Currently, the background color in the menu has the same color as the general background of the rest of the application, which can distract the user in their navigation through an application.Menu designWe want to introduce the primary color as background of the menu.This provides a better visual hierarchy and helps the user focus on the data. With this change, we also introduce a lot more color in the application.We also want to change the alignment of the Open Documents (aligned with the submenu items) and the badges in the menu (make them stick to the right). Prefilter buttonsThe current setup of the Prefilter buttons is based on an icon, with a primary-colored underline when the prefilter is active.Prefilter buttons with solid background Like you, we think this can improved by making the Prefilter button a more distinctive button, by introducing a solid background in a round shape.When the prefilter is active, the background could get the primary color or secondary color. Which do you prefer, the primary or the secondary color for active prefilter?  CRUD and Task/Report buttons Like with the prefilters, we introduce a solid background for the CRUD and Task/Report buttons.By making these button backgrounds square, they are better distinguishable against the round prefilter buttons.Default CRUD and Task/Report button styling Also, we would like to know what your stance is on introducing the primary/secondary color to the Task buttons to make it a clear Call To Action button.Concept of button with color What do you think of introducing the primary or secondary color to the CRUD and Task/Report buttons? Conditional layoutThe current setup of the Conditional layout colors the entire cell. We want to improve on this visual cue, highlighting the text only.Conditional layout around text With text fields and an icon, we could encapsulate the icon with the text highlight:Icon in Conditional Layout highlight Or we could give the icon the conditional layout color (if it’s an SVG icon of course) and place it outside the text highlight.Icon in Conditional Layout color Which one do you prefer?  Lookup controlEspecially in read-only Grids, the lookup control needs a little love.To make the Universal GUI more consistent with other controls like the email, map, URL or phone number control, we want to change the current lookup control into a hyperlink. This way we follow behavior the users expect from other platforms.Evergreen, Kim Wilde, Country building and Budget office are the Lookups in this image. In this idea, the underline in the grid is only shown on active row/hover, to prevent a grid full of underlined data. Column headersVertical space is a great challenge in the Universal GUI.The grid headers now demand a lot of vertical room compared to the rows, and the styling of the header text make them fall into the background.In this design, we want to introduce a lower header bar and a bold font style. Subtle vertical dividers between the columns in the header and the active row are also added to emphasize column width.Column headers design What do you think of this Column headers design? Form fields – Outlined styleOne of the major elements in this design is changing the Filled style to the Outlined style form fields.We think the Outlined style holds a lot of answers for data density, control alignment, conditional formatting, visual hierarchy, focus indication, etcetera.To give you an impression, we put the current Filled style next to an Outline style setup. The field content and setup are the same.On the left the current Filled Form Field styling, on the right the Outlined Form Field style Because this will be a major change, this is not exactly a ‘quick win’. We want to get rid of the Form field background color setting and implement this idea. This also means that forms in non-edit mode have no background nor outline.Forms in non-edit mode without background color What do you think of the Outlined Style for Form fields replacement? Active row colorUniversal uses grayscales to draw the attention of the user, we think that color is a better guidance and looks nicer.While using a hint of the primary color (a pass through of 12% to be precise), the active row would stick out a lot more.Active row indication in Primary colorWhat do you think of coloring the active row? ConclusionAs stated in the intro, these Design changes are predominantly focused on visual changes. They will have an impact on how the Universal GUI looks and feels, but not on its behavior.To react to the designs, use the number of the subject and place your comment next to it, so we know which subject you are referring to.We look forward to your opinions!  

This is an additional release for the Universal GUI version 2024.2.11. It contains one change:In specific and rare circumstances a default editable grid caused a crash when opening a detail tab. This has been resolved.The 2024.2.11.2 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2024.2.11. It contains one change:The theme background was not displayed. This has been resolved.The 2024.2.11.1 release is now available for download in TCP.

June 10, 2024:Full release 2024.2.11We solved two issues that had been introduced in the 2024.2.11 release candidate: The pop-up of a marker in the Maps screen component would not show up properly, especially after switching documents. This has been fixed.  An issue could occur in some specific scenarios, such as applying sorting in a grid within a document but also in some other scenarios. After closing the document, the application would stop working, and the user would be presented with a crash report submission form. This has been fixed. Now, the user can continue using the application normally after closing the document. Hello everyone,In this release, we added the ability to start a process flow from within a custom component. We also made some performance improvements, added general keyboard shortcuts for pop-ups and a confirmation when closing a lookup or pop-up. Lastly, we solved some issues. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to familiarize yourself with the GUI. Universal GUI version 2024.2.11For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.2.11 here ContentsDemo Universal GUI version 2024.2.11 (release candidate) Contents New and changed Start process flow from within a custom component Performance improvements General keyboard shortcuts for pop-ups Confirmation when closing a lookup or pop-up Minor fixes and tasks What we will be working on next release Questions or suggestions? New and changedStart process flow from within a custom componentnewYou can now start a process flow from within a custom component by sending an instruction to the Universal GUI. For example:window.parent.postMessage({ type: 'startProcessFlow', processFlowId: 'refresh_document_detail_from_component', dataParams: {}}, '*');The process flow needs to be a deeplink process flow. See Deep linking in a process flow. The Universal GUI allows origins from the same master domain, for example, *.thinkwise.app.WarningIf you introduce custom screens or custom components into your application, you will also introduce a piece of traditional programming. If you are making changes to your model, the Software Factory will not alert you about the use of process flows and their parameters in your custom components. It is your responsibility to put a change process in place for this. For more information, see Custom screens. Performance improvementschangeWe have upgraded our general component library, which has resulted in performance improvements.Actions that triggered multiple re-draws of the interface now update the interface once. We also expect an improved grid edit-mode experience, although we have planned more improvements in this area in the upcoming sprints.Also, switching between documents and tabs looks much calmer now. Forms position their editors directly in the right place now. The same goes for (detail) tiles. General keyboard shortcuts for pop-upsnewYou can now use the following keyboard shortcuts when interacting with a pop-up:Esc - Cancel Ctrl + Enter - Confirm Confirmation when closing a lookup or pop-upnewPreviously, when users edited a record and clicked on one of the buttons, the lookup or pop-up would close without any confirmation. This could result in them losing their changes. Now, when users edit a record and try to close it, they are asked if they want to discard their changes or return and finish editing. Minor fixes and tasksIf the page size was set to -1, paging would incorrectly be presented by the Universal GUI. This has been fixed. If the checkbox Allow sort was cleared, users were unable to manually change the column width in the grid. This has been fixed. A lookup editor in an editable form or as a task parameter was emptied when the value was entered before the dropdown list options were loaded and the control was left. For example, when copy-pasting or barcode scanning. Now, the value remains and is matched once the dropdown list options are received. We have fixed an issue in the form where any field with Field number of positions further = 0 would disappear if placed directly after a file upload field. The Max no. of records indicator was not translated. Now, the indicator will display "There are more records than can be displayed". An issue could occur in the card list when the page size and the maximum number of rows were set to zero or a negative number. This has been fixed. With these values, there will be only one page with all the records.Fixes for process flows:A process flow that starts with activating a detail tab would sometimes start multiple times. This has been fixed. When a task had Await result set to No and a process flow would use this task as Start table task, the process flow would not continue after executing the task. This has been fixed.Fixes for slower connections: Sometimes, especially on slower connections, quickly changing the active row would cause the detail tab to break and no longer show data unless manually refreshed. This has been fixed. On a slower connection, the data on a detail grid could be out of sync when switching between multiple records. This has been fixed. On a slower connection, detail tab data could be out of sync after switching to the parent record and back. This can be fixed by adding the following option to config.json: "disableTabPageCaching": true, Only use this option when you experience the mentioned issue since it lowers performance.  What we will be working on next releaseThe next release will be about:Solving issues - For the status of your own issues, please refer to TCP. Improved default edit mode - Closing a document will allow the user to cancel their current changes and errors. Performance improvements. Set filter from process flow - The filter form in a process flow was no longer displayed as a user filter. We will address this issue. HTTPS Security warning - When the Universal GUI is started over plain HTTP, it will give a warning that the connection is not secure. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!   

May 21, 2024:Release 2024.2.10 This release is the same as 2024.1.14.0May 13, 2024:Full release 2024.1.14.0 We have solved the following known issues in the release candidate: The image combo would erroneously show text in the grid when no image was available. The grid had empty space at the bottom. The chart would not respond to size changes. Fixed: When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours.  Hello everyone,In this sprint, we have added the possibility to resize the width of the vertical tab panel, new keyboard shortcuts, the ability to display domain element translations as values in the pivot grid, and more. Continue reading to see what else is new and what we have fixed in this release. DemoAs always, we have made a demo for you: try it here . Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI  user interface guide to get familiar with the GUI. Universal GUI version 2024.2.10For more information about setting up the Universal GUI, see the Universal GUI setup  guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.2.10 here  ContentsDemo Universal GUI version 2024.2.10 New and changed Resize vertical tab panel Added "Max no of records" indicator, page size, and pagination Drag and drop in the sort pop-up Shortcut support in filter pop-up Navigate with "Enter" in Filter form component 'Remember me' on login page renamed to 'Stay signed in' F5 / ALT+F5 shortcut keys to refresh data Pivot grid supports displaying domain elements Export wizard - visible columns Added element name to tooltip Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedResize vertical tab panelnewUsers can now resize the width of the vertical tab panel by dragging its edge sideways. This makes it possible to view detail tabs with longer names. The width of the vertical tab panel is remembered between sessions. Added "Max no of records" indicator, page size, and paginationnewWhen the setting Max no of records is specified on the subject, and more records than the maximum are available, an indicator is displayed to let the user know there are more records. Also displayed are the number of records per page and the pagination.If no Max no of records is specified, the indicator will not be shown, but the page size and pagination details will still be available. Drag and drop in the sort pop-upnewThe user can now drag and drop an item from the left to the right and vice versa in the sort pop-up. In addition, the user can use drag and drop to rearrange the position of items within the list on the right.Drag and drop in the sort pop-up Shortcut support in filter pop-upnewWe have added support for keyboard shortcuts in the filter pop-up. Users can use Enter or Tab to navigate to the Operator or Value fields.If the extended property Keybindings=classic is enabled for the application (classic mode), you can use Enter for navigation. If the extended property Keybindings=classic is disabled for the application (modern mode), you can use Tab for navigation.In addition, for both keybinding modes, we have changed the initial focus to the first Value field.Filter pop-up with keyboard shortcuts Navigate with "Enter" in Filter form componentnewIf you use the classic keybinding in the Filter form component, Enter now moves to the next filter form field. 'Remember me' on login page renamed to 'Stay signed in'change'Remember me' on the login page has been renamed to 'Stay signed in' to prevent any confusion about this functionality. This functionality is for preventing the user from being logged out, not for remembering login details. F5 / ALT+F5 shortcut keys to refresh datachangeInstead of loading the entire web application, users can now refresh the data in the current view by pressing the F5 or Alt+ F5 keys.If the extended property 'Keybindings’ is set to 'classic’, the refresh shortcut key is F5. If the extended property 'Keybindings’ is set to 'modern’ or not set at all, the refresh shortcut key is Alt+F5.This change means that the F5 / Alt+ F5 keys now have the same behavior as clicking Refresh   in the action bar. Pivot grid supports displaying domain elementschangeThe pivot grid can now display domain element translations as values. If no domain element is defined for a value, the original value is displayed. Export wizard - visible columnschangeThe export wizard showed subject columns that were marked as hidden on the subject or its variant in the Software Factory. These are now hidden from the wizard, except for the primary key columns. This is because the primary key columns are needed to re-import the modified Excel sheet later. Added element name to tooltipchangeWe have added element names to the tooltips of tasks, reports, buttons, and tiles. If you hover your cursor over, for example, a task, the tooltip shows the task name, its shortcut, and its information text. The tooltip shows the task name, shortcut, and information text Minor fixes and tasksIn some cases, hovering over a screen with a chart could cause errors. These errors were ignored, but could be seen in the browser development tools. They no longer occur. Fields on the same line would always equal 100% even when the field width would indicate otherwise. We removed this limitation, allowing fields on the same line to exceed 100% of the available width. This allows the Universal GUI to better scale sets of fields. You can set the Field width in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > group Form. When using a Filter form on a screen that did not allow searching, the Filter form would not show up at all. This has been fixed. A bad request error was displayed when pagination was combined with the maximum number of records and the active record would fall outside of the maximum number of records. This has been fixed. The user is now asked whether they want to open the active record on a separate screen.  Click "Show" to open the row on a separate screen Previously, you could not save your report with a custom name. Now, you can give your report a custom name by including a report parameter with Property set to Export path (menu Processes > Reports > tab Report parameters > group Model settings). When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Fixes for grid and form:A combo box with the bit datatype would not display the expected values in both the grid and form. This issue has been resolved, so now domain elements can be used in place of Boolean values. In a read-only grid, the summary row would be cut off if the row height was set too low. Now, it will always have a minimum height of 44, and appear correctly regardless of the row height. When a hidden column was used in the grouping of a grid, its values were visible to the user. Now, the hidden column is still used, but no longer visible. In some cases within the Formlist screen component, the fields would be slightly misaligned if an auto-complete combo control was present. This has been fixed. Navigating over editable datetime controls using the Tab or Enter keys without changing its value caused the field to PATCH its value and the record to get marked as changed. This is now prevented. Navigating over datetime controls in the editable grid by arrow keys without making changes caused the field to PATCH and the record to save. This was especially undesirable on mandatory fields since it made the previous record red because it could not be saved. This is now prevented. If you typed a dot as the first character in a numeric field, then a dot again to reach the decimals, and then added some numbers, only the first number entered was displayed as a decimal. After typing the first decimal, the cursor would jump to the beginning of the field and add the next numbers at the front. This would turn 0.1200 into 2.1000, for example. This has been fixed. When navigating through records in the editable grid using ↑ or ↓, the value of the previous record that was just changed was not always processed correctly, especially on date/time type columns. This has been fixed. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours. What we will be working on next sprint The next sprint we will be working on:Performance improvements (including grid default edit mode performance) Support report generation action dropdown Breadcrumb update on detail subject navigation More shortcut support Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!    

May 13, 2024:Full release 2024.1.14.0 We have solved the following known issues in the release candidate: The image combo would erroneously show text in the grid when no image was available. The grid had empty space at the bottom. The chart would not respond to size changes. Fixed: When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours.  Hello everyone,In this sprint, we have added the possibility to resize the width of the vertical tab panel, new keyboard shortcuts, the ability to display domain element translations as values in the pivot grid, and more. Continue reading to see what else is new and what we have fixed in this release. DemoAs always, we have made a demo for you: try it here . Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI  user interface guide to get familiar with the GUI. Universal GUI version 2024.1.14For more information about setting up the Universal GUI, see the Universal GUI setup  guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.1.14 here  ContentsDemo Universal GUI version 2024.1.14 New and changed Resize vertical tab panel Added "Max no of records" indicator, page size, and pagination Drag and drop in the sort pop-up Shortcut support in filter pop-up Navigate with "Enter" in Filter form component 'Remember me' on login page renamed to 'Stay signed in' F5 / ALT+F5 shortcut keys to refresh data Pivot grid supports displaying domain elements Export wizard - visible columns Added element name to tooltip Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedResize vertical tab panelnewUsers can now resize the width of the vertical tab panel by dragging its edge sideways. This makes it possible to view detail tabs with longer names. The width of the vertical tab panel is remembered between sessions. Added "Max no of records" indicator, page size, and paginationnewWhen the setting Max no of records is specified on the subject, and more records than the maximum are available, an indicator is displayed to let the user know there are more records. Also displayed are the number of records per page and the pagination.If no Max no of records is specified, the indicator will not be shown, but the page size and pagination details will still be available. Drag and drop in the sort pop-upnewThe user can now drag and drop an item from the left to the right and vice versa in the sort pop-up. In addition, the user can use drag and drop to rearrange the position of items within the list on the right.Drag and drop in the sort pop-up Shortcut support in filter pop-upnewWe have added support for keyboard shortcuts in the filter pop-up. Users can use Enter or Tab to navigate to the Operator or Value fields.If the extended property Keybindings=classic is enabled for the application (classic mode), you can use Enter for navigation. If the extended property Keybindings=classic is disabled for the application (modern mode), you can use Tab for navigation.In addition, for both keybinding modes, we have changed the initial focus to the first Value field.Filter pop-up with keyboard shortcuts Navigate with "Enter" in Filter form componentnewIf you use the classic keybinding in the Filter form component, Enter now moves to the next filter form field. 'Remember me' on login page renamed to 'Stay signed in'change'Remember me' on the login page has been renamed to 'Stay signed in' to prevent any confusion about this functionality. This functionality is for preventing the user from being logged out, not for remembering login details. F5 / ALT+F5 shortcut keys to refresh datachangeInstead of loading the entire web application, users can now refresh the data in the current view by pressing the F5 or Alt+ F5 keys.If the extended property 'Keybindings’ is set to 'classic’, the refresh shortcut key is F5. If the extended property 'Keybindings’ is set to 'modern’ or not set at all, the refresh shortcut key is Alt+F5.This change means that the F5 / Alt+ F5 keys now have the same behavior as clicking Refresh   in the action bar. Pivot grid supports displaying domain elementschangeThe pivot grid can now display domain element translations as values. If no domain element is defined for a value, the original value is displayed. Export wizard - visible columnschangeThe export wizard showed subject columns that were marked as hidden on the subject or its variant in the Software Factory. These are now hidden from the wizard, except for the primary key columns. This is because the primary key columns are needed to re-import the modified Excel sheet later. Added element name to tooltipchangeWe have added element names to the tooltips of tasks, reports, buttons, and tiles. If you hover your cursor over, for example, a task, the tooltip shows the task name, its shortcut, and its information text. The tooltip shows the task name, shortcut, and information text Minor fixes and tasksIn some cases, hovering over a screen with a chart could cause errors. These errors were ignored, but could be seen in the browser development tools. They no longer occur. Fields on the same line would always equal 100% even when the field width would indicate otherwise. We removed this limitation, allowing fields on the same line to exceed 100% of the available width. This allows the Universal GUI to better scale sets of fields. You can set the Field width in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > group Form. When using a Filter form on a screen that did not allow searching, the Filter form would not show up at all. This has been fixed. A bad request error was displayed when pagination was combined with the maximum number of records and the active record would fall outside of the maximum number of records. This has been fixed. The user is now asked whether they want to open the active record on a separate screen.  Click "Show" to open the row on a separate screen Previously, you could not save your report with a custom name. Now, you can give your report a custom name by including a report parameter with Property set to Export path (menu Processes > Reports > tab Report parameters > group Model settings). When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Fixes for grid and form:A combo box with the bit datatype would not display the expected values in both the grid and form. This issue has been resolved, so now domain elements can be used in place of Boolean values. In a read-only grid, the summary row would be cut off if the row height was set too low. Now, it will always have a minimum height of 44, and appear correctly regardless of the row height. When a hidden column was used in the grouping of a grid, its values were visible to the user. Now, the hidden column is still used, but no longer visible. In some cases within the Formlist screen component, the fields would be slightly misaligned if an auto-complete combo control was present. This has been fixed. Navigating over editable datetime controls using the Tab or Enter keys without changing its value caused the field to PATCH its value and the record to get marked as changed. This is now prevented. Navigating over datetime controls in the editable grid by arrow keys without making changes caused the field to PATCH and the record to save. This was especially undesirable on mandatory fields since it made the previous record red because it could not be saved. This is now prevented. If you typed a dot as the first character in a numeric field, then a dot again to reach the decimals, and then added some numbers, only the first number entered was displayed as a decimal. After typing the first decimal, the cursor would jump to the beginning of the field and add the next numbers at the front. This would turn 0.1200 into 2.1000, for example. This has been fixed. When navigating through records in the editable grid using ↑ or ↓, the value of the previous record that was just changed was not always processed correctly, especially on date/time type columns. This has been fixed. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours. What we will be working on next sprint The next sprint we will be working on:Performance improvements (including grid default edit mode performance) Support report generation action dropdown Breadcrumb update on detail subject navigation More shortcut support Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

April 15, 2024:Full release 2024.1.13 Fixed: Pressing Alt + Enter when using the `classic` key binding in a multiline control, would not insert the enter at the caret position, it was always added at the end. This has been fixed. While using 'classic' key bindings, there was an issue navigating through grid records in a default editable grid. When the arrow keys were used to leave a record, the changed value wasn't always saved. This has been fixed. A bad request error occurred in both key binding modes when leaving an empty text field using arrow key navigation in the default editable grid. This has been fixed. We fixed a bug in the release candidate where some bars (like tasks, reports, prefilters, cube views, search) were erroneously removed from the screen. We fixed an issue in the release candidate where the cube view bar buttons sometimes were too big when the bar was placed vertically.  Hello everyone,In this sprint, we added support for user-defined prefilters, improved the screen component bars, and more. Read on for the full list of changes. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.1.13For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2023.1.13 here New and changedUser preference - User-defined prefiltersNewUsers can now save their custom filters as a prefilter with the new Save as new prefilter button that is available at the bottom of the filter dialog. When saving a filter as a prefilter, they must provide a unique name.After saving, the prefilter is automatically updated and becomes available in the toolbar for the specific subject. In the overflow menu, with the option Own prefilters, users can add, delete or edit their own prefilters. Edited prefilters can be saved as a new prefilter with a different name.For IAM administrators, the user-defined prefilters are located in the menu Authorization > Users > tab User preferences > vertical tab Prefilters. These options are only available for the Thinkwise Platform version 2024.1 and up.Save as prefilter User preference - Remember prefilter statusnewThe Universal GUI can now remember and apply a user's preferred state for a prefilter (activated or de-activated). A prerequisite for this feature is that in the Intelligent Application Manager, the setting Prefilter status is enabled in the Advanced menu > Master data > UP availability.For example, if a user deactivates a prefilter that was initially activated, and returns to that screen, the prefilter will automatically be deactivated by default. Enhanced filter from grid column headersnewWe have further enhanced the column header filter functionality in the grid, specifically for lookup-type columns. Users can now select multiple lookup values in the pull-down filter on a grid column header. This update is designed to make data filtering more intuitive and efficient for users.The column header filter in a grid now includes the following features:More comprehensive filtering options: when you open the column header filter on a lookup column, a pull-down appears with a list of options. It takes into account all relevant subject filters, except the one on the column you are currently filtering. This means you have access to all relevant options within your current context. Checkbox selection: each option in the list is preceded by a checkbox. Select the checkboxes for the items you want to include in your filter. Limit on filtering options: to ensure optimal performance and usability, the list of options is limited to 25 items. If the list exceeds this limit, a search/suggestion field is shown to find and select specific options in the extensive list. To customize the limit, use the extended property called LookupGridHeaderFilterOptionsLimit. When you re-open the filter pull-down, any active filters are checked, making it easy to see your current filter settings. IN operator filter functionality: the selected options are added to the IN filter. This gives you more control over your data and makes it easier to customize your view. Dropdowns in the filter pop-up from the toolbar allow multi-item selection and the IN operator, to present the filter at both ends.Checkbox selection in a column headerA search field when the number of items exceeds the limit Screen component bar improvementsnewWe have made the following changes to improve the screen component bars:We have added support for the following screen components: Search Cube view bar Prefilter bar Report bar You can now position screen component bars vertically. This includes the Task bar and Action bar screen components. To include a bar into the action bar, you can add the AlwaysMergeToActionBar screen component property to any bar. It will stay in place in the Windows GUI. Screen component bars now listen to their alignment/dock properties. Task tiles are now removed if no tasks have been defined. Show grand total of a rownewIn the Software Factory, the cube view setting Show row grand total adds a row containing the rows' summed values to the pivot. You can configure this row to appear at the top or the bottom of the pivot.You can define the settings for the grand total of a row in the menu User interface > Subjects > tab Components > tab Cube > tab Cube views > tab Form:Show row grand total - Select to add a row containing the summed-up values of the rows Total position - Select the position of the row: Far: the row will be shown at the bottom of the pivot. This is the default behavior. Near: the row will be shown at the top of the pivot. The row grand total, set to position "Far" Change pivot settingsnewUsers can now change the pivot settings. When a pivot is available, users can open the Pivot settings pop-up from the overflow menu. Here, they can enable totals for rows or columns. They can also choose where to display the grand total. Cube view sortingnewUsers can now set the sorting of the dimensions through the overflow menu of the cube view: Sort. The dimensions can be sorted Ascending or Descending on their own display value or on a value present in the cube view. Mass update on lookupsnewIn release 2024.1.12, we introduced a feature allowing users to update multiple records simultaneously through the Mass update functionality. It had a known limitation: it did not allow updating lookups. Mass update now supports updating lookup fields. Conditional layout for progress bars the same in grids and formschangeThe form progress bar was displayed according to the conditional layout settings. Still, the grid progress bars displayed the default style with the conditional layout behind it on the grid cell. Now, the grid and form progress bars look the same. A progress bar in the cardlist component now also displays conditional layouts.All three (form, grid, and cardlist) now apply the text color setting to the percentage. Make sure that there is enough contrast with the background color(s).Progress bars now have a uniform look Search bar translationchangeIf you are using the Software Factory version 2024.1 or older, and upgrade to version 2024.1.13 of the Universal GUI, you will see Filter instead of Search in the search bar. If you do not want this, you can change the translation. In the menu User interface > Translation, filter for the Translation object combined_filter and change its translation.As of Software Factory version 2024.2, the translation will be Search again by default.The translation object 'combined_filter' Minor fixes and tasks Fixes for HTML fields:We have fixed the following security advisory: https://github.com/advisories/GHSA-5359-pvf2-pw78. This fixes a security issue in the HTML editor in case the HTML data would have a malicious SVG in an <embed> or <object> tag. Adding an SVG in this way is not possible through the Universal GUI or Windows GUI, so in normal usage, this problem couldn't occur. If an HTML field was able to be filled by a malicious actor, for example, directly through the Indicium API, this vulnerability would become relevant. In that scenario, if a user would go into edit mode on a HTML control, the attacker's JavaScript payload inside the SVG file would be executed. In the worst case, if the SVG file was served from the same origin as Indicium, the attacker would have been able to execute Indicium requests under the victim user's credentials. Links added to HTML fields will now properly open in a new tab. Previously, the HTML control text could overlap with the action button. This has been fixed.Fixes for display and usability:If you do not declare a page size in the Software Factory, the table only displays the first 100 rows. We have added pagination so you can still navigate to the rows after row 100. When opening a lookup popup, the correct page is now activated to show the currently selected record. If you used dark mode and collapsed the sidebar and expanded it again, a brief white flash would show on the right-hand side. This has been fixed. The dropdown scrollbar on mobile devices was only visible when scrolling. It is now always visible. The dropdown is configured to display all items regardless of the dimensions of the device on which it is being viewed. Group headers in a form are now placed lower to show they are connected to their group. Some users experienced continuous resizing of tiles paired with the appearance and disappearance of a scrollbar. This would happen if multiple tiles were stacked vertically, and the list was just long enough to make a scrollbar appear and also narrow enough that any less space would cause the tiles to shrink. In applications with multiple menu options (on the Windows platform), closing a document in the tile menu sometimes automatically selected the next open document. This has been fixed. We fixed a bug in the release candidate where some bars (like tasks, reports, prefilters, cube views, search) were erroneously removed from the screen. After a user saved a cube view, the order of the series or category fields was sometimes not maintained correctly. This has been fixed. We fixed an issue in the release candidate where the cube view bar buttons sometimes were too big when the bar was placed vertically.Fixes for grid and forms:In an auto-editable grid, users should be able to switch records without saving if no changes have been made. However, if they switched records after selecting a date-type cell, the grid would always behave as if changes had been made, even if only the focus had been set. It caused validation errors if the record had unfilled required fields. This has been fixed. Pressing Ctrl + Enter now only saves the record and does not navigate to the next field. After saving a form, the focus always moved to the first field of a form, although it should remain on the last field edited, or in case of an error, on the first field that contained an error. This problem has been fixed. The active record of all parent subjects is refreshed while working in a detail subject. While the lookup data of a grid column was loading, a loading indicator was shown which was not aligned correctly. This has been fixed. Subjects with auto-save enabled would sometimes make multiple requests to Indicium to delete the staged resource. Only one request would succeed, the others would return a 404, which could be observed in browser development tools. This has been fixed. If the parent subject had no record, the Universal GUI used to make detail tabs and detail tiles of unrelated details read-only, so they could not be clicked. This was wrong because unrelated details do not need a parent record and should therefore remain clickable. This has been fixed. Occasionally, when a user pressed Shift to select something in the browser, the grid or tree could enter a state that prevented the selection of rows. This has been fixed. Using the arrow keys to navigate through checkbox cells in a grid would be very inconsistent. This has been fixed. While using "classic" key bindings there was an issue navigating through the grid records in a default editable grid. When a record was left by the arrow-keys the changed value wasn't always saved. This has been fixed. Pressing Alt + Enter when using the “classic” key binding in a multiline would not insert the enter at the caret position. It was always added at the end. This has been fixed. In both key binding modes, a bad_request error occurred when leaving an empty text field using arrow-key navigation in the default-editable grid. This has been fixed. Pressing Alt + Enter when using the `classic` key binding in a multiline control, would not insert the enter at the caret position, it was always added at the end. This has been fixed. While using 'classic' key bindings, there was an issue navigating through grid records in a default editable grid. When the arrow keys were used to leave a record, the changed value wasn't always saved. This has been fixed. A bad request error occurred in both key binding modes when leaving an empty text field using arrow key navigation in the default editable grid. This has been fixed.Fix for reports:Exporting a report to PDF would open the PDF in a new tab in preview mode. Now, the PDF will be downloaded directly, based on the configuration in the Software Factory.Fixes for import:When using the Import wizard, a problem could occur if you went back one screen and then continued with the wizard. If you selected how to import the data, went to the next screen, and then went back to change that selection, your updated selection would not be registered at the Indicium API side. The wizard would appear to have the correct option selected, but the actual import would be performed using your original selection. This has been fixed. We found an issue when importing .csv files in Firefox. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Shortcut support in pop-ups Technical and functional maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

This is an additional release for the Universal GUI version 2024.1.12. It contains one change.Lookup dropdowns were not (always) filtered by the active prefilters of the lookup subject. This caused dropdowns to offer too many items, even the ones the user was not allowed to see. This has been fixed.The 2024.1.12.2 release is now available for download in TCP.We strongly advise updating to this version if your product uses Universal GUI releases 2024.1.12.0 or 2024.1.12.1. 

March 18, 2024Full release 2024.1.12. In the Release Candidate, we added support for user-defined prefilters. However, we had to make the decision to postpone that feature due to unexpected issues. We expect to release it again as part of the next release. Several fixes Hello everyone,In this sprint, we have added a large number of user preference features to the Universal GUI. Users can now, for example, save custom cube views, show or hide columns, and save their custom filters as a prefilter. To improve the migration from the Windows GUI to the Universal GUI, we have added Windows GUI-like navigation options for editable fields in forms and grids. Additionally, we have further enhanced the Formlist component and the pivot grids. For custom CSS, we have added more options.We have also done some minor fixes and tasks. DemoAs always, we have made a demo for you: try it here . Before trying it out, Select Clear Cache on the login screen.Read the Universal GUI  user interface guide to get familiar with the GUI. Universal GUI version 2024.1.12For more information about setting up the Universal GUI, see the Universal GUI setup  guide.Note:Use a modern browser to access the Universal GUI, such as a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.1.12 here  ContentsDemo Universal GUI version 2024.1.12 New and changed User preference - Save custom cube view User preference - Show or hide columns User preference - Remember prefilter status User preference - Sort & group Changed filtering in lookup-type columns Windows GUI-like navigation option for editable fields in form and grid Formlist - Lookup editors Formlist - more enhancements Grid - Update multiple records Custom CSS - More control over combo and suggestion controls Custom CSS - Classes for identifying mandatory fields in a grid Import - Asynchronous import function on Azure Pivot grids - Conditional layout Pivot grids - Access underlying cell data Pivot grids - Collapse/expand nested series Minor fixes and tasks Fixes in full release 2024.1.12 What we will be working on next sprint Questions or suggestions? New and changed User preference - Save custom cube viewnewUsers can now save custom cube views by selecting Save as cube view from the overflow menu. They can enter a name and select the default type.Save as cube viewThe saved cube view will show next to the model cube views.A custom cube view next to the model cube views To delete it, users can select Delete cube view [name] from the overflow menu. User preference - Show or hide columnsnewUsers can now show or hide grid columns in read-only grids. This option is available in the overflow menu of the grid. Additionally, they can change the Lock columns until setting.To configure the availability of these options for your users, see Configure user preferences .Show or hide grid columns in read-only grids User preference - Remember prefilter statusnewThe Universal GUI can now remember and apply a user's preferred state for a prefilter (activated or de-activated). A prerequisite for this feature is that in the Intelligent Application Manager, the setting Prefilter status is enabled in the Advanced menu > Master data > UP availability. For example, if a user deactivates a prefilter that was initially activated, and returns to that screen, the prefilter will automatically be deactivated by default.In this release candidate, the status for user-defined prefilters is not yet remembered. User preference - Sort & groupnewUsers can now change the sort order in a grid if the permission Allow sort has been selected for that table (menu User interface > Subjects > tab Settings > tab Permissions > group Data).With this permission enabled, a user's changes in the sort order and grouping will be saved, and the next time they log in, their preferences will be applied to the table.If a user selects the option Sort... in the menu, the Sort popup will appear. Here, a user sees the current status of the table: the columns on which the grid is sorted, the order of the sorted columns, and the direction in which the data in every column is sorted. If the Group permission has been selected in the Software Factory, a user also sees the Group button and if the data in the table is grouped by column(s).In the Sort popup:To sort data, users can select column(s) on the left and use the >> button to add and sort columns in ascending order. To exclude columns from sorting, users can select column(s) on the right and use the << button to move the columns to their default position on the left. To group columns, users can select columns on the right and then select the Group button. If the selected column has been grouped already, the columns will be ungrouped. To move all the columns from the right to the left, users can select the Clear button. If OK is selected, all the groups and sorting will be removed. To return to the default settings as set in the Software Factory, users can select the Default button. To change the column order on the right, users can select a column and the Up button. If the column above is grouped and the selected one is not, the selected one becomes grouped, too. Users can use Down to move columns down in the same way. To change the sorting direction in a column, users can select a column at the right and the button Direction.Known issue:When a column that is not visible in the grid is added to the sorting, it will be temporarily visible. Refreshing the Universal GUI, going into edit mode, closing and reopening the document, or switching pages in pagination will hide the column. Then, it will no longer become visible.The Sort popup Changed filtering in lookup-type columnschangeTo enable further development of filtering from grid column headers, we have changed how other column filtering methods like filter forms and quick filters work.Multiple records may have the same display value, like two employees with identical names. When filtering by that name, we now show all matching records for both individuals. This means we filter by the display value and duplicate names appear only once in the dropdown list.However, column filters applied through the Change filter process flow action filter by key. These filters are treated as system filters and no longer visible in the filter form or grid header. Users can add more filters to the column to refine their filtering. System filters are automatically cleared using the Clear filters option from the toolbar because system filters may be applied to hidden columns.Once a column is filtered, the in-line filter form dropdown shows all relevant options. Previously, the dropdown was filtered by its filter value, resulting in a single option being shown. Windows GUI-like navigation option for editable fields in form and gridnewUsers can now use Windows GUI-like navigation through the editors of editable components in the Universal GUI. This can be helpful if you migrate from the Windows GUI to the Universal GUI.We have added the extended property KeyBindings to support changing how you navigate your application with the keyboard. You can configure it per application or model in the Software Factory. Choose the value "Classic" for Windows GUI-like navigation or the default value "Modern" for the standard Universal GUI navigation.The keyboard shortcuts are as follows:Navigation Classic Modern Move to next editable control in form/grid Enter Tab Move to previous editable control in form/grid Shift + Enter Shift + Tab Open the file explorer from the file editor Alt + Enter Enter  We have added new keyboard shortcuts to avoid conflicts if you choose to use "Classic" navigation.You can create a new line in a multiline editor by pressing Alt + Enter instead of Enter. You can open a dropdown list by pressing ↓.The following editors do not support "Classic" navigation:Label Group header label Group header icon Signature Image upload Image blob Image link Video link HTML (in grid) Formlist - Lookup editorsnewWe have added support for lookup editors in the Formlist screen component. Previously, it only showed a loader and no editor.Now, the editor is shown, and the selected value is saved right after the user selects an option, just like the supported types of editors already do.Note:Related lookup editors are not yet supported. For example, booking hours: the selected project filters the subproject field with the subjects that belong to the selected project. The pop-up button is not available. We aim to keep the Formlist simple, so there is no option to look up or select a record from the pop-up. The configuration of a lookup relation in the Software Factory knows different control types. In a Formlist, comboboxes will become suggestion controls. Comboboxes (dropdowns) have the disadvantage that the list of options is loaded directly. This would result in many requests for options on initial load or data refresh. Suggestion controls load a limited number of options and only when working on the field. Formlist - more enhancementsnewIn addition to the support for lookup editors as described above, we have added even more functionality to the FormList component:In a default procedure, the Formlist will now correctly apply new values, also to other columns than the edited column. For a layout procedure, the layout will be applied after a value has been changed. For the following setting, the Formlist rows will be refreshed after a value has been changed: menu User interface > Subjects > Settings > Performance > group Refresh > field After update > select Subject. Note: if refreshing is not strictly necessary, select None since refreshing slows down performance. Grid - Update multiple recordsnewUsers can now update multiple records ('mass update') in tables at once, by selecting the Update option from the overflow menu. They can select the fields to update and enter a new value for each of themAfter the update, a message appears, showing the number of records updated and any errors found.Updating lookups directly is not supported. This feature will be included in a future update. Mass update is unavailable while the subject is in edit mode.Update multiple records in tables Custom CSS - More control over combo and suggestion controlsnewWe support two different types of combobox controls: the Combobox (dropdown list) and the Combobox with a suggestion. Previously, these types shared the same CSS styling.We have added new CSS classes to make it possible to use different CSS styling for each type of combobox:'combo-select' applies to the Combobox (dropdown list) control 'autocomplete-select' applies to the Combobox with a suggestion controlYou can now visually distinguish between the controls if needed. Custom CSS - Classes for identifying mandatory fields in a gridnewThe grid now includes classes on each cell to show the column's state. This allows you to hook into these classes in your custom CSS. You can find these classes on the .conditional-layout-container. Use this option to make certain types of cells stand out more, for example, if they contain an error.The classes are:.mandatory for cells with a mandatory field .readonly for cells with a disabled field .has-error for cells with a field that has an error Import - Asynchronous import function on AzurechangeThe import function on Azure now runs asynchronously to avoid timeouts. This ensures the file imports are completed regardless of their duration. This feature requires WebSockets. The system will fall back to the synchronous method if WebSockets are not configured.For more information on the configuration of WebSockets, see Enable WebSockets in Azure. This also applies to the Universal GUI. Pivot grids - Conditional layoutnewWe have added support for conditional layouts for pivot grid fields (menu User interface > Business Intelligence > tab Cube views > tab Conditional layout). This allows you to draw a user's attention to specific fields.Situations where the conditional layout is useful:In standard cube views (not custom cube views) In basic conditional layouts. A cube view can have multiple conditional layouts. For grand totals and nested fields (categories) Pivot grids - Access underlying cell datanewIt is now possible for a user to double click a pivot grid cell to open a pop-up with a grid containing the underlying data for that specific cell. This new grid is read-only and adheres to any filters set on the pivot grid. Pivot grids - Collapse/expand nested serieschange newNested series (columns) in pivot grids are no longer default expanded, but users can still expand them manually. This is now similar to the categories (rows).For both series and categories, we have added support for the setting to expand them by default. It is available in the menu User interface > Business intelligence > tab Tables > tab Cube fields > tab Cube view fields > tab Form > checkbox Expand. Minor fixes and tasksA layout can change from mandatory to non-mandatory. Saving an empty non-mandatory field that was previously saved as mandatory resulted in the error cannot_save_document_field_error. This has been fixed. Non-existent data was incorrectly displayed as 0 in the chart. Now, the chart no longer draws these absent data. We have resolved two issues that incorrectly positioned tasks in the action bar, even though they were located elsewhere on the screen. This has been fixed. Sometimes, the overflow menu did not appear in the action bar on mobile phones. This has been fixed. Now, when space is limited, the CRUD buttons will collapse individually into the overflow menu. It was possible to use the CRUD buttons while an operation was already in progress, resulting in an error. This is no longer possible. When the process action Activate detail was used as a starting point, a 'bad request' error would appear. This has been fixed. In some cases, the pinned cell within the grid that shows the sum aggregation of data showed a non-numerical element like a checkbox instead of a number. Now, it always shows a number if a sum value can be calculated. In grids with the option Auto-save enabled, manually saving a record left the grid in edit mode. This has been fixed. Now, the grid exits edit mode automatically after saving. Editing shortcuts are now limited to components on the screen that allow add, copy, and edit actions. Lookup pop-up buttons did not always open the pop-up on the first click. This has been fixed. If a user opened a lookup pop-up and clicked the Add button quickly enough, the pop-up would occasionally not switch to the tab where the data for the new item could be inserted. This has been fixed. If you used the filter form with numeric or date/time controls, this could result in a bad request network error, causing empty controls on dropdowns. This has been fixed. Fixes in full release 2024.1.12The value "Classic” of the KeyBindings extended property that was added to the release candidate was case-sensitive. We have fixed this, so it is no longer case-sensitive, and the value "classic" now also works. Filtering a dropdown using the IN operator was not applied since the last release candidate. This is fixed now. On both numeric controls and dropdowns (data value), filters on value 0 are now applied. ​​​We have fixed an incorrect translation in the new Mass update feature. The default width of fields in filter forms has been reduced to 250px, just like fields in the regular form. As part of the release candidate of this version, we introduced the concept of system filters. These are filters from the change filter process flow action. We decided not to show system filters to the user anymore. It turns out that some of our customers used these filters as initial input for the filter form, where users can modify it to see another set of data, for example, to show all data from the current year 2024 initially. It is now possible again to filter on these columns from the filter form.  The system filters are still not displayed to the user. They will be replaced when the user filters for a different value/criteria in the same column.  What we will be working on next sprintThe next sprint we will be working on:Grid header filtering for look-up-type columns Pivot row (category) grand totals Mass-update lookup-type columns Pivot grid sorting improvement Pivot grid total positioning user preferences Vertical bars Freely positionable prefilter, cube view, report and combined filter (search) bar Action bar content alignment Questions or suggestions?Do you have any questions or suggestions about the release notes? Let us know in the Thinkwise Community!

This is an additional release to Universal GUI 2024.1.11. It contains one change.On a slow or unstable connection it may happen that the task or report tile buttons were not loaded. This has been fixed.The 2024.1.11.1 release is now available for download in TCP.

February 19, 2024Full release 2024.1.11 In the Software Factory, we have the concept of unrelated details. Tables are linked but no columns are linked to each other to bind them. We have fixed an issue where an action was executed from an unrelated detail, causing the parent subject to be emptied. In that case, the detail was cleared too, which was unexpected.   Hello everyone,In this sprint, we have added support for features that have been introduced in the Thinkwise Platform 2024.1 release, such as tying a column to a double-click task and auto_commit for default logic. We have also improved the task shortcuts and the preview component. Additionally, we have added a new extended property to lift grid row height safeguards and another one to open lookups full-screen. We have also made some minor fixes and tasks. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.1.11 For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.1.11 here ContentsDemo Universal GUI version 2024.1.11  Contents New and changed Support for tying a column to a double-click task Support for auto_commit for default logic Shortcut support Task shortcuts available in every context Preview component PDF enhancements Extended property to lift grid row height safeguards Active cube view retained Handling OpenID provider in poor network conditions Logout button when application or platform is not available Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedSupport for tying a column to a double-click tasknewIt is now possible to tie a double-click task to a column, as introduced in the Thinkwise Platform 2024.1 release.This feature allows each column in a grid to start a different process or handle specific data. For more information, see Configure a double-click task. Support for auto_commit for default logicnewThe Universal GUI now supports the auto_commit feature introduced in the Thinkwise Platform 2024.1 release. This feature makes it possible to automatically save the record after filling in a field. This opens up new possibilities, such as, after receiving input, starting a process flow for validations and automatically returning to edit mode. For more information, see New parameter for default logicThe Universal GUI supports this for:Editing a new or existing record after changing a value Directly after add/copy Changing a parameter value of a task or reportNot yet supported:In combination with auto-edit and auto-save The 'confirm update' confirmation on tables The 'ask' confirmation for tasks A task without tsf_send_progress does not show progress Shortcut supportnew changedIn addition to the shortcuts that we have added in the previous sprint, we have added some new options and made a change in behavior: Ctrl + R opens the advanced filter pop-up. For iOS, we have added Cmd key support since this is used more often than Ctrl. If you add your own shortcut for a task, Ctrl will be replaced by Cmd. You can add your own shortcuts for your application in the menu Processes > Tasks > tab Settings > tab General. After opening a new subject, the detail subject was activated for shortcuts. However, this differed from the Windows GUI where the main subject is activated. Therefore, we have changed this behavior, now, the Universal GUI also activates the main subject. You can switch between subjects to activate its shortcuts by: navigation between tabs focusing a form control activating a grid cell (new)  Task shortcuts available in every contextnewTask shortcuts now function in every context, including detail subjects and subjects opened in a pop-up. Previously, they only executed tasks on the main subject.See, for example, the lookup pop-up in the screenshot below. When editing the Employee field in the Hours subject and clicking the zoom button behind the field, the pop-up opens with tasks in the taskbar. Now, you can do the same using keyboard shortcuts.Determining which subject is triggered follows the same logic as the CRUD shortcut keys introduced in the previous sprint. Additionally, the active subject is now also determined when a grid is activated, so the tasks with a shortcut are immediately available. Previously, the active subject was only determined when navigating to another subject, limiting the ability to return to a parent subject to execute shortcuts.Opening a pop-up using keyboard shortcuts Preview component PDF enhancementschangePreviously, when the Preview component showed a PDF file on Chrome on Android, the user had to open it in a PDF app to see its contents. On iOS, the preview would only show the first page and no toolbar. To address these issues, we now use an alternative way to display PDFs.NoteUse iOS version 15.4 and up. Use a recent version of Chrome (as required by the Lifecycle policy). Older versions like Chrome 114 do not work well with this new way of showing PDFs.This new way of previewing PDFs also fixes password protection and enables the use of links and forms in the PDF preview on iOS.To implement this solution, you need to configure two more MIME types on your web server. The web.config file included with this Universal GUI release already contains this configuration, so it can handle it for the IIS. Other web servers need the additional configuration:Extension MIME type .mjs application/javascript .ftl application/octet-stream  Extended property to lift grid row height safeguardsnewIt is already possible to set the row height in the grid. The Universal GUI will mostly adhere to the set height but does add some safeguards to:Ensure the tap targets are large enough Ensure controls fit in the cells in edit modeIn some instances, you may want to remove these safeguards. This is now possible with the following extended property: DisableGridRowHeightSafeguards: trueNote:When you disable the safeguards, it is your own responsibility to ensure all the content in the grid fits and looks good. This setting also affects the values at the bottom of the grid. Another height may be necessary to ensure the values are visible. Check this carefully when testing this setting. Extended property for opening a pop-up full-screennewA new extended property, 'OpenLookupsFullScreen', is now available. By setting it to 'true', all lookup pop-ups will open at a larger size, around 90% of the screen. The size is not entirely full-screen to maintain recognition as a pop-up. Active cube view retainednewThe active cube view will now be retained when opening the same screen on different devices or in different browsers. Handling OpenID provider in poor network conditionschangeThe Universal GUI depends on Indicium to receive information about the usage of OpenID providers. This information determines whether the GUI should redirect to a provider. In poor network conditions, the request for this information might be lost, and the Universal GUI would show its login page instead. This could lead to errors when local login was disabled in IAM.Now, if the Universal GUI does not receive information from Indicium but has a loginAuthProviderHint in the config.json file, it will not show the username and password fields. Logout button when application or platform is not availablechangedWhen an application or platform is unavailable, users previously received one of the following error messages:'This platform isn't available for the application. 'This application is not available. Contact your administrator.' 'No applications available. Contact your administrator.'Now, a logout button appears adjacent to the login button in such situations. This prevents users from being unable to perform any actions due to user authorization failures. Minor fixes and tasksA few months ago, we changed the default position of tooltips from the bottom to the top. However, at specific heights, when the tooltip reached the top of the window, it would start flickering. This problem was partially resolved in the last sprint. Now, we have addressed the remaining occurrences. Tooltips will still be displayed at the top by default, but if they are too large, they will be shown at the bottom. We have solved some issues with the styling of the progress bar. The cut off label has been fixed and the alignment has been improved. The Formlist component disappeared after clicking the refresh button on the main subject. This has been solved. It was possible to use the CRUD buttons while an operation was already in progress, resulting in an error. This is no longer possible. We have fixed an issue that, some specific cases, a record was auto-saved directly when it was added or copied. This would lead to a validation warning. The labels in a chart were displayed in datetime format even though the datatype was date. This has been fixed. Previously, a horizontal scrollbar appeared in a filter as long as there was a filter condition. Now, it will no longer appear as it is unnecessary. What we will be working on next sprintThe next sprint we will be working on:Save and delete a user defined cube view. This allows a user to save a cube view they made with the pivot field editor. Save and delete a user-defined pre-filter. This allows a user to save a filter they created with the filter form as a pre-filter. Formlist improvements Excel-style filter look-up control Sort- and group pop-up Cube view pivot conditional layout Open drilldown from cube view pivot grid Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

An additional release is available to Universal GUI 2024.1.10. It contains one change. Changed handling of OpenID provider informationThe Universal GUI depends on Indicium to receive information about the usage of OpenID providers. This information determines whether the GUI should redirect to a provider.In poor network conditions, the request for this information might be lost, and the Universal GUI would show its login page instead. This could lead to errors when local login was disabled in IAM.Now, if the Universal GUI does not receive information from Indicium but has a `loginAuthProviderHint` in the `config.json` file, it will not show the username and password fields. The 2024.1.10.1 release is now available for download in TCP.