Product Updates

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.2 to 2023.120240910 - Clean up pref When IAM contains very old user preferences, the task of cleaning up unused preferences (Optimization > Clean up unused preferences) could give an error on tenant_id. This has been fixed.

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!  

Hi everyone!We’ve released the following platform improvements this week: SF 2024.220240829 - Merge session generate delta action improvement When merging an arbitrary branch to its true origin branch (usually MAIN), the difference analysis could skip untouched model objects if they were not changed in the branch. This has been resolved.   20240830 - Show subflow input and output details for web connections The input and output parameter details for the process action type Web connections were not assigned properly, causing them to be invisible. This has been resolved.

Hello everyone,In this sprint, we done a security update and fixed a minor issue.You can read more about the Windows GUI's features, in the user interface guide.Download Windows GUI 2024.2.14 here. ContentsNew Security update Minor fixes and tasks Questions or suggestions? NewSecurity updateWe have updated a NuGet package (Newtonsoft.Json) to the latest version to ensure that the application is up to date and to prevent any potential vulnerabilities. This should not result in any changes in behavior. Minor fixes and tasksIn some situations, the Save file dialog would not be shown if the file name already existed in the directory. This has been fixed. Now, the dialog is always shown if a user does not want to overwrite an existing file.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  

Hello everyone,In this release, we have added more events to the process flow monitor to help you troubleshoot process procedures. We also added support for public clients in OpenID Connect in IAM.Make sure to check the breaking change, as it might affect your input constraints.You can read more about Indicium's features in the Indicium user manual. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.2.10 here.  ContentsAbout Indicium Breaking SQL Domain input constraints New and changed Process procedures shown in the process flow monitor Support for Public clients in OpenID Questions or suggestions? BreakingSQL Domain input constraintschangeThe SQL domain input constraints incorrectly used the column id instead of the domain id in the expression. This was incorrect, because you can use the same domain on different columns. Now the domain id is used in the expression.Validate your input constraintsIn many cases, but not always, the column id and the domain id are the same. Check your input constraints before upgrading to this version of Indicium. New and changedProcess procedures shown in the process flow monitornewThe process flow monitor now shows the process procedures and process variable values before and after execution. This information helps troubleshooting because is shows the changes in variables, making it easier to identify and resolve issues within the process procedures.The following events are new in the process flow monitor:ProcessProcedureStarted ProcessProcedureCompleted ProcessProcedureSubFlowStarted ProcessProcedureSubFlowCompleted Support for Public clients in OpenIDnewIt is now possible to create Public clients for SSO using OpenID Connect in IAM. These clients do not require registration of a client secret. You can use this for applications that cannot keep the secret secure, like a browser application.For more information, see Client applications.Public clients require IAM version 2024.2 or higher. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!   

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.220240823 - Change control of path field of apply database role tasks IAM has tasks for applying roles and rights on the database. This is only relevant for 2-tier environments due to users needing access rights to the database. The underlying domain control of the Save filename field had been changed but resulted in the apply role rights script being written to an inaccessible location. This has been resolved.

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.220240816 - Show web connection columns in sub flow screen The assignment fields for process action type Web connection were not visible in the Software Factory's Subflow process action screen. This has been fixed.

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! 

Hello everyone,In this sprint, we resolved an issue in the menu modeler of the Software Factory.You can read more about the Windows GUI's features, in the user interface guide.Download Windows GUI 2024.2.13 here.ContentsMinor fixes and tasks Questions or suggestions? Minor fixes and tasksWe've resolved an issue in the menu modeler of the Software Factory that caused menus to show as a flat list, rather than as a grouped list or tree. This issue occurred when using platform versions 2023.3 or 2024.1 with a Windows GUI newer than version 2024.2.10.0.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we added the parameter ‘Nonce’ to the OAuth user login URL, improved the Database Event Log page, and updated the SMTP protocol support for sending emails. We have also fixed some issues.You can read more about Indicium's features in the Indicium user manual .About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2024.2.13 here . ContentsAbout Indicium New and changed Parameter 'Nonce' in the OAuth user login URL Improved Database Event Log page Updated SMTP protocol support for sending emails Fixes and tasks Questions or suggestions?New and changedParameter 'Nonce' in the OAuth user login URLnewThe process action OAuth user login now includes the parameter 'nonce' in the URL. Although it is an optional feature, some third-party OpenID providers require it.Improved Database Event Log pagechangeWe have improved the Database Event Log page:Just like the Live Error Log and the Process Flow Monitor, the Database Event Log now automatically shows new entries as they occur, when web sockets are enabled on the web server. It still stores the last 100 event log entries persistently, either in memory or in a Redis cache, as well. We have added a request URL to make it easier to see what the corresponding request URL for any given database statement was. We have added a request ID that allows you to filter on all database statements caused by an individual request. You can now filter by text and minimum duration, as well as increase or decrease the number of items shown on the page. Note that when the number of items exceeds 100, the items beyond the last 100 will be removed after a refresh. We have updated the design to make it more in line with the Live Error Log and the Process Flow  Monitor.Updated SMTP protocol support for sending emailschangeWe have updated the implementation of sending emails via the SMTP protocol to a new, modern version.This only applies to sending system emails or emails through an SMTP type email provider when using the email connector. The SMTP connector has not been updated to use this implementation, consider migrating to the email connector instead.This update provides better support for modern protocols and authentication options, allowing us to send emails more effectively and with greater reliability. Key improvements include:Sending emails in bulk is now more reliable. The connection to the SMTP server is now reused, reducing server load and minimizing the risk of disruptions.Fixes and tasksWe have fixed an issue in the process action Show message where an error was erroneously displayed if the corresponding message was not translated. In the event that an issue occurs with sending a two-factor authentication (2FA) email, the error was not logged by Indicium. This has now been fixed. When a system flow is finished, Indicium will write the end time to IAM. This communicates to IAM that the system flow is finished and that it can be scheduled again (if it's not allowed to run concurrently). Sometimes it would occur that writing the end time to IAM failed due to, for example, a short network hiccup. When this happened, IAM would assume that the system flow is still running and not schedule it again. We have fixed this specific type of issue by adding a retry mechanism for writing the end time of the system flow. It will now try writing the end time for 30 seconds before giving up. When multiple Indicium instances were run behind a load balancer, connecting to the debug pages (live error log or process flow monitor) could take some time. This has now been resolved, and live data is displayed immediately. Indicium would always instruct the Universal GUI to offer a report as a preview, even when the report action was not Print preview or Print, but for example Export to PDF. Now, only report actions that involve a preview will cause the report to be previewed, while others will provide it as a download.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hi everyone!We’ve released the following platform improvements this week: SF 2024.2, 2024.120240724 - Include enrichment run data in job clean-up The Software Factory runs a clean-up job every night to remove any jobs that are completed and where the retention period was exceeded. During this process, enrichment run data will also be cleaned up but due to an oversight this led to an underwater error, resulting in the job not being deleted. This has been resolved. From now on, the entire enrichment run and its parameters and model updates will be cleaned up when the retention period is exceeded.

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.

