Product Updates

Hello everyone,In this sprint, we updated the IdentityServer component, we added some query string and template parameters, Azure Active Directory can be used as a pool user, and you can now set the initial password with the Forgot Password function.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.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, for example, system flows and OpenID.Download Indicium Basic release 2022.2.15 here (no new version this time). Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2022.2.16 here. Contents of this releaseAbout Indicium Breaking IdentityServer component updated Indicium - New New two-factor authentication query string parameter New email template parameters for password reset Use Azure Active Directory as a pool user Set the initial password with the Forgot Password function Indicium - Changed Logging in the Indicium database event log improved Performance improvements Scheduled license refreshes Minor fixes and tasks BreakingIdentityServer component updatedThe IdentityServer component is updated to the latest version. This component is used when you have configured OpenID clients in IAM. There should be no noticeable changes. The refresh and access tokens generated with the previous version will remain valid after the update.Due to license changes for the external IdentityServer component, a maximum of five OpenID clients are allowed after this update. Please contact Thinkwise if you need more than five clients.Indicium - NewNew two-factor authentication query string parameterFor two-factor authentication, we added a new query string parameter. This allows the two-factor authentication flow to be automated through links in the emails sent.The Indicium /account/ui/twoFactor two-factor authentication page has a new twoFactorToken query string parameter. The two-factor authentication email template already had a {twoFactorToken} parameter that sent the token to the user by email, but adding this parameter to the query string allows you to turn it into a hyperlink:/account/ui/twoFactor?twoFactorToken={twoFactorToken}. Using this URL, the user does not need to copy and paste the token.New email template parameters for password resetThe Indicium /account/ui/resetPassword password reset page has two new query string parameters: username and resetToken. The password reset email template already had a {resetToken} parameter, and we added a username parameter. Now, you can turn it into a hyperlink:/account/ui/resetPassword?username={username}&resetToken={resetToken}.Using this URL, the user does not need to enter these two parameters.Use Azure Active Directory as a pool userWe have implemented the ability to use Azure Active Directory users as the database pool user for Indicium. There is one drawback to this feature at the moment: it cannot be used to create a new database using the creation screen in the Software Factory.To use this feature, in the appsettings.json configuration file, set the UseAzureActiveDirectory setting under MetaSourceConnection to true. Optionally, you can set the PoolUsername and PoolPassword parameters as well.If the PoolUserName and PoolPassword are not set, Indicium will use the managed identity which is running the App Service in Azure as the pool user (similar to how it would use the Application Pool Identity for IIS). To enable using the managed identity of the App Service on your Azure SQL Database, add the App Service as a user to the database using the following statements:CREATE USER {APP_SERVICE_NAME} FROM EXTERNAL PROVIDER;ALTER ROLE db_owner ADD MEMBER {APP_SERVICE_NAME};Set the initial password with the Forgot Password functionIf you have not yet configured a password a user in IAM, the user can now set their own initial password using the Forgot password feature of Indicium. This feature allows you to reset your password via email.Indicium - ChangedLogging in the Indicium database event log improvedWe have improved the logging of SQL statements for SQL Server in the Indicium database event log. You can access this Indicium database event log from the Indicium landing page. As of this version, we log the entire "exec sp_prepexec" statement, including its parameters, in the database event log. This allows you to view the parameter values and copy and run the SQL statement into your SQL Server Management Studio or Azure Data Studio without having to define the parameters yourself.Performance improvementsIn some situations, Indicium must validate whether a parent record is still available. In this release, we improved the performance of the associated SQL queries. The performance improvement depends on several factors, but we now ensure that only the required columns are selected. The performance improvements will be most noticeable when working on detail screens in the Universal GUI.Scheduled license refreshesA few weeks ago, our license server went down during the weekend, which made it impossible for instances of Indicium to automatically extend licenses. This by itself is not an issue, because Indicium will start extending licenses long before they actually expire. However, it came to our attention that whenever Indicium is unable to extend a license, it retries this so frequently that it causes considerable load on the database server. In this release we have greatly reduced the frequency of retries in order to prevent such performance issues in the future.Minor fixes and tasksIf the Indicium root URL contained a base path segment such as /indicium, the returning @odata.context metadata URL in several Indicium responses was incorrect. The extra segment would then be missing from the metadata URL. This has been fixed. When Indicium is running in Production mode (default), it will not send all database errors/messages to the client, because they might contain sensitive information about the architecture of the database or the network. Nearly all of these messages could be found in the error log, but there were a few that were not logged anywhere. This has now been fixed.

Hi everyone!We’ve released the following platform improvements this week: IAM 2022.220221103 - OpenID provisioning default value override fix Previously when logging in through the means of OpenID provisioning there were situations where values that were updated manually within IAM, such as first name, surname or gender, would be updated back to their default value the next time those users logged in. Since this was not a desirable situation, this has been changed in such a way that the following options are now possible: The user does not yet exist in IAM: The user is provisioned. For those values that cannot be determined based on the returned claim values, the default static value from either the mapping or the column itself will be used. The user already exists in IAM: The user is updated based on the returned claim values. In the situation that a specific claim value is not present in the returned data set, the following will happen: If said value is already present in the user table (i.e. the field is not empty), it will not be updated. If said value is empty in the user table, it will be updated with the static default value as specified in the OpenID user template or the underlying mapping, which can be present for Tenant, Gender, Language and Time zone.

Hi everyone!We’ve released the following platform improvements this week: IAM 2022.220221027 - IAM printer and Indicium model refresh Overriding the printer address for a specific application in IAM would not work, because the required information was not provided to Indicium. Additionaly, you would get an error message when trying to reset the override value to the original value. Also, when certain changes are made to an application model, Indicium needs to refresh the model. This did not occur in all required scenarios, because it should also occur when printer or OAuth settings are adjusted.

