Hi everyone!We’ve released the following platform improvements this week: IAM 2022.1 and up20230403 - Performance improvement clean up system flow log The task to clean up system flow logging could potentially cause a lot of wait times. This service fix significantly improves the performance of this task, so that the wait times no longer occur.  SF 2022.2 and up20230331 - Show display type option Universal GUI version 2023.1.15 and up now supports display types for table tasks and table reports. After installing this platform improvement, the field will be available in the Software Factory.   For example, in the Table task screen:   SF 2023.120230405 - Fixed datetime check point in time In the check if the chosen point in time is in the future, the time was converted to UTC. However, it already is converted to UTC time by the GUI and only shown as local time. So the conversion was not needed and could result in false error message that the chosen point-in-time is in the future. This has been resolved by removing the conversion to UTC in the Default procedures.

Hi everyone!We’ve released the following platform improvements this week: SF and IAM 2023.120230330 - IgnoreFloatingLabelWidth support A new extended property is now available. It is called 'IgnoreFloatingLabelWidth' and ignores configured label widths in the model for form columns, task- and report parameters when the form control type in the Universal GUI uses a 'floating label'. Enabling this extended property will match the Universal GUI's form configuration more closely to the Windows GUI's.   For example: given the following form configuration in the Software Factory: The Windows GUI and Web GUI will visualize the form as follows: The orange color indicates the full-form element widths, including the label. The green color indicates only the input field widths.   The current behavior of the Universal GUI interprets this as follows: When you add the extended property 'IgnoreFloatingLabelWidth' and set it to 'yes', the label width will no longer be considered in the field width calculations when the control uses a floating label: This matches the Windows GUI's form layout more closely for input fields and allows for a smooth transition between GUI technologies.   Note: this may result in large labels getting too little space as floating labels in small input fields.   In the upcoming 2023.2 release, this will become the default behavior for any model that does not yet support the Universal GUI as a target platform. Any model with the Universal GUI as a target platform will remain unmodified unless the extended property 'IgnoreFloatingLabelWidth' has been set to 'yes'. The reason for not changing the default behavior for models supporting the Universal GUI as the target platform is that you may very well have taken the label width impact into consideration when designing the form layout for Universal GUI applications.   This service fix also enables this setting for the Intelligent Application Manager. In addition, this service fix also enables support for variant-specific parameter ordering for tasks and reports.

A hotfix release of the Universal GUI was requested to fix the latest production release:We've decided to revert this fix from the 2023.1.14.0 release:   Previously, switching between documents would briefly show the form with only one column, despite there being room for multiple columns. Also, the action bar would become visible with a slight delay. The fix was causing crashes on entrance of a new subject on iOS and Firefox in some cases and we also noticed incorrect representation of the breakpoint screen type in all browsers.This item is back on our backlog now.The 2023.1.14.1 release is now available to download in TCP.

Hi everyone!We’ve released the following platform improvements this week:IAM 2022.1 and up20230324 - Changing default status for model defined prefilters When editing prefilters from the Windows GUI or Web GUI, it is possible to deviate from the model settings by indicating whether a prefilter should be active by default. However, this setting was not saved in the IAM user preferences. As a result, the change was lost after restarting the GUI. We have corrected this so that the changes are saved again in IAM. IAM 2023.120230320 - API change for update data migration source ​​​​​We have released a platform improvement to address the job_id parameter of the add_job_to_update_data_migration_source_version task. After running the improvement, the API call can look as follows: Option 0 - Obtain from database: POST [indicium]/iam/sf/add_job_to_update_data_migration_source_version{  "model_id": "[MODEL]",  "branch_id": "[BRANCH]",  "select_data_migration_source_version_option": 0,  "runtime_configuration_id": "default"} Option 1 - Specific model version: POST [indicium]/iam/sf/add_job_to_update_data_migration_source_version{  "model_id": "[MODEL]",  "branch_id": "[BRANCH]",  "select_data_migration_source_version_option": 1,  "from_branch_id": "[BRANCH]",  "from_model_vrs_id": "2023-03-18T12:00:20.859Z"}  

