Product Updates

Hello everyone!We’ve released the following hotfixes this week:SF 2021.320211216 - Fix unit test system flow duplicate result parameters A select statement in the code may cause duplicate result parameter records. This situation led to an error in the unit test system flow without notice. The duplicate records will now be deleted and an assertion error message will be shown as the result of the unit test to prevent false positive unit tests runs.

December 17, 2021:Changed beta release to full version: 2021.3.14. Added fix: We fixed that process flows sometimes crashed on continue.Hello everyone,In this sprint, we have added, among other things, support for zoom levels in Maps, improved the look-up popups, and added a shortcut for opening a look-up from the grid. And you can now hide the Remember me option from the login screen.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 2021.3.14Like with every blog, we have released a version to test the Universal GUI out for yourself. 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. 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 2021.3.14 here Contents of this releaseUniversal GUI version 2021.3.14 Changed The confirmation of tasks can now show the value of hidden task parameters Resetting the dataset will spin the refresh icon in the toolbar New Support for Zoom level in Maps Improved look-ups New setting to hide "Remember me" option from the login page Improved loading performance of model icons by caching them Minor fixes and tasks What we will be working on next sprint Changed The confirmation of tasks can now show the value of hidden task parametersAs of this release, confirmation messages can show the value of hidden task parameters since Indicium now handles the translation for the Universal GUI.This change makes this Universal GUI version only compatible with the latest Indicium version: 2021.3.16. Resetting the dataset will spin the refresh icon in the toolbarNow, after resetting the dataset, the Refresh icon will spin in the toolbar to indicate that the Universal GUI is processing the change. The dataset is reset when you apply a filter or prefilter or change the sorting. New Support for Zoom level in MapsThe Universal GUI now supports the initial Zoom Level for Maps in the Software Factory.At the moment, only a zoom level with a value between 2 and 19 is supported. A value higher than 19 (for example, 23) will be set to 19. A value lower than 2 (for example, 1) will be set to 2. Improved look-upsNow, you can use the Ctrl+Alt+P shortcut to open the look-up for the selected field in a grid in a non-editable subject. Note that this shortcut only works when the focus is on the grid component. Alternatively, you can use the "Show look-up" options from the toolbar.After opening, we have improved the look-up popup in cases where the requested record does not exist in the current data set when it is opened. The Universal GUI validates whether the record is available. If so, the set is filtered, without prefilters, to show it. If not, a snack bar message will inform you something else is selected: "The desired data cannot be found because of the active filters."Note: this is only available when you open a look-up popup from a non-editable editor. When editable, we expect that you open the popup to select something else.Related to this, a look-up will now activate a tab with a grid (or card list) if the parent is editable. This allows you to pick a different record. If the parent is not editable, it will activate a tab with a form to show more details about the current value.When the record is filtered out after adding/editing it inside the look-up popup, you will get a message with the question to open it in a new document to continue working on it: "The just saved data cannot be displayed on this screen because of active filters. Would you like to open it in the background?". New setting to hide "Remember me" option from the login pageYou can now configure the Universal GUI to hide the "Remember me" option from the login page by adding "loginRememberMeHidden": true, to the config.json. This option allows users to remain logged in for 14 days instead of 30 minutes. Remaining logged in is not always desired, for example, when tablets are shared between multiple users. Improved loading performance of model icons by caching themWe are now fetching icons from the i_ui_views of the meta model in a different way so the browser can cache them. This has resulted in slight performance improvements when, for example, logging in or opening a screen for the second time in the same browser instance. Minor fixes and tasksWe fixed that the Universal GUI would crash when opening a startup document that had never been opened in a process flow. When uploading a file that is not whitelisted as a file extension, for example, a .png file while only .jpg is whitelisted, the Universal GUI displayed "Stage patch failed. Error: bad_request". It also crashed sometimes. The crash has been fixed, and we now display "The used file extension, .png, is not allowed, only the following file extensions are allowed: '.jpg" instead of the technical error message above. We fixed that, after editing, a date field changed spontaneously due to the browser's time zone. Deleting records in details will no longer result in a progress popup that freezes the GUI. The previewer is now also refreshed after a document or subject is refreshed manually from the toolbar. A Refresh document process flow action in a detail no longer crashes the Universal GUI. The Maps component no longer crashes on invalid data. Previously, when the user was on a tab with a grid, the Universal GUI would wrongfully switch to a form tab. Now, if Edit is allowed in the grid, it will stay on the grid tab (menu User interface > Subjects > tab Settings). This makes more sense because the user already has an editable component available, so there is no need to switch to a Form tab. We fixed that process flows sometimes crashed on continue. What we will be working on next sprintThe next sprint we will be working on:Export using grid columns - Exports just the visible columns in the grid. If no grid is available, all columns will be exported. Task popup for each row - When multiple rows are selected, a task popup is available for each row. Form list - We will also work on a POC (proof of concept) for the form list. General maintenance.

Hello everyone,In this sprint, we have added support for double-clicking a task in screen types that contain a tree. In addition, you can now link a task to deleting an appointment in the Resource Scheduler. We have also solved a lot of 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 2021.3.17 here. Download Web GUI 2021.3.17 here. New Double-click task support for tree screen types(Windows & Web GUI) As of this version, it is possible to add a double-click task to screen types that contain a tree. Resource Scheduler: new extended property for a task after deleting an appointment(Windows & Web GUI) In the Resource Scheduler, it was already possible to link tasks to actions, for example, double-clicking, moving, or resizing an appointment.You can now also link a task that has to be executed when an appointment is deleted with the Delete key, with the new extended property DeleteAppointmentTaskScheduler. For example:DeleteAppointmentTaskScheduler = "scheduler_delete_appointment". Minor fixes and tasks(Windows GUI) For images that were uploaded using the AWS file storage system, the file name was displayed instead of the image. This has been fixed. Now, image uploads via AWS appear as images in both the grid and the form. (Windows GUI) We have fixed a bug in the OAuth connector that resulted in a blank login screen. Also, we have added some extra debug logging for the OAuth connector. You can find these log messages in the Debug screen (Developer ribbon). (Windows GUI) Previously, when the value of a variable contained more than 43,500 characters, the Windows GUI showed a blank value in the Process flow monitor (Developer ribbon). Now, it shows a notification that the value is too long. You can copy the value to the clipboard by double-clicking on the text box. (Windows GUI) When a group header contained only one visible column, and this column was hidden using the User Preferences ribbon in your end-application (Subject configuration > Grid), the column was removed, but the group header remained, along with a dummy empty column underneath it. This has been fixed. Now, the entire group header is removed when no underlying columns are visible. (Windows GUI with Indicium (Basic)) We fixed a look-up with suggestion control that resulted in a query error. (Windows & Web GUI) If the name of an uploaded file already existed in the AWS file storage, the file was replaced. This has been fixed. Now, the name will be made unique automatically. (Windows & Web GUI) Now, the maximum value that can be set in the Software Factory domains will be enforced in the Windows and Web GUI. (Web GUI) In a task form, when a file upload field was filled by a default stored procedure, a form refresh would clear the field. This has been fixed. (Web GUI) Previously, when inserting the first record into a grid, the look-up dialog would not show when it was openend from the context menu or CTRL+L. This problem has been fixed. (Web GUI) Now, the Web GUI will ask the client to refresh the GUI to prevent that a timeout occurs. (Web GUI) We have fixed a bug in the DevExpress reports error logging that caused high CPU usage in Azure environments. This bug occurred when a report could not find any row in its source tables.

