Product Updates

Hi everyone!We’ve released the following platform improvement this week:SF 2021.3 & 2022.1 20220729 - Staged tables correction for DB2 control procedures A lot of control procedures in base projects now use the staged strategy. Some of these control procedures in the DB2_BSR base project did not have a #-prefix for the temporary tables. This led to the unjustified usage of the permanent equivalents of these tables, which resulted in an error message stating that the columns 'project_id' and 'project_vrs_id' were expected. By adding the #-prefix the tables are recognized again as temporary tables, and the error does not occur anymore. Wish you all a great weekend.

Hello everyone,In this sprint, we updated Indicium to .NET 6. Furthermore, you can now use Windows command tasks to open URIs in the Universal GUI, and use the Print File process action to print PDF files on a Windows platform.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.11.0 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.11.0 here.  Contents of this releaseAbout Indicium Breaking Update to .NET 6 Thinkwise Platform support release 2020.2 is ending Indicium Print File process action supported Use Windows command tasks to open URIs Minor fixes and tasks BreakingUpdate to .NET 6As of this version, Indicium requires .NET 6. This requirement aligns with the .NET lifecycle policy and ensures that you receive security updates.Important: To run Indicium Universal on IIS, you must install the ASP.NET  Core Runtime 6.0.7 Hosting Bundle: https://dotnet.microsoft.com/en-us/download/dotnet/6.0 Thinkwise Platform support release 2020.2 is endingIn accordance with our Lifecycle policy, Indicium support for Thinkwise Platform release 2020.2 is ending. Please upgrade to at least release 2021.1 to use this release of Indicium.IndiciumPrint File process action supportedAs of this release, Indicium supports the 2022.2 Print File process action.Please note that currently, you can only print files in PDF format on a Windows platform, and the printer must be installed on the web server.Use Windows command tasks to open URIsYou can now use Windows command tasks to open URIs in the Universal GUI, as follows: In the Task logic type field, specify 'Windows command':   In the Object name field, specify the URI to open:   When executing this task in the Universal GUI, the corresponding URI is opened in the browser. You can also use dynamic URIs via task parameters.Please refer to the Thinkwise documentation for more information about Windows Command tasks, with the following limitations:This implementation only supports opening URIs and not executing Windows commands. Windows command tasks cannot be used in process flows.Minor fixes and tasksIn a database storage configuration, the BLOB data column was not always cleared when clearing the corresponding file column. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week:SF 2022.2 Correction in upgrade script: renamed icons with duplicate names not reconnected to their objects During the upgrade to the 2022.2, all icons are placed in the new icon repository. After this, the icon is reconnected again to its corresponding objects. A problem occurred in the upgrade code that reconnects those icons having duplicate names to their corresponding objects. This resulted in these objects losing their icon. This has been fixed in the Upgrade script. Unfortunately, existing installations can not be fixed retroactively. In case you haven't started using the 2022.2, it is advised to redownload the Installation package from TCP. Otherwise, the affected objects should be manually linked to the correct icon again. We apologize for any inconvenience this may cause. 20220718 - Default database collation for new temp tables In the 2022.2 release, the code responsible for generating source code has been extended with two new temporary tables. These tables were not provided with a default database collation, which could result in an error while generating source code when the collation of the temp table was different from the collation of the database. This has now been fixed. 20220721 - Correct path for imported projects Used folder and file specification paths for Thinkwise base projects have been revised as there was a mismatch between them. This has been resolved. SF 2022.1 20220721 - Unlock imported project version before updates Due to locking the imported project version during the import of a model.dat file, some triggers did not trigger as intended. The project version will now be unlocked before these update statements.

Hello everyone!We’ve released the following platform improvements this week:SF 2022.2 20220714 - Base project edit for checks on generated_by_control_proc_id Fix implemented to ensure objects generated by base projects are also taken into consideration when executing certain sql_ scripts.  IAM 2021.1 and up20220715 - Fill field_in_next_col width We added an addendum for the hotfix to support field_in_next_col for future release of Universal.

 July 15, 2022:Changed beta release to the full version: 2022.2.10.0 Improvements for issues found in the previous beta release: In grids, the left and right arrow keys to switch between cells and the up and down arrow keys to switch between rows did not work. This has been fixed.  Hello everyone,In this sprint, among other things, we completed support for the Download file process action, and users can see the date and time in their local time zone. Furthermore, we now support vertical tabs, and we have improved the styling of read-only controls.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.10.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 2019.2 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.10.0 here  Contents of this releaseUniversal GUI version 2022.2.10.0 New Thinkwise Platform release 2022.2 support Subject variants support Process flow action: download file Process flow action: send user notification Display the date and time in the time zone of a user Vertical tabs Changed Improved styling of read-only controls Start empty with filter functionality Minor fixes and tasks What we will be working on next sprintNewThinkwise Platform release 2022.2 supportWe are currently working on support for:Activate Maps process action. Activate Scheduler process action. Play a sound after a message popups up.We have already completed support for:Subject variants (see below). Process flow action: download file (see below). Process flow action: send user notification (see below). Display the date and time in the time zone of a user (see below).Subject variants supportAs of Thinkwise Platform version 2022.2, Indicium can handle subject variants and variant-specific settings from the Software Factory. For example:Provide default values while editing. Apply the correct set of prefilters. Apply process flow rights. Use the correct set of columns in a combined filter.The current Universal GUI 2022.2.10.0 release informs Indicium which subject variant is involved in a user action. This makes the Universal GUI release dependent on the 2022.2.10 release of Indicium:If you install this Universal 2022.2.10.0 release, you must also install the Indicium 2022.2.10 release.Process flow action: download fileAs of Thinkwise Platform release 2022.2, the Universal GUI supports the new Download file process flow action.You can set process variables and use them in the input parameters to make a file available for download to the end-user. The file can originate, for example, from a database, or from file storage using a Read file connector, or it can be the result of a Generate report connector.Process flow action: send user notificationAs of Thinkwise Platform version 2022.2, a user can send a notification message to a specific user from a process flow. The Universal GUI receives this notification after the next request to Indicium and displays this notification as a snack bar message at the bottom of the screen.Display the date and time in the time zone of a userAs of Thinkwise Platform version 2022.2, a user will be able to see the date and time in their local time zone. The Universal GUI will support this.You can enable the local time zone for users in a control. When you select a control for a domain that shows a DateTime value, you can choose whether it should display the time for the user's current time zone or as stored in the database (Software Factory > menu Data > Domains > tab Form).The time zone for a new user will be set to Etc/UTC by default but can be changed in IAM, in menu Authorization > Users > tab Form > tab User > group User preferences > field Time zone.Vertical tabsThe Universal GUI now supports a new type of tabs called vertical tabs. This gives a new look to your screen types and looks like a small submenu within the related subject. The list of tabs that would by default appear horizontally side by side can now be displayed stacked on top of each other.To convert a (horizontal) tab panel in the Tab container component of a screen type to a vertical tab panel, change the Tab orientation property in the screen type modeler in the Software Factory to Vertical:(menu User interface > Screen types > tab Design. The Tab page properties are on the right-hand side.) Tab orientation property in the screen type modeler  Horizontal tabs example  Vertical tabs exampleKnown issue: If a vertical tab label is too long and cut off by ellipsis (...), a badge behind it, as shown in the EMAILS tab in the screenshot, will not be displayed.ChangedImproved styling of read-only controlsWe improved the styling of read-only controls: In a form, a control's background color can be affected by a Conditional layout. If no conditional text color is specified, the displayed value now has a contrasting color. The control label already behaves like this. When the control is disabled, the opacity of the contrast color is reduced so the value appears slightly gray. On a form component in edit mode, read-only fields were not consistently grayed out, making them appear editable. That has been corrected, so all read-only fields look the same now.  Name field before Name field afterStart empty with filter functionalityThe existing Start empty with filter option specifies that subjects are opened without data, and the filter pop-up is activated automatically. This configuration option was applied to main subjects and detail subjects. However, this functionality is unnecessary for detail subjects, as a detail already shows a limited list of records. As of this version, the Start empty with filter option will only be applied to the main subject.Minor fixes and tasksWhen adding a record in a non-editable grid, with Form and detail subjects on a separate tab, the Form tab was activated and incorrect detail data were displayed in some cases. This has been fixed.What we will be working on next sprintIn the next sprint, we will be working on: Asynchronous editing in a grid - To improve grid edit mode performance, we plan to have multiple records in edit mode behind the scenes. This allows the user to proceed while records are being saved in the background. Resizable grid columns - Users can resize the grid column width. Formlist domain control - Implementation of the domain control in the Formlist. Password control In progress: Drag and drop records UI/UX. Add row in grid.