March 24, 2023Full release 2023.1.14 Fixes: Since the last beta release, the clear and dropdown buttons of the lookup control were misplaced when the grid column got too narrow, causing the text to be out of view. Now, they disappear (again) when the grid column gets too narrow. We fixed regression on Safari and Chrome on iOS. Some screens would show an error due to toolbar positioning when the subject is opened. Because of this fix, the following fix is no longer available for iOS devices,: Previously, switching between documents would briefly show the form with only one column, despite there being room for multiple columns. Also, the action bar would become visible with a slight delay. These issues have been fixed. Update: we reverted this fix completely for all cases as part of the 2023.1.14.1 hotfix release.  Hello everyone,In this sprint, we have added support for changing the row height in a grid, tooltip translations on multiple components, persistent navigation URLs for history browsing, performance improvements, and more.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.14Do not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 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.14 here ContentsUniversal GUI version 2023.1.14 New Tooltip translations on prefilter buttons, task and report tiles, and task and report buttons Tooltip support on form editors New process action: Copy to clipboard Process flow progress indicator Configurable row height in grid Navigation URL now uses application alias when present Changed Performance improvement grid Performance improvement lookups Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New Tooltip translations on prefilter buttons, task and report tiles, and task and report buttonsThe Universal GUI now displays the configured tooltip translation on prefilter buttons, task and report tiles, and task and report buttons.If a task has a keyboard shortcut, it will be displayed next to the configured tooltip translation.Tooltip on a prefilter buttonTooltip on a task buttonYou can configure the translation in the menu User interface > Translations or in the object, task, or report. HTML formatting is allowed in tooltips. For example, to make part of a text stand out or add a bullet list.The example below shows the translation for a prefilter: Tooltip support on form editorsThe Universal GUI now displays the configured tooltip translation on editors of the general form and task/report parameter input. You can configure the translation in the menu User interface > Translations or in the subjects column of the task/report parameter. HTML formatting is allowed in tooltips, for example, to make part of a text stand out or add a bullet list.The customized tooltip overrules a potential tooltip on an overflowing label or value within the editor, to prevent multiple tooltips from being displayed.Tooltips are supported now on all editors, except for:HTML Checkbox Radio button LabelTooltip on a text editor New process action: Copy to clipboardThe Universal GUI now supports the new process action Copy to clipboard. This action allows you to take a value and copy it to the user's clipboard.The value can be a single-column value, multiple-column values combined, or something else.Depending on the browser or device, a user may get a question for permission to copy information to the clipboard.This process action is only available through a hotfix on the Software Factory/IAM version 2023.1. Process flow progress indicatorAn indeterminate progress bar will now appear as a thin line underneath the top bar once a process flow has been activated.A progress bar for a progress flow Configurable row height in gridIt is now possible to define the row height of the grid, just like in the Windows GUI. This means that the Universal GUI will take the setting Row height (px) into account.You can set the row height in the following locations:menu User interface > Subjects > tab Subjects > tab Default settings > tab Default settings > group Grid menu User interface > Subjects > tab Subjects > tab Default > tab Settings > group GridFor compact mode, the exact value provided will be used. For comfortable mode, padding is added to this setting. If comfortable mode is active, the row height value will always be at least the minimum touch target of 44px.Limitations for this iteration:When in edit mode, the controls do not scale. When the grid is editable, the row height value will be at least 36px.The grid header height follows the grid row height but adds a bit of spacing to emphasize the separation between the rows and the headers. Both the grid header and summary row have a maximum height cap, and the summary row has a minimum height of 40px. Navigation URL now uses application alias when presentThe navigation URL that is used for history browsing now uses the application alias. This makes it persistent and suitable to be bookmarked and shared. Changed Performance improvement gridWe have done a performance optimization on the grid component. Actions like refreshing a grid, switching records, and editing in the grid should all benefit from this optimization. Rendering additional records in the grid due to scrolling should also be faster. Performance improvement lookupsWe have optimized the loading time of lookups when entering edit mode by removing unnecessary network requests. This improves the performance on slower connections. Minor fixes and tasks When opening multiple screens with auto-save enabled, sometimes the auto-save stopped working correctly. This has been fixed. If no records were available in the default-editable grid after applying a filter, selecting Cancel would result in an error. This has been fixed. Combo images are now aligned horizontally in compact mode. This fix removes some safety guards on SVGs in combo images. Note that poorly formatted SVGs seemed to work before this change, but now might give different results. Ensure that there is no height/width information in the SVG if you do not intend to influence those properties. The GUI will size the SVG correctly, but it will try to conform to what the developer indicates as much as possible while keeping the SVG within bounds. Previously, switching between documents would briefly show the form with only one column, despite there being room for multiple columns. Also, the action bar would become visible with a slight delay. These issues have been fixed. Note: we've reverted this fix as part of the 2023.1.14.1 hotfix release and will take a look at it later on. We fixed regression on Safari and Chrome on iOS. Some screens would show an error due to toolbar positioning when the subject is opened. The HTML control no longer overlaps other controls when placed side-by-side. HTML fields would not show up when placed behind another field. This has been fixed. The Universal GUI no longer shows an error after closing a lookup dialog. This would happen after double-clicking a record if the lookup dialog only contained a grid component. If the Universal GUI encountered a view in which duplicate primary keys were found, the grid would crash with a nondescript error. We have created a clear error message for this situation:Since the last beta release, the clear and dropdown buttons of the lookup control were misplaced when the grid column got too narrow, causing the text to be out of view. Now, they disappear (again) when the grid column gets too narrow. What we will be working on next sprintThe next sprint we will be working on:Catching up with quick wins and quality-of-life stories. Performance optimization for showing lookup translations in the grid. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

  Hello everyone,In this sprint, we improved the behavior of the Use process procedure setting and fixed an error that could occur when switching screen type.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.14 here.* Download Web GUI 2023.1.14 here.Contents of this releaseChanged Process actions will always execute the logic on completion if ‘Use process procedure’ is set Changed the default timeout for windows - indicium basic connections Minor fixes and tasks Questions or suggestions?Changed Process actions will always execute the logic on completion if ‘Use process procedure’ is setWindows GUI With the setting Use process procedure, you can reference and use returned values (output parameters) from a process action in a process procedure.Previously, the Use process procedure check and the actual procedure call were only evaluated on completion if a process action had follow-up actions.For platform version 2023.1, this procedure will always execute on completion if Use process procedure is set. You can find this setting in the menu Processes > Process flows > tab Process actions > tab Performance.Changed the default timeout for windows - indicium basic connectionsWindows GUI The default timeout for windows - indicium basic connections is changed from infinite to 100 seconds We've added a new global extended property "indiciumRequestTimeout" so that you can change this to whatever you want.This setting is in milliseconds. The value '-1' can be used for an infinite timeout.Minor fixes and tasks - Windows GUI An error would occur if a detail screen contained a form list component, and the user changed the screen type in their User preferences tab in the ribbon. This has been fixed. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone, As technical writers, we publish release notes and documentation for the Thinkwise products every release. In addition, we structurally improve and extend the Thinkwise Documentation.Depending on the extent and impact of the structural changes, we will keep you informed about them. Some changes you may have already noticed; others may be new to you.You can find the Thinkwise Documentation at docs.thinkwise.com. Contents Clickable breadcrumbs ‘Platform deployment' now ‘Environment setup’ Containerized setup Getting started Expandable screenshots Questions or suggestions? Clickable breadcrumbsThe breadcrumbs above each page in the Thinkwise Documentation are now clickable. This facilitates navigation through the various levels of information.Clickable breadcrumbs ‘Platform deployment' now ‘Environment setup’An important change has been made to the ‘Platform deployment’ manual. It has been completely restructured. Each platform now has its own section, improving the overview of what you need to deploy the Thinkwise Platform in a specific environment. ‘Platform deployment’ has been renamed ‘Environment setup’. In addition, the Thinkwise Deployment Center has been given its own manual: 'Thinkwise deployment'. Further improvement of these manuals is an ongoing process in smaller steps.Read ‘Environment setup’‘Platform deployment’ is now ‘Environment setup’Containerized setupAs you can see in the screenshot above, we have added an entirely new chapter to the Environment setup. In the ‘Containerized setup’ guide, you can read how to deploy the Thinkwise Platform in a containerized environment.Read ‘Containerized setup’ Getting startedIf you have just finished the Thinkwise associate training and started working with the Software Factory, you may still need some help with the basics. To assist you, we have included a "Getting Started" manual that repeats the basic steps. For more detailed information, you can read the more specialized manuals in the Thinkwise Documentation.Read ‘Getting started’ Expandable screenshotsSome chapters in the Thinkwise Documentation contain a lot of screenshots to give you more assurance that your are on the right path. In some cases, to improve readability, we are going to make these screenshots expandable.See some expandable screenshots Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

A hotfix release of the Universal GUI was requested to fix the latest production release: The GUI no longer shows an error after closing a lookup dialog. This would happen after double-clicking a record if the lookup dialog only contained a grid component. The 2023.1.13.1 release is now available to download in TCP.

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.