Product Updates

Hi everyone!We’ve released the following platform improvements this week: IAM 2023.1 20230316 - Synchronizing custom schedules to IAM During the synchronization to IAM, the process will check to see if the Allow custom schedule setting is turned off. If that is the case, the active custom schedule will be disabled. Rather than checking for the particular process flow, it checked all process flows to see if any of these process flows has this setting turned off. This resulted in custom schedules being disabled unintentionally. This has been resolved. SF 2023.1 20230223 - Create process action Copy to clipboard We have implemented a Copy to clipboard process action. This process action works from Universal GUI 2023.1.14. 

Hello everyone,In this sprint, we have added support for debug tracing to troubleshoot issues with reverse proxy settings, and we have fixed some minor issues.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. No 2023.1.14 release available. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2023.1.14 here.  ContentsAbout Indicium New Debug tracing for reverse proxy settings Minor fixes and tasks Questions and suggestions? New Debug tracing for reverse proxy settingsIndiciumWe have added the ability to turn on debug tracing to troubleshoot issues with reverse proxy settings. It could be challenging to configure the reverse proxy settings correctly and debug why the settings do not work.The debug tracing will log information to Indicium's log file. It can be turned on by configuring the new TracingEnabled property in the ReverseProxy settings in appsettings.json:"ReverseProxy": { "Enabled": true, "TracingEnabled": true,} Minor fixes and tasksIndicium We have fixed an issue that caused the X-Forwarded headers sent by a reverse proxy to not be respected by process flows. This affected the URLs produced by the OAuth User Login connector and the Download File connector. Both process actions would build a URL to their own internal address, instead of to the external address of the reverse proxy. We have fixed an issue that could cause the properties of lookup references to be cleared unexpectedly during data entry. This could happen on lookup references with three or more reference columns. The second reference column, for example, would not necessarily be dependent on the first reference column, but it would always be cleared when the first reference column was changed. The problem is described in detail in this topic. We have fixed an issue that prevented previewing of some EML files.  Questions and suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvements this week:  SF 2021.3 and up20230309 - Unit test rollback result correction If a unit test would result in a rollback, this was correctly executed by the job executing the unit test itself. However, it was not displayed correctly in the unit test's result window. This has been fixed in such a way, that it is now clear to the user executing the unit tests or checking executed unit tests, that a unit test has actually been rolled back:Unit test expected to rollback: Unit test did in fact rollback correctly: SF 2023.120230303 - Execute Code difference delta actions in merge session When merging from Origin to the Branch, any conflicts that were resolved using the Code difference task were not processed correctly causing the Branch value to be overwritten by the original Origin value. This has been resolved. SF and IAM 2023.120230303 - Smoke test truncation correction Smoke tests are preliminary tests to reveal simple failures on several type of objects. The names of these objects are being used as input for the smoke test name, which is stored in the database. When these object names would become too long, a truncation error would arise in the Indicium log, causing the system flow responsible for executing the smoke tests to fail. This is now resolved.

Hi everyone!We’ve released the following platform improvements this week: SF 2023.1 20230303 - Execute Code difference delta actions in merge session When merging from Origin to the Branch, any conflicts that were resolved using the Code difference task were not processed correctly causing the Branch value to be overwritten by the original Origin value. This has been resolved.