Hello everyone,We have become aware of a performance issue in Indicium. It occurs when a Redis cache is configured, that is, when the appsettings.json contains a RedisSettings section (or if it is set through an environment variable).If you use a Redis cache as a part of your Indicium setup, we recommend updating to version 2024.2.12.1 for improved performance.The 2024.2.12.1 release of Indicium is now available for download in TCP.Our apologies for any inconvenience caused by this issue.

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.

Hi everyone!We’ve released the following significant platform improvements this week: SF 2024.2, 2024.1, 2023.3, 2023.2, 2023.120240711 - Creation improvements When using the task Execute complete creation, the Software Factory will first extract the model version from the selected runtime configuration or change the source version to the selected model version. However, there was a slim chance that the update of the source version could take a while and interfere with the process Generate definition, causing an error to occur. This has been resolved. The creation will now wait until the update is finished. In addition to that, the model version extraction from the runtime configuration has been significantly improved to perform the operation more quickly.  SF 2024.2, 2024.1, 2023.320240712 - Merge conflict resolvement improvements Several improvements have been made when resolving conflicts. Where prior to this improvement resolving conflicts in conflicting manners could cause errors, now the Software Factory will reset this resolution for the developer. That way the conflict will be resolved in the correct way. It is advised to install this improvement swiftly for the most optimal merging process.

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!  

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.220240701 - Improvement in determining the exported branch for usage metrics In some situations, the determination of which branch is most relevant for sending anonymized usage metrics to Thinkwise was incorrect. This resulted in no data being sent. This has been resolved.  IAM 2024.2, 2024.120240702 - Check classic user preference table for modified prefilter In a hybrid environment where the Universal GUI and Windows GUI are used alongside, there is specific scenario in which modifying user defined prefilters in the Windows GUI would cause an error. This has been resolved.

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!  

Hello everyone,In this sprint we have fixed a few minor issues, which are outlined below.You can read more about Indicium's features in the Indicium user manual. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2024.2.12 here.  ContentsAbout Indicium Breaking Support for Thinkwise Platform release 2022.2 has ended Changes Security enhancements Minor fixes and tasks Questions or suggestions? BreakingSupport for Thinkwise Platform release 2022.2 has endedIn accordance with our Lifecycle policy, we no longer support the Thinkwise Platform version 2022.2 as of this release. ChangesSecurity enhancementsAs part of our ongoing effort to maintain the highest security standards and protect your data, we have implemented several security enhancements that improve the overall safety and resilience of our platform.We recommend all users upgrade to this version as soon as possible to take advantage of these improvements and enhancements. Minor fixes and tasksWhen you are using a case-sensitive filesystem, the process flow monitor did not work. The JavaScript could not be loaded, due to a difference in the file name case. This has been fixed. The initial setup for two-factor authentication would only work if the setup was completed within one minute. This has been fixed. Our OData metadata document was missing the field PreviewContentType. This caused issues with certain integrations. This has been fixed. 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.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.

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.220240614 - Limit returned application data for references When having multiple IAM applications sharing the same model and branch, there is the possibility that the Windows GUI would not return any data in table, task and report look-ups. This has been resolved.  SF & IAM 2024.1 and below (including 2022.2)20240617 - Always return percentage for field sets When using Universal GUI version 2024.1.13 and below, having multiple fields on a single line could cause all but the first field to be invisible to the user. Using TAB, the user could see and fill in the focused field but this is suboptimal. This has been resolved for all supported versions including 2022.2. Platform version 2022.2 is no longer supported but does receive this improvement. It is advised to upgrade.

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.