Hello everyone,In this sprint, we have added support for deep-linking in a process flow, so you can use values from variables to start a process flow. We have also updated the DevExpress Reporting library and changed the OpenID behavior when signing in and out.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.3.16 here. Contents of this releaseBreaking Invalid input parameters values will now stop the process flow in Indicium Universal Indicium Universal Deep link support for process flows Changes Update DevExpress Reports Changed OpenID behaviour Minor fixes and tasks  Breaking Invalid input parameters values will now stop the process flow in Indicium UniversalFrom now on, process flows will stop when the data types of an input parameter and the process variable do not match.When this happened in previous versions, Indicium would continue with a null value since it could not convert the value into the expected data type. This could result in unwanted or unexpected behavior.Now, when a process variable has datatype varchar(12), its default value is "Hello Indicium", and it's passed to an input parameter that expects an Int, it will result in an exception. Indicium Universal Deep link support for process flowsIf deep-linking is enabled in a process flow, you can now post process flow variables with their values to start the process flow with those values. Previously, these values had to be set with a task. This feature will be available as of IAM version 2022.1. Changes Update DevExpress ReportsIn this version of Indicium, the DevExpress Reporting library is updated to a newer version (21.1.6). Changed OpenID behaviourWe changed the behavior of Indicium when signing in and out.In the appsettings.json, we added a new property to OpenIDConnect named AlwaysPromptLogin. This is a boolean field, its value by default is false.When it is set to true and you sign in using that OpenID Provider, the login screen will always appear.If the specified OpenID is the only login option available and the value of AlwaysPromptLogin is false, Indicium will automatically log you out when pressing the button to go to the logout page.Also, if logging in with local accounts is disabled, then the logout button for local accounts will no longer be available. Minor fixes and tasksWe fixed the issue that the uploaded files of a staged resource were deleted when a commit failed. Now they will remain in the temp folder until the staged resource is committed or canceled. When staging a task or report in the context of a table, Indicium will now copy all parameter values that have been linked from the table context row. Previously, file columns linked in this way did not provide a download link for the file. This made it impossible for clients to show, for example, image previews since they did not receive a file from the link in the staged resource response.

Hello everyone!We’ve released the following hotfixes this week:SF 2021.320211202 - Ensure last agent check in only has one record When multiple instances of Indicium were present, it would in rare occasions occur that the table logging Indicium's last check-in contained multiple records. This would lead to an error in the creation screens, and has therefore been fixed. 20211130 - Function to get linked objects optimizations Due to some optimizations in the get_linked_objects function, it is now possible again to export your SF or IAM 2021.3 database from an Azure environment. IAM - All supported versions20211202 - i_ui views performance optimizations​​​​​ This service update provides optimizations that improve the performance for 3 i_ui views: i_ui_col_form, i_ui_task_parmtr and i_ui_report_parmtr. When starting an end product created with the Thinkwise Platform, the model must be loaded. For the Universal GUI, this is done by using so-called i_ui views. These views load the data in the most efficient way, which is a challenge because the model and amount of data can differ enormously per customer. We always strive to offer a solution that works as well as possible for everyone.

Hi everyone!We’ve released the following hotfixes this week:SF 2021.320211123 - Correction to sort Unit test data properly In rare occasions it would be possible that Unit test data was incorrectly sorted, causing the data to be inserted into the wrong column. This has been fixed. 20211124 - Corrections in creation process In some occasions the Execute source code log would show the incorrect message in the Log screen. This has been resolved and now all returned messages are shown. The Complete creation task would show an informational message about it being queued after a job the task created. This has been fixed and the task will only show the message once the first job is queued after another job. IAM 2021.320211123 - Validation tree refresh frequency In the 2021.3 version of the SF, jobs are no longer performed by a client (the GUI) but instead by Indicium. To keep track of the progress, the creation screens are periodically auto refreshed. This means that the data in the screen must be retrieved again.  This also applies to the validation screen. When a large amount of validation messages were unsolved, it could occur that not all data was retrieved before the next auto refresh. The screen could then not be used properly.  We now changed the frequency of the auto refresh in IAM. As a result, you will be kept informed less regularly about the progress during validation. However, this does solve any performance issues you might experience. Of course, this optimization for dealing with a large amount validation messages, does not change anything in our advice to always solve your validations. Hope you all enjoy your weekend!

November 26, 2021:Full release from version 2021.3.13 BETA. Hotfixes: We fixed two bugs that caused the Universal GUI to crash when the session had expired or the user had logged out. We fixed errors that occurred when a task deleted the current record.  Hello everyone,In this sprint, we added support for showing messages thrown from the Badge logic and we now support the lookup control type 'Combo (sorted)'. We also improved some features, like the form's HTML editor, and fixed some issues.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. Contents of this releaseUniversal GUI version 2021.3.13 Changed Tasks marked as "double click" hidden in the toolbar Process flow continues in the last document when the follow-up action says so New Messages from the Badge logic Support for 'Combo (sorted)' HTML edit / non-edit popup Minor fixes and tasks What we will be working on next sprint Universal GUI version 2021.3.13Like with every blog, we have released a version to test the Universal GUI out for yourself. 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 it should be an allowed origin in the 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 2021.3.13 here Changed Tasks marked as "double click" hidden in the toolbarTasks marked as ‘double click’ are hidden in the toolbar now. This setting is available in the menu Processes > Tasks > tab Table tasks > tab Form. Process flow continues in the last document when the follow-up action says soWe made process flows a little smarter when running outside the context of a document, e.g., when running a task from the menu. When the follow-up action points to a subject, it tries to find it in the last involved open document of the flow.This is helpful when running a task that should not be accessible from the document's toolbar. The task can be executed globally filled by process variables, and afterward, the flow can continue in the active document.We strongly advise you to thoroughly test your process flows if they contain one of the following actions:add / copy / edit / delete task / report execution open / activate / close document zoom detail. New Messages from the Badge logicLike the other GUIs, the Universal GUI now shows messages thrown from the Badge logic.Notice that the badge may be displayed multiple times and run again after a certain interval. As a Software Factory developer, you are responsible for preventing messages from popping up multiple times. Support for 'Combo (sorted)'Universal GUI now supports the lookup control type 'Combo (sorted)', so you can configure a combo in another way than just alphabetically.This setting is available in menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > field Def. control.Note that:Some more complicated combinations of sort fields, like a domain element with values followed by another sort on a lookup field, are not yet available. This lookup control type is not yet available for lookup controls in the filter form. HTML edit / non-edit popupWe have improved the form's HTML editor. It is now possible to show and edit the formatted document in a larger popup.You can click on the new icon to open the popup for editing HTML in edit mode. The formatting toolbar (to make text, for example, bold) has also been moved to the popup. In the form editor, you can still edit the text in the currently applied format. In both the popup and form editor, you can use the shortkeys for formatting.In non-edit mode, you can use the popup to inspect the contents in a larger display.This was the previous HTML editor, with the formatting toolbar:Previous HTML editor with formatting toolbarNow, the formatting toolbar has been removed, and a popup icon has been added:New editor without the formatting toolbar, but with a popup iconThe new popup in edit mode now contains the formatting toolbar:The new popup editor in edit mode, with formatting toolbarThis is the new popup in non-edit mode (read-only):The new popup editor in non-edit mode (read-only, no formatting toolbar)This is only the first release of this feature. For future releases, we have planned:To replace the Close button with Save/Cancel buttons. Now, after opening the popup while editing, changes made to the HTML text are always synchronized. Later on, the Cancel button should provide the option to ignore them. To improve the styling of the formatting toolbar. We wish to apply equal padding at the top and bottom and add a border between the buttons and content. To solve a known issue, which has been in the Universal GUI for a couple of releases. At the moment, scrolling in the HTML control of the form in edit mode is not possible with the scroll wheel. Manually grabbing the scrollbar still works. We will plan this as a separate issue. Minor fixes and tasksMessages from a process flow now show parameter values. In some cases, a type error 'Cannot read properties of undefined (reading 'applications')' occurred when the login token had expired. This has been fixed. When adding a record in a task was followed by a Go to row process action, the new record was not selected. This has been fixed. The controls for the Cortex and regular barcode scanners used to lose focus when the scan button was still loading. This has been fixed. The input now retains the focus. We fixed two bugs that caused the Universal GUI to crash when the session had expired or the user had logged out. These bugs made the GUI unusable with a `reading properties of undefined` error that kept recurring. We are working on a final fix to prevent these types of errors when logging out. That final fix will be available next release. For now, the Universal GUI will no longer become unusable when such an error occurs. We fixed errors that occurred when a task deleted the current record. What we will be working on next sprintThe next sprint we will be working on:Record not found on lookup open - When a look-up popup is opened and the selected record is not in the current filtered set, it should try to fetch the record by removing all the pre-filters. Lookup from grid Ctrl+Alt+P shortcut - Open the look-up for the currently selected field in the grid with the Ctrl+Alt+P shortcut. Form list design Automated testing General maintenance.