March 3, 2023:Full 2023.1.13 release Fixes: When reopening the last opened document after refreshing the browser window, its icon was not displayed. This has been fixed. We fixed an error message being shown when canceling a task from a start object or the menu. We also fixed an issue with start objects being started twice.  Hello everyone,An important change in this release is, that we improved the responsiveness of controls in a form. This might require some adaptations to your model, so read the notes on this subject carefully.A new feature is the possibility to provide Indicium with a hint about your authentication provider(s), which will add the required OpenID providers to the login screen. We also improved the developer experience by adding support for refreshing the model and reloading the application model when it has expired.A full overview of all features, changes, and fixes can be found below.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal GUI's progress. Universal GUI version 2023.1.13Do 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.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium.Download the Universal GUI version 2023.1.13 here ContentsUniversal GUI version 2023.1.13 New Provide an authentication provider hint to Indicium Refresh model from profile menu Reloading on model change History browsing supported Changed Improved responsiveness Toolbar positioning and density improvements Activate the form on double click Single cube view button hidden Mandatory indication changes to indeterminate checkboxes Minor fixes and tasks Fixes for process flows Fixes for the grid Fixes for documents Fixes for tasks Fixes in the layout What we will be working on next sprint Questions or suggestions? New Provide an authentication provider hint to IndiciumCommunity ideaIt is now possible to provide Indicium with a hint about the authentication provider that should be used by adding the setting 'loginAuthProviderHint' to the config.json file. It can be used for single Indicium instances with multiple OpenID providers configured.Imagine a scenario where three OpenID providers are configured: Google, Facebook, and AzureAD.You can host a Universal GUI with the 'loginAuthProviderHint' set to "Google, Facebook" to show both OpenID Provider buttons for signing in. You can host another Universal GUI for your employees on a different URL with the 'loginAuthProviderHint' set to "AzureAD". To provide a hint that allows only local sign-in, you should add "localLogin".If, after filtering the options on the hint, only one option is available, it will be chosen automatically.A login screen with three authentication providers Refresh model from profile menuWe have added an option to refresh the model. It is available from the profile menu (this is the menu you can open from the top-right corner). This option will reload both the model on Indicium and the Universal GUI. It is only available to users configured as developers in IAM.Refresh the model from the profile menu Reloading on model changeWe now support reloading the application when the application model has expired. Just click 'Update now' to reload and use the new model. This is the same as when the GUI version is renewed. It also adds an indicator to the user profile menu if a user closes the message without updating (now).Reload the application on a model change History browsing supportedWe now support history browsing. With history browsing, you can use the back and forward buttons in your browser or device to navigate between previously active subjects. Reloading the Universal GUI, for example, by pressing F5 or using the refresh model function, re-opens the last opened subject.It has some limitations:When browsing back, a subject with a selected tab and an active record will be restored only if it was present as an open document. If it is closed or if the entire Universal GUI is reloaded, the subject will start in a default state. After reloading, only the last subject is restored. Open documents are not. In this first version, the history browsing does not recognize an opened detail subject (double clicking on a tab header or detail tile). Changed Improved responsivenessThis change may require some adaptations to your model in the Software Factory.The Form component of the Universal GUI has been designed to be responsive. This means that editors will fill out 100% of the available space while respecting side-by-side placement.In the Software Factory, the width of the fields is configured in pixels, whereas the Universal GUI's responsive design asks for percentages. Previously, this calculation did not respect hidden controls ('hidden outside form' or number 3 in the layout logic). This resulted in empty space around the visible controls on the same line, which looked a bit messy. This has been fixed for the Form component and the task/report parameter input. Of course, the open space will remain reserved for controls defined as 'hidden inside form' or number 2 in the layout logic.Before:Form component: field width before the changeAfter:Form component: field width after the changeThis change is also visible in the Form list component. Previously, the width of controls placed side-by-side was spread equally over the number of controls without the possibility to change it. Now, the Universal GUI will listen to the field width configured in the Software Factory with the algorithm described above. Toolbar positioning and density improvementsPreviously, the toolbar containing the search and filter bar and the action bar had the width of the entire subject. When an area of the subject only contained detail subjects with their own toolbars, it could be unclear which buttons belonged to which subject.Now, the toolbar only has the width of the components of the subject, so it no longer extends above the details. In addition, we have removed the Filters and Actions labels.Before, the toolbar spanned the entire widthNow, the toolbar is only as wide as the components it applies to Activate the form on double clickThe grid and the card list will now activate the form on a double click if no double-click task is set. Single cube view button hiddenWhen a cube subject contains a single cube view, a button for it in the toolbar is not necessary. From now on, it will be hidden. Mandatory indication changes to indeterminate checkboxesIf a checkbox is set to mandatory (menu Data > Domains), it may give users the impression that they have to select it, even if they do not want to. To address this issue, you can set the checkbox to a default state of 'null' (indeterminate). After selecting an indeterminate checkbox, the mandatory indicator will now disappear, making it less confusing for the user. Minor fixes and tasksFixes for process flowsIn some situations, in a process flow in combination with an Add row process action, a 'Bad Request' error could occur. This has been fixed.Fixes for the gridWhen an image column was used as a grid group, the image would not be displayed. This has been fixed. When canceling touch multiselection in the grid on a touch device, it would wrongly keep showing the multi-select checkboxes. This has been fixed. When scrolling in the grid on a slower touch device, the performance would be somewhat worse because the active row was changed wrongly with each swipe. This has been fixed. We also made some minor extra performance improvements in the grid.Fixes for documentsWhen an auto-saving document is open (with or without changes), it is now possible to log off via the profile menu. The document will be saved automatically. When an already opened document was re-activated, it sometimes opened empty. This has been fixed. When reopening the last opened document after refreshing the browser window, its icon was not displayed. This has been fixed.Fixes for tasksWhen a task is configured with the refresh option Row, the Universal GUI now refreshes all the selected rows after the task has been executed successfully. Note: as of 5 selected records and up, the entire set is refreshed instead of only the selected records plus their logic. At some point, the latency on the number of network calls will overrule the performance win. The form controls in a task popup would show as read-only when something went wrong during the execution. This has been fixed. Now, the task popup is editable after an error. When using [CTRL]+click to select grid rows, the Universal GUI would not always take all the selected rows into account when executing a task. This has been fixed. We fixed an error message being shown when canceling a task from a start object or the menu. We also fixed an issue with start objects being started twice. Fixes in the layout The Label control type now listens to the Field width setting (menu Data > Domains > tab Form > tab Domain). In compact mode, the progress bar is now aligned vertically in the center of the grid. SVG icons in the tree are now limited to 20px in compact mode and 24px in comfortable mode to keep the tree tidy. A form can be divided into groups with or without a title. Without a title and only a separator, the separator line was shown sticky against the first control. Now, the separator has proper padding. The bottom borders of buttons in the toolbar were missing. This has been fixed. A missing bottom border What we will be working on next sprintThe next sprint we will be working on: Custom settings for the grid line height sizes.  A new process action that allows you to copy anything to the clipboard. Tooltip translations in action bars and form controls.  Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,In this sprint, we have changed the way starting process actions works when they are canceled. Note that this is a breaking change, so read these release notes carefully.We also fixed some issues.You can read more about the Windows and Web GUI's features, in the [GUI user manual](https://docs.thinkwisesoftware.com/docs/user/winweb). We will keep you updated regularly about the Windows and Web GUI's progress.* Download Windows GUI 2023.1.13 here.* Download Web GUI 2023.1.13 here.Contents of this releaseBreaking Starting process flow actions after cancelation Minor fixes and tasks Questions or suggestions?Breaking Starting process flow actions after cancelationWindows GUI Web GUIWe have changed the way starting process actions works when they are canceled.Previously, an action like addrow would only start the process flow when it succeeded. If a user canceled the flow or if the row could not be saved, the process flow would abort, even if the next step had a red arrow (or unsuccessful flow) that should be followed.This has been changed for nearly all unsuccessful statuses. Now, a process flow will no longer be aborted if one of the following starting actions is unsuccessful:Add row Edit row Delete rowOnly cancellation by the user will abort the process flow.We think that a process flow should not be started if the starting action has been canceled by a user. If you think differently, please let us know in the Thinkwise Community!As this is a breaking change, we have added a global extended property called cancelStartingProcessActionWillCancelProcessFlow.This property is default false, which means the mentioned changes will apply. If you set it to true, you will regain the way it has worked before.This property has been introduced only as a transition to the new way and to offer time to change your process flows. It will be removed for the Windows and Web GUIs as of Thinkwise Platform version 2023.2.10.0.Minor fixes and tasks- Windows GUI If a user had an expired password due to a password expiration policy, the Windows UI returned an undefined "Authentication failed..." message. It will now return a more helpful "Password expired" error message.We have also fixed two problems in the Windows GUI regarding the edit mode in a grid.- Windows GUI We have fixed navigation with Enter in a grid in edit mode. If you used Enter to leave a row, the row was saved, but the focus was lost, and you could not continue navigating with the keyboard. This problem no longer occurs.- Windows GUI We have fixed clicking a checkbox with a mouse. When clicking a checkbox in an editable grid, you needed an extra click to toggle the checkbox, or it would only toggle each other row. Now, a single click suffices to toggle checkboxes in grid edit mode.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,A breaking change in this release is that identity properties can no longer be set using a default procedure, and the input parameter of an identity column can no longer be used in a process flow. We have also improved the error messages for data type violations and the system flow logging. For the Universal GUI, we have added support to limit the available authentication options on Indicium's login page.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 2023.1.13 here. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2023.1.13 here.  ContentsAbout Indicium BREAKING Identity column as parameter New Authentication provider hints Changed Improved system flow error logging Minor fixes and tasks Questions and suggestions BREAKING Identity column as parameterIndiciumTo prevent problems, you can no longer set identity properties using a default procedure. Indicium will log a warning and skip the property.The same applies when the input parameter of an identity column is used in a process flow. Then, too, the value will be skipped. New Authentication provider hintsIndiciumWe have added support for the Universal GUI to allow the limitation of the available authentication options on Indicium's login page. With it, two Universal GUIs on different domains can each show their own authentication options to the user without needing two instances of Indicium or IAM.For more information, see the Universal GUI 2023.1.13 release notes. Changed Improved system flow error loggingIndiciumWe have improved the logging of system flows. Previously, it was hard to see when an exception was thrown. In this release, we have added more descriptions about whether it went wrong while starting, executing, or ending the process flow. Minor fixes and tasksIndiciumWe fixed an issue where patching filenames containing a hashtag to a file storage column would cut off the value at the location of the hashtag character. E.g.: "example#file.txt" would end up as "example" inside the resource. Questions and suggestionsQuestions or suggestions about the release notes? Let us know in the Thinkwise Community!  