Hello everyone,In this release, we have added steps to enrich your upcycled project, new technical Upcyclers, and extractors for Oracle and MySQL. In addition, it is now mandatory to enter a reason when you add a step or a variation to a technology or application. We have also added a default value for the application database server and name, made some changes and solved some issues.You can download the latest version of the Upcycler in TCP.  ContentsContents Requirements New Enrich your upcycled project Upcyclers and extractors for Oracle and MySQL Mandatory reason for creating (variation on) a step Default values for the application database server and name Changed Fields and tabs hidden when irrelevant DB2 Upcycler and extractor enhanced Minor fixes and tasks New and changed in Upcycle steps Upcycle step 2000 Source model loader Upcycle step 3000 Cleaner: Remove logicals Upcycle step 3400 Cleaner: Object identifiers Upcycle step 3500 Cleaner: Expression defaults Upcycle step 4500 Pre-processor: Assign new domains Upcycle step 5110 Transform Check constraints Upcycle step 5260 Fix: Code for changed table names Upcycle step 5261 Fix: Code for changed column names Upcycle step 5050 Transform Domains Upcycle step 5300 Transform List bar items Upcycle step 5400 Transform Transl objects Upcycle step 5410 Transform Transl objects Upcycle steps 6000-6999 Prepare data Upcycle step 7600 Update: Remove superfluous domains Data import step 1000 Drop temporary tables Data import step 2000 Source Model Loader Data import step 5000 Migrate to SF schema Data import step 6000 Create transfer steps Data model changes New tables Renamed tables Column changes  RequirementsSoftware Factory 2022.2 or higher is required. New Enrich your upcycled projectAfter you have created your application and imported data, you can now enhance your application with several enrichments, if necessary.To support you in this step, Enrichment runs are available.Enrichments are a way to automatically enhance an application.Some examples are to put an EMAIL control on all columns containing an email address, add a row count to the first column in a grid, or set main screen typesfor tables.These and many more enrichments are available by default.If they do not suffice, you can create variations on existing ones at the technology or application level or create your own.The enrichment process consists of two phases.First, you need to execute an analysis run. This run inspects both the model and data and produces a list of proposed actions. The proposed actions can contain updates to both the model and the data. Next, you can review the list, select the actions you wish to apply and execute the action run.The analysis run in the enrichment procesThe action run in the enrichment proces Upcyclers and extractors for Oracle and MySQLIn this version, we have added Upcyclers and extractors for Oracle and MySQL. Mandatory reason for creating (variation on) a stepWhen you add a step or a variation on a step to a technology or application, it is now mandatory to enter a Reason. This will highly improve the reporting of your Upcyclers.When upgrading your Upcycler with this version, the new field is filled with a default value.You can find the Reason fields in:menu Upcycle > Upcycle runs > tab Application upcycle steps > tab Form menu Upcycle > Data import runs > tab Application data import steps > tab Form menu Definition > Technology Upcyclers > tab Technology upcycle steps > tab Form menu Definition > Technology Upcyclers > tab Technology data import steps > tab Form. Default values for the application database server and nameWe have added default values for the application database server and name.The default value for the application database server is the current server (menu Upcycle > Applications > tab Form > field Application database server).The default value for the application database name is the application's name, in uppercase, with the illegal characters replaced (menu Upcycle > Applications > tab Form > field Application database server). Changed Fields and tabs hidden when irrelevantTo make it easier to find what you are looking for, some fields and tabs are now hidden when they are irrelevant. An example is the Transfer code. DB2 Upcycler and extractor enhancedThe DB2 Upcycler has been enhanced. It now generates descriptions and translations for tables and columns, and it no longer creates Views for DB2 Logicals.The DB2 Extractor has been enhanced to extract translations for tables and columns. Minor fixes and tasksThe default value for encoding model and data files when adding a new technology was UTF-16. Since the Extractor produces UTF-8 BOM files, the default has been changed to UTF-8 BOM. In the Technology Upcyclers, the encoding of model and data files was UTF-16. This has been changed to UTF-8 (already available in a hotfix). The Transfer code tab was editable (menu Upcycler > Data import runs > tab Application > tab Executed data import steps > tab Transfer code). This has been fixed. Data import runs would not start. The flow `system_execute_import_data_run` was not set to active in IAM (already available in a hotfix). New and changed in Upcycle steps Upcycle step 2000 Source model loaderWe have added loading of the extracted translations for DB2.Step New or changed Generic step Unchanged Variation for DB2 for iSeries Added: loading translations Variation for PostgreSQL Generic Variation for Progress OpenEdge Unchanged Variation for SQL Server Generic Variation for Uniface Unchanged  Upcycle step 3000 Cleaner: Remove logicalsWe have added a specific step for DB2.Step New or changed Generic step Not applicable Variation for DB2 for iSeries Specific. Stop DB2 Logicals from becoming Views Variation for PostgreSQL Not applicable Variation for Progress OpenEdge Not applicable Variation for SQL Server Not applicable Variation for Uniface Not applicable  Upcycle step 3400 Cleaner: Object identifiersIn Software Factory release 2022.2, the maximum length for an object name (for example, a table or a column) has been increased to 128.Step New or changed Generic step Changed Variation for DB2 for iSeries Generic Variation for PostgreSQL Generic Variation for Progress OpenEdge Added Variation for SQL Server Changed Variation for Uniface Changed  Upcycle step 3500 Cleaner: Expression defaultsIn MS SQL Server, the built-in functions newid(), newsequentialid(), rand() and textprt() are not allowed in a user-defined function. The Software Factory generates user-defined functions for expression defaults. Therefore, table creation will fail when column defaults that contain these built-in functions have been upcycled.As of Software Factory release 2022.2, an expression default that contains the function newid() is generated as default on the column, instead of a user-defined function, so the creation of the table does not fail. This used to be a Generic step, but it was for MS SQL Server specifically. This has been rectified.The Upcyclers have been updated accordingly.Step New or changed Generic step Removed Variation for DB2 for iSeries Implicitly removed Variation for PostgreSQL Implicitly removed Variation for Progress OpenEdge Was deactivated, now removed Variation for SQL Server Updated and now a Technology specific step Variation for Uniface Was deactivated, now removed  Upcycle step 4500 Pre-processor: Assign new domainsWe have made a small improvement to the coding of this step.Step New or changed Generic step Changed Variation for DB2 for iSeries Generic Variation for PostgreSQL Generic Variation for Progress OpenEdge Still deactivated Variation for SQL Server Generic Variation for Uniface Still deactivated  Upcycle step 5110 Transform Check constraintsIn Software Factory release 2022.2, the maximum length for a check constraint has been removed. It used to be 4000. The check on that length in this step has been removed.In MS SQL Server, the code of a check constraint is in round brackets. This is specific to this technology.Step New or changed Generic step Changed Variation for DB2 for iSeries Removed Variation for PostgreSQL Changed Variation for Progress OpenEdge Generic Variation for SQL Server Added Variation for Uniface Still deactivated  Upcycle step 5260 Fix: Code for changed table namesThe Upcycler changes the name of a table if it contains illegal characters, is too long, or when it occurs in multiple schemas. These changes are also made in all the upcycled code as a 'best effort' action.This step is now slightly more ‘aggressive’ to get a better balance between automatic changes and manual corrections. It now also processes the check constraints.Step New or changed Generic step Changed Variation for DB2 for iSeries Still deactivated Variation for PostgreSQL Generic Variation for Progress OpenEdge Still deactivated Variation for SQL Server Generic Variation for Uniface Still deactivated  Upcycle step 5261 Fix: Code for changed column namesThe Upcycler changes the column name if it contains illegal characters or if it is too long. Now, the column name is also changed in all the upcycled code as a 'best effort' action. This new step processes the control procedure templates and the check constraints.Step New or changed Generic step Added Variation for DB2 for iSeries Still deactivated Variation for PostgreSQL Generic Variation for Progress OpenEdge Still deactivated Variation for SQL Server Generic Variation for Uniface Still deactivated  Upcycle step 5050 Transform DomainsFor MS SQL Server, we have added the transformation of datatype rowversion.Step New or changed Generic step Unchanged Variation for DB2 for iSeries Unchanged Variation for PostgreSQL Unchanged Variation for Progress OpenEdge Still deactivated Variation for SQL Server Changed Variation for Uniface Unchanged  Upcycle step 5300 Transform List bar itemsThe Generic step has been improved, so it will also work for Oracle and Progress OpenEdge.Step New or changed Generic step Changed Variation for DB2 for iSeries Still generic Variation for PostgreSQL Still generic Variation for Progress OpenEdge Now generic Variation for SQL Server Still generic Variation for Uniface Unchanged  Upcycle step 5400 Transform Transl objectsWe have added table and column translations for DB2.Step New or changed Generic step Not applicable Variation for DB2 for iSeries Table and column translations Variation for PostgreSQL Not applicable Variation for Progress OpenEdge Not applicable Variation for SQL Server Not applicable Variation for Uniface Not applicable  Upcycle step 5410 Transform Transl objectsWe have added table and column translations for DB2. This step also fills the descriptions for tables and columns.Step New or changed Generic step Not applicable Variation for DB2 for iSeries Table and column translations Variation for PostgreSQL Not applicable Variation for Progress OpenEdge Not applicable Variation for SQL Server Not applicable Variation for Uniface Not applicable  Upcycle steps 6000-6999 Prepare dataTo ease the development of new Upcyclers, the Generic steps have been improved so it is no longer necessary to deactivate and activate the steps while you are incrementally developing an Upcycler.Step New or changed Generic step Changed Variation for DB2 for iSeries Still generic Variation for PostgreSQL Still generic Variation for Progress OpenEdge Now, all Prepare steps are generic Variation for SQL Server Still generic Variation for Uniface Unchanged  Upcycle step 7600 Update: Remove superfluous domainsThe Generic step has been improved so it will also work for Uniface.Step New or changed Generic step Changed Variation for DB2 for iSeries Still generic Variation for PostgreSQL Still generic Variation for Progress OpenEdge Still generic Variation for SQL Server Still generic Variation for Uniface Now generic  Data import step 1000 Drop temporary tablesThis step was not necessary and has been removed.Step New or changed Generic step Removed Variation for DB2 for iSeries Was generic, so automatically removed Variation for PostgreSQL Was generic, so automatically removed Variation for Progress OpenEdge Removed Variation for SQL Server Was generic, so automatically removed Variation for Uniface Removed  Data import step 2000 Source Model LoaderWe have added the column is_nullable when loading columns, to make it possible for the MySQL Upcycler to use the generic step.Step New or changed Generic step Changed Variation for DB2 for iSeries Generic Variation for PostgreSQL Generic Variation for Progress OpenEdge Unchanged Variation for SQL Server Generic Variation for Uniface Unchanged  Data import step 5000 Migrate to SF schemaWe have added the column is_nullable when loading columns, to make it possible for the MySQL Upcycler to use the generic step.Step New or changed Generic step Changed Variation for DB2 for iSeries Generic Variation for PostgreSQL Generic Variation for Progress OpenEdge Unchanged Variation for SQL Server Generic Variation for Uniface Unchanged  Data import step 6000 Create transfer stepsWhen importing data, it is not possible to insert a value in a column of types timestamp or rowversion.Step New or changed Generic step Changed Variation for DB2 for iSeries Generic Variation for PostgreSQL Generic Variation for Progress OpenEdge Generic Variation for SQL Server Generic Variation for Uniface Unchanged   Data model changesData model changes for the Thinkwise Upcycler meta-model are listed here. New tablesNew tables application_enrichment_analysis_step enrichment_run enrichment_run_action_step enrichment_run_analysis_step generic_enrichment_analysis_step hotfix last_agent_check_in technology_enrichment_analysis_step  Renamed tablesFrom table To table application_step application_upcycle_step generic_step generic_upcycle_step technology_step technology_upcycle_step  Column changesTable From column To column application_import_data_step - reason application_upcycle_step application_step_id application_upcycle_step_id application_upcycle_step generic_step_id generic_upcycle_step_id application_upcycle_step technology_step_id technology_upcycle_step_id application_upcycle_step - reason generic_upcycle_step generic_step_id generic_upcycle_step_id import_data_run - appl_lang_id import_data_run - data_db_name import_data_run - data_db_server import_data_run - data_file_encoding import_data_run - data_file_extension import_data_run - data_file_typ import_data_run - project_folder_spec import_data_run - project_id import_data_run - project_vrs_id import_data_run - sf_db_name import_data_run - sf_db_server import_data_run - import_data_run_error_text import_data_run - import_data_run_status import_data_run started_at import_data_started_at import_data_run ended_at import_data_ended_at technology_import_data_step - reason technology_upcycle_step technology_step_id technology_upcycle_step_id technology_upcycle_step generic_step_id generic_upcycle_step_id technology_upcycle_step - reason upcycle_run - data_db_name upcycle_run - data_db_server upcycle_run - data_file_encoding upcycle_run - data_file_extension upcycle_run - data_file_typ upcycle_run - data_folder upcycle_run target_sf sf_db_name upcycle_run dbserver sf_db_server upcycle_run - upcycle_run_error_text upcycle_run - upcycle_run_status upcycle_run started_at upcycle_started_at upcycle_run ended_at upcycle_ended_at upcycle_run_step upcycle_run_status status   