October 28, 2022:Changed beta release to the full version: 2022.2.15.0 Improvements for issues found in the previous beta release: Due to changes in the previous beta release, in some cases opening a dropdown control could result in an error. In our case, the lookup presentation field was optional. This has been fixed. Now, if there is no value to display, the Universal GUI displays the database value. In some cases, charts did not load their data. This has been fixed.  Hello everyone,In this sprint, we made some improvements in the Scheduler and the Maps components. Also, we added a URL to include with TCP tickets, and you can now select all current page records in a grid with the keyboard shortcut Ctrl+A.In these release notes you will find a full overview of these main features and all minor features and tasks.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress.Universal GUI version 2022.2.15.0Do not forget the documentation  and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2021.1 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.2.15.0 here  Contents of this releaseUniversal GUI version 2022.2.15.0 New Scheduler component improvements Select all current page records with the shortcut Ctrl+A Added URL to include with TCP tickets Changed Maps component improvements Other fixes and tasks Known issues in this release What we will be working on next sprint NewScheduler component improvements You can now activate the Scheduler component from a process flow. With input parameters, you can now specify the date and time to scroll to. Select all current page records with the shortcut Ctrl+AWhen the focus is on a grid, you can now press the keyboard shortcut Ctrl + A to select all records currently displayed. With multiple pages, all records on a single page are selected.Added URL to include with TCP ticketsWhen an error occurs in a Universal application, the error message now contains a URL that you can include when reporting this issue as a TCP ticket. This URL makes it easier for Thinkwise to find and solve the reported problem. Error message with URL ChangedMaps component improvementsIn the Maps component, when using a marker of type Circle, you can now set the circle size, as follows. The default value for radius is 200 pixels.{ "CoordSets": [ [ { "Lon": "10.865400", "Lat": "55.565922" } ] ], "Radius": 120}Other fixes and tasks In this sprint, we fixed some scenarios where a process flow could become unresponsive without any possible user intervention to continue and finish. For example: An unknown process action within a process flow. Recovery when Indicium returns an error after being called. A process action targeting an unknown object, for example, a hidden detail tab or detail tile. The following user actions resulted in unwanted auto-adjusted column widths. This has been fixed. Resizing empty header columns in a grid. Clicking on a column with attribute grouping on it. Switching documents. Opening row groups. When executing a task that uploaded a large file, crashes and bad network requests could occur. This has been fixed. When searching for an item in a lookup dropdown by typing, items were also matched by their underlying data value, which was unwanted. Now, items are only matched by the value shown on the screen. In the Software Factory, you can configure the filter condition (type) of a field displayed in the filter form. However, in some situations, the filter conditions chosen are not supported. For example, a lookup field filtering with Contains did not behave as expected. Unsupported configured filter conditions will now be replaced internally with Equal to. The Refresh functionality changed in the 2022.2.14 release did not work as expected in a default editable grid. When refreshing a record after an edit, the old values were restored. This has been fixed. In a default editable subject, when typing in a combined filter, pausing, and then continuing typing, the focus moved to the top visible row, causing you to continue typing there. This has been fixed. In some scenarios, a grid would blink when saving an edited record. This has been fixed. The overall grid performance has also been improved. When filtering or pre-filtering process actions, the data was refreshed too often. This has been fixed. These process actions now wait until the data is refreshed in the client before the process flow continues. Known issues in this releaseThese two issues are planned for the next sprint.In default edit mode, when changes are saved or canceled manually without leaving the record, in some cases the subject jumps out of edit mode. In default edit mode, when a record contains an error after a refresh, for example, a mandatory field without a value, in some cases you cannot cancel the changes.What we will be working on next sprintThe next sprint we will be working on:Deep link to process flow - Final implementation of deep linking to process flow actions. History browsing (stage 1) - Enable history browsing for the main subject. You can then use the next and previous buttons in a web browser to open the previously opened subject. Implement new HTML Component - Add the new HTML component to Universal instead of the existing control.

Hello everyone,In this sprint, we made it possible to add sound files to messages, and we introduced a new extended property that sets the type of prefilters to be applied after a refresh.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.2.15 here. Download Web GUI 2022.2.15 here.BreakingOnly locked prefilters are applied after a refreshAs of this version, only locked prefilters are applied by default after an automatic refresh.This is a refresh that occurs for example after a task is finished, or after a detail subject has been edited.Until now, all prefilters were applied after a refresh. To change this default behavior, you can set the new extended property UseOnlyLockedPrefilterForRefresh to No.This extended property specifies that only locked prefilters are applied after an automatic refresh. The default value is Yes. When changed to No, all prefilters will be applied after an automatic refresh.NewWindows GUI performance improvedThe Windows GUI performance has been improved when running on the Indicium Basic application tier.These performance enhancements are especially noticeable in documents with a large data set. Playing audio messagesIf you want to add a sound to your message, you can now upload an Audio file. The file will be played upon receiving the message. The allowed extensions are .wav and .mp3. This feature was introduced earlier but contained some shortcomings.Example of a message with an audio file 