Hello everyone,In this sprint we have updated the DevExpress Report Designer, and we have 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 2021.3.16 here. Download Web GUI 2021.3.16 here. New DevExpress Report Designer updated to Devexpress version 21.1.6 (Windows GUI & Web GUI)The DevExpress Report Designer has been updated to DevExpress version 21.1.6. Version 1.50 from the Devexpress Report Designer can now be downloaded. Double-click task support (Windows GUI & Web GUI)We have added formal double-click task support to the Windows and Web GUIs. This concerns task execution by clicking twice on a row.The formal setting is available in the menu Processes > Tasks > tab Table tasks > tab Form > checkbox Grid double click. It has been part of the Software Factory since the 2021.2 release, and that release has already upgraded all double-click extenders to the formal model.Therefore, we no longer support the double-click extenders set in the menu Projects > Full model > Extender. If you have made changes to the double-click extenders since the 2021.2 release, please update the formal model so that all functionality remains the same. Minor fixes and tasks(Windows GUI) We fixed an issue regarding auto-refresh. Previously, when you had auto-refreshes in child subjects and switched to a new subject, the old auto-refresh would persist. This resulted in unnecessary refreshes that negatively impacted the user experience. (Windows GUI & Web GUI) We have fixed a DevExpress report export bug caused by a missing required DevExpress DLL. Released as hotfix(Windows GUI) When entering values in the zoom editor of a text field with the Multiline control, the changes were lost when the zoom editor was closed. This has been fixed, and the changes are now also updated in the form field once the zoom editor popup has been closed.

 Hello everyone,It has been a while since the Thinkwise Deployment Center (or 'Deployer' for short) has received new features, but over the past year, we have been gradually reworking the code to support some of the most frequently requested ones.There have been a couple of breaking changes compared to the last version, which we will highlight in this post.Download the Thinkwise Deployment Center 2.0.2 here. Deployer GUI and CLI New Support for specifying manifests as YAML Deployer GUI BREAKING CHANGES No more GUI and Indicium deployment during IAM installation and upgrade No more assistance for selecting a target meta source for Indicium and GUIs New Landing page rework Universal GUI deployment Installing a Universal GUI Upgrading a Universal GUI Local IIS support Indicium deployment reworked Windows GUI deployment reworked Web GUI deployment reworked Known issues Indicium application initialization not configured properly when using IIS API Deployer CLI BREAKING CHANGES Changed command-line library New Indicium commands Universal GUI commands Generic IIS commands Next release Deployer GUI and CLI New Support for specifying manifests as YAMLIn addition to the current JSON manifests:{ "schema": 2, "products": [ { "type": "IAM", "version": "2021.3", "projectFolder": "T:\\Product Innovation\\Applications", "dependencies": [ "CompatibilityLevel130" ], "packages": [ { "type": "Install", "path": "IAM/Install", "defaultDatabaseName": "THINKWISE_IAM" }, { "type": "Upgrade", "path": "IAM/Upgrade", "supportedVersions": [ { "version": "2021.1", "upgradesTo": "2021.2", "files": [ "2021.2\\020_Upgrade.sql", "2021.2\\030_Checks.sql", "2021.2\\040_Constraints.sql", "2021.2\\050_Indexes.sql", "2021.2\\060_Functions.sql", "2021.2\\065_Table_valued_functions.sql", "2021.2\\070_Views.sql", "2021.2\\080_Procedures.sql", "2021.2\\090_Instead_of_triggers.sql", "2021.2\\100_Triggers.sql", "2021.2\\110_Tasks.sql", "2021.2\\120_Defaults.sql", "2021.2\\130_Layouts.sql", "2021.2\\140_Contexts.sql", "2021.2\\145_Badges.sql", "2021.2\\150_Processes.sql", "2021.2\\999_Apply_roles_on_database.sql", "2021.2\\999_Manual.sql" ] }, { "version": "2021.2", "upgradesTo": "2021.3", "files": [ "2021.3\\020_Upgrade.sql", "2021.3\\030_Checks.sql", "2021.3\\040_Constraints.sql", "2021.3\\050_Indexes.sql", "2021.3\\060_Functions.sql", "2021.3\\065_Table_valued_functions.sql", "2021.3\\070_Views.sql", "2021.3\\080_Procedures.sql", "2021.3\\090_Instead_of_triggers.sql", "2021.3\\100_Triggers.sql", "2021.3\\110_Tasks.sql", "2021.3\\120_Defaults.sql", "2021.3\\140_Contexts.sql", "2021.3\\150_Processes.sql", "2021.3\\999_Apply_roles_on_database.sql", "2021.3\\999_Manual.sql" ] } ] }, { "type": "Hotfix", "path": "IAM/Hotfixes" } ] } ]}YAML can now also be used:schema: 2products: - type: "IAM" version: "2021.3" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel130" packages: - type: "Install" path: "IAM/Install" defaultDatabaseName: "THINKWISE_IAM" - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.1" upgradesTo: "2021.2" files: - "2021.2\\020_Upgrade.sql" - "2021.2\\030_Checks.sql" - "2021.2\\040_Constraints.sql" - "2021.2\\050_Indexes.sql" - "2021.2\\060_Functions.sql", - "2021.2\\065_Table_valued_functions.sql" - "2021.2\\070_Views.sql" - "2021.2\\080_Procedures.sql" - "2021.2\\090_Instead_of_triggers.sql" - "2021.2\\100_Triggers.sql" - "2021.2\\110_Tasks.sql" - "2021.2\\120_Defaults.sql" - "2021.2\\130_Layouts.sql" - "2021.2\\140_Contexts.sql" - "2021.2\\145_Badges.sql" - "2021.2\\150_Processes.sql" - "2021.2\\999_Apply_roles_on_database.sql" - "2021.2\\999_Manual.sql" - version: "2021.2" upgradesTo: "2021.3" files: - "2021.3\\020_Upgrade.sql" - "2021.3\\030_Checks.sql" - "2021.3\\040_Constraints.sql" - "2021.3\\050_Indexes.sql" - "2021.3\\060_Functions.sql", - "2021.3\\065_Table_valued_functions.sql" - "2021.3\\070_Views.sql" - "2021.3\\080_Procedures.sql" - "2021.3\\090_Instead_of_triggers.sql" - "2021.3\\100_Triggers.sql" - "2021.3\\110_Tasks.sql" - "2021.3\\120_Defaults.sql" - "2021.3\\130_Layouts.sql" - "2021.3\\140_Contexts.sql" - "2021.3\\145_Badges.sql" - "2021.3\\150_Processes.sql" - "2021.3\\999_Apply_roles_on_database.sql" - "2021.3\\999_Manual.sql" - type: "Hotfix" path: "IAM/Hotfixes" Deployer GUI BREAKING CHANGES No more GUI and Indicium deployment during IAM installation and upgradeIn the old Deployer, when installing or upgrading IAM, you would be asked if you liked to install an Indicium or any of the GUIs.However, since new deployment options for those products have been introduced, configuring them during the IAM flow has become quite complicated. For this reason, we have decided to remove the ability to deploy other products during the IAM flow.The Deployer was always meant as a helper tool for deploying our products, and thus we expect someone using it to at least know the basic cohesion between our products. So, as a user, you should know which products you need to deploy and in which order to make your environment work. For more information, we recommend reading the Thinkwise Platform Overview section on our documentation site. No more assistance for selecting a target meta source for Indicium and GUIsPreviously, the deployment flows of Indicium and the Windows/Web GUI had steps for selecting a target IAM to use as the meta source.Due to the new way we configure these products in this release, we had to cut these steps from the flow.We are looking into the possibility of adding additional buttons to the configuration steps that have a Simple mode to once again select a meta source with the assistance of UI dialogs. New Landing page reworkDue to adding more options and splitting existing ones to accommodate the deployment process better, the number of items on the landing page got rather long.To solve this problem, we have reworked the landing page to group the deployment options per product. You can find them in a drop-down menu on the left side of the landing page.Product menu on the landing page Universal GUI deploymentWe added the ability to install or upgrade the Universal GUI on an IIS server.The landing page of the Universal GUI Installing a Universal GUIThe process to install a Universal GUI has been broken down into:Select the site on IIS where to deploy the Universal GUI. Select an empty path relative to the selected site. Specify the contents for the Universal GUI's config.json configuration file.The configuration step supports two modes: Simple and Advanced.In the Simple mode, you can only change the basic options for running a Universal GUI:Universal GUI Simple configurationTo configure an option not listed in the Simple mode, you can use the Advanced mode instead.In the Advanced mode, the Universal GUI will only check if the serviceUrl property has been specified correctly. Other options are used as-is.Universal GUI Advanced configuration Upgrading a Universal GUIThe process to upgrade a Universal GUI has been broken down into:Select the IIS site containing the Universal GUI to upgrade. Select the path relative to the site that contains the Universal GUI installation. Optionally change contents for the Universal GUI's config.json configuration file. Just as with the installation process, you can select either the Simple or the Advanced mode to upload a new config.json file. You can choose to skip this step altogether and keep the current config.json in the installation directory. Optionally, mark any additional files that contain settings for changing how the Universal GUI works.Universal GUI: files/folders of the current installation to preserve Local IIS supportAn important feature request we received was the ability to deploy products to an IIS instance running on the current server without the need for the Microsoft IIS Administration API.After a considerable effort in re-implementing the entire IIS deployment code, this has been made possible.Products that deploy to IIS now have both a Local and an IIS API option on the landing page:IIS API deployment options on the landing pageThis is available for the following products:Indicium Indicium for Mobile GUI Universal GUI Web GUI. Indicium deployment reworkedThe deployment process for Indicium and Indicium (Mobile) has been reworked.Previously, there was a single deployment option for both installation and upgrading. This made the logic for the deployment more convoluted than necessary, and it made it harder to add new features to the process.For this release, we have split the single deployment process into separate install and upgrade flows.Just like with the Universal GUI process, there is now a dedicated step to configure Indicium's appsettings.json. Both the Simple and Advanced modes are included, and the step can be skipped during the upgrade process.Indicium: Simple mode for configuring the appsettings.jsonAdditionally, there is an option to help configure the application initialization feature for Indicium. When running Indicium as an agent of an IAM, e.g., to generate projects in the Software Factory 2021.3 or run scheduled system flows, we recommended turning on this feature.Additional Indicium settingsLastly, just like with the Universal GUI process, it is now possible to retain certain files as-is inside the installation that is being upgraded.Indicium: files/folders of the current installation to preserve Windows GUI deployment reworkedThe deployment process for the Windows GUI has been reworked.Just like with Indicium, there was previously only one deployment process for the Windows GUI. This process has also been split into separate installation and upgrade flows. Additionally, we have added an option to only create a new startup configuration file (.ini) by selecting an existing installation.Windows GUI deployment options on the landing pageWhen creating a startup configuration for the installation, there are three options to choose from:Create new Link existing Skip.By choosing Create new, you can load a preset template based on the meta source connection you are going to use and then modify it with the required values.When using the Indicium template, make sure that the Windows GUI you are using supports it.Create a new configuration file for the Windows GUIIf you choose Link existing, e.g., to create a shortcut later in the deployment process, simply enter the path to the desired ini file.Windows GUI: link an existing startup config to this installationIf you select the Use ClickStart option, any shortcuts made during this deployment will target TSF_CS.exe instead of TSF_dotNET.exe. It is possible to modify the clickstart.ini to configure the behavior of TSF_CS.exe.Windows GUI: configuring the ClickStart iniLastly, you can either Skip creating or create a new shortcut that links the selected startup configuration to the Windows GUI installation. Remember that selecting Use ClickStart in the Startup configuration step will make this shortcut to TS_CS.exe instead of TSF_dotNET.exe.Windows GUI: create a shortcut for the startup configuration Web GUI deployment reworkedJust like in the Indicium and Windows GUI deployment, the Web GUI deployment has been split into separate installation and upgrade flows.This rework is not as broad as the other two, but we have enabled the options to enter your own settings.ini and to preserve files/folders when upgrading.Configure the settings.ini of the Web GUI Known issues Indicium application initialization not configured properly when using IIS APICurrently, the Microsoft IIS Administration API does not expose the properties we need for configuring the application initialization feature properly for Indicium.We have made pull requests to the official repository on GitHub to try and fix this, but there will seemingly only be one more update by Microsoft to this repository to upgrade the software to .NET 6.We are currently discussing whether it is worth it to continue support for this way of deploying our products. Deployer CLIThe command-line version of the Deployer has also received some updates. Some of these updates are breaking changes compared to the previous version. BREAKING CHANGES Changed command-line libraryThe previous version of the Deployer used a command-line argument parser that did not support sub-commands. Due to this, several command names were appended together instead, e.g., iam-install/iam-upgrade/iam-hotfix. This made adding more commands to the CLI difficult since the help would soon be a lot more cluttered, as was the case for the landing page in the Deployer's GUI.Because of this, we have changed the underlying command-line library to a different one that does support sub-commands.This is a breaking change. Not only because, for example, iam-install must now be called as iam install but also because some subjects, like argument parsing, might be handled differently than before.We recommend using this version to thoroughly test the scripts that use the Deployer CLI program before updating any previous executables currently used in production.As part of adding sub-commands, the commands to auto-install, upgrade, or hotfix an IAM, Software Factory, or application have been moved fromtwdeployer.exe iam (OPTIONS) twdeployer.exe sf (OPTIONS) twdeployer.exe app (OPTIONS)to the following commands:twdeployer.exe iam auto (OPTIONS) twdeployer.exe sf auto (OPTIONS) twdeployer.exe app auto (OPTIONS) New Indicium commandsWe added commands to install, upgrade or reconfigure Indicium on a local IIS instance.We also added a command to create an application pool with recommended settings for Indicium.These commands can be called using twdeployer.exe indicium iis.The commands must be run from an elevated prompt because modifying IIS requires admin privileges.Indicium CLI commands Universal GUI commandsWe added commands to install, upgrade or reconfigure the Universal GUI on a local IIS instance.These commands can be called using twdeployer.exe universal iis.The commands must be run from an elevated prompt because modifying IIS requires admin privileges.Universal GUI CLI commands Generic IIS commandsSome commands were added to the Deployer CLI to control application pools on the local IIS instance.You can now:List information about every or specific pools Create new pools Edit the properties of one or more pools Start one or more pools Stop one or more pools Delete one or more pools.These commands can be called using twdeployer.exe iis pools.These commands must be run from an elevated prompt because modifying IIS requires admin privileges.IIS application pool commands Next releaseEven though Thinkwise has no dedicated Deployer team (like there are dedicated teams for the GUIs and Indicium), we would still like to ship the following changes before the 2022.1 Thinkwise Platform release:Dedicated support for deploying the Thinkwise Upcycler. Move Deployer CLI to .NET 6 While the commands that target IIS might not work on anything other than Windows, users would still be able to deploy IAM, the Software Factory, or application products on other operating systems. Depending on the amount of work, we might have the Deployer GUI run on .NET 6 (Windows only) as well. Add options to install an application without syncing the model to an IAM. Add a separate flow that only syncs the application model to IAM. Check access rights on the target directory when installing Indicium to a local IIS. One of the most common causes we encounter where users cannot start their Indicium installations is that the user the application pool is running on does not have write access to Indicium's installation directory. We plan to add a deployment action that checks if this is configured correctly. Would like to have:A simple configuration mode for Windows GUI flows to make it easier to get a basic installation up and running. A UI-assisted meta source selection for simple configuration modes during Indicium and Windows GUI flows. 