We are very excited to announce version 2022.2 of the Thinkwise Platform.This release contains so many new and improved features! For example, handler procedures for replacing GUI actions, OpenID provider registration and user provisioning, new process flow actions and connectors, improved file storage handling, time zone support, and a lot more.We will highlight some of these features in this blog. The release is available for download in TCP now.For more extensive information on these features and a complete listing of everything new, improved, and fixed in this release, please refer to the release notes in the Thinkwise Docs. Do not forget to check the breaking issues and data model changes which may affect your custom code. Some highlights in this releaseA new logic concept: handler procedures OpenID provider registration and user provisioning File storage handling New and changed in process flows Other highlights A new logic concept: handler proceduresA highly requested functionality in our Thinkwise Community has come available: you can now replace the insert, update and delete GUI actions by handler procedures.This new logic concept allows you to override the default insert, update and delete SQL commands initiated by the user interface and Indicium with your own business logic. It can be used best for actions that need to be performed row-by-row.Like other logic concepts, you can (de)activate the handler logic per table and action (menu User interface > Subjects > tab Default > tab Settings > tab Performance). In Functionality (menu Business logic), you have to assign code group HANDLERS to the control procedure. Then, you can assign the templates.Activate the handlersTo set a good example, we have replaced delete tasks in the Software Factory and IAM by a handler, where possible. As a result, you can now delete a record and its underlying data simply by executing delete from the CRUD action bar. This change only applies to the delete tasks for the immediate corresponding subject, such as delete table for tables, delete column for columns, etc.‘Delete’ in the CRUD actions OpenID provider registration and user provisioningAnother wish from our Community was OpenID provider registration and user provisioning. So, that is another feature we built.It was already possible in IAM to configure external OpenID clients, thus using the Thinkwise Platform as an OpenID provider. External OpenID provider configuration (using the Thinkwise Platform as a client) was only possible in Indicium's appsettings.json.  As of this release, the external OpenID provider configuration is available in IAM instead, in menu Authorization > OpenID providers. When registering an OpenID provider, it is possible to enable provisioning. In that case, users will be created and updated in IAM after authentication, based on the claim values received from the OpenID provider. If you configure user groups, they will also be automatically created or updated for the user. You can set up a template for automated provisioning, manually modify requested scopes, update mappable claims, and provide mappings when necessary.OpenID provider settings in IAMFile storage handlingIt is now possible to deviate from the initially configurated file storage location type. For example, the Software Factory writes its code files to disk (default) but this can be switched to AWS. Then, if a system flow contains a Write file connector using the reconfigured file storage, Indicium would write it to AWS S3. This is available for applications in IAM and runtime configurations in the Software Factory.The initial file storage location for a project version is set in the Software Factory, in the menu Projects > Project overview > tab Project version > tab File storage locations. In IAM, you can override the file storage location for an application in the menu Authorization > Applications > tab File storage locations > task Switch file storage location type. In the Software Factory, you can configure the base file storage location for each runtime configuration in the menu Maintenance > Runtime configurations > tab File storage locations > task Switch file storage location type.  New and changed in process flowsA big change in the process flows is the renewal and extension of the file- and folder connectors. The reason is the change from ad-hoc disk connectors to file storage-based connectors.To keep the two apart, the old connectors have been renamed (for example, from Copy file to Copy disk file (non-file storage), and moved to the bottom of the list of available process flow connectors. They should no longer be used if they are not necessarily required. We strongly advice using the new, file-storage based connectors.Thus, renaming the ad-hoc disk connectors has made room for adding new file storage-based connectors. An example is the new Copy file connector, that allows copying files from one storage location to another. If you select this or one of the other new file storage-based connectors, it is mandatory to select the file storage location.New file storage-based connectorsIn addition to the new file and folder connectors, the SMTP connector now also supports file storage to store attachments.Other new process flow actions are:Download file - Make a file available for download to the end-user. The file can originate, for example, from a database, or from file storage using a Read file connector, or it can be the result of a Generate report connector. Zip and Unzip - Process flow actions for zipping and unzipping files and folders. Activate scheduler - Allows users to navigate to a specific date and time inside the scheduler. Activate maps - Allows users to open the Maps component and zoom in on a specific coordinate. Send user notification - send a notification text to a specified user as soon as they are logged in. Note: in IAM, you can send notifications without a system flow in menu Analysis > Notifications > tab Notifications. Encrypt and Decrypt - Store sensitive data in databases with the new Encrypt and Decrypt system flow actions. Indicium will take care of the sensitive data by encrypting them and returning them to be processed afterward.  Other highlightsTime zone setting for users In IAM, it is now possible to set a time zone for a user. In addition: - If you are using the Universal GUI and select a control for a domain with a DateTime value, you can choose whether it should display the time for the user's current time zone or as stored in the database. - If you are using OpenID Connect provisioning, you can add time zone claim mappings for users. Icon repository - It is no longer necessary to download and re-upload icons you already used. By introducing the Icon repository, the icons within a project version can now be selected from the central repository. Performance improvements - The source code generation for program objects has been improved. Program objects are objects such as triggers or defaults, layouts or handler procedures. - Many generation-related subroutines have been improved by reducing CPU pressure on the Software Factory database. - We have added a system flow for `tsf_optimize`. This is a procedure inside the SQLSERVER_DB base project. It can speed up the performance of SQL Server when many indexes are fragmented and statistics outdated. If you would like to use it, you need to add your own schedule for the system flow.