Hi everyone!We’ve released the following platform improvements this week: SF 2023.1 20230214 - Correct user_defined_dttp for upgraded uniqueidentifier domains During the upgrade to platform version 2022.2, a value has been changed in the base table data of "dttp" regarding uniqueidentifier domains. This change has corrected the placement of the uniqueidentifier datatype inside generated source code. Whilst the base data has been corrected, domains that existed pre-upgrade may still have an incorrect value for field user_defined_dttp which causes the domain name to be used inside generated source code rather than the uniqueidentifier datatype. This has been fixed as both a hotfix and in the Upgrade script for 2023.1.

  February 15, 2023Hotfixed 2023.1.12.0 to version: 2023.1.12.1 A crash could occur when opening a resource scheduler in Universal 2023.1.12.0 after having opened the same scheduler in 2023.1.11 or earlier. This has been fixed.Hello everyone,In this sprint, we have added support for OAuth login, support for task and report tiles, and record navigation with the arrow keys. Please read on for a complete overview of all new features, changes, and fixes.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 GUI's progress. Universal GUI version 2023.1.12.1Do 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 the appsettings.json. The Universal GUI only works with version 2021.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium. Download the Universal GUI version 2023.1.12 here Contents of this release Universal GUI version 2023.1.12.1 New Support for OAuth connectors Support for task and report tiles Changed Record navigation in default editable grid Opening a subject looks smoother and does not flicker anymore Active application hook Timescales and custom timescales Minor fixes and tasks What we will be working on next sprint Questions or suggestions? NewSupport for OAuth connectorsThe Universal GUI now supports the use of OAuth connectors as process actions in your process flows. This includes both the login and the refresh token connectors. You can read more about the OAuth connectors in our Documentation.With the OAuth login connector, you can safely authenticate and log in using an external provider. The OAuth login connector requests the user to log in at an external provider, which results in a login token that Indicium receives. This token can be used in follow-up process actions to request data from the external provider.You can also use the OAuth refresh token connector in your process flows.To use the OAuth connectors, you need Indicium version 2023.1.12 or higher. Support for task and report tilesThe Universal GUI now supports task and report tiles. Adding task and report tiles is supported by Software Factory version 2022.2 and higher.You can add task and report tiles under User interface > Screen types > tab Design. Task and report tiles support displaying badges.Example of two task tiles with badgesChangedRecord navigation in default editable gridYou can now navigate through records in a default editable grid using the arrow keys. This gives an even faster editing experience.Drop-down controls use the arrow up and arrow down keys to open the drop-down at the moment.In those cases, these arrows won't navigate to another record. Opening a subject looks smoother and does not flicker anymoreWe have improved the styling of the loading element of a just-opened subject. Opening a subject has become smoother and does not flicker anymore. To achieve this, we have removed the paper with a background color around the spinner element.  Active application hookWe have added a hook to the root element of the web page of the GUI. It indicates the active application and can be used to bind custom CSS to a specific application. The hook is called data-active-application, and you can prefix any CSS selector with html[data-active-application="insights"] to style only that active application. Timescales and custom timescalesIn the new Thinkwise Platform release (version 2023.1), the Scheduler has been made a formal part of the Software Factory. It is available in menu User interface > Schedulers.Universal GUI supports the formalized Scheduler, which means that custom timescales are available now.The highest timescale will be used as the scheduler's scale and the lowest for the scheduler's cells. The lowest timescale and any other available timescales will become scheduler headers. For example, if you customize one year, one month, and one day, your scheduler will scale across a year, the cells will be one single day, and a header will show which day and month.It is possible to not show the lowest timescale header (in the previous example: day) by clearing the Labels for lowest timescale checkbox.Just like before, the highest two headers are combined when relevant to save space, for example, by placing the year number behind the month or before the week number.You can configure all kinds of variants, but at the moment, some of them will not show up properly yet. In this release, we have focused on the most common configurations of the 2023.1 platform release:Both default timescales we offered before Year-month-day Year-week-day Day-hour Quarter as a header Quarter as a cell For now, we have removed the option to initially look back one month in time. This functionality will be replaced later by the Sliding window option. Minor fixes and tasksWe have improved the caching of images and icons shown in grids and forms. This leads to fewer network requests to Indicium. If Field number of positions further was set to 2 or higher, the following control types would wrongly fill up that space: This has been fixed. The space will be empty instead, as it should be. IMAGE_LINK, IMAGE_UPLOAD and IMAGE_BLOB MULTILINE HTML SIGNATURE  What we will be working on next sprintThe next sprint we will be working on:Smarter positioning of the action bar if there are details Grid performance on mobile Reload model from user menu Stability improvements and bugfixes Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvements this week: SF 2023.1Connect domain ID in data migration of Tab variant map data mapping In the 2023.1 release, the column dom_id has been added to the primary key of table tab_variant_map_data_mapping. During the Upgrade, the column did not get the intended value. This has been corrected in the Upgrade script. IAM 2022.2 and up20230210 - Updated self-rename and self-deletion of user prevention A previous fix to prevent self-renaming and self-deletion of users in IAM turned out to be a bit too harsh, since it was also no longer possible to update any additional values of a user's own user within IAM. This has been fixed.

Hello everyone,In this sprint, we have fixed a few bugs. Read on for more details on what has changed.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 2023.1.12 here. Download Web GUI 2023.1.12 here.Contents of this releaseMinor fixes and tasks Minor fixes and tasksWindows GUI - We have fixed a bug where you would get an error message when starting a task from a tree component while you still had unsaved changes in an auto-save form. The error message was "This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row". Windows GUI - We have fixed a bug where the process action Close all documents would not actually close all documents from the currently active application. This process action was used in the Switch branch task in the Software Factory.