Hello everyone,In this sprint, we added support for generating DevExpress reports on .NET 6, and we have improved our support for Amazon SNS (Simple Notification Service).You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.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, for example, system flows and OpenID.Download Indicium Basic release 2022.2.15 here. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2022.2.15 here. Contents of this releaseAbout Indicium Indicium - New Support for generating DevExpress reports Amazon SNS (Simple Notification Service) support Indicium - Changed Minor fixes and tasksIndicium - NewSupport for generating DevExpress reportsWe have added support for generating DevExpress reports on .NET 6. This allows Indicium to generate reports on Linux. Please note:Reports targeting DB2 data sources are not supported. You must install and update the dependencies mentioned here On Linux, Indicium will use the .NET 6 version of the DevExpress reports plugin by default. Windows will continue to use the .NET Framework 4.7.2 version by default, but you can use the .NET 6 plugin by changing the Runtime app setting to NET:{ "Reporting": { "DevExpress": { "Runtime": "NET" } }}Amazon SNS (Simple Notification Service) supportAs of this release, Amazon SNS can be used to call Indicium's standard APIs (for example, tasks, tables, etc.).Until now, Amazon SNS could not call these standard APIs because while Amazon SNS sends JSON messages, it sets the Content-Type header to text/plain, instead of application/json. We have introduced a new middleware that recognizes Amazon SNS requests and changes the text/plain Content-Types to application/json, making them compatible with the Indicium APIs.Indicium - ChangedWe have improved our error logging regarding features that are not supported on some platforms, for example, Linux. The error message now clearly indicates that this is the reason.We have improved Indicium's error logging in several places. The severity, content, and category of many error messages are now more accurate, and these error messages are now easier to parse for Azure Application Insights and AWS CloudWatch. Some additional improvements for AWS CloudWatch will be coming up in the next release.By default, Indicium only allows redirects to its own domain. For OpenID clients, it is also possible to redirect to the URLs that are allowlisted in the OpenID clients.  Finally, redirect URLs can also be allowlisted in IAM's global settings. If Indicium does not accept a redirect URL, then Indicium redirects to its own root URL. This was considered confusing, so we improved our logging to state why a redirect URL was not accepted and how to fix this.Indicium's import API now calls layouts and defaults with @import_mode=1.We updated the description of secrets stored in AWS Secrets Manager to clarify their purpose and the implications of deleting them.Minor fixes and tasks[Indicium Basic] In a group of mandatory and mutually exclusive prefilters, when the Look-up state of all filters was set to "Off hidden", Indicium did not show any result. This has been fixed. Now, if no filter is selected, all filters are combined with OR clauses into one statement.

Hi everyone!We’ve released the following platform improvements this week: SF 2022.220221017 - Show correct percentage during synchronization When starting the Generation of synchronization scripts via the Indicium API, the progress of the job can be followed inside the Software Factory in the Synchronization to IAM screen. If this process had no follow-up process, the process would simply finish and leave the screen showing a completed process and a progress of 20%. This could falsely indicate the process hadn't finished, so it has been changed to show 100% upon completion. IAM 2022.220221019 - Pooled OIDC provisioning fix Changes to users in IAM are restricted in such a way that the application pool account used by Indicium needed to be an administrator in IAM to be able to perform OpenID user provisioning. This has been resolved.

Hi everyone!We’ve released the following platform improvements this week: IAM 2021.1 and up20221003 - cardlist translation correction When using a cardlist translation in Universal, the wrong translation was retrieved. Now the correct translation will be retrieved. 20221004 - Copying extended properties When copying a GUI application in IAM, we only included the extended properties in the copy that also existed in the SF model. This was not correct, because it is also possible to manually add extended properties in IAM. You also want to include these extended properties. This has now been fixed. SF 2022.220221005 - Correct user_defined_dttp for upgraded uniqueidentifier domains During the upgrade to platform version 2022.2, a value has been changed in the base table data of "dttp" regarding uniqueidentifier domains. This change has corrected the placement of the uniqueidentifier datatype inside generated source code. Whilst the base data has been corrected, domains that existed pre-upgrade may still have an incorrect value for field user_defined_dttp which causes the domain name to be used inside generated source code rather than the uniqueidentifier datatype. This has been fixed. 20221005 - i_ui views performance optimizations This service update provides optimizations that improve the performance for 3 functions used in the i_ui views: i_ui_col_form, i_ui_task_parmtr and i_ui_report_parmtr.   When starting an end product created with the Thinkwise Platform, the model must be loaded. For the Universal GUI, this is done by using so-called i_ui views. These views load the data in the most efficient way, which is a challenge because the model and amount of data can differ enormously per customer. We always strive to offer a solution that works as well as possible for everyone. SF and IAM 2021.1 and up20221005 - Universal column width adjustment The minimum form column width for Universal GUI has been reduced by omitting the default label width for the form column width calculation. This compensates for the fact that labels are generally shown inside the input fields in Universal GUI. This change increases the data density of the form in the Universal GUI. Input fields in the form will now better match the Windows and Web GUI in width. Click to enlarge This change may have an adverse effect on fields that had their label size set to zero and the resulting available form entry width added to the field width (e.g. 335px). These fields may be reduced to a smaller size compared to their appearance in the Windows and Web GUI. To counter this effect, you can adjust the field width in Subjects to change the minimum form column width in Universal GUI for a certain subject to 335 or adjust this at value at the Default settings to change this globally.

 October 7, 2022:Changed beta release to the full version: 2022.2.14.0 Improvements for issues found in the previous beta release: When double-clicking a row in a grid to execute a task, the task was executed before applying the context application logic. This has been fixed. This is especially important when double-clicking an unselected record to determine whether or not task execution is allowed.  Hello everyone,In this sprint, we made it possible to add or copy a row in a pinned top row of a grid, and we slightly changed the refresh functionality. Also, we started with a UI/UX design for advanced filters.In these release notes you will find a full overview of these main features and all minor features and tasks.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress.Universal GUI version 2022.2.14.0Do not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2021.1 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.2.14.0 here  Contents of this releaseUniversal GUI version 2022.2.14.0 New Adding a row in a pinned top row of a grid Refresh functionality Improvement when forgetting your password Activate the Maps component from a process flow UI/UX design for advanced filters Other fixes and tasks Known issues in this release What we will be working on next sprintNewAdding a row in a pinned top row of a gridAs of this version, in an editable grid, you can now add or copy a row by using a pinned top row.Adding a row in a pinned top row in a grid Refresh functionalityThe refresh functionality has changed. In previous versions, we supported most refresh options for task execution and editing. The refresh row option refreshed the entire subject.Now, the refresh row option is not only supported for tasks, but also after updating a single record.The refresh options for a task are available in menu Processes > Tasks > tab Default/Variants > tab Table tasks > tab Form > tab Table task. The refresh options for a row are available in menu User interface > Subjects > tab Default > tab Settings > tab Performance.Improvement when forgetting your passwordWhen you enter your username in the login screen, and then click Forgot your password?, your username will now be filled in automatically on the next screen.Activate the Maps component from a process flowYou can now activate the Maps component from a process flow. You can now also use input parameters to change the zoom level and navigate to a specific location on the map.UI/UX design for advanced filtersTo help you get an overview of what is coming up in the Universal GUI, we will, from now on, include new component designs in the release notes. In this sprint, we dived into the advanced filters.According to our design, it becomes possible to set up your own specific set of filter criteria and filter with different filter operators (such as 'Starts with', 'Between', or 'Is not empty'). You can open the advanced filter popup using a button in the filter bar's overflow menu or a shortcut key.My customers advanced filterAfter this action, a popup opens, in which a user can add or remove filter criteria. In the Software Factory, you can specify a filter configuration for a subject, and add filter criteria. These criteria, if any, are then displayed in the filter popup in the application, and can be changed.Example of an advanced filter Other fixes and tasksIn some languages, the toolbar label would overlap the toolbar's action buttons. This has been fixed. When quickly changing the sorting order of multiple columns in a grid, some columns could incorrectly change position. This has been fixed. When counting the number of records in a grid summary row, the result was not displayed, only the label. This has been fixed. If the Show label option was disabled for a grouped tree, the label was still displayed. This has been fixed. In process flows, specific process actions did not provide active record information to Indicium, preventing the process flow from using this information. This has been fixed. In a card list, the labels did not get the specific card list translation but the general translation. This has been fixed when connected to the Software Factory. This issue has not yet been fixed when connected to IAM. A software Factory hotfix will be available in the near future to solve this. On a mobile device, when switching to edit mode, the size of detail tiles could change, resulting in the tiles changing position. This has been fixed. When a grid or form was open while a process flow was active, the flow waited for a tab change before continuing. However, a tab change did not always happen, causing the flow to stop and remain active. This has been fixed. In a conditional layout, for fields that had both a conditional background color and a text color defined, only the conditional background color was applied. This has been fixed. When switching between rows with multiple views of a cube displayed simultaneously, inactive cube views did not refresh. This has been fixed. Some specific screen type configurations could cause misalignment between vertical and horizontal tab strips. The horizontal tab strip would then be displayed in an undesirable location on the screen and become unusable. This has been fixed.Known issues in this releaseThe Refresh functionality changed in the beta release does not work as expected in a default editable grid. When refreshing a record after an edit, the old values are restored. What we will be working on next sprintThe next sprint we will be working on:When selecting or clearing a checkbox in a grid, this change is currently not immediately visible. This will be improved. Process flow action Activate scheduler - With this process flow action you can activate the scheduler component, similar to Activate grid and Activate form. Technical design New HTML Component. Select all records on the current page using the shortcut key Ctrl + A. In a card list, double-clicking a card will execute the corresponding table task, if any. In a grouped tree, double-clicking a tree item will execute the corresponding table task, if any.