Hello everyone,In this sprint, we solved 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.10 here. Download Web GUI 2022.2.10 here. Minor fixes and tasks [Windows GUI] When opening an invalid URL in the Preview component, the application stopped responding. This has been fixed. Now, an error message is displayed if an URL is invalid. [Web GUI] If a process flow contained multiple Show message process actions, only the first message was displayed. This has been fixed.

Release notes Indicium (2022.2.10)Hello everyone,In this sprint, we have made several error messages more descriptive. Furthermore, we are working hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.In Thinkwise Platform release 2022.2, we have added support for several new features. Some examples are:Support for table, task, and report variants. Automatic provisioning (registration) of users in IAM when signing in through a third-party Identity Provider. Push notifications to the Universal GUI via a new process action. Support for file storage configurations in various file process actions  (read/write/copy/move/delete/list actions on files and folders on Azure File/AWS S3/FTP/File systems). Zip and Unzip process actions. Download file process action.You can read all the details of these features and more in the release notes for Thinkwise Platform version 2022.2. These will be published shortly.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.10 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.10 here.  Contents of this releaseRelease notes Indicium (2022.2.10) About Indicium Breaking Thinkwise Platform support release 2020.2 is ending Indicium HTTP connector error handling More descriptive error messages for conversion errors More descriptive error messages for non-unique primary key and data type mismatch Minor fixes and tasks BreakingThinkwise Platform support release 2020.2 is endingIn accordance with our Lifecycle policy, Indicium support for Thinkwise Platform release 2020.2 is ending. Please upgrade to at least release 2021.1 to use this release of Indicium. IndiciumIf you install this Indicium 2022.2.10 release, you must also install the Universal 2022.2.10 release.HTTP connector error handlingThe HTTP connector has a new return status code:-6 - Unsuccessful (request timed out)The error message when an HTTP header does not contain a Key value is now more descriptive:"The HTTPConnector header has an empty key, which is not allowed. Consult the documentation for the right format."More descriptive error messages for conversion errorsData conversion error messages have been made more descriptive. For example:"The prefilter my_prefilter for table my_table has a value (some value) that does not match the data type." "The variable my_variable for process flow my_process_flow has a value (some value) that does not match the data type." "The column my_col for table my_table has a value (some value) that does not match the data type." "The parameter my_param for task/report my_task/report has a value (some value) that does not match the data type."More descriptive error messages for non-unique primary key and data type mismatchWhen a request containing context filters fails to select a unique record for that context, a new error message is logged containing the table or view in which the error occurred. For example:"The select query for 'my_table' returned more than one record. Validate that the primary key is unique."If Indicium fails to convert column data to the data type specified for that column in the application model, for example, because an expression column returns the wrong type of data, an error message is logged containing the table or view, and column:"The column 'my_col' for table 'my_table' has an invalid value. The column data type might be incorrect."Minor fixes and tasks[Indicium Basic] We fixed an issue where all data types for the SSRS data source were converted to a string. As a result, SSRS reports did not always print correctly.