Hello everyone,In this release, we introduce a new manifest schema version that will be used by the Software Factory in platform version 2023.2. We have added the possibility to specify more than one upgrade path for database products from the same version. We have also fixed some regressions that were introduced in version 3.0.0.​​All the examples in this release note post use YAML for readability but JSON is also supported.Download the Thinkwise Deployment Center 3.1.0 here. ContentsManifest schema version 3 Model property for Application products The defaultDatabaseName property has been moved Package type keys SyncModel package type Renamed supportedVersions version property to upgradesFrom Encoding Full examples New Multiple upgrade paths Allow install into empty database Changed (GUI) Also use defaultDatabaseName during upgrade/hotfix/syncModel Install and upgrade flow step order changed Fixed DefaultDatabaseName property not read in manifest schema version 2 Indicium Basic installation is not detected when upgrading Questions or suggestions? Manifest schema version 3This version of the Deployment Center introduces support for a new manifest schema version. The main reason to create this new version is to change the default encoding used for scripts from windows-1252 to utf-8, but we also took the opportunity to change some other things. The Software Factory will start using this new schema in the 2023.2 platform release.Model property for Application productsSome properties that describe information about the model of an application have been moved to a model property:schema: 2products: - type: "Application" projectId: "MY_APPLICATION_MODEL" version: "3.0.0" metaVersion: "2022.1"This must be specified in manifest schema version 3 as:schema: 3products: - type: "Application" model: id: "MY_APPLICATION_MODEL" version: "3.0.0" metaVersion: "2023.2"This is only the case for products using the `Application` type, as `model:id` and `model:metaVersion` cannot be overwritten for `IAM/SF/Upcycler` products:schema: 3products:  - type: "IAM"    # The IAM/SF/Upcycler types use an implicit value for model:id and consider model:version to be the same as model:metaVersion.    # Because of that, there is no model property, and only version has to be specified.    version: "2023.2" The defaultDatabaseName property has been movedThe defaultDatabaseName property can be used to let the Deployment Center know what the default name of the application database should be.In schema version 2, this property was part of the install package:schema: 2products: - type: "Application" # etc. packages: - type: "Install" path: "Install" defaultDatabaseName: "MY_APPLICATION_DATABASE"It was only used during the installation flow and (using an appsetting for the GUI) as the default name for a script variable that can be used during the post model synchronization script.In schema version 3, the property has been moved to the product level:schema: 3products: - type: "Application" defaultDatabaseName: "MY_APPLICATION_DATABASE" # etc.When using schema version 3, the Deployment Center will also try to use this value during the upgrade, hotfix, and syncModel (for selecting an IAM database) flows.See (GUI) Also use defaultDatabaseNAme during upgrade/hotfix/syncModel for more information.Package type keysIn manifest schema version 2, the packages property inside an IAM/SF/Upcycler/Application product used to be an array. Each item had to specify a type to indicate what kind of package it was:schema: 2products: - type: "Application" # etc. packages: - type: "Install" path: "Install" - type: "Upgrade" path: "Upgrade" supportedVersions: # etc. - type: "Hotfix" path: "Hotfixes"This makes it seem like a product can support multiple packages of the same type, but the Deployment Center code never accounted for that. It was an array due to a technical limitation in the code which read the manifest. This has since been changed. To avoid confusion, the type property has now been turned into specific property keys on the packages property.schema: 3products: - type: "Application" # etc. packages: # Type values are turned into property keys. install: path: "Install" upgrade: path: "Upgrade" supportedVersions: # etc. hotfix: path: "Hotfixes" syncModel: path: "MetaModel"SyncModel package typeIn manifest schema version 2, the package that described to the Deployment Center that a product had the ability to synchronize the meta model into an IAM was inferred by checking if a MetaModel directory was present as the sibling to the directory where an Install or Upgrade package was located.This was not ideal because it added a hidden feature of sorts to the manifest, and the path to the directory containing the package could not be changed. In schema version 3, the syncModel package can be added to a database product and its path must be explicitly specified like in the other packages:schema: 3products: - type: "Application" # etc. packages: syncModel: path: "MetaModel"The syncModel package is considered optional for SF, Upcycler and Application product types, in the sense that an install or upgrade package will not break if it is not specified. They will simply skip the IAM synchronization step during deployment, which may or may not be what you want, depending on your deployment strategy.For the IAM product type, it is considered mandatory to have a syncModel package. This is because every IAM is expected to have at least its own model synchronized to it.Renamed supportedVersions version property to upgradesFromYou could specify an upgrade path from version 1.0.0 to 2.0.0 for a database application in schema version 2 as follows:schema: 2products: - type: "Application" projectId: "MY_APPLICATION_MODEL" version: "2.0.0" metaVersion: "2022.1" # etc. packages: - type: "Upgrade" path: "Upgrade" supportedVersions: # Upgrade from version 1.0.0 - version: "1.0.0" # to 2.0.0 upgradesTo: "2.0.0" # using the scripts contained in directory 2.0.0 (relative to the package path, which itself is relative to the manifest location) path: "2.0.0"This remains practically the same in schema version 3, but the version property did not immediately convey to users that it was the source version from which the upgrade could be performed.To clarify what the property's relation is to the upgradesTo property, it has been renamed to upgradesFrom. version will remain available as an alias to upgradesFrom to make it easier to manually migrate manifests from schema version 2, but we recommend using upgradesFrom from now on.schema: 3products: - type: "Application" model: id: "MY_APPLICATION_MODEL" version: "2.0.0" metaVersion: "2023.2" # etc. packages: upgrade: path: "Upgrade" supportedVersions: - upgradesFrom: "1.0.0" upgradesTo: "2.0.0" path: "2.0.0"EncodingIn platform version 2022.1, the Software Factory has been changed to generate scripts in utf-8 encoding instead of the previously used windows-1252 encoding. To support this, manifest schema version 2 was updated to include the ability to specify the encoding to use for scripts in several places of an IAM/SF/Upcycler/Application product.The default had to remain windows-1252 for backwards compatibility reasons. This meant that the Software Factory also had to specify that utf-8 had to be used when it generated a deployment package:schema: 2products: - type: "Application" # Override default script encoding for the entire product. encoding: "utf-8" # etc.In schema version 3, this will no longer be needed, because the default has been changed to utf-8. Any scripts generated by a Software Factory older than 2022.1 can still be specified as using windows-1252 by using the encoding on the package or supportedVersion level:schema: 3products: - type: "Application" model: id: "MY_APPLICATION_MODEL" version: "3.0.0" metaVersion: "2023.2" # Encoding does not have to be specified as utf-8 since that is now the default. packages: upgrade: path: "Upgrade" supportedVersions: - upgradesFrom: "1.0.0" upgradesTo: "2.0.0" # 1.0.0 to 2.0.0 was generated by a 2021.3 Software Factory and thus uses windows-1252 encoding. # encoding: "windows-1252" files: - "1.0.0/020_Upgrade.sql" # etc. - upgradesFrom: "2.0.0" upgradesTo: "3.0.0" # 2.0.0 to 3.0.0 was generated by a 2023.2 Software Factory so the scripts use the new utf-8 default. path: "3.0.0"Full examplesschema: 3products: - type: "Application" model: id: "MY_APPLICATION_MODEL" version: "2.0.0" metaVersion: "2023.2" dependencies: - "CompatibilityLevel140" defaultDatabaseName: "MY_APPLICATION_DATABASE" packages: install: path: "Install" upgrade: path: "Upgrade" supportedVersions: - upgradesFrom: "1.0.0" upgradesTo: "2.0.0" path: "2.0.0" hotfix: path: "Hotfixes" syncModel: path: "MetaModel" - type: "IAM" # "SF", "Upcycler" version: "2023.2" dependencies: - "CompatibilityLevel140" defaultDatabaseName: "MY_IAM" # "MY_SF", "MY_UPCYCLER" packages: install: path: "Install" upgrade: path: "Upgrade" supportedVersions: - upgradesFrom: "2023.1" upgradesTo: "2023.2" path: "2023.2" hotfix: path: "Hotfixes" syncModel: path: "MetaModel"NewMultiple upgrade pathsThe Deployment Center now considers the supportedVersions section of the upgrade package type a graph instead of a sequential path. This makes it possible to specify more than one upgrade path from the same source version.We do still recommend that upgrades should be performed sequentially in the order they were developed. However, if you have created an upgrade from one major version to the next while skipping any version in-between, you will no longer have to maintain a separate manifest for that.The Deployment Center will always pick the path with the fewest steps/edges.The summary screen will also mention which path the Deployment Center is going to use:The selected upgrade path upgrading an IAM database from 2022.1 to 2023.1ExampleGiven the following manifest:schema: 3products: - type: "Application" model: id: "MY_APPLICATION_MODEL" version: "3.0.0" metaVersion: "2023.2" dependencies: - "CompatibilityLevel140" packages: upgrade: path: "Upgrade" supportedVersions: - upgradesFrom: "1.0.0" upgradesTo: "1.1.0" path: "1.1.0" - upgradesFrom: "1.1.0" upgradesTo: "1.2.0" path: "1.2.0" - upgradesFrom: "1.2.0" upgradesTo: "1.2.1" path: "1.2.1" - upgradesFrom: "1.2.1" upgradesTo: "2.0.0" path: "2.0.0" - upgradesFrom: "2.0.0" upgradesTo: "2.0.1" path: "2.0.1" - upgradesFrom: "2.0.1" upgradesTo: "3.0.0" path: "3.0.0" - upgradesFrom: "1.0.0" upgradesTo: "2.0.0" path: "1.0.0_to_2.0.0" - upgradesFrom: "2.0.0" upgradesTo: "3.0.0" path: "2.0.0_to_3.0.0"The upgrade package contains the following steps/edges:1.0.0 -> 1.1.0 1.1.0 -> 1.2.0 1.2.0 -> 1.2.1 1.2.1 -> 2.0.0 2.0.0 -> 2.0.1 2.0.1 -> 3.0.0 1.0.0 -> 2.0.0 2.0.0 -> 3.0.0The target version of the application is 3.0.0, so if the database that is being upgraded reports it is currently on version 1.0.0, there are three possible paths for the upgrade. The Deployment Center will always pick the path with the fewest steps, so in this case it will use (2 steps):1.0.0 -> 2.0.0 2.0.0 -> 3.0.0Instead of (5 steps):1.0.0 -> 1.1.0 1.1.0 -> 1.2.0 1.2.0 -> 1.2.1 1.2.1 -> 2.0.0 2.0.0 -> 3.0.0Or (6 steps):1.0.0 -> 1.1.0 1.1.0 -> 1.2.0 1.2.0 -> 1.2.1 1.2.1 -> 2.0.0 2.0.0 -> 2.0.1 2.0.1 -> 3.0.0Allow install into empty databaseThe Deployment Center will now allow empty databases as valid targets for the installation flow of IAM/SF/Upcycler/Application products. This can be helpful when deploying to Azure, because you will be able to create a database using the desired tier beforehand.It will consider the database empty if it meets all of the following requirements: It contains no objects other than ones added by Microsoft. It is not a database with a reserved name (e.g. 'master', 'model' etc.). It is not otherwise a system database. Summary screen showing IAM being installed into an empty database target.Changed(GUI) Also use defaultDatabaseName during upgrade/hotfix/syncModelWhen using a schema version 3 manifest, the Deployment Center GUI will now pre-fill the database selection drop-down lists with the value of defaultDatabaseName if a database with that name is available on the connected server.So, given the following manifest:schema: 3products: - type: "IAM" defaultDatabaseName: "THINKWISE_IAM" # etc. - type: "SF" defaultDatabaseName: "THINKWISE_SF"And starting an upgrade flow for the Software Factory:THINKWISE_SF is pre-selected during database selection because a database with that name exists on the server.And selecting to synchronize the meta model into an IAM:THINKWISE_IAM is selected because that is the defaultDatabaseName of the IAM product in the manifest and a database with that name exists on the server.Install and upgrade flow step order changedThe installation and upgrade flow for SF/Upcycler/Application  products did not use the order specified by the flow. For example, the upgrade flow previously used the following order: Sync model into IAM Upgrade database Apply hotfixes However, the order as specified by the flow was actually:Upgrade database Apply hotfixes Sync model into IAMWhich was the intended order.This was caused by the deployment step copying the steps order from the review/confirmation step. This applied a grouping of the steps and caused the IAM "group" to come before the others.This grouping was introduced at a time where the IAM installation and upgrade flows also tried to allow configuring other components, such as Indicium. Because we do not allow this anymore, the grouping had become useless. Since it also influenced the deployment order in an unexpected way, we have removed it.FixedDefaultDatabaseName property not read in manifest schema version 2When we worked on version 3.0.0 of the Deployment Center to prepare for the introduction of schema version 3, changes were made to the way manifests were being read.This accidentally broke the defaultDatabaseName property when using schema version 2. This has now been fixed, so it is once again used during the installation flow.Indicium Basic installation is not detected when upgradingWe have fixed an issue where a selected IIS app was not being detected as an Indicium Basic installation when upgrading or reconfiguring.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,In this sprint, we have removed the '@' from the property names in AWS CloudWatch, added Server-Timing metrics for opening database connections, and updated the HTTP connector. We have also added support for sending two factor authentication and password reset token mails using the Microsoft graph API.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: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2023.1.12 here. 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 2023.1.12 here. Contents of this releaseAbout Indicium Breaking Remove '@' from the property names in AWS CloudWatch New Added Server-Timing metrics for opening database connections TSFMessage for datatype violations Microsoft Graph support Changed HTTP connector will now set a default Content-Length and User-Agent Minor fixes and tasks Questions or suggestions? BreakingRemove '@' from the property names in AWS CloudWatchWe have improved the property names of AWS CloudWatch. Some properties contained the `@` symbol, which made it difficult to use them in metric filters.We have removed the `@`, and property names are now fully written out. These property names are case-sensitive.Refer to the table below to view what has changed.Old property name New property name @t timestamp @l Level @@m MessageTemplate  NewAdded Server-Timing metrics for opening database connectionsServer-Timing metrics are returned in the responses to most requests to Indicium.We have expanded these Server-Timing metrics with information on how long it took to open the connection to the database and set the session variables. This improves insight into performance issues related to bad network connections between the web server and the database server. TSFMessage for datatype violationsWe have added a TSFMessage for when a data type violation occurs.In previous versions, a bad request response was sent with the message "Invalid Value 'X' for property 'Y'". Now, this response will also contain a TSFMessage, explaining why the violation happened. Microsoft Graph supportWe have added support for sending two factor authentication and password reset token mails using the Microsoft graph API.To enable this, you need to add the following data to the appsettings.json:"Email": { "Provider": "MsGraph", "MsGraph": { "ClientID": "<Your clientID>", "ClientSecret": "<Your ClientSecret >" "TenantID": "<Your TenantID >" }}If you are hosting your application in Azure, maybe you can skip the MsGraph section because the credentials can be inherited in Azure.We also made it possible to write the SMTP settings in the same way, though we still support the current way. An example of  the new way:"Email": {            "Provider": "SMTP",            "SMTP": {                        "Server": "<Server>", "Port": <Port>, "UseSSL": <SSL>, "Username": "<Username>", "Password": "<Password>",            }} ChangedHTTP connector will now set a default Content-Length and User-AgentThe HTTP connector process action now sets the Content-Length header to 0 for POST, PUT and PATCH requests that do not specify a request body or a Transfer-Encoding header.It also adds a default User-Agent header with the value Indicium/<version> to every request. Minor fixes and tasksWe have fixed an issue with the *Delete Row* process action. The output parameters were not propagated correctly. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hi everyone!We’ve released the following platform improvements this week: SF 2022.2 20230201 - Subroutine option copying from base models Regarding subroutine options - The same fix as  20230116 - Subroutine option copying from base models (https://community.thinkwisesoftware.com/product-updates/platform-improvements-for-week-3-3666) but implemented for 2022.2. IAM 2022.2 and up20230201 - Updated OpenID provisioning procedure In certain situations, OIDC user provisioning mapping relying on 'Contains' conditions for arrays would not function correctly, depending on the order of array- and non-array claim properties in the claims object. This has been resolved. IAM 2023.120230131 - Set mandatory false for managed identity field Fixed an issue where the task to switch file storage configuration types could not be executed because the use managed identity field was empty, even if the field was not being used.  