Hello everyone,In this sprint, we fixed some issues.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.2.14 here. Download Web GUI 2022.2.14 here.Minor fixes and tasksWe fixed a compatibility issue related to the 2021.2 platform release and the latest Windows and Web GUIs. When starting the application, this issue caused an error about a sub_flow_modeler key. In the Windows GUI with Indicium Basic, when searching with a 'between' filter between two dates, the start date and end date were not included. This has been fixed.

Hello everyone,In this sprint, we changed the process flow behavior when this flow is marked as Deep linking allowed. Also, we made some logging improvements, and we added a session variable for the actual logged-in user.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.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, for example, 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 2022.2.14 here. Contents of this releaseAbout Indicium Breaking Process flows behavior when marked as Deep linking allowed Indicium - New Logging improvements New session variable for the actual logged-in user Indicium - Changed Process flow behavior when canceled by the user  BreakingProcess flows behavior when marked as Deep linking allowedProcess flows marked as Deep linking allowed were never intended to be started automatically by their start actions: a task or adding a record should never start the process flow.These process flows were not started automatically in the Thinkwise Windows and Web GUIs, as intended.However, Indicium was inconsistent in this matter and this has been corrected in this release. Deep links must be started via an API call to the process flow itself, which initiates the process flow start action in the GUI. While this was always the intent of the feature, this is a breaking change for Indicium, so please be aware of this change.Indicium - NewLogging improvementsIn this release, we have added more logging functionality to make troubleshooting easier.When a default procedure sets a value for a lookup property that is not hidden from the user, and the value is outside of this user's mandatory lookup prefilters, Indicium would reject this value and set the lookup property to null. Since it was difficult to see why this was happening, we added an error log message for this. All log messages related to process flows now also contain the application ID to which the process flow belongs. This is especially useful when troubleshooting scheduled system flows.New session variable for the actual logged-in userWhen simulating users, you can now use the tsf_original_login session variable to retrieve the user who initially logged in. In this release, you can use this session variable as follows:On SQL Server: select SESSION_CONTEXT(N'tsf_original_login') On Oracle: select sys_context('session_vars', 'tsf_original_login') from dual;Indicium - ChangedProcess flow behavior when canceled by the userIn a process flow, when the first action is a task or report, and the user cancels the popup dialog, until now, the process flow was not started. Indicium will now continue the process flow if the last process action was not successful (marked by a red arrow), and indicates that the result of the task is "User canceled".