Hello everyone,In this release, we further simplified the product configuration by adding a button for selecting the correct IAM database. To improve working with the Deployment Center GUI, we have added two new default settings. We also fixed some issues with the dependency checks.Download the Thinkwise Deployment Center 2.3.0 here. New and fixed in this releaseNew (GUI) IAM selection dialog in the Indicium and Windows GUI flows Setting: hide the script variables step Setting: default database name as default value Fixed (GUI) Fixed some issues with dependency checks  New (GUI) IAM selection dialog in the Indicium and Windows GUI flowsIn the Deployment Center's GUI, we have added a Select IAM button to the configuration steps in the Indicium flows (Simple mode) and Windows GUI flows. The button opens a dialog where you can connect to a server and host and select an IAM database. This change further simplifies the product configuration.This is an example of the Select IAM button and dialog in the Indicium configuration (Simple mode):A 'Select IAM' button in the Indicium configuration flow (Simple mode)Note that in a Windows GUI configuration flow, you need to re-select the IAM when (re)loading any of the configuration templates:A 'Select IAM' button in the Windows GUI's configuration flow Setting: hide the script variables stepWhen going through the model synchronization flow for an application, you will be prompted for a database name to be used in the post-synchronization section of the script.This value is optional, and since it might not be used in the post-synchronization section, we have added an option to skip this screen in the Deployment Center GUI. You can set this option using the Flow:ModelSync:Application:HideScriptVariablesStep key in the twdeployerGUI.appsettings.json file.{ "Flow": { "ModelSync": { "Application": { "HideScriptVariablesStep": true } } }} Setting: default database name as default valueWe have added a new setting for using the default database name as default value for the model synchronization script variable. The settting is called Flow:ModelSync:UseDefaultDatabaseName and you can add it to the twdeployerGUI.appsettings.json.{ "Flow": { "ModelSync": { "UseDefaultDatabaseName": true } }}When set to true, the Deployment Center GUI will attempt to use the value of the product's defaultDatabaseName property in the manifest. For example, with the following manifest, the GUI will use MY_APP as the default value for <@db_name,,> in the script variables step. This also works in combination with the HideScriptVariablesStep setting as described above.{ //... "products": [ { "type": "Application", //... "packages": [ { "type": "Install", "path": ".../MY_APP/Install", "defaultDatabaseName": "MY_APP" } ] } ]} Fixed (GUI) Fixed some issues with dependency checksPreviously, the Deployment Center GUI only checked dependencies, such as the compatibility level of the targeted database or server, once per flow execution. So if, for example, the specified compatibility level had not been met, you needed to restart the flow after fixing the issue.We have improved this process in two ways:We have added a Refresh button to the screen for each specified database dependency in the manifest. The dependencies will now be re-checked when switching server or targeted database in one of the previous flow steps.A 'Refresh' button in the Dependency Check 

Hello everyone!We’ve released the following platform improvements this week: IAM 2022.120220627 - Prevent duplicate preview entries when multiple gui applications When multiple GUI applications exist for the same project/project version, this could lead to double rows in the 'Scheduled runs' (preview) tab in the IAM 'Scheduled system flows' screen. This would cause problems in identifying the unique rows in our GUI's. This has now been fixed.

 June 24, 2022:Changed beta release to the full version: 2022.1.17.0 Improvements for issues found in the previous beta release: In right-aligned grid column headers, the asterisk indicating a mandatory field was not visible. This has been fixed. In a grid, group headers were cut off, even if there was enough space. This has been fixed. In a grid, centered column headers jumped to the left when entering edit mode. This has been fixed. When opening a detail tab or switching between parent rows, badges on detail tabs did not refresh instantly but only after the interval period. This has been fixed. When sending an OData request to Indicium, including a primary key value with a date and time, a bad request error occurred. This especially happened when (re)activating a record or saving a newly inserted record that was not in the current set of (pre)filters. This has been fixed. Known issues in this release: During testing, we found that the default editable grid can still behave incorrectly in a detail subject when the entire document is refreshed after changing a record. After changing some values and clicking the next record (which saves the changes), the clicked record may not be activated. We will plan for improvements in this case later.  Hello everyone,In this sprint, we reduced the row height in grids, made grids less flickering while editing, show the numeric keypad on tablets when editing a numeric field, and when adding or editing a row, a document is now marked as 'unsaved'.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.1.17.0 Do 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. This has been fixed. The Universal GUI only works with version 2019.2 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.1.17.0 here  Contents of this releaseUniversal GUI version 2022.1.17.0  Changed Add row and Edit row process actions marked as unsaved Display the numeric keypad on tablets Row height in grids and pivot grids reduced Supported conditional layout conditions Third-party library needed for grids upgraded Minor fixes and tasks What we will be working on next sprintChangedAdd row and Edit row process actions marked as unsavedAs of this version, when performing the actions Add row or Edit row from a process flow, the document is now marked as 'unsaved'. If the user closes this document, they will be prompted to save or cancel the changes.Display the numeric keypad on tabletsOn tablets, the numeric keypad was not visible when editing a numeric field. Now it is.Row height in grids and pivot grids reducedIn compact mode, the row height in grids is reduced from 44px to 36px.The same applies to pivot grids in compact mode and comfortable mode.Supported conditional layout conditionsIn the Universal GUI, the following conditional layout conditions can now also be used:Starts with Does not start with Ends with Does not end with.Third-party library needed for grids upgradedWe upgraded the third-party library needed for grid functionality. This has improved grid performance, made the default editable grid more stable, and made grids less flickering while editing,Also, with this upgrade, the following warning no longer appears in the DevTools Console:"agGrid: getSortModel() is deprecated." Minor fixes and tasks We have fixed many grid alignment issues: The alignment in edit mode versus non-edit mode was different in many cases. This caused the position of fields to change between edit mode and non-edit mode, especially for Combo control values. Right-aligned column headers were left-aligned. Individual cells were not aligned identically with the summary cell. For read-only date, time, and datetime fields in edit mode, the buttons to open a date/time picker were visible while they should be hidden. This has been corrected. When a user was executing a task while a process flow was running, they could get stuck in the running process flow, or spend time filling in task parameters for a task that was not allowed for the selected record. This has been fixed. The task execution now waits for running logic (for example, a stored procedure) to know whether the task execution is allowed or not. When a context procedure was applied when double-clicking a row in a grid, the grid double-click task should wait for the context application logic. However, this was not the case and has been fixed. This is especially important when double-clicking a record that is not selected to decide whether to allow task execution. When opening a subject, the action bar did not always immediately contain the correct buttons, only after switching rows. This has been fixed. In a document that contains unrelated details (for example, two tables with no explicit reference or link to each other), executing a task would refresh the document based on the configurations defined in the Software Factory, except for the unrelated details. Each unrelated detail had to be refreshed manually to reflect the changes. This has been fixed. The whole document is now refreshed when necessary and will show the updated version of each detail. Start objects with a badge did not initially display this badge, only when opened a second time. This has been fixed. When opening a lookup popup a second time, the grid detail tab was opened instead of the form. This has been fixed. When opening a document in one project version from the tiles menu and switching to another project version, the currently open document was reactivated. This has been fixed. Now a new document opens in the correct project version. On tablets, when editing multiple records, the (numeric) values entered for a previous record could temporarily reappear in a later edited record if the same numeric field was empty. This has been fixed. What we will be working on next sprintIn the next sprint, we will be working on: DateTime controls with time zone - This allows DateTime values to always be stored in UTC+0 and displayed to the user in the time zone configured for that user. This will only work in Software Factory platform 2022.2. Vertical tabs - Align your tabs vertically. Variant API - Variants are now more specific in the Indicium API and the Universal GUI will implement this. This will only work in Software Factory platform 2022.2. Make process flow execution more stable - Prevent a process flow from staying active if the user cannot continue the desired steps. Such process flows blocked the execution of subsequent process flows. In progress: Technical research add row in grid.