Hi everyone!We’ve released the following platform improvements this week: IAM 2022.2 and up20230125 - Prevent self-rename and self-deletion of user In a previous platform improvement a handler was added to the user screen which allowed the user to delete other users through the delete action in the ribbon. The problem was that by adding the handler it also became possible to delete your own user, which would obviously cause some other problems. That is why a fix has been released to disable the handler when any user selects their own user in the Users screen in IAM. IAM 2023.1 20230127 - Fix for IAM file storage not updating correctly Fixed an issue where some fields for IAM file storage locations would not update correctly.

Hello everyone,In this release, we have:Updated some checks used to determine application database information so the Deployment Center works with Thinkwise Platform version 2023.1. Changed the runtime of the Deployment Center from .NET Framework 4.6.2 to .NET 6. Added a setting to the Deployment Center GUI which can be used to skip the screen that asks for confirmation on, for example, whether a database backup has been created. Ensured that application initialization can properly be set for Indicium when using the IIS Administration API.Download the Thinkwise Deployment Center 3.0.1 here. ContentsNew Deployment Center updated to .NET 6.0 (GUI) Setting to skip manual checks screen Fixed Upgrade summary states wrong version Setting application initialization for Indicium through IIS Administration API Questions or suggestions? NewDeployment Center updated to .NET 6.0The Deployment Center CLI and GUI have both been updated to run on .NET 6. The main advantage of this is that, in the future, we will be able to offer a version of the CLI that works on Linux.Due to the amount of work that was involved into updating from .NET Framework 4.6.2 to .NET 6, only an x64 build for Windows can currently be downloaded from TCP.If you urgently need a Linux build, please enter a ticket in TCP.The Deployment Center executables are shipped as a self-contained binary, which means that nothing else needs to be installed to use it on a machine. It has also somewhat increased the size of the binaries, however.Some native assemblies might be extracted to %TEMP%\.net when starting the program. If this location is an issue for your use case, it can be changed through a DOTNET_BUNDLE_EXTRACT_BASE_DIR environment variable. See https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?tabs=cli#include-native-libraries for more information.We plan to keep the Deployment Center up to date with the latest LTS version of .NET. This means the next update target will be .NET 8, which should be released later this year. (GUI) Setting to skip manual checks screenWe have added a Flow:ApplicationUpgrade:SkipManualChecks setting to twdeployerGUI.appsettings.json which, if set to true, skips the screen that mentions to backup your database and to stop Indicium before upgrading a database. This can be useful if you already documented or setup to do those things in your upgrade process. Fixed Upgrade summary states wrong versionThe upgrade summary for custom applications stated that the version being updated to was the meta version. This has been fixed to show the actual version of the application itself. Setting application initialization for Indicium through IIS Administration APISetting application initialization for Indicium through the IIS Administration API should now work as long as the latest release has been installed on the server. If you are using it, please download the latest release (6.0.0 at time of writing) from https://github.com/microsoft/IIS.Administration/releases.Some things to keep in mind while updating:It cannot be upgraded in-place using the installer, first de-install the previous version. Due to this, it is a good idea to backup the configuration files (located by default at %PROGRAMFILES%\IIS Administration\<version>\Microsoft.IIS.Administration\config). Remember to reconfigure the service to the way it was before. API keys should keep working if the configuration files are put back in the same location. Consult the documentation page for the IIS Administration API for more information on how to configure the service. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvements this week: SF 2023.120230116 - Subroutine option copying from base models Subroutine options are now limited to a single value per option when importing these option values from a base model. This prevents situations where functions such as tsf_user would have multiple schemabinding options when they are present in more than one base model. It is still possible to manually add more than one value for an option - this will be resolved in release 2023.2. 20230116 - Unit test type-output checks The fix 20221228 - Unit test performance improvement could cause Layout and Context output assertions regarding access types to not be included in the results section. This has been resolved. Unit tests for Layout and Context logic will now always store and show the assertions done on access types. IAM 2023.120230118 - Apply user rights to IAM fix The problem where code concerning the assignment of roles to members was missing from the script when executing user rights to the IAM database has been fixed.   

