Product Updates

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.

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.