Hello everyone,In this sprint, we solved 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.1.19 here. Download Web GUI 2022.1.19 here. Minor fixes and tasks [Windows GUI] When a Claim timeout setting for Indicium (Basic) was set in the Software Factory, and the claim expired, the Windows GUI no longer retrieved the data. This problem has been fixed. As of this version, the Windows GUI attempts to renew the claim for the application when a claim expires. [Windows GUI] When connected via Indicium (basic), the Windows GUI did not terminate the user log sessions correctly, leaving claims active. This has been fixed.

Hello everyone,In this sprint, we changed the message on the logout page to show the user's first and last name, and you can now remove the 'Stay signed in' option on the Indicium login page. Furthermore, we are working hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.You can read more about Indicium's features in the Indicium user manual .We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.20 here. Download Indicium Basic release 2022.1.20 here.Contents of this releaseIndicium Universal Show the user's first and last name when logging out Remove 'Stay signed in' option on login page Indicium UniversalShow the user's first and last name when logging outWhen a user was logged in, the Indicium landing and logout page showed a message like:"You are logged in as: <usr_id>".Since a user ID can be a non-descript GUID or another type of unintelligible identifier, this message has now been changed to:"You are logged in as: <first_name> <last_name>".This message is only visible to a user after logging in. For development and testing purposes, the tooltip still shows the user ID. This allows developers to distinguish between different test users, which could all be named "Test Test".Example of a logout page (fragment)Remove 'Stay signed in' option on login pageYou can remove the 'Stay signed in' option from the Indicium login page by adding the following JSON property to the appsettings.json file."LoginOptions": { "AllowStaySignedIn": false}When the AllowStaySignedIn property (default: true) is set to false, the 'Stay signed in' option is removed. It will also cause the ‘Remember my choice’ option to be removed when there are multiple login options available, for example when OpenID providers are configured.

Hello everyone!We’ve released the following platform improvements this week: SF 2021.1 and up 20220601 - Fixed sorting of icon columns in i_ui menu views Due to the listing of icon columns in the menu item views that the Universal GUI uses to show the menu, it was possible that menu items were showing a different icon than intended. This has been fixed.  SF 2022.120220603 - Fill reachable object tables upon syncing Due to an oversight, reachable objects were not calculated before syncing projects to IAM. This has been fixed.

June 3, 2022:Changed beta release to the full version: 2022.1.16.0 Improvements for issues found in the previous beta release: When a record was edited by a process flow and the subject was closed at the same time, an error message appeared unnecessarily: "Request error: The object was not found. You may have insufficient rights or the object no longer exists" This has been fixed. In the beta release, we improved the style of the task buttons in the toolbar. As a result, the toolbar was not always the correct size, and the task buttons could continuously change size while editing the subject or executing a task. This has been fixed.  Hello everyone,In this sprint, we fixed several issues, and we added two configuration settings to config.json. When searching on a tablet or touchscreen, these settings prevent that after each keystroke, search results are updated immediately. Furthermore, toolbar buttons have been slightly enlarged.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.1.16.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 2019.2 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.1.16.0 here Contents of this releaseUniversal GUI version 2022.1.16.0 Changed Configurable debounce time Enlarged toolbar buttons Minor fixes and tasks What we will be working on next sprintChangedConfigurable debounce timeWhen you type into the search field, the search starts a moment after each keystroke if no new keystroke occurs. This is called the debounce time. The default value of this debounce time is considered too short when typing on a tablet or touchscreen, resulting in search results being updated after each keystroke.Therefore, this debounce time can now be configured in the config.json file. Also, the default debounce time has been doubled for mobile devices, as typing on a touch keyboard is much slower.New settings for config.json are:searchDebounceTime - in ms, with a default value of 300 ms and a minimum value of 300 ms. searchDebounceTimeMobile - in ms, with a default value of 600 ms and a minimum value of 300 ms.Enlarged toolbar buttonsToolbar buttons with both an icon and text appeared too close together. They are now slightly enlarged, and there is more space between them. Also, the color has been changed for clarity when hovering.Resized toolbar buttonsMinor fixes and tasksIf a task start object or report start object was not included in the menu, it would not open at startup. This has been fixed. When leaving a field with a default setting to fill another field, the default value was filled in correctly, but the default value was not selected. Instead, the mouse cursor was placed right after the default value. This has been fixed. When tabbing through an editable grid, the dropdown lists of combo boxes could not be opened with a keyboard shortcut. This has been fixed. When zooming in on a screen until the menu on the left-hand side was hidden and then zooming out again, the menu remained hidden. This has been fixed. When adding a new parent record, incorrect child records were shown in the detail tab in some cases. This has been fixed. Now, when adding a parent record, only unrelated details will be displayed.  In some cases, when opening a subject with a default editable grid, the application could stop responding with a message: "Cannot read "allowUpdate" of undefined". This could especially occur when two or more grids were loaded and displayed at the same time. This has been fixed. What we will be working on next sprintIn the next sprint, we will mainly focus on fixing known issues. Furthermore, we will be working on:DateTime controls with time zone - This allows DateTime values to always be stored in UTC+0 and displayed to the user in the time zone configured for that user. This will only work in Software Factory platform 2022.2. Grid edit mode flashing - To reduce this, we need to upgrade a third-party library. Technical design for asynchronous editing in a grid - To improve the performance of the grid edit mode, we plan to have multiple records in edit mode behind the scenes. This allows the user to continue while the records are saved in the background. In this sprint, we will start with a design. In progress: Variant API - This will only work in Software Factory platform 2022.2. UI/UX Drag and drop. UI/UX Design Vertical tabs.

Hello everyone,In this sprint, we worked hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.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.1.18.0 here. Download Web GUI 2022.1.18.0 here. 