January 20, 2023Changed beta release to the full version: 2023.1.11 Hello everyone,In this sprint, we have added some new features and fixed some problems. Some highlights are: playing a sound while showing a message, and executing tasks upon double-clicking a card list, grouped tree, or resource scheduler.Please read on for a complete overview of all new features, changes, and fixes.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 GUI's progress. Universal GUI version 2023.1.11Do 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.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium. Download the Universal GUI version 2023.1.11 here Contents of this release Universal GUI version 2023.1.11 Breaking Fixed Field no. of positions New Execute double-click task from card list, grouped tree, or resource scheduler Play a sound while showing a message Changed addContext API Performance Improvement Import and Export immediately have been swapped in the overflow menu Minor fixes and tasks What we will be working on next sprint BreakingFixed Field no. of positionsThe form setting Field no. of positions further has been updated to match the behavior in the Windows GUI. For example, if you set the Field no. of positions further to 3, there will now be 2 positions above that field.This is a breaking change. If you are using Field no. of positions further in the Universal GUI, make sure to verify that the result is still as intended.You can find this setting in the Software Factory,  under the menu User interface > Subjects > tab Default/Variants > tab Components > tab Form.There is a known issue that some controls (multiline, HTML, image link, image upload, and signature) will claim the extra space given by Field no. of positions further for the control after them. This will be fixed in a later release. NewExecute double-click task from card list, grouped tree, or resource schedulerYou can now specify that a task will be executed automatically when a user double-clicks a card in a card list, a grouped tree, or the resource scheduler.Select Double click on record in the task's settings to set this up. Play a sound while showing a messageThe Universal GUI now supports playing a sound when showing a message. You can add sound to popups or snackbar messages.You can configure the sound file in the menu User interface > Messages in the Software Factory. Messages can be used in the following ways:Process flow messages Messages from application logic (Custom) task confirmation ChangedaddContext API Performance ImprovementWhen a task was performed on multiple selected records, each selected record would have its own HTTP call to add it to the staged resource. This process has been improved. The Universal GUI now executes one call to Indicium for the entire selected record set, which speeds up task execution.Indicium must be upgraded to the latest version as older Indicium versions don't support this feature.Executing a task with multiple records will not work correctly on Indicium versions older than 2023.1.10. Import and Export immediately have been swapped in the overflow menuIn the overflow menu of the grid, the options Import and Export immediately have been swapped. Minor fixes and tasksIn some cases, the label of a checkbox displayed '...', indicating text overflow. However, there was enough space to display more characters. This has been fixed. If a screen with task shortcuts was closed and reopened, the task shortcuts could stop working. This has been fixed. If you clicked on a task to continue with a process flow after auto-saving a record, the process flow would not start. You had to click on the task a second time to start it. This has been fixed. When clicking on a different tab in a form while in default edit mode, the tab would not be selected on the first click. You had to click on the tab a second time to open it, and you would not be in edit mode anymore. Now, you will switch to a different tab immediately without losing edit mode. When clicking on a different row in the grid, the tab page with the form in it would be selected for that row. Now, you can click on a different row without anything else changing. The alignment of the Model Insights options in the user profile menu has been improved. When adding or copying in a subject or switching records, the corresponding detail grid summary rows would remain, even though there were no detail records at that point. In these scenarios, the grid summary row is now updated as empty to reflect this. When a subject with change detection was opened, the first request to detect changes would not include @last_refresh_utc, even though the dataset had already been fetched when the subject was opened. This has been corrected. @last_refresh_utc now gets updated with each dataset refresh. What we will be working on next sprintThe next sprint we will be working on:Resource scheduler custom time scales - when used in combination with he 2023.1 platform, custom time scales can be configured as hours/15 minutes. Editable grid key up/down - this will allow the user to use key up or down to navigate the cells in a default editable grid. Task and report tiles - much like detail tiles components that show tasks or reports as large tiles OAuth login process flow action support - a process flow action can request the user to log in to an external party to obtain an OAuth token for the remaining process flow.

Hello everyone,In this sprint, we have fixed a memory issue, and support for Thinkwise Platform release 2021.1 has ended.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 2023.1.11 here. Download Web GUI 2023.1.11 here.Contents of this releaseBreaking Support for Thinkwise Platform release 2021.1 has ended New Open Link process action status codes Minor fixes and tasks Breaking Support for Thinkwise Platform release 2021.1 has endedWindows GUI Web GUI In accordance with our Lifecycle policy, the Windows and Web GUI support for Thinkwise Platform release 2021.1 has ended. Please upgrade to at least Software Factory release 2021.2 to use this Windows and Web GUI release. New Open Link process action status codesWindows GUI The Open Link process action now supports the following two status codes in the GUI:0 for successful -1 for unknown error Minor fixes and tasksWindows GUI - We have identified and resolved an issue where documents were being kept referenced in memory for the remainder of the process's lifetime. With this fix, a document's memory is freed up immediately after it has been closed. This might only become visible in the Windows task manager after some time. Windows GUI Web GUI - We have fixed an issue where, in some situations, a mandatory prefilter group would prevent the user from editing or inserting new data. They would encounter the message "This row does no longer exist". Questions or suggestions about the release notes? Let us know in the Thinkwise Community.