Hello everyone,In this sprint, we made it possible to add or copy a row in a pinned top row of a grid, and we slightly changed the refresh functionality. Also, we started with a UI/UX design for advanced filters.In these release notes you will find a full overview of these main features and all minor features and tasks.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress.Universal GUI version 2022.2.14 BETADo not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2021.1 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.2.14 BETA here  This is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Friday. Contents of this releaseUniversal GUI version 2022.2.14 BETA New Adding a row in a pinned top row of a grid Refresh functionality Improvement when forgetting your password Activate the Maps component from a process flow UI/UX design for advanced filters Other fixes and tasks What we will be working on next sprint NewAdding a row in a pinned top row of a gridAs of this version, in an editable grid, you can now add or copy a row by using a pinned top row.Adding a row in a pinned top row in a grid Refresh functionalityThe refresh functionality has changed. In previous versions, we supported most refresh options for task execution and editing. The refresh row option refreshed the entire subject.Now, the refresh row option is not only supported for tasks, but also after updating a single record.The refresh options for a task are available in menu Processes > Tasks > tab Default/Variants > tab Table tasks > tab Form > tab Table task. The refresh options for a row are available in menu User interface > Subjects > tab Default > tab Settings > tab Performance.Improvement when forgetting your passwordWhen you enter your username in the login screen, and then click Forgot your password?, your username will now be filled in automatically on the next screen.Activate the Maps component from a process flowYou can now activate the Maps component from a process flow. You can now also use input parameters to change the zoom level and navigate to a specific location on the map.UI/UX design for advanced filtersTo help you get an overview of what is coming up in the Universal GUI, we will, from now on, include new component designs in the release notes. In this sprint, we dived into the advanced filters.According to our design, it becomes possible to set up your own specific set of filter criteria and filter with different filter operators (such as 'Starts with', 'Between', or 'Is not empty'). You can open the advanced filter popup using a button in the filter bar's overflow menu or a shortcut key.My customers advanced filterAfter this action, a popup opens, in which a user can add or remove filter criteria. In the Software Factory, you can specify a filter configuration for a subject, and add filter criteria. These criteria, if any, are then displayed in the filter popup in the application, and can be changed.Example of an advanced filter Other fixes and tasksIn some languages, the toolbar label would overlap the toolbar's action buttons. This has been fixed. When quickly changing the sorting order of multiple columns in a grid, some columns could incorrectly change position. This has been fixed. When counting the number of records in a grid summary row, the result was not displayed, only the label. This has been fixed. If the Show label option was disabled for a grouped tree, the label was still displayed. This has been fixed. In process flows, specific process actions did not provide active record information to Indicium, preventing the process flow from using this information. This has been fixed. In a card list, the labels did not get the specific card list translation but the general translation. This has been fixed when connected to the Software Factory. This issue has not yet been fixed when connected to IAM. A software Factory hotfix will be available in the near future to solve this. On a mobile device, when switching to edit mode, the size of detail tiles could change, resulting in the tiles changing position. This has been fixed. When a grid or form was open while a process flow was active, the flow waited for a tab change before continuing. However, a tab change did not always happen, causing the flow to stop and remain active. This has been fixed. In a conditional layout, for fields that had both a conditional background color and a text color defined, only the conditional background color was applied. This has been fixed. When switching between rows with multiple views of a cube displayed simultaneously, inactive cube views did not refresh. This has been fixed. Some specific screen type configurations could cause misalignment between vertical and horizontal tab strips. The horizontal tab strip would then be displayed in an undesirable location on the screen and become unusable. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:When selecting or clearing a checkbox in a grid, this change is currently not immediately visible. This will be improved. Process flow action Activate scheduler - With this process flow action you can activate the scheduler component, similar to Activate grid and Activate form. Technical design New HTML Component. Select all records on the current page using the shortcut key Ctrl + A. In a card list, double-clicking a card will execute the corresponding table task, if any. In a grouped tree, double-clicking a tree item will execute the corresponding table task, if any.