Hello everyone,In this sprint, we added, among other things, a Cancel button to the login pages. In addition, we built support for password changes from RDBMS users. We also fixed a rare issue that might possibly be breaking.You can read the Indicium user manual to read about Indicium's features.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.15 here. Download Indicium Basic release 2021.3.15 here. Contents of this releaseBreaking Indicium Universal: fixed dependent lookups being cleared erroneously in rare situations Indicium Universal Change password from RDBMS users SQL print statements available in log Login pages have an extra button for cancel Minor fixes and tasks Indicium Basic Minor fixes and tasks  Breaking Indicium Universal: fixed dependent lookups being cleared erroneously in rare situationsIn this release, we have addressed an issue that caused lookups filtered by expression columns to become empty in certain situations when they should not have. In particular, this issue would occur if the expression value changed and the dependent lookup got a new, valid value in the default procedure. Indicium Universal would not respect the value set in the default procedure and clear the dependent lookup. This scenario is quite rare, and the changes that we have made to address it are fairly subtle, but they are technically breaking changes, so please be aware of this. Below you will find a description of the old behavior versus the new situation.Old behavior:Apply default logic. Validate all editable lookups that were set in the default procedure. Validate all editable lookups that are dependent on properties that were set in the default procedure. Reevaluate the expression properties with the current state of the resource. Validate all non-expression lookups that depend on an expression property whose value has changed.New behavior:Apply default logic. Reevaluate the expression properties with the current state of the resource. Validate all editable lookups that were set in the default procedure or are expressions whose value changed. Validate all editable lookups that are dependent on properties that were set in the default procedure or expressions whose value changed. Indicium Universal Change password from RDBMS usersIndicium Universal now supports password changes from RDBMS users. This was already available for Windows and Web. SQL print statements available in logIf a stored procedure contains a print statement, it will now show up in the dbeventlog in Indicium's root page. We made a new column that contains all the print statement messages. Login pages have an extra button for cancelWe improved the behavior of the different login pages and now allow canceling the login flow.For instance, when you try to log in and are presented with the two-factor validation page, you can now cancel the login and return to the original page. This also applies to the change password page and the two-factor setup page. Minor fixes and tasksWe fixed the issue that parameters were not replaced in messages thrown from triggers. We fixed that the id_token_hint parameter was not sent along with the OpenID Connect remote logout requests. This did not cause issues with Microsoft Azure AD integration, but it did cause issues while logging out with other OpenID Connect implementations. These issues have now been resolved. We fixed an issue that caused that dependent lookups were not imported correctly. When translating the display values of a lookup from the Excel or CSV file back to their data values for the inserts/updates into the database, it would not take the context of the lookup into account. For example, the display value 'Subproject 1' would be resolved to the same data value regardless of the corresponding project. Indicium Basic Minor fixes and tasksWe fixed a bug when a record was updated in a table with a prefilter on an expression field. Indicium would throw an exception in that case. We fixed an issue with default value expressions that returned DateTime types. For example, having a column with a default value expression of 'GETDATE()' would cause an error.