Hi everyone!We’ve released the following platform improvements this week: SF 2021.2 and up20230112 - Fix upgrade of mandatory varbinary columns When copying data from old tables to the new tables during an upgrade, mandatory varbinary fields will no longer be filled with an empty string if no data is present in the old table as this could not be implicitly converted. Instead it will be filled with some binary data that represents an empty string. SF 2023.120230109 - Exclude tab variant values from refs in task_copy_tab When copying tables, the option to also copy references would include table variant settings that cannot be copied to the new object. This has been resolved by excluding the values form being copied. 20230111 - Constraints correction for merge execution When deleting or renaming a task, report, table, tag, role or machine learning model, a constraint error could occur in certain cases when merging these changes to another branch regarding reachable objects, training data or user simulation. This has been resolved. 20230113 - Corrections in DB2 definition generation When generating the definition for a DB2 model, an error would arise for 2 control procedures. This has been fixed, resulting in a successful definition generation again. IAM 2023.120230106 - IAM file storage cleanup IAM installations upgraded over time from version 2019.2 or earlier to 2023.1 may have a lingering file storage override that can mess with the icons of IAM in 2023.1.  This has been resolved.

Hello everyone,In this sprint, we have added support for downloading reports directly when using resource staging, and fixed some minor issues.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: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2023.1.11 here. Contents of this releaseAbout Indicium Indicium - New Download reports directly when using resource staging Minor fixes and tasks Indicium - NewDownload reports directly when using resource stagingIndicium Indicium BasicWhen using resource staging, you can now download a report. This means it will be returned directly on the call to /commit the resource. You can force this by adding?direct_download=true to the URL.Previously, Indicium would return a response with a location header containing the location to download the report. Minor fixes and tasksWe have added support for exporting a table when running Indicium on Linux. Some specific logs did not show up in AWS CloudWatch and Azure ApplicationInsights. This has been fixed. The ‘Enable local accounts’ setting on the ‘Global settings’ screen in IAM, which can be used to turn off authentication via local accounts, was ignored by Indicium. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week:SF 2023.120221223 - Validation code fix for 3 validations There were 3 validations regarding control procedures with status development/review/disapproved, that did not provide a value for mandatory columns. This resulted in an error executing this validation. This has been fixed in the VALIDATIONS base model by providing the required values. Afterwards, be sure to generate your work model before validating again. 20221227 - Remove platforms in Thinkwise base models Some Thinkwise base models were supplying platforms to work models unintentionally. This has been resolved by removing them. 20221228 - Unit test performance improvement Unit test performance has been improved. The time it takes to assemble the unit test code and to perform declarative assertions after a unit test is executed has been sharply improved. The pop-up to preview unit test code is also a lot faster.  You can no longer provide input for button types when unit testing layout logic. These button types are to be treated like access types and mandatory states - stateless. Existing input mappings in unit tests for button types will be ignored IAM 2022.2 & 2023.120221230 - Additional delete handler for users In the 2022.2 version of IAM delete handlers were introduced to make it possible for developer to also delete a record by using the delete button in the ribbon. This wasn't working in the Users screen in IAM (Authorization > Users) so we introduced an additional delete handler that will take care of this from now on. Best wishes!On behalf of the Thinkwise Product Development team: we hope to welcome you back to our Community in 2023, and wish you all a great New Year's Eve!

 December 29, 2022Changed beta release to the full version: 2023.1.10.0. Improvement for issues found in the previous beta release: When selecting a non-alphanumeric column to provide the tooltip of an activity, the scheduler could crash. This has been fixed.   Hello everyone,In this sprint, we added support for the Thinkwise Platform release 2023.1,for example, for a number of new process actions, and a custum label for markers in the Maps component.In addition, Model insight is now available from the profile menu, which makes it easier to use this tool.A visual change is that the same scrollbar is now used throughout the entire applicationAs 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 GUI's progress.Universal GUI version 2023.1.10Do 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.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium. Download the Universal GUI version 2023.1.10 here Universal GUI version 2023.1.10 Breaking Support for Thinkwise Platform release 2021.1 has ended New Support for new process actions Custom look-up display column for Maps Support for the 'DisableZoomIn' extended property Support for dynamic input constraints Tooltip from translation in grid headers Improved user settings Changed Support for formalized Scheduler The same scrollbar in the entire application Changed and fixed in Model insight Minor fixes and tasks What we will be working on next sprintBreakingSupport for Thinkwise Platform release 2021.1 has endedIn accordance with our Lifecycle policy, Universal GUI support for Thinkwise Platform release 2021.1 has ended.Please upgrade to at least Software Factory release 2021.2 to use this Universal GUI 2022.2.13 release.NewSupport for new process actionsWe have added support for some new process actions in the 2023.1 platform release, Open link and Close all documents.For more information on these process actions, see the Thinkwise Platform version 2023.1 release notes (https://docs.thinkwisesoftware.com/blog/2023_1).Custom look-up display column for MapsBy default, a marker uses the tables' look-up display as a label in the Maps component.Now, it is also possible to use a custom label for markers. This is available in the 2023.1 platform release.In the menu User interface > Maps, you first must select the Use custom label column checkbox.Then, select the Label column you wish to use as a label for the marker.If the custom label is empty, no label will be shown.Support for the 'DisableZoomIn' extended propertyThe Universal GUI now listens to the DisableZoomIn extended property.See Extended properties https://docs.thinkwisesoftware.com/docs/sf/extended_properties for more information on extended properties.Support for dynamic input constraintsThe Universal GUI supports the dynamic input constraints which are available in the 2023.1 platform release.If you choose timing Immediate, it will be processed as On change. Immediate will be supported later on.Tooltip from translation in grid headersWhen hovering over a grid header, we will now show its tooltip if it is set in the Software Factory (menu User interface > Translations).The tooltip text provided is allowed to contain HTML to, for example, make text bold or cursive.Support for editors in a form/task/report and tooltip buttons will follow later on.Improved user settingsPreviously, user settings were indexed on the application ID, which meant that you would lose information likesplitter distances, the active resource scheduler view, and grid column sizes when a new application was created.Now, the user settings are indexed on alias, which is much less likely to change.We advise you to set an application alias (in IAM, menu Authorization > Applications > tab Form > field Application alias).This means your users will lose their settings only when installing this version and when the application alias changes.ChangedSupport for formalized SchedulerIn the new Thinkwise Platform release (version 2023.1), the Scheduler has been made a formal part of the Software Factory.It is available in the menu User interface > Schedulers.Universal GUI supports the formalized Scheduler, which means that in the future custom timescales will become available.At the moment, only the previous (heuristic) timescales will be available and can be configured limitedly.The same scrollbar in the entire applicationDue to a lack of updates and crashes from the third-party component we used for our scrollbars, we have decided to remove that component entirely.This means that all scrollbars are now similar to the scrollbars in the grid.Changed and fixed in Model insightWith the Model insight feature for developers, you can find which column, table, or variant you have selected in the Universal GUI.It also helps to debug breakpoint problems in your screen type.Model insight used to be only available if "debugMode": true was added to the config.json file.This is no longer necessary. Now, developers can open and close Model insight from the profile menu if they have been configured as a developer in IAM.Model insight available from the profile menuWe also fixed two problems.The first is that Model insight would reopen after it had been closed and a new subject was opened. This has been fixed.It will now only reopen when reopened from the menu.The other problem was that the screen type breakpoint information used to have a high probability of overlapping important contentsince it appeared in the top right of the subject.It is now placed at the bottom left instead.Breakpoint information at the bottom leftMinor fixes and tasks A sorted combo now shows all options in the grid, like a normal combo. In some cases, a default editable grid would become read-only: If there was an auto-refresh, and the user changed a field. If the user clicked save in the toolbar. If the user started a task. When the user tried to delete a row that was not allowed to be deleted. All these cases have been fixed now. What we will be working on next sprintThe next sprint we will be working on:Double click to execute a task from the: Scheduler Cardlist Tree Playing a sound when triggering a messageIssues:5033S - Process flow only gets started after click task button twice 5034S - Table (variant) immediately goes out of edit mode 5065S - Checkbox fields labels are cut short 5108S - Field nr positions further is showing strange behavior 85982 - Shortcut task doesn't respond