Hi everyone!We’ve released the following platform improvements this week:SF 2022.220220923 - Correction in the Synchronization run orchestration when using API-calls When there was a large enough time difference between the two API-calls to Generate synchronization scripts and Synchronization to either IAM or Disk, it would lead to these two processes to not be linked correctly in the Synchronization run. Without that link, the Synchronization to IAM screen could not show the processes properly. This has been fixed. IAM 2022.2, 2022.1, 2021.3, 2021.220220923 - Granted execute rights to is_authorized_tenant function Some roles have not gotten execute rights for the is_authorized_tenant function. This has been fixed.

 September 16, 2022:Changed beta release to the full version: 2022.2.13.0 Improvements for issues found in the previous beta release: In a grid, when the Edit in grid option was disabled, it was still possible to edit if the corresponding form was also available. This has been fixed. In a subject with the Auto-save option enabled, it was not possible to execute a task or open a report after making changes in edit mode. This has been fixed. The row is now saved, and the task is executed, or the report is opened.  Hello everyone,As of this sprint, the resource scheduler remembers the selected timescale. Also, performance has been improved, and you can now apply a filter by pressing [Enter] when focused on a field.In these release notes you will find a full overview of these main features and all minor features and tasks.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress.Universal GUI version 2022.2.13.0Do not forget the documentation  and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2021.1 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.2.13.0 here  Contents of this releaseUniversal GUI version 2022.2.13.0 Breaking Thinkwise Platform support release 2020.2 is ending New Resource scheduler remembers the selected timescale Formlist with Combo and Image Combo elements Changed Performance improved when first opening a subject Default editable grid performance improved Filters applied with the 'Enter' key in a Filter component Minor fixes and tasks What we will be working on next sprint BreakingThinkwise Platform support release 2020.2 is endingIn accordance with our Lifecycle policy , Universal GUI support for Thinkwise Platform release 2020.2 is ending. Please upgrade to at least Software Factory release 2021.1 to use this Universal GUI 2022.2.13 release.NewResource scheduler remembers the selected timescaleThe resource scheduler now remembers the timescale the user selected: When reopening the scheduler window, the last timescale chosen is displayed. This preference is saved in the browser (for example, Google Chrome on your device) but is not persisted across browsers or devices.Formlist with Combo and Image Combo elementsThe Formlist component now supports Combo and Image Combo controls, using domain elements (as items to choose).ChangedPerformance improved when first opening a subjectWhen opening a subject for the first time in a session, the performance has been improved by loading the subjects' model data in parallel. As background information: A session starts when opening the Universal GUI. This session ends when refreshing or closing the Universal GUI browser tab.Default editable grid performance improvedTo improve the performance of the default editable grid, we changed the way it works. Previously, the Universal GUI was locked until the active row was saved and error-free. This made switching between rows very slow because committing the previous record and then setting the new row in edit mode was a sequence of actions.As of this version, a user can start editing the next row while the previously edited row(s) are still waiting for the commit. If an error occurs in a previous row, the user receives a message and visual help about it but can continue to edit the row they are working on and fix the error later.Filters applied with the 'Enter' key in a Filter componentIn a filter component, you can now apply a filter by pressing [Enter] when focused on a field. Previously, the filter would only apply after removing focus from the field ([Tab]).Minor fixes and tasks For a grid with a row group, double-clicking a row group header would also incorrectly execute the double-click task assigned to a selected record within the group. This has been fixed. Importing records into a detail subject or lookup subject from Excel failed because the data was tried to be imported into the main subject. This has been fixed. When editing in a default editable grid and selecting another record, the grid could scroll unnecessarily. This could result in the edited record not being visible in the current view. This has been fixed. When executing a task on multiple records, the execution order was sometimes incorrect compared to the order in which the records were displayed. This has been fixed. In charts, translated domain elements were not shown. This has been fixed. We fixed a bug where the splitter content width exceeded its limits. Before this release, this could, for example, result in action bar buttons not appearing on the screen: Incorrect action bar buttonsThis has been fixed: Correct action bar buttonsWhat we will be working on next sprintThe next sprint we will be working on:Technical research: Deep link to process flow - A deep link to a process flow allows the developer to create links that can be sent via email or otherwise. These links start the Universal GUI and then a process flow. In the technical research, we design the underlying functionality. Activate maps process flow action - This process flow action allows you to activate the Maps component for the user, similar to the Activate grid and Activate form process actions. Activate scheduler process flow action - This process flow action allows you to activate the Scheduler component for the user, similar to the Activate grid and Activate form process actions. Add row in grid - The ability to add a row directly in a pinned top row of a grid. Refresh row functionality - The refresh row option will be supported for tasks and after inserting, updating, or copying a record. UI/UX design for advanced filter popup - The advanced filter option will be available as a popup to all users and offers more complex options than the current filter form. This functionality will become the basis for the user-defined prefilters.

Hello everyone,In this sprint, we made several improvements to the resource scheduler.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.2.13 here. Download Web GUI 2022.2.13 here.ChangedResource scheduler improvementsSeveral fixes and minor improvements have been made to the Resource scheduler:Hidden hours are correctly displayed in all view types. Work times are correctly displayed in all view types. Buttons to navigate to the next or previous appointments are removed in all view types. The date picker navigates to the current date when you click Today. Dragging an external row to an all-day area triggers the external drop task.

Hello everyone,In this sprint, Indicium can periodically remove unused application models from memory.Furthermore, you can now log to AWS CloudWatch, and the internal OpenAPI specification has been improved.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress. About IndiciumFor this version, one type of the Thinkwise Indicium Application Tier is available: Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2022.2.13 here.  Contents of this releaseAbout Indicium Indicium - New Periodic removal of unused application models from memory Logging to AWS CloudWatch Indicium - Changes Indicium OpenAPI specification improved Minor fixes and tasks  Indicium - New Periodic removal of unused application models from memoryIndiciumAs of this release, Indicium can periodically remove unused application models from memory.An application model is considered unused when:It has not received any API calls during the specified time. There has been no active system flow during the specified time. It has not been marked as a preloaded application model.We have added a new configuration option for this feature that you can set in the appsettings.json. Please note that "Applications" is the same configuration section as the "Applications" section mentioned in preloaded application model."Applications": { "RemoveUnusedModelAfterHours": 72}The default (and recommended) value of this setting is 72 hours. This may feel like a long time to keep unused application models in memory, but the goal is not to clear the memory as quickly and often as possible. After all, it is a cache that serves an important purpose. The performance-memory trade-off needs to be considered because once an application model is removed from memory and requested again through an API call, it needs to be loaded from the database, which will be a performance hit on that API call.The main goal of this feature is to ensure that Indicium instances that are rarely restarted, for example, because they are in use 24/7, don't gradually use more and more memory for 'dead' application models that have not been used for weeks.We recommend to lower this value only if all of the points below are true:Indicium is restarted rarely. Many applications are used for a short time within a short time. Indicium's memory usage is noticeably growing to several gigabytes within the 72-hours.Logging to AWS CloudWatchIndiciumWhen running Indicium on AWS, you can now log to AWS CloudWatch. This AWS functionality makes it easier to monitor the behavior and performance of your Indicium instance. For example, you can show the logs on your AWS dashboard or create an alarm based on a log pattern.To enable AWS CloudWatch, add the following code to the appsettings.json configuration file, under the "Logging" section: "AWSCloudWatch": { "LogGroup": "indicium-tst" }To get access to AWS CloudWatch, your EC2 instance needs to have the following policy attached to it:{ "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": "logs:DescribeLogGroups", "Resource": "*" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "logs:CreateLogStream", "logs:CreateLogGroup", "logs:PutLogEvents" ], "Resource": "arn:aws:logs:<location>:<account-number>:log-group:indicium-tst:*" } ]}In this code fragment, replace indicium-tst with the name of your log group in appsettings.json and specify your account-number and location.To add the logs to your AWS CloudWatch Dashboard:Open the AWS console. Open the AWS CloudWatch dashboard. Click Add widget. Select Logs table. In Logs Insights, select Log group. This is the name of the log group in appsettings.json. Add the following query to the log to show, for example, the last 20 items:fields @timestamp, @message| sort @timestamp desc| limit 20Click Create widget to show your logs on the dashboard.Indicium - ChangesIndicium OpenAPI specification improvedIndicium In this release, the internal OpenAPI specification has been improved. This API specification can be used by a third-party code generation tool like NSwagStudio or Swagger to call or to display the Indicium API. These third-party tools can then generate higher quality code with improved readability.Minor fixes and tasksIndicium Filter conditions containing a negation (for example, not equal to, does not start with, does not contain) were not handled correctly. For example, the condition <some_column> not equal to 1  would result in false when <some_column> was NULL. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week:SF 2022.120220902 - Usage of quoted identifiers for datatypes in base projects Some data types, such as FILESTREAM, ROWGUID and UNIQUEIDENTIFIER, do not support quoted identifiers when being executed on the database. Therefore, these data types will no longer allow aliases. This had already been fixed in version 2022.2, but is now also fixed for version 2022.1. SF 2022.220220825 - Optimize AutoML training process The training of machine learning models has been improved regarding the wall-clock training time estimations. In some cases, the training of machine learning models would stall.  