Hello everyone!We’ve released the following hotfixes over the last few weeks:SF 2021.220211111 - Sort order index columns When generating projects, sort order indexes are created for tables based on its sorting. The order of the index columns was alphabetically instead of based on the order no. This has been fixed. IAM 2021.320211103 - Execute source code regex update It was possible that code files would be split into multiple statements at wrong places causing errors during the Execute source code process. This has been adjusted.

There is a new E-learning course is available in the Thinkwise Learn environment. In this course we will guide you through all the basics of SQL and data modelling, in order to help you prepare for the Software Factory Associate training. The topics that will be covered are all of the most essential parts a developer needs when working with the Thinkwise Platform. Although the target audience for the course is the starting Thinkwise Developer, it is open for everyone to enroll. Perhaps you would like a recap on certain topics, or want to test your own SQL and data modelling knowledge.Why do we have this course?You will find many courses about SQL and data modelling on the internet. None of them, however, are specifically designed to be used in combination with the Thinkwise Platform. We use SQL in a different way than it is used in most applications. If you follow our SQL course, we can assure you that you will pick up on all the guidelines and best practises for the Thinkwise platform. You will also learn more on how SQL and data modelling are related to working with the Software Factory. In this way, the course help you focus on the parts that matter the most for a Thinkwise Developer.The course consists of two modules:Data Modelling and SQL - General TheoryIn this module, we will cover the most important aspects of data modelling, like the relational model, strong and weak entities, database normalisation, data types and the language SQL. Additionally, we will also have a look at how a relational model and SQL relate to the Software Factory. This module will be mostly theoretical, but you will perform quick knowledge checks during the process.SQL BasicsIn this module, we will focus on writing queries in SQL. We will go through all the basic elements that you will need to create your application with the Software Factory. We will follow the Thinkwise coding guidelines and cover best practises from our in-house developers when writing SQL. For every subject, we have created exercises to directly bring the theory that you have learned into practise. You can complete the exercises in a training database, which you can download from the course. You will also find an example solution to check your own work at the end of every subject.We also offer the possibility to receive coaching from our own trainers/developers during this course. Your code will be reviewed and you will receive more tips and tricks adapted to your own learning path. If you are interested in this, please contact your sales contact person.Coming soon: Update Thinkwise Associate - The Software FactoryCurrently, we are working on a new version of the Thinkwise Associate learning path. The new course will cover the relevant content about the recent Platform releases. As well as an educational, instructive and graphical update. In 2022, you will be hearing a lot more about the online learning content for the Thinkwise Platform. Keep an eye on our posts to stay informed!