Hi everyone!We’ve released the following platform improvements this week: SF 2022.220221221 - Updated OpenID provisioning procedure Provisioning of new users will no longer cause issues when the default tenant is used, no tenant is matched via the claim or claim value mapping and user groups of the default tenant are mapped.    Existing provisioned users will now be moved to the default tenant if the user template does not result in a tenant being matched via the claim or claim value mapping. This in turn will cause the correct user groups to be mapped which are part of this default default tenant. SF 2023.120221223 - Validation code fix for 3 validations There were 3 validations regarding control procedures with status development/review/disapproved, that did not provide a value for mandatory columns. This resulted in an error executing these validations. This has been fixed by providing the required values.  

The new platform release is here, and what a release it is!To improve performance and reduce data storage, we completely changed the way version control is handled in the Software Factory.This really is a major change. It offers a lot of benefits but affects many screens and processes. Read all detailed release notes in the Thinkwise Docs.In this summary of the release notes, you will read about the key features of the version control and some other highlights.A major change in version control 'Project' and 'project version' renamed Branches and model versions (point in time) Branching and merging Some other highlights Domain input constraints New process actions Scheduler formalized Support for Azure Blob storage and SAS token Smoke tests Questions or suggestions? A major change in version controlUp to the 2022.2 release, version control in the Software Factory was handled by creating a copy of an entire model as a project version. This had a major drawback: since changes make up only a minor percentage of the entire model, all the other unnecessarily copied data made the Software Factory databases grow over time and become slower due to their size.To solve this problem, we will handle version control from now on by using temporal tables. These tables, also known as system-versioned tables, are a database feature that brings built-in support for providing historical data. It means that only the latest version of every project will be stored, and all old data will be moved to history tables. This way, data modifications will be stored only once. The historical data can be accessed whenever required by requesting them for a specific time in the past.The use of temporal tables offers great benefits:The main benefit is performance improvement by separating the operational data in the Software Factory from the non-operational data. Less operational data needs to be called upon when, for example, copying a project or branching/merging. It is no longer needed to store massive amounts of unnecessary data. Less risk that a developer accidentally modifies an earlier version of the model because they will always be working on the most recent version.The decision to use temporal tables has affected quite some screens and processes. We'll name a few here. 'Project' and 'project version' renamedIn the Software Factory, a project used to be similar to a model. However, outside the Software Factory, a project can be much more than just the application or part of an application being built.Since the Thinkwise platform is based on model-driven software development, we have decided to replace the term Project with Model. For example, the menu item Project overview is now called Model overview. To prevent confusion due to this change, the menu item Full model has been renamed to Model content. This better covers the core of the Software Factory and prevents confusion about how the word 'project' is used in daily life.‘Model’ instead of ‘Project’ Branches and model versions (point in time)Implementation of temporal tables means it is no longer required to copy all model data into a new project version to save a specific point in time. This means that project versions as we used to know them will cease to exist in the 2023.1 release.Instead, we will start using branches. These are versions of the same model that can differ from each other. Every model will have at least a MAIN branch and can contain one or more additional branches based on a specific point in time in the past.Within a branch, you can mark the situation at any point in time (except for the future) as a model version. This is similar to the branching model used in GIT, where branches are effectively a pointer to a snapshot of your changes.When necessary, you can compare two model versions, for example, between two branches or two points of time within one branch. It is also possible to mark a model version with a name for easy communication.A Model overview with branches Branching and mergingThe use of branches also changes the branching and merging processes. In the new situation, branching and merging consist of the following steps:When you create a new branch, it is no longer a stand-alone project branch but a branch within the model. You can base it on the current point in time, a specific point in time, or select a specific model version. The origin is tagged with the current point in time, and the branch is copied from that point in time. Create a branch from a point in time or a model versionWhen you create a merge session, changes are determined by comparing the situation at the origin point in time vs. the current point in time (i.e., the moment when the merge session started). When you execute the merge session, only changes from either the source or the origin are executed.To resolve conflicts, there are  now two situations, each with its own resolutions.The first situation is when an entity has been inserted in both the origin and the branch. In that case, you can choose not only what to do with the conflict actions but also with the dependent actions.In the other situation, an entity has been deleted or updated in both the origin and the branch or deleted in one and updated in the other branch. For these types of conflicts, you can choose what to do with the conflict action (not the dependent action). For example, when the ‘delete’ action of a table is chosen, the table is no longer available, so column ‘insert’ or ‘update’ actions cannot be executed. Some other highlights Domain input constraintsCommunity idea  Universal GUI Windows GUI with IndiciumWhen creating domains, it was already possible to add some static constraints (minimum and maximum values or lengths, and a pre-defined selection (Elements)). These constraints are applied to the database (stored data will be checked). Data is also checked by the UI and the API. However, if a domain is used in, for example, a view or a task, a static database constraint cannot be applied, though the UI and API will still check the input.Now, input constraints are available as a feature. This makes the Thinkwise Platform even more low code.An Input constraint is a more dynamic extension of a domain constraint. It is a simple check on entered data at the domain level, similar to the minimum and maximum values or lengths. Data stored on the database will not be checked, but the UI and API will not accept unallowed input and not process it. Using these constraints, it is no longer necessary to create default or layout procedures to perform these checks. New process actionsWe have added three new process actions:Open link - Opens a URL. By default, the link opens in a new tab in the web browser, but you can change that with an input parameter. It can either wait for a user to complete an action inside the opened link or continue the process flow right after opening the link. You can use this, for example, to direct users to an external payment environment in a new tab. After a successful payment, the process flow will continue inside the application. Merge PDF - Merges files in alphabetical order, as found in the source folder. The output consists of the merged PDF file and a JSON array with the absolute path of all the merged files. Close all documents - Closes all open documents. You can use this action, for example, when switching between different administrations inside your end application. This situation affects all documents, which, therefore, should be closed. Scheduler formalizedUniversal GUITo extend the configuration of the Scheduler component in the Universal GUI, we have made the scheduler a formal part of the Software Factory. The Schedulers screen allows more settings for customizing different scheduler views. In the future, this enables setting up different timescales. At the moment, only the previous heuristic timescales can be limitedly configured.So, the Universal GUI will no longer heuristically configure schedulers but rely on the configured schedulers in the model instead. Support for Azure Blob storage and SAS tokenWe have extended and improved the support for Azure:Azure Blob storage is now a supported file storage location. It is possible to authenticate with a managed identity or by specifying the Tenant id, Client id, and the Client secret. Azure files as a storage type now requires a username/SAS (Shared Access Signature) token combination instead of a username/password combination. The SAS token is required for all new Azure file storage configurations. Existing configurations have not been altered. However, if you clear the username/password for an existing configuration, the password field will be hidden, and the SAS token will become mandatory.  Smoke testsSmoke tests are now available in the Software Factory.Smoke tests are preliminary tests to reveal simple failures severe enough to, for example, reject an upcoming software release. In the Software Factory, you can use smoke tests to ensure a basic quality level of SQL queries in your application. SQL queries that are not placed on the database as application logic may be malformed. Running smoke tests will discover these malformed queries in advance instead of at runtime.The smoke tests also detect editable views without RDBMS editing support, ‘instead-of’ triggers, or handlers. They also detect outdated parameterization of logic, and some forms of outdated dependencies for views, triggers, and stored procedure logic on the database. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!