Hi everyone!We’ve released the following platform improvements this week:IAM 2022.220220823 - Exclude executionmode extended property Because the executionmode setting is now set through a different property, it is no longer necessary to pass this setting along in the global configuration settings. Thus it has been excluded.

 August 26, 2022:Changed beta release to the full version: 2022.2.12.0 Improvements for issues found in the previous beta release: In the Preview component, images that were too large for the available space were not displayed. In the Preview component, TXT and JSON files were not displayed. Both issues have been fixed.  Hello everyone,As of this sprint, passwords will no longer be shown in plain text in the GUI. Instead, we have added a visibility icon to the PASSWORD control. We have also added a change detector to the Preview component and improved the way incoming process flows work.In these release notes you will find a full overview of these main features and all minor features and tasks.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress. Universal GUI version 2022.2.12.0Do not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2021.1 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.2.12.0 here Contents of this releaseUniversal GUI version 2022.2.12.0 New Password visibility Version recorded in IAM Changed Smart remote file change detection for preview component Incoming process flow allowed Minor fixes and tasks Known issues in this release What we will be working on next sprint New Password visibilityIn password control fields, passwords will no longer be shown in plain text in the GUI. A user can now use the 'visibility' icon to hide the password from view or display it in plain text. The PASSWORD control is set for a column at the domain level. It is available in grid, form, and card list components.When a password field is non-editable or read-only, the visibility icon is hidden, and the number of characters is set to 8 instead of revealing the password length.CautionPasswords are not sent or stored encrypted, so this feature only protects against being displayed in plain text.A user can display or hide their password Version recorded in IAMAfter loading the application, the used Universal GUI version will now be recorded in IAM. Changed Smart remote file change detection for preview componentThe Preview component will now check whether the previewed file has been changed remotely. A check occurs when a user manually refreshes the document or the subject's data is updated due to another cause. If the content of a previewed file has been changed remotely, it will be reloaded.This is only available for File type preview columns. URL type columns will show the content from the given web address as is. Incoming process flow allowedIf a process flow was running and a new flow came in for the same subject, the Universal GUI used to ignore the incoming flow. From now on, it will stop the running flow and start the incoming flow.This change also fixes that a new process flow could not start when another process flow got stuck due to an action that was unable to execute. In the next sprint, we will continue our work on preventing stuck process flows. Minor fixes and tasksIn a Maps component with markers and popups, when you moved the position of the map and changed it to a different record, the map would not center correctly on the marker. This has been fixed. The process flow was not started when using a process flow to set filters in combination with the Start empty with filter setting. This has been fixed. When clicking on a field in a default editable grid, it did not get the focus. You had to click it again to start editing. Universal GUI will now put the focus on the field you actually clicked. One limitation: a cursor_to_col will always be performed in the form. When dragging events in the resource scheduler, sometimes duplicate events would be created. These were not stored in the database since they would be gone after closing and reopening the subject. This issue happened when auto-refresh had been enabled, and the user dragged an event during an auto-refresh. It has been fixed now. If the active record changed in the resource scheduler, the scheduler would jump to the current date. Now, the scrollbar will stay in the same position. We have improved the performance when switching to an already opened subject or an already opened detail tab. When expanding a cube row based on elements, the Universal GUI would give a bad request. This has been fixed. We have resolved an error shown in snack bar messages when navigating between records in a detail subject with another detail subject underneath. Because of this error, the lowest set would not refresh. We have resolved a crash that occurred after opening an application with a task as a start object. Known issues in this releaseSometimes, when a pivot is opened for the first time it shows no data and the text 'This pivot type is not supported'. What we will be working on next sprintThe next sprint we will be working on:Add row in grid - The ability to add a row directly in the grid. Refresh row update strategy. Activate Maps and Scheduler components from a process flow Scheduler component remembers time scale selected by the user.

Hi everyone!We’ve released the following improvements in the Upcycler 2022.2:Special characters in object names (e.g. tables) were replaced by underscores. This could result in tables with the same name. Now these characters are replaced by their ascii code. During an upcycler run sometimes the following error could occur: Process action 'delete_mock_model_appl' in processflow 'delete_mock_appls' threw an exception. (3b2832e8). Indicium.Shared.TSF.NonFatalDbException: The DELETE statement conflicted with the REFERENCE constraint "ref_server_gui_appl". The conflict occurred in database "IAM", table "dbo.gui_appl", column 'server_id'. This is fixed

Hello everyone,In this sprint, we have solved a problem with conditional layouts for the Web GUI.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.2.12 here. Download Web GUI 2022.2.12 here. Changed Stylesheets and conditional layouts (Web GUI)Previously, the Web GUI created a stylesheet file (CSS) based on the theme name.This naming caused problems in IAM environments where multiple applications could use the same theme.Since those style sheets also contained the conditional layout styles, and the file names contained only the theme name,they were overwritten when another application that used the same theme was loaded.To solve this problem, we split the themes and conditional layouts into multiple files.The conditional layout style sheets will now be specified using the application ID instead of the theme name.