November 5, 2021:Changed beta release to full version: 2021.3.12. Added fix: We fixed that the grid did not update summary values. Hello everyone,In this sprint, we added, among other things, support for opening lookup pop-ups from the grid and improved the marker in Maps. We also fixed some issues in default editable grids, lookups, and messages.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 2021.3.12 Like with every blog, we have released a version to test the Universal GUI out for yourself. 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 it should be 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 2021.3.12 here New Improved marker in MapsWhen clicking the marker in a map, the grid will now navigate to the row that the user clicked on.Additionally, Maps now supports custom markers. As of the Thinkwise Platform release 2021.3, the Maps model extender has been replaced by a Maps component. Using a custom marker in the Maps component requires a Data mapping column with an 'Image combo' control. The image from the grid is used as a marker. For platform versions older than 2021.3, using the Maps model extender, the Type column binding needs an 'Image combo' control to use a custom marker. Custom marker in Maps Support for opening lookup pop-ups from the gridIt is now possible to open lookup pop-ups from the grid, using the menu on the right. This option is only available for look-up columns with Lookup has pop-up enabled in the menu Subjects > Links > Lookups.Opening a lookup pop-up from the menu in the grid Minor fixes and tasks We upgraded our core grid component to a newer version that can better compute changes when the columns change. A user can now scroll from an HTML control to the next available field. In some screens, it could take seconds for the task and report buttons to become clickable. This delay was caused by an or query on i_ui_task_parmtr, i_ui_task, i_ui_report_parmtr, or i_ui_report. The Universal GUI now asks for this information in multiple requests.  We fixed a bug that blocked users from logging in with 2-factor authentication. We fixed that the grid did not update summary values. If users lost their internet connection without going into the offline mode or restoring it, problems arose. For example, task pop-ups could not be canceled or reopened. These problems have been fixed. We also added a visual offline indicator to the task pop-up, so users cannot accidentally use it without an internet connection. Before: Problems after a lost internet connection      After:Clarity on the disconnection Fixes in default editable gridsWhen opening a default editable grid, an error could be displayed: method not allowed. The  cause of this error was that the record was set to 'read-only' by the layout. The Universal GUI did not wait for the layout correctly. When clicking a checkbox in a default editable/autosave grid, the value would change to 'checked' and then return to its previous value. This has been fixed. We partly reduced the flickering grid content while modifying data in the edit mode.  Fixes in lookups In the pop-up of a read-only lookup, the Select button has now been disabled. A lookup can be set to read-only in the Layout stored procedure. We also fixed that a read-only grid lookup field (as set in the Layout stored procedure) appeared as editable in grid edit mode. In the example below, the Country lookup column is read-only due to the layout. Before the fix, it seemed editable, but as you can see at the bottom of the screen, changing the value failed because the column is read-only: Read-only lookup with error message     Now, the column is displayed correctly as read-only:Read-only lookup without error message Fixes in messagesConfirmation messages now show the value of hidden task parameters. Error messages are no longer shown with [ ][] blocks around it. General messages, like [application_model_expired], are now translated correctly. Messages did not include a subject's translation if the subject had never been opened in the GUI at least once. This has been fixed. Messages thrown by a process flow now use the process variable values in the message translation. What we will be working on next sprintIn the next sprint, we will be working on:Support for the lookup control type 'Combo (sorted)'. Editing HTML in a full-screen pop-up.

Hello everyone,In this sprint we made logging easier, and 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 2021.3.13 here. Download Web GUI 2021.3.13 here. Breaking Developer mode no longer necessary for logging (Web GUI)Previously, when you wanted to enable logging for the Web GUI, you needed both the extended property WriteLogToFile and the option ExecutionMode (developer) in the settings.ini file.Now, we have removed the developer mode as one of the conditions. So, you can enable or disable logging solely by changing the extended property in IAM. This facilitates limited logging but prevents that users need to log in as a developer.Limited logging (e.g., only exceptions) can be set by combining the extended properties WriteLogToFile and LogSeverity. Minor fixes and tasks(Windows GUI) The scheduler yielded a divide by zero exception when the default row height for the grid was 0. This has been fixed. (Windows GUI) We have fixed an issue with failing file uploads in the Windows GUI in combination with Indicium. This issue only occurred in tables without a default procedure.

Hello everyone,In this sprint, we reduced the amount of double messages, and we fixed a problem with a false positive check. We also worked on some technical issues that do not affect functionality.You can read the Indicium user manual to read about Indicium's features.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.13 here. Download Indicium Basic release 2021.3.13 here. Indicium Universal Reduced amount of double messages in the Universal GUITo eliminate the number of double messages, Indicium will no longer send messages from layout and context procedures if the procedures determine that the action is allowed. If necessary, the messages will be sent by the Universal GUI. Minor fixes and tasksSeveral of the file system I/O connectors in process flows, for instance, the Write File connector, would first validate if the root location of the file path was accessible (e.g., C:\ or \myFileServer) and then if the direct parent directory was accessible (e.g., C:\files\myProject or \myFileServer\files\myProject). In practice, only the second check is necessary. Moreover, the first check can fail where the second would have succeeded. Users may have access to a specific folder but not to the root of that folder. Therefore, we have removed the first check to solve the false positive 'access denied' scenarios.

Hi everyone!We’ve released the following hotfixes for 2021.3 platform version:SF 2021.320211029 - Corrections in creation process The task to run a complete creation now waits for other jobs to finish, no longer result in the possible failing of a creation. When a project version was upgraded, the question is now asked again if a new project version should be created. The process flow responsible for focusing on the active definition generation step has been made a little bitt less aggressive, leading to a better user experience. 20211027 - Corrections in creation process A possible situation where the upgrade script was not automatically checked does not arise anymore. There no longer is a specific situation where it might appear that executing a new project version to the database succeeds, when it actually doesn't. Some other minor improvements. IAM 2021.320211029 - Corrections in creation process We've been getting several questions on how to deal with messages stating that a job will not be started (directly). These messages have been improved to include the sentence "More information can be found in the Advanced Menu > Log > Jobs." 20211028 - Agent check-in reduced abandon rate A scenario was discovered where scheduled system flows that only allowed a single instance to be running, could end up running multiple times due to the earlier instance of the system flow being marked as abandoned when the interval was expired. This has been resolved. 20211027 - Grant rights to end user role for Get gui maps procedures The necessary rights for the new get gui maps procedures were not granted to the IAM-role “End user”. This could cause errors while starting an application for this role, only when rights to the database were applied. The rights are now granted. 20211026 - Set ‘Legacy API’ to on for Get gui maps procedures Get gui procedures for maps were not available for Indicium Basic causing applications run via Indicium Basic to be unable to open successfully. This has been resolved.