Hello everyone,In this sprint, we solved some issues. Furthermore, we are working hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.1.19 here. Download Indicium Basic release 2021.1.19 here.Contents of this releaseMinor fixes and tasksMinor fixes and tasksThe (legacy) DB2 iSeries driver can throw errors on SQL statements that are valid but where comment text is incorrectly treated as SQL, for example when a comment contains a question mark. However, the application connector did not handle this as an error, resulting in DB2 iSeries driver error messages that were not passed through. The application connector now correctly handles the DB2 iSeries error as an error. Note: The IBM DB2 .NET CORE driver does not have this issue and does not consider comments in SQL statements.

Hi everyone,The 2022.2 release of the Thinkwise platform is just around the corner, and it is packed with great new features and improvements such as handler procedures, notifications, time zone support, OpenID user provisioning, performance optimizations, and many new and improved process flow actions, for example for zipping, encryption and file storage handling.This release was originally planned for the end of June, but unfortunately we need one more sprint to dot the i's and cross the t's. As a result, the release will now be generally available in mid-July.If this impedes with any of your plans, please contact us to see how we can be of assistance.

Hello everyone!We’ve released the following platform improvements this week: SF 2021.3 and up20220509 - DB2 updated sf_product_info insert When installing or upgrading a DB2 end product, the insert into sf_product_info used a timestamp without a format. This led to problems, which now have been corrected.  

May 13, 2022:Changed beta release to the full version: 2022.1.15.0 Improvements for issues found in the previous beta release: In a specific case, when a subject was opened from a process flow step and this process flow activated a filter simultaneously while loading, parts of the subject appeared empty, or showed unrelated data. This has been fixed. In some components, for example, the Resource Scheduler and the Maps component, user interface styling was not applied correctly. This has been fixed. When opening (for example) the User Preferences menu while an auto-refresh screen was open, the application stopped responding. This has been fixed.  Hello everyone,In this sprint, we made a number of changes and improvements and fixed some issues. One important change is that process flows are now disabled by default in a lookup popup or context. To enable process flows, you can use an extended property. You can read more about the other changes, improvements, and fixes in the topics below.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.1.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 2019.2 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.1.15.0 hereContents of this releaseUniversal GUI version 2022.1.15.0 Changed Process flows by default disabled in lookup popup or context Pivot grid improvements and changes Improved performance: layout calculated based on model settings Improved (grid) performance Tooltips more legible Minor fixes and tasks What we will be working on next sprintChangedProcess flows by default disabled in lookup popup or contextDue to some issues with process flow execution from within a popup of a lookup field, the process flows are no longer executed by default within a lookup popup or context. Similar to our other interfaces, they now listen to the extended property AllowProcessFlowsInLookupDialogs. We will solve the known issues later on.Pivot grid improvements and changesIn this sprint, we have improved the pivot grid in several ways:The look and feel have been improved. When expanding a category (row), the total will be shown in the parent row. We have added nested series (columns) for all aggregation types. Previously, when a cube view had multiple series (columns) and the values were not of type 'SUM', the pivot would not start. We have added nested groups for all aggregation types. Previously, when a cube view had multiple categories (rows) and the values were not of type 'SUM', the pivot would not start.Another change is that nested series (columns) are always expanded in this release, though collapse and expand will be available again in a future release. Previously, if conditions were met, these were expandable and collapsible. The main reason for this is a necessary technical overhaul that will pave the way for future improvements:series (columns) subtotals series (columns) grand totals expand and collapse series (columns) category (row) grand totals default expanded series/categories. Improved look and feel in the pivot gridImproved performance: layout calculated based on model settingsPreviously, the Universal GUI would request Indicium to get the model's layout settings. Now, it can calculate the model layout settings itself, so the request to Indicium is no longer necessary.So, if you deselect the logic concept Layout in a subject's settings, the Universal GUI will now use the model settings instead of executing the layout's stored procedure. This setting is available in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab Performance > group Use concept > checkbox Layout.This can slightly speed up the performance when switching a row, editing, and opening a screen.Improved (grid) performanceWe made several (grid) performance improvements. In the coming sprints we will continue to focus on more performance improvements.Tooltips more legiblePreviously, a tooltip appeared below an element when a user hovered over it. Sometimes this would cause the cursor to cover part of the text, making it partially unreadable. This has been fixed by changing the placement of the tooltip. Now it appears above an element when the user hovers over it.Minor fixes and tasksOn mobile devices, when selecting multiple rows in a grid, the checkbox to select all rows was horizontally not aligned with the checkboxes for the individual rows. This has been fixed. When typing a value in a filter field on a tablet, the extended touch keyboard pushed the filter component away from the screen and reverted the typed value. This has been fixed. Now the filter component in a document claims at least the height of a single control, so the filter fields always remain visible. Opening a lookup while no record was selected resulted in a Bad Request error. This has been fixed. If the preview component cannot generate a preview for a file, it now displays the message No preview is available. Fixes for file upload: Uploading a file in edit mode was only possible by clicking the icon, not the bar itself. This has been fixed. When you select a file in a form in edit mode, you can now click the upload control or press Enter to open the file selector and easily overwrite the previously selected file. The cursor now changes to a 'pointer' icon when you hover over the field, in both edit and read mode, since the text cannot be edited. When a user switched tabs in a resource scheduler component and returned to the first tab, the years and weeks were no longer displayed. This has been fixed, they remain visible now. A right-aligned control in an editable grid got too much padding at the left, so it got cut off at the right. This has been fixed. When saving an edited record in the grid with validation errors, the grid row height reserved some room for a validation error that did not come. As a result, some types of controls did not align properly. The height now remains the same. Auto-refresh would stop working after a record in its subject was edited. This has been fixed. After filtering the data set, the Change detection logic is now prevented from firing more often than required. We have fixed that a date value sometimes was not processed when directly executing a task after filling in a date. If the tiles menu is the default menu for an application, and the last open document was closed by a process flow, the Universal GUI showed an empty screen. It only contained the backplate and no tiles menu. This has been fixed, the tiles menu now is displayed as it is supposed to be. When switching fast between records and clicking edit, the wrong record would be edited. This has been fixed.What we will be working on next sprintIn the next sprint, we will mainly focus on fixing known issues. Furthermore, we will be working on:Pivot column subtotals - Subtotals on the columns and series of the pivot. Suggested GUI Action: Download file. (grid) performance research. In progress: UI/UX design for add row. UI/UX design for vertical tab pages.

Hello everyone,In this sprint, we added the possibility to disable the automatic password filling on the Login page. Also, cubes can now show the cube title in the active graph.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.1.17 here. Download Web GUI 2022.1.17 here.NewDisable automatic password filling on Login page[Web GUI] Login passwords used to be automatically filled in for users who had their passwords saved in their browsers. As of this version, the application manager can disable this behavior by setting the new parameter AutoFillPassword with the default value true to false in the settings.ini configuration file.Add cube title to active graphIt is now possible to show the cube title in the active graph by adding the extended property ShowTitleActiveChart and setting it to true.Minor fixes and tasks[Web GUI] A look-up control displaying suggestions did not get the focus until it was clicked twice. Only then you could start typing. This has been fixed.