Hello everyone,In this sprint, we have added support for environment variables in File System storage configurations.We have also improved model loading in general and for system flows specifically.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress. 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, for example, system flows and OpenID.Download Indicium Basic release 2022.2.12 here. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2022.2.12 here.  Contents of this releaseAbout Indicium Indicium - New Support for environment variables in File System storage configurations Indicium - Changes Improved model loading Minor fixes and tasks Indicium - New Support for environment variables in File System storage configurationsIndiciumFile system storage configurations now support environment variables in their base path (for example, %TEMP%). These variables are also supported by process actions that use these file system storage configurations.ExampleD:\files\%FileLocation%\file.txtwhere %FileLocation% is, for example, thinkwise/textfiles. Indicium - Changes Improved model loadingIndiciumIn this release, we have tremendously improved the loading of application models.If multiple applications (IAM) or runtime configurations (Software Factory) are based on the same project and project version, the application model will only be present in memory once.  The only exceptions are those parts of the application model that can be overridden per application or runtime configuration, such as storage configurations or extended properties. Application models containing Azure/AWS/FTP storage configurations that are used many times across different columns, task/report parameters, and process variables will load significantly faster now. On adding an extended property or overriding a storage/OAuth configuration for an application or runtime configuration, Indicium will no longer refresh the entire application model. Minor fixes and tasksIndicium We fixed an issue where a process flow would not start correctly if the start action was a Start table task or Start table report on a variant. Indicium Indicium Basic We fixed an issue for DevExpress reports where parameters could not intentionally be left or set to null even if "Allow null values" had been turned on for said parameter. Indicium  We have fixed an issue regarding user provisioning and claim types with multiple values. When an Identity Provider supplied an array of claim values for a single claim type, Indicium would only send the first of these values to IAM for user provisioning. An example of this for Azure AD is the "groups" claim, which can contain an array of GUIDs, one for each group of which the user is a part. These claims will now be sent correctly to IAM as a JSON array.

Hi everyone!We’ve released the following platform improvements this week:SF 2022.220220805 - Resolve index object creation for views When changing the Table type setting for Tables to View, it can occur that a View will have an Index. This situation is incorrect and is validated by the Software Factory. The control procedure that generated the objects for indexes missed a check that resulted in an error when having an index on a View. This has been resolved. IAM 2021.1 and up 20220802 - Fix for override configurations in copy application When creating an additional application in IAM, based on an already existing application, the option exists to include certain configuration settings when copying the application. Previously this copy action would also include configuration settings that were no longer present in the SF model. This has been resolved by adding a check that will ensure only those settings that still exist are included.

 August 5, 2022:Changed beta release to the full version: 2022.2.11.0 Improvements for issues found in the previous beta release: When selecting multiple records in a grid and then clicking a task button, only the active row was displayed as part of the selection. The task was still executed for all selected records, but this was unclear to users. This has been fixed. The selection remains visible until the task is executed.  Hello everyone,In this sprint, we made it possible to resize grid columns, and when opening the scheduler component, the displayed period now starts from the previous month instead of the current day.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress.Universal GUI version 2022.2.11.0Do not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2021.1 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.2.11.0 here  Contents of this releaseUniversal GUI version 2022.2.11.0 New Resizable grid columns Changed Displayed period in Scheduler component Minor fixes and tasks What we will be working on next sprintNewResizable grid columnsYou can now resize grid columns and change the column width manually. The column widths are retained after closing and reopening a document and after a refresh.ChangedDisplayed period in Scheduler componentWhen opening the Scheduler component, the displayed period started with the current day. If you wanted to view the previous week, you had to navigate back. This behavior was not desired. As of this version, when opening the scheduler component, the displayed period starts from the previous month.Minor fixes and tasksIn certain time zones (for example, GMT-12), when choosing a date using the date picker icon, for example, July 28th, an incorrect date value (July 27th) was used. This has been fixed. In default edit mode, when a user did not modify the record, they had to cancel edit mode before executing a task or report. This has been fixed. Now, when executing a task or report, edit mode is automatically canceled if the user has not modified the record. After adding or copying a record, the edit, delete, and copy buttons were available too early. This would result in a "bad request" message when quickly trying to perform any of these actions after adding or copying. These three buttons are now disabled until they can be used. When executing a task containing a file upload, the application could stop responding. This has been fixed. When a parent grid was in edit mode, it was incorrectly allowed to switch between rows in a child subject. When a child subject was in edit mode, it was also incorrectly allowed to switch rows in the parent grid. This has been fixed. In both cases, switching between rows is no longer allowed. Loading lookup translations used to fail if there were 800 or more filter conditions. This situation could occur, for example, if there were 800 rows with only one primary key or 400 records with two primary keys. This has been fixed by splitting the lookup translations into multiple requests if there are many filter conditions.What we will be working on next sprintIn the next sprint, we will be working on: Ensure that a new process flow always starts. This prevents the user from getting stuck in an old process flow. Asynchronous editing in grids. New Password control. Research performance rendering nested details. In progress: Drag and drop records UI/UX.

Hello everyone,In this sprint, we updated the DevExpress components and the DevExpress Report Designer, and we solved an issue.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.2.11 here. Download Web GUI 2022.2.11 here.ChangedUpdated DevExpress components and Report DesignerFor the Windows GUI and Web GUI, the DevExpress components have been updated from version 21.1.6 to 21.2.8. The Thinkwise DevExpress Report Designer has also been updated.Please let us know if you encounter any unexpected changes in the Scheduler component, or with date or time controls, DevExpress Reports, or cubes.Minor fixes and tasks[Windows GUI] Default active prefilters did not work correctly after a restart of the application. This has been fixed.