Hello everyone,In this sprint, we have improved the logging and the import functionality. We have also solved some issues.You can read the Indicium user manual to read about Indicium's features.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.11 here. Download Indicium Basic release 2021.3.11 here. Breaking Indicium Universal: Process procedure errors now stop the process flowFrom now on, errors in process procedures will abort your process flow or system flow. Previously, the order from the model was used if something went wrong, but this could cause unintended effects when the process procedure did not work as expected. Indicium Basic: Support for IAM/Software Factory 2019.2 expiredThe support for reading application models from the Thinkwise Platform version 2019.2 has expired. Please update IAM and the Software Factory to at least version 2020.1 to use this version of Indicium. Indicium Basic: Now requires the IIS module AspNetCoreModuleV2  to be installedInstall the latest ASP.NET Core Windows Hosting module that is linked here. Indicium Universal Updating rows when importingWhen you tell Indicium not to insert rows and only update, it will throw an error for the rows it cannot update. So, you can download the failed records into a new Excel file.To control this behavior, two new query string parameters have been added to the stage_import endpoint: add_new_rows and update_existing_rows. Their values can be set to true and false, but at least one of them must be true. Improved loggingIn this version of Indicium, we improved the logging, to make it easier to detect where an error occurred.In process flows and system flows, it is now clear which step caused the error. System flows with invalid actions are logged now. More explanation is available for errors that occurred when editing a resource. ChangesIndicium will no longer treat an SQL print message as a TSF message. In the near future, SQL print messages will be logged to Indicium Universal's Database Event Log. Minor fixes and tasksWe solved an issue that occurred when you used mandatory exclusive prefilter groups, and the table had an expression column. This issue could cause Indicium to crash and require a restart. On some occasions, Indicium would call the subroutine procedures with the wrong parameter order on DB2. This has been fixed. We solved an issue with the query for lookup references that contained an expression column in its target columns. When configuring an API alias for subroutine parameters, the API alias was not used correctly. This has been fixed. We fixed an issue that could cause failed queries for the combination of `select detail` references with `groupby' clauses. In particular, this could cause pivot grid and charts on detail subjects unable to load their data.

We are very excited to announce version 2021.3 of the Thinkwise Platform.Our highlighted feature of this release is the redesigned and improved Creation process. This redesign offers many advantages:All jobs are no longer performed by a client (the GUI) but instead by Indicium. This shift means that generation, validation, etc., will continue even if you close the Software Factory GUI. Since all jobs are performed by Indicium, it is possible to automate the entire process. All developers can track a job's progress. For example, if one developer starts generating the definition of a project version, another developer can see this in their Creation screen. This behavior extends to the validation- and unit test tabs in various modelers. The Validation and Unit test screens that can be opened directly from the menu have also been updated. You can execute the steps in the Creation process separately or all at once.The screens and steps you already know in the Creation process are still available. But to move the responsibility of the creation process to Indicium, some screens have changed, and we have cleaned up some unused features.For more information, see:Redesigned creation process Task to execute a complete creation Automate your creation processA task for executing all creation stepsOf course, this release brings more new features and changes. Some other highlights are:Reusable subflows Multiple running instances of system flows Generation optimization Generation strategies for control procedures Manual test administrationFor a comprehensive overview, please check out the release notes.The Thinkwise Platform 2021.3 is available for download in TCP now! 

Hello everyone,in this sprint we have improved the autorefresh functionality for the Windows GUI.You can read the GUI user manual to read about the Windows and Web GUI's features. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.3.11 here. Download Web GUI 2021.3.11 here. Changed Support for IAM/Software Factory 2019.2 expiredThe support for the Thinkwise Platform version 2019.2 has expired. Please update IAM and the Software Factory to at least version 2020.1 to use this version of the Windows and Web GUI. Autorefresh disabled when a grid or tree is in multiselection (Windows GUI)From now on, autorefresh is disabled when a user selects more than one row in a grid or tree.Before this change, when the screen refreshed, the selection would reset to only the active row. That made it almost impossible to execute tasks based on multiple row selection.Now, autorefresh pauses for as long as the user has multiple rows selected, and thus multiple row task execution can be used. New The new Maps feature supported in the Windows and Web GUIThe new Maps feature in the Software Factory (version 2021.3), including its settings, is now supported in the Windows and Web GUI. New application setting (Windows GUI)We added a new application setting: oauthredirecturi. You can use this setting to change the standard OAuth connector redirect uri (http://localhost/oauth-callback). Minor tasks and fixesWindows GUI: a bug with an empty task output in combination with indicium has been fixed.

October 19, 2021:Changed release version to 2021.3.11.1. Added fix: Chart was not visible when a document was opened for the first time.October 15, 2021:Changed beta release to full version: 2021.3.11. Added fix: The process flow Go to next row would return as successful when used on the last record in the dataset. With this fix, it will return as unsuccessful. The same problem has been fixed for Go to previous row/first record. Hello everyone,In this sprint, we added support for changing an expired password, and for editing multiple rows in a grid with autosave enabled. We also made the resource scheduler more compact in the day view. And again, we fixed some issues, mainly for lookup 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 2021.3.11.1Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, eg 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 it should be an allowed origin in the appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Furthermore, 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 2021.3.11.1 here New Stay in grid edit mode when autosave is turned onWhen autosave is enabled, and you are working in an editable grid, it is now possible to edit multiple rows without the need to reactivate the edit mode for every row. Edit mode will be turned off when, e.g., deleting a record, adding a record, refreshing, or filtering. It is also turned off by saving manually or canceling.Edit multiple rows in the grid in edit mode Support for changing an expired passwordA user logging in with an expired password is now redirected to Indicium, where they can change their password. After that, the user is sent back to the Universal GUI. Please note that sending the user back only works when Indicium and the Universal GUI run on the same origin (recommended) or if the Universal GUI is configured as an allowed origin in Indicium.Previously, the Universal GUI displayed "Incorrect username and password." Changed Resource scheduler more compactIn the day view, the year and week labels have been merged, which saves vertical space.In compact mode, the height per resource row and padding below each resource row have been reduced. This row height and padding reduction win 13px per resource row, resulting in more resources fitting in the same height.Before:The resource scheduler before the changesThe resource scheduler now: more compact Changed and fixed in lookup controlsThe lookup suggestion control now shows the start of the options list if it is opened while an option is already chosen. Previously, the options got filtered on the selected value, which resulted in only one option to choose. The lookup controls now have their focus state reimplemented to make them feel like the other controls. Also, we did a few alignment fixes to make them look the same. In some cases, the Clear button showed in an empty lookup control. Now it only appears when a value is chosen. On an empty lookup control without focus, but with a large format label in the middle of the input, the label blocked the mouse cursor from focusing on the field or clicking the buttons. Now, the label is placed "behind" the field to only display the column name without blocking anything. Loading the options for untranslated lookup columns in the filter form has been fixed. Screen components that cannot have data pruned from the screen typeScreen components that cannot have data are now pruned from the screen type. Previously, a screen showed empty space or an error message if a component could never show data. Removing these components provides more space for the components that can display data. For example:Detail tiles without details Grid without columns Form without columns Card list without columns Cube without cube definition Scheduler without two date(time) columns Previewer without suitable column Tab with only detail tab pages and no details. Minor fixes and tasksCard lists and form components now keep their scroll position after a screen switch, e.g., after a tab change and back. The process flow Go to next row would return as successful when used on the last record in the dataset. With this fix, it will return as unsuccessful. The same problem has been fixed for Go to previous row/first record. Fixed that a chart was not visible when a document was opened for the first time. What we will be working on next sprintThe next sprint we will be working on:Maps Navigate to a row from the map. Customize marker icons. Lookup popup from the grid - Allows the user to start the lookup for a field from a non-edit mode grid. And we will solve some issues.

Hello everyone, We have just released a hotfix for Universal that fixes Universal crashing when logging out or clearing the cache while working on HTTP.This has been released as version 2021.3.10.2 and can be downloaded here.Please note that we strongly advise using HTTPS with Universal, without HTTPS Universal can't work offline and can't detect when a new version has been deployed.

Hello everyone!We’ve released the following hotfix this week:SF 2021.220210921 - Exclude clustered indexes from drop all Clustered indexes are now created when the tables are created but were still being dropped by the drop all indexes script. The drop all indexes script has been updated to no longer drop clustered indexes.

Hello everyone,in this sprint, we fixed several bugs.You can read the GUI user manual to read about the Windows and Web GUI's features. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.3.10 here. Download Web GUI 2021.3.10 here. Minor fixes and tasks(Windows GUI) We have fixed a bug where auto-refresh continued after you entered edit mode. Now, auto-refresh will pause after you enter edit mode and only continue when you leave. (Windows and Web GUI) Fixed a bug in the OAuth connector which could result in an Object reference error. [2125S] (Web GUI) Fixed a bug in the 2FA email notification flow where HTML was not correctly decoded.  [2069S] (Windows GUI) Fixed a bug in the multiline control popup where changes where not saved on close. [2225S]

Hello everyone,in this sprint, we improved the import functionality and updated the Thinkwise Reporting Service. Moreover, it is now possible to simulate a user. This can be a powerful tool for testing the access control or debug an issue with a specific user.You can read the Indicium user manual to read about Indicium's features.We'll keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.10 here. Download Indicium Basic release 2021.3.10 here. Indicium Universal Importing subjects with untranslated lookupsIt is now possible to import into a subject that contains untranslated lookups. Multiple results from a single query in the application connectorThe application connector can now retrieve multiple result sets from a single query. If multiple result sets are detected, the application connector will retrieve them and put them in a single JSON file. This can be used for a stored procedure that you want to use in the application connector, returning multiple result sets. User simulation in IndiciumAs of version 2021.3 of the Thinkwise Platform, which will be released very soon, it is possible to simulate a user if you are an administrator or a simulation administrator. User simulation can be a powerful tool for testing the access control or debug an issue with a specific user. It is also available in IAM.With the proper rights to simulate a user, you see a new link on the root page of Indicium: User simulation.New link: User simulationWhen you click the User simulation link, you navigate to the page where you select the user you want to simulate from the drop-down list. Then, press Simulate.The user simulationWhen you're ready with the simulation, press the Stop simulation button.It is visible on the root page of Indicium that you're impersonating a user:The user simulation in the root pageIt is also possible to simulate a user via the API by using the following call. It will return the user you're simulating. If you're not simulating, it will return the status code NoContent.GET account/api/usersimulationThis call will start the simulation for the selected user and return the status code Ok when the simulation succeeds. If not, you will receive a badRequest with the error message.PATCH account/api/usersimulationRequest body:{"simulated_user": "{username you want to simulate}"}To stop the user simulation, send the following command:DELETE account/api/usersimulation Disable "Forgot your password"From now on, it is possible to disable the Forget your password? link on the Indicium login page by adding the following JSON property to your appsettings.json."LoginOptions": { "AllowPasswordForget": false }When the AllowPasswordForget property is set to false, the Forget your password? link is disabled. Also, the Forget your password page or API cannot be used any longer. Thinkwise Reporting Service version 5We also released a new version of the Thinkwise Reporting Service, version 5. It contains some improvements and bugfixes:For Crystal Reports, the Thinkwise Reporting Service can now detect and use any 64-bit service pack (so, also service pack 26 and higher). For DevExpress Reports, we updated libraries to enable parameters for data sources using stored procedures. We also fixed that a parameter dialog appeared if not all parameters had received a value from rpt_get_parmtrs. Finally, DevExpress is now an accepted value (instead of TR) for report_type in rpt_get_reports. Two general settings are available now: PrinterNameCaseSensitive: sets whether printer names should be case sensitive. PrinterTrayCaseSensitive: sets whether printer tray names should be case sensitive. .NET Framework 4.8 is the new prerequisite for the Reporting Service. For more information on the new and changed prerequisites, configuration, logging, installation, and upgrading, see Reporting Service. Changes Minor fixes and tasksOn some occasions, an OpenIDConnect provider can throw an error. These errors are now correctly handled by Indicium, so a message is shown on the login page. It won't give away details as it might contain sensitive information. Logging in to an IAM user without a configured password would show an HTTP error instead of a message. This has been fixed. The maximum file size in a storage configuration for files over 2GB didn't work correctly. This has been fixed.  

 September 24, 2021:Changed beta release to full version: 2021.3.10: Fixed a bug where the checkbox would always be center aligned in the gridSeptember 29, 2021:Fixed a bug where Universal would crash when logging out or clearing the cache while working on HTTP. This has been released as 2021.3.10.2 and can be downloaded here.Hello everyone,In this sprint we implemented support for unavailable domain elements in combo boxes and added the release date to the About box. We also made some changes to existing features and functionality. But most of all, we solved a lot of minor issues.As always, we've 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 2021.3.10Like with every blog, we've released a version so you can test the Universal GUI out for yourself. Don't 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 it should be an allowed origin in appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Furthermore, 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 2021.3.10.2 here Breaking Default form field background color changedWe changed the default value of config.json setting useFormFieldBackgroundColor, which turns on background colors of editors. It was false, now it is true. When you're keeping your previous config.json file, there is no impact.See Form field background color. New Support for unavailable domain elements in combo boxesIn release 2021.2, the Software Factory introduced an option for marking domains as 'unavailable'. See Making a domain unavailable. Now, this setting also applies to the combo boxes in the Universal GUI, both textual and image variants.As a bonus, we fixed combo boxes in the editable grid to send value changes directly to Indicium after choosing them. In the form, it already worked this way. Release date in the About boxThe About box (under User Preferences) now also contains the date that the Universal GUI version was released.Universal GUI release date in the About box Changed Spin loader when deleting a recordPreviously, when deleting a record took a while, e.g., in a large data set, no indication was available that records were being deleted. Deleting a record twice resulted in an "action not allowed" error.Now, a loading panel will come up until the operation is carried out on the database, so the user will not continue working with the deleting record. Button visibility of task and report parameter popupsThe Universal GUI now listens to the layout application logic for the button visibility in task and report parameter popups. The confirm_button_type and cancel_button_type parameters can now be used to disable or hide one of the buttons. See Business logic. Minor fixes and tasks Fixes in process flows We fixed a crash that occurred when a process flow was running on a detail subject, and the user closed the document. The Open document process flow action, with use an existing document enabled, now skips the already opened (zoomed) detail documents of the same subject. The Go to row process actions (including next, previous, last, and first) previously did not work outside the page. Now, they work regardless of the page you are on. We fixed the Start task process action causing a crash at various events. Also, we fixed scenarios in which a crash could occur when the user started a task before the task definition was loaded. The scenario below would not behave correctly. After the Edit Row in the root subject, the Go to first row process action that was supposed to execute in the detail, was executed on the root subject. Additionally, the dataset refresh after the Edit row would come after the Go to first row, resulting in the Go to first row having no effect. Example scenario Small styling improvementsFixed the height of the top tab bar in opened documents to match the menu Search control again. Fixed the height of the application menu in comfortable mode. Aggregation values are aligned better now with the grid's headers and column data. Fixed the size of generated icons in action bar buttons. We solved a lot of little alignment issues with controls in both the grid and the form. Fixed the padding at the bottom of the toolbar in comfortable mode. Fixed the padding around images in the grid and centered them correctly.Known issue: the grid column values do not always have the desired padding yet. The solution for this is planned for a later date. Fixes for lookup controlsWith the latest version of Indicium, the lookup controls would stop working and give no result. This has been fixed. (Suggestion) lookups were not aligned properly. When no icon was shown, the text in the form would be over the label. Now, in grid edit mode, the whole control is shifted down and to the right. We fixed that lookup controls were being cleared by the default application logic. Previously, it was not possible to select another value afterward. Fixes for paginationDeleting the last record of, e.g., page 5, resulted in the Universal GUI going back to the first record of the first page. This has been fixed. Now, the Universal GUI will go to the last record of the previous page. Transitioning between pages will look more fluid now. OtherThe colored bitmap and vector images now get grayed out when the button (e.g., a task) is disabled. When a hidden HTML field was made read-only by the layout, it would not show data. This has been fixed. We fixed filter form combo boxes still displaying a value after clicking Clear all filters. (Quick) filters were not applied to the grid summary totals, which caused them to be bigger than the visible dataset. This has been fixed. We fixed strange behavior in the formatting of received data, where a textual value with a date was replaced with a date-only value. When a login options error occurred, the application would refresh and you would not be able to see the error. This has been fixed. We fixed a problem with the screen type breakpoint on mobile devices after opening a subject. We fixed the use of the Cortex scanner control on an offline executed task. What we will be working on next sprintThe next sprint we will be working on:Grid temporary auto-edit mode - When the Autosave property is enabled, the grid wil stay in autosave/edit mode until an explicit Save or Cancel. And again, we will solve issues and technical debt.