Hello everyone,In this sprint, we have added new settings for OpenID Identity Providers and solved some issues. Furthermore, we are working hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.18 here. ContentsIndicium Universal New settings for OpenID Identity Providers Minor fixes and tasks  Indicium Universal New settings for OpenID Identity Providers IncludeProfileScope - Indicium default requests the openid and profile scopes for external Identity Providers. However, not all Identity Providers support the profile scope. We have, therefore, introduced a new setting: IncludeProfileScope. You can add it to the appsettings.json file with the value false to prevent Indicium from requesting the profile scope. PromptLogin - Indicium already supported the AlwaysPromptLogin setting, but this only allowed you to specify true in order for Indicium to use the "login" prompt. The new PromptLogin setting allows you to specify a string, for example, select_account, to use any prompt setting supported by the Identity Provider.NoteAs of platform version 2022.2, the settings for external Identity Providers will be available in IAM. Minor fixes and tasksIndicium did not supply a file name hint to the browser for previewed files. As a result, when saving a file from the PDF previewer in the Universal GUI, it would use a part of the URL as the file name. This has been fixed. We have fixed a performance issue that occurred on process flows that required interaction with the Universal GUI when using an SF meta source (i.e., /sf/appl instead of /iam/appl). The issue could cause a delay of several seconds on every action that required communication with the Universal GUI. System flow actions were not affected.

April 22, 2022:Changed beta release to the full version: 2022.1.14 Improvements for issues found in the previous beta release: When opening one of some specific screens after opening another screen, the specific screen was correctly listed in the OPEN DOCUMENTS section, but it did not show any content. This has been fixed. Hello everyone,In this sprint, we made it possible to open multiple instances of the same subject by Ctrl-clicking the corresponding menu item. Double-clicking a detail tab opens a new document zooming in on the detail. Furthermore, we added two configuration settings to improve grid performance. And splitter positions are now retained after refreshing the Universal GUI.More new functionality and improvements are listed below.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.1.14Do 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 2019.2 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.1.14 here Contents of this releaseUniversal GUI version 2022.1.14 New Open a subject twice through Ctrl-clicking Double-click a detail tab to open a new document and zoom in on the detail Splitter positions retained after refreshing the Universal GUI Changed New configuration settings for grid performance Overflow menu changes Minor fixes and tasks What we will be working on next sprintNewOpen a subject twice through Ctrl-clickingYou can now open multiple instances of the same subject by holding CTRL and clicking the corresponding menu item.Double-click a detail tab to open a new document and zoom in on the detailYou can now double-click a detail tab to open a new document and zoom in on the detail. This does not apply to mobile devices as there is no double click functionality.Splitter positions retained after refreshing the Universal GUISplitter positions were retained after closing and reopening a subject but disappeared when refreshing the Universal GUI. As of this version, the splitter positions are also retained after a refresh.ChangedNew configuration settings for grid performanceWe have added two configuration settings to improve grid performance. These settings can be useful for applications running on mobile devices with low hardware specifications. Record changes and scrolling appear to be slow on such mobile devices. We added two config.json options: gridDisableRowSwitchDebounce and gridRowBuffer.gridDisableRowSwitchDebounce: true | false | mobile. Default = falseWhen set to true or mobile while working on a mobile device, the first record change will be processed immediately instead of waiting for the 300ms debounce timeout. Any subsequent record changes will still be debounced.gridRowBuffer: any number. Default = 10The gridRowBuffer property sets the number of rows the grid displays outside the visible area. The default is 10. For example, if a grid shows 30 rows (the number of rows that fits on your screen without scrolling), the grid will render 50 rows in total (10 extra rows before and 10 extra rows after). When scrolling, 10 rows can immediately be displayed, so the user will not see any redraw.Setting a low row buffer makes the initial loading of the grid faster (for example, when data is first loaded, or after filtering or grouping). Setting a high row buffer will reduce the visible vertical scrolling of the redraw.Overflow menu changesIn the overflow menu of the search and filter bar, when users are not allowed to filter, the Quick filter and Clear all filters options were read-only. This has changed. As of this version, these buttons are hidden. In addition, if a subject does not contain any prefilters, filters, or sorting, the overflow menu in the search and filter bar will be hidden.Minor fixes and tasksIn some cases, when a user opened a document containing a map component, no base layer was selected. Now a default base layer is selected. Cubes did not filter on values entered in a filter form field. This has been fixed. For look-ups with Def. control set to 'Combo (sorted)', the look-up control was still sorted alphabetically instead of according to the default sorting of the look-up subject. This happened in some cases if there were multiple sorting columns. When a user created a lookup value with an ID of '0', the lookup would only be visible in edit mode. The '0' would become invisible again when the user exits edit mode. This has been fixed. Deleting a record in a detail tab would sometimes change the parent's active record. This has been fixed. Recently we implemented task bars as a screen component. The task bar component is removed from the screen if it is directly below the default action bar. Otherwise, you would see two bars directly below each other. However, the task bar was not removed if it was on a tab. This has been fixed. If the task bar is elsewhere on the tab, its buttons will be correctly removed from the default action bar. In a specific case, some action bar buttons were displayed over the nearby task or report buttons, especially the Refresh and Delete buttons. This has been fixed. After dragging the cursor outside the browser window while moving a splitter, the application temporarily stopped responding. This has been fixed. In fields with the Image Combo domain, the images were not correctly colored when viewed (read) in dark mode. This has been fixed. If a chart showed a total number of objects and there were none, the tooltip would show Undefined instead of 0. This has been fixed. When opening a page with the Hide main action bar setting enabled and then reopening a page with this setting disabled, the action bar was still hidden. This has been fixed. When editing in a grid, numeric columns could not be left-aligned. This has been fixed. When adding a record in a detail subject, all data was intentionally refreshed, but a Bad Request error could also occur. This has been fixed. Look-ups based on an unauthorized look-up column did not refresh automatically. This has been fixed. Indicium now correctly instructs the Universal GUI to refresh the look-up column. In the previous version, the preview component did not support the file formats .txt, .xml, and .json. Now, these file formats are supported again. If a document was open and a process flow action Open document with input parameter open_doc_existing_yes would switch to this document, the process flow would not continue. This has been fixed. When a document was first opened, detail tiles were not visible in some cases. This has been fixed. For this fix, you must also install the Indicium 2022.1.17 release: When signing out from the Universal GUI while connected via an OpenID connection (by a third party authentication provider), the user was not redirected to the correct logout page (see below) that provides the option to sign out, either from Indicium only or sign out from the third party authentication provider. Instead, the user stayed logged in. This has been fixed. Now the correct sign-out dialog is displayed. Signing out from the third-party authentication provider also signs out from other applications connected via OpenID in the same browser session. Signing out from the Universal GUI with an OpenID connectionWhat we will be working on next sprintThe next sprint we will be working on:Improving grid performance In progress: UI/UX designs for cube panel and add row in grid.

Hello everyone,In this sprint, we solved 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.1.16 here. Download Web GUI 2022.1.16 here.Minor fixes and tasks(Web GUI) In a screen with a default editable autosaved detail tab, when making changes and then immediately selecting another row in the parent grid, the changes were saved but the row was not selected. This has been fixed. (Web GUI) When editing in a grid with multiple drop-down columns, only the first column showed the correct data. Any subsequent drop-down list was empty. This has been fixed. All drop-down lists are now correctly updated. (Web GUI and Windows GUI) After an upgrade to Thinkwise Platform release 2022.1, detail tile icons were not displayed correctly. This has been fixed. (Windows GUI) When executing a task for multiple rows with the Popup for each row setting enabled, task parameter values in drop-down lists were not updated after each task run. This mainly happened when executing the task using the Ctrl + Enter keyboard shortcut. This has been fixed. (Windows GUI) If HTTP URLs were redirected to HTTPS URLs in IIS, the OAuth connector would fail. This has been fixed.