Product Updates

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.

We have a challenge for you!We are in the midst of designing the Universal GUI version of filtering within the Pivot Table. We've made a prototype to let you experience the Universal GUI version of this feature and we would like to hear your opinion.Please leave your comments in the comment section below.You will see:A new expandable/collapsable panel, where the user can find the Pivot Table Editor and Pivot Table Filter. Filter Dimension only as a top row drop zone for Dimension Values A new Filter Tab in the expandable/collapsable component to see all used Dimension ValuesWe give you 3 assignments to go through this prototype:Use Dimension Value ‘Invoice status’ for the Filter Dimension (this prototype doesn't support Drag and Drop, clicking on the element is enough). Set the filter of ‘Invoice Status’ to only ‘Paid’ (clicking on any checkbox will directly set this filter correctly for this prototype)  Set the filter of ‘Sub project’ to Exclude ‘Braggs apts’ from the data  Reset ‘Sub project’ with the RESET button. Set filter ‘Invoice status’ so that all checkboxes are checked (again, clicking one checkbox in this prototype activates them all again) Set ‘Sub project’ to Include the value ‘Boardwalk center’ in the dataClick here to open the Prototype.Use password ‘pivot filter’ to access the design.Use ‘R’ to restart from the beginning of the prototype if you are stuck.  

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!   

Hi everyone!We’ve released the following platform improvements this week: SF 2024.2 20240605 - Enrichment improvementsWe made several improvements to enrichments themselves and the enrichment execution mechanism: Enrichment: Add a table description with AI Exclude generated tables in AI completion prompt for enrichment Enrichment: Create prefilters for checkboxes Exclude generated columns in Model update query and change instructions accordingly Suggest the to be created prefilter groups to be nonmandatory by default instead of mandatory Use the 'is_truthy' function to validate truthy input for the parameter @mand_grp in the enrichment templates 'create_prefilter_grp' and 'create_prefilters' Enrichment: Create prefilters for image combos Exclude generated columns in Model update query and change instructions accordingly Suggest the to be created prefilter groups to be nonmandatory by default instead of mandatory Use the 'is_truthy' function to validate truthy input for the parameter @mand_grp in the enrichment template 'create_prefilter_grp' Enrichment: Include every lookup column in the search Ensure that the enrichments not only supports tables but also table variants Rename template 'include_in_global_filter' to 'include_in_filter_tab' Add new template 'include_in_global_filter_tab_variant' to support table variants Task code: Generate model updates (technical: task_add_job_to_run_enrichment) Add enrichment title + parameters as job parameters

Hello everyone,In this sprint, we have updated a number of Thinkstore models with the new Web connections .The changes in this release are available for Thinkwise Platform version 2024.2 and higher. About the ThinkstoreThe Thinkstore is a fully integrated way for downloading and installing ready-made solutions directly into your models right from the Thinkwise IDE. It contains a collection of scripts and samples to help you get the most out of the Thinkwise Platform. You can find the Thinkstore in the Software Factory, in the menu Enrichment > Thinkstore.The Thinkstore only contains solutions specifically for the Software Factory version you are using. Therefore, the Thinkstore will be cleared before every platform upgrade. After the upgrade, if you open the Thinkstore in the new Software Factory version, it will initiate a refresh and retrieve all the available solutions for that version. This process runs in the background. It can take up to ten minutes before the solutions are available.You can read more about the Thinkstore in the Thinkstore guide . ContentsAbout the Thinkstore New, changed, and fixed in the Thinkstore models Updated the model "Currencies API" Updated the models "RDW car info", "KVK info", and "Webservice example to retrieve address info from zipcode" Removed the model "Use T-SQL OPENJSON for accessing JSON data" Questions or suggestions? New, changed, and fixed in the Thinkstore modelsUpdated the model "Currencies API"changeWe have removed the currency tables because this solution only provides a web connection and a task to start the API call and show the response. If you want to process the JSON response, this blog post with JSON examples might be useful. Updated the models "RDW car info", "KVK info", and "Webservice example to retrieve address info from zipcode"changeWe have replaced the last message with a task pop-up to make it easier to show the given JSON and process the information. Removed the model "Use T-SQL OPENJSON for accessing JSON data"changeThe model "Use T-SQL OPENJSON for accessing JSON data" has been removed from the Thinkstore. This blog post with JSON examples should give you enough information to work with JSON in T-SQL. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this sprint, we have changed the error handling for system flows. We have also fixed an issue that could occur when importing files that contained lookup translations.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.11 here. ContentsAbout Indicium New and changed Changed error handling for system flows Minor fixes and tasks Questions or suggestions? New and changedChanged error handling for system flowschangeIf multiple Indiciums are running against the same database, they will all try to execute the system flows. Only the first one will execute the system flow and the others will receive an error. These errors ('system_flow_already_running') would be logged to Azure Application Insights. Now, they are no longer logged. Minor fixes and tasksWe have fixed an issue that could occur when importing files that contained lookup translations. It would occur when the lookup reference had more than one column and the filter columns of the reference (i.e. all but the last reference column) had different IDs on the target and source sides of the reference (e.g. sub_project.project_id <-> project.id). The issue would not occur if data values were used for the import instead of translations or if the reference columns had the same ID in both tables. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!