Product Updates

Hi everyone!We’ve released the following platform improvements this week: IAM 2025.120250414 - Return default global configuration extended properties when none specified The procedure responsible for returning global configuration extended properties would not return the data of the default global configuration when no global configuration ID was specified. This has been fixed. 20250417 - Improve performance of get_gui_drag_drop_link We made a change to the underlying view that ensures procedure get_gui_drag_drop_link returns unique records. However, this had the potential to decrease the performance and even lead to timeouts. This has been fixed. SF 2025.120250417 - List included index columns for non-clustered history table indexes Non-clustered (history) index columns that were set to be 'Included' were not included in the generated code due to an oversight. This has been fixed. 20250418 - Improve sync data processing for role_tab_variant_look_up The step to synchronize model data for role_tab_variant_look_up had the potential to stall the synchronization process. This has been fixed for this procedure. In 2025.2 for all synchronization procedures.

Hello everyone,Earlier today we did an early release of Indicium with version 2025.1.12.1 to support the “Report file (non-file storage)” report parameter property in Generate Report process actions as well. Due to a mistake, this version of Indicium would not start up. We have just released version 2025.1.12.2 which fixes this problem.Our apologies for any inconvenience caused by this.

This is an additional release for the Universal GUI version 2025.1.12.We found out that the 2025.1.12.0 did not contain the changes of last sprint as we wanted it to have. So if you already deployed the 2025.1.12.0 version, please replace it with this.The 2025.1.12.1 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements this week: IAM 2025.120250410 - Correct UP setting for storing collapsible section states Existing IAM environments that upgraded to 2025.1 had the User preference configuration setting for storing the Collapsible section state false by default, whilst two default configurations should have this setting set to True. This has been fixed. The default User preference configurations Move, On_Off and Complete now allow the user to store the collapsible state of Sections. Universal GUI version 2025.1.12 or up is recommended.

April 13, 2025Full release (from release candidate 2025.1.12) Additional fixes in this release: Collapsing or expanding collapsible form sections would sometimes trigger the message "This action is not allowed." This issue has been resolved. Hello everyone,in this release, we have added support to some refresh options to also refresh the subject's parent row, and for the form Column width factor setting in the Software Factory. Aggregations in the grid have been improved to use selected records instead of the entire dataset.We have also restyled the grid header and the pivot tables. For editable pivot tables, we have added some functional changes as well, such as cell navigation, and editing cells on focus. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.12For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.12 here ContentsDemo Universal GUI version 2025.1.12 New and changed Refresh parent subject row Grid header restyling Improvements for aggregations Pivot table UI/UX update Support for 'Column width factor' in the Software Factory Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedRefresh parent subject rownewWe have extended the following Refresh options: Row and Subject (menu User interface > Subjects > tab Settings > group Refresh > fields After insert/copy/update/delete). They now also refresh the subject's parent row. The parent row is also refreshed when a table task is executed with Refresh after execute set to Row or Subject (menu Process flows > Tasks > column Refresh after execute).This change solves several issues where the parent row was missing after executing a task, and subsequent actions, such as a process flow, would crash. Furthermore, the refresh option Document, which is performance-heavy, is now less essential. Instead, you can now update a calculated field in the parent with the child subject's update trigger or handler, by setting the child's refresh option to Row or Subject.Note: the Universal GUI refreshes the parent row only one level up. Grid header restylingchangeThe grid column headers have been redesigned:The border and text styles have been updated. The header height is now fixed and no longer responds to the data record height. Previously, when the header text did not fit the column width, it was cut off. Now, the text wraps over multiple lines.Note: with the new styling, the header height, in general, has decreased. If you are using longer column names with multiple words, they take up more space now. Using column header groups may be a better alternative for very long names. Configuring the column (auto) size also helps to properly show the header text.Grid column header restyling Improvements for aggregationsnew Previously, the Universal GUI always calculated aggregations in a grid based on the entire dataset. When selecting multiple records, the Universal GUI will now use selected records to calculate the aggregate. When a single record is selected, the Universal GUI will use the entire dataset.The Universal GUI supports aggregation types average, sum, count, min, and max. Before, when an unsupported aggregation type was selected in the Software Factory, the Universal GUI would default to using the aggregation type sum. Now, if an unsupported aggregation type is selected in the Software Factory, no aggregation will be shown. Pivot table UI/UX updatechangeWe have updated the styling and some UX aspects of the pivot tables. Additional functional changes in pivot tables are:The pivot row height now follows the grid row height (menu User interface > Subjects > Settings > Grid > Row height). The pivot header height no longer follows the grid row height. The category columns are now pinned. The category and value columns now auto-wrap their header titles. Note that this can cause the header to use more rows in existing cubes. An Enter on a cell now behaves like a double click and opens the drilldown.Additional functional changes in editable pivot tables:Cells are now editable on focus. Cell navigation is possible with Tab, Shift + Tab, and arrow up and down. Arrow left and arrow right navigate the cursor in the value of the cell. Drill-down in editable cells is suppressed.Known issue: when the editable field is a domain with elements, cell navigation does not yet work like it should. Support for 'Column width factor' in the Software FactorynewWe have added support for the form setting Column width factor in the Software Factory. It allows you to control the column width of task and report pop-ups. For more information, see Form column width factor. Minor fixes and tasksFor lookup fields and editors:Selecting the Clear button for a lookup field did not apply the defaults correctly. This issue has been fixed. We have fixed an issue where the default value was not properly applied when typing an exact value in a lookup editor and leaving the field. In editable grids and forms, a modified lookup editor briefly showed different values before the actual value appeared after leaving the field or record. This issue has been fixed. As usual, the latest version of Indicium (2025.1.12) is required for this fix. When switching rows repeatedly by clicking a lookup editor in a default editable grid, clicks would sometimes get ignored. As a result, the desired row did not become active and editable. This has been fixed. After switching to a different row, lookup editor cells could appear as if they were still active. This issue has also been improved. When selecting checkboxes on the same row in a default editable grid, a different checkbox than the one selected would change its state as well. This issue has been fixed. When rapidly selecting checkboxes on different rows in a default editable grid, some checkboxes would revert to their original state. This issue has been fixed. In a default editable grid, the layout logic was not applied to the active record when the record was updated by triggers, update handlers, or other users. This has been fixed.Other:If a FormList was set to refresh the subject after an update, it scrolled back to the top, and the focus was no longer on the correct editor. This issue has been fixed. When navigating to a different tab that uses a subject variant and returning to the initial tab, the conditional layouts would sometimes not apply correctly. This issue has been fixed. When an action bar button with a non-SVG icon was disabled, the icon was not grayed out like it was with the old toolbar. This has been fixed. Importing column mapping failed for mandatory fields with a default value. This issue has been fixed. Now, a mandatory column without a mapping will not be selected by default, respecting the default value. A constant value is not required for this field, as it is handled by the default value from the Software Factory. Only when a user explicitly provides a value will it be sent to Indicium. This change prevents the default value from being overridden unnecessarily and resolves the import block. We have fixed an issue that occurred when a URL or HTML domain control contained a URL with special characters (such as %A7). As of Thinkwise Platform version 2025.1 or when the Action bar was hidden, the Model insights component no longer showed model information. This issue has been fixed. What we will be working on next sprintThe next sprint we will be working on:Conditional layouts for charts Opening a zoomed detail as a new document by a process flow (Thinkwise Platform 2025.1 feature) Scheduler improvements Pop-up size settings from the 2025.1 platform release Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have added a new button to the Process Flow Monitor that allows you to refresh the model without leaving the Process Flow Monitor. To make troubleshooting failed import rows easier, the reason for the failure is now included in the error file. For the process flow action Download file, we have added support for the input parameter Try to preview.You can read more about Indicium's features in the Indicium user manual. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available:Indicium Basic (EoL): for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2025.1.12 here. ContentsRelease notes Indicium (2025.1.12) About Indicium New in Indicium Added a refresh model button to the Process Flow Monitor Added reasons for failed import rows Implemented input parameter for 'Download file' Minor fixes and tasks Questions or suggestions?  New in IndiciumAdded a refresh model button to the Process Flow Monitornew Universal GUIYou can start system flows manually in the Process Flow Monitor for debugging purposes. This feature works by showing all eligible system flows from a Software Factory runtime configuration in a dropdown menu. However, Indicium cannot detect model changes in a Software Factory meta-source.For this reason, logging out and back in or calling the refresh_model method with an external tool was necessary when testing a newly added or changed system flow. To improve this process, we have added a new button: Refresh model. It allows you to refresh the model without leaving the Process Flow Monitor.Refresh model in the Process Flow Monitor Added reasons for failed import rowsnewWhen importing data, the downloadable Excel file with rows that could not be imported only contained which rows and columns failed, but not the reason why they failed.To make troubleshooting failed import rows easier, we have added a new column called '(Errors)' to this Excel file. This new column contains the error message for each failed row. Implemented input parameter for 'Download file'newIn the Thinkwise Platform 2025.1 release, the input parameter Try to preview was added to the process flow action Download file. We have now added support for this input parameter in Indicium, which indicates whether a file should be previewed before downloading. Previewing is not possible for all file extensions. Minor fixes and tasksWe have fixed an issue where a record import was reported as successful when, in reality, it failed. It would occur when the import failed due to certain types of database-level errors. We have fixed a small styling issue in the Process Flow Monitor which could cause text to overflow their cells and overlap with text in other cells. 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 2025.1Package fix for Cube views We have resolved an issue where a drag-drop link was added twice. This resulted in the Software Factory not being able to start up properly. Important: If you plan upgrade to 2025.1 or later, download a new package from TCP to obtain the latest up-to-date version of the package.   20250404 - Correct code search error for default value queries When performing a code search where the search query found code in both the Data migration column default value query as well as in the Column itself, the code search execution would fail. This has been resolved.

Hello everyone,In this release, we have added support for newer Indicium distributions that only provide an appsettings.sample.json file to use as a reference when creating the actual appsettings.json configuration file. We have also added new Microsoft Entra authentication options to use when connecting to SQL Server databases.Download the Thinkwise Deployment Center 3.3.0 here. ContentsContents New in the Thinkwise Deployment Center Support for Indicium's appsettings.sample.json Microsoft Entra authentication options Questions or suggestions? New in the Thinkwise Deployment CenterSupport for Indicium's appsettings.sample.jsonGUI CLIWe have added support for newer Indicium distributions that only provide an appsettings.sample.json file to use as a reference when creating the actual appsettings.json configuration file.GUI Some deployment combinations can cause the comments from the Indicium sample configuration to become unavailable in the final appsettings.json. To accommodate this when using the Advanced edit mode during an Indicium upgrade flow, the Deployment Center offers a View sample button to view the appsettings.sample.json file from the package in a separate window. This will allow you to reference any newly added settings or view the descriptions of settings should they be missing in the appsettings.json file of the deployed Indicium.Configure Indicium appsettings.jsonMicrosoft Entra authentication optionsWe have added new Microsoft Entra authentication options to use when connecting to SQL Server databases. The following fields have been added to the GUI when selecting a database server host instance:SQL Server Authentication Authenticate using a regular SQL Server account username and password. Using this is the same as previously clearing the checkbox Integrated security. Windows Authentication Authenticate using the current Windows user account. Using this is the same as previously checking the checkbox Integrated security. Microsoft Entra Password Authenticate using your username and password against the Microsoft Entra tenant configured for the SQL Server instance. The username is always your email address. Microsoft Entra Integrated Authenticate using the current Windows user against the Microsoft Entra tenant configured for the SQL Server instance. Requires the computer to be domain joined/federated with the Microsoft Entra tenant. Microsoft Entra MFA Authenticate interactively using a browser window like most Microsoft/Azure service web sites. Due to being handled by the OAuth/OIDC this option also supports Multi-Factor Authentication methods. Microsoft Entra Service Principal Authenticate using an Application Service Principal in a Microsoft Entra tenant. Requires the App ID and a client secret value from the target application registration.In addition, the following advanced options have been added:Encryption - Sets the level required for SSL/TLS when connecting to the server and can be set to: Optional - Uses SSL/TLS if it is available but it is not required. Mandatory - Requires the server to provide SSL/TLS. Strict - Same as Mandatory but requires the connection to support at least TDS 8.0. Trust server certificate - Production servers should always use a valid SSL/TLS certificate. However, development servers might not be properly configured with one. This option can be used to always trust the certificate given by the server even if it, for example, is self signed. Certificate host name - This setting can be used to specify the host name that is expected to be provided in the SSL/TLS certificate in case it does not match with the host being connected to.Configure Microsoft Entra authentication in the GUIFor the command-line interface, new Microsoft Entra authentication options have been added when connecting to SQL Server databases through the iam/sf/upcycler/app commands. These can be set through the --auth-method and --iam-auth-method options depending on the subcommand. The --auth-method option might become required in the future, but currently falls back to previous implicit authentication methods for backwards compatibility.The following commands are available:UserPassword - Authenticate using a regular SQL Server account username and password. Using this is the same as previously providing a --username value. WindowsAuthentication - Authenticate using the current Windows user account. Using this is the same as previously not providing a --username value. MSEntraUserPassword - Authenticate using username/email and password against the Microsoft Entra tenant configured for the SQL Server instance. MSEntraIntegrated - Authenticate using the current Windows user against the Microsoft Entra tenant configured for the SQL Server instance. Requires the computer to be domain joined/federated with the Microsoft Entra tenant. MSEntraMFA - Authenticate interactively using a browser window like most Microsoft/Azure service websites. Due to being handled via OAuth/OIDC this option also supports Multi-Factor Authentication methods. However, due to the interactive nature of this flow, this value is not suitable for use in scripts running inside a CI environment. MSEntraServicePrincipal - Authenticate using an Application Service Principal in a Microsoft Entra tenant. Requires the App ID (--username) and a client secret (--password) value from the target application registration.To remain backwards compatible with previous behaviour, the advanced options currently available in the GUI are interpreted as follows in the command-line interface:Encryption - always set to Optional which will use SSL/TLS if available but it is not required. Trust server certificate - always set to True which allows incorrectly configured/invalid certificates from the server. Certificate host name - always empty, due to Trust server certificate always being true this option does not do anything anyway.Configure Microsoft Entra authentication in the CLIQuestions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone, In this release, we have resolved a problem with drag & drop.You can read more about the Windows GUI's features, in the user interface guide.Download Windows GUI (2-tier) 2025.1.11 here. FixedFreeze when dragging & dropping If a user scrolled in a list for a long time during drag & drop while holding a record, the Windows GUI would freeze. This issue has been fixed. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  

March 17, 2025Full release (from release candidate 2025.1.11) Additional fixes in this release: The Search in the action bar stayed hidden while the dataset was still loading and no longer appeared properly. This occurred especially on slow connections. This has been fixed. Hello everyone,In this release, we have updated the row visibility in the card list. We have also fixed several issues. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.11For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.11 here ContentsDemo Universal GUI version 2025.1.11 Contents New and changed Row visibility in the card list Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedRow visibility in the card listchangeWe have enhanced the way selected and hovered rows are displayed in the card list by changing the row highlighting. The selected and hovered row colors now use a gradient based on the main color selected for your theme in the Software Factory rather than a grey tone. Minor fixes and tasksWe have fixed an issue where scrolling in the grid on a touch device mistakenly changed the active record due to scrolling gestures being misinterpreted as clicks. Previously, when a record was updated from a related subject or by another user on a default editable subject, the editor did not show the most recent changes. Now, when the record has not been changed by the user, the most recent values are shown. A default editable parent or child subject is now updated when, for example, a task is executed on the subject. The Universal GUI uses timers per subject to manage auto-refresh, which can have the option for change detection. Under certain conditions, more than one timer was created for the same subject which caused several issues. This issue has been fixed. If the user initially opened a tab using a default variant of a subject, conditional layouts were applied correctly. However, if the user switched to another tab that used a variant of the same subject and then returned to the initial tab, the conditional layouts sometimes failed to apply. This issue has been fixed. If, for example, an Action bar task was placed in the overflow menu by setting the Custom display type to Overflow, it was sometimes displayed incorrectly as an icon only element in the overflow menu. This has been fixed. On mobile devices, the background image showed a gap at the top of the screen. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Grid header re-styling Pivot table re-styling Pivot table pinned categories Maintenance 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 2025.120250307 - Modify create_breakpoint_screen_types enrichment with ActionBar With the introduction of the Action bar, the old Toolbar has been removed. Any references to the toolbar have been changed to the Action bar for this enrichment.   20250313 - Correct data in variant screen Changes compared to default The 2025.1 feature to compare a variant to its default (see Release notes and Docs) did not display the complete set of data that it should: We did show data when the default table/task/report has no value, and the variant does have a value. We did show data when when the default table/task/report has a value, and the variant has a different value. We did not show data when when the default table/task/report has a value, and the variant has no value. This has now been fixed.   SF 2025.1, 2024.3, 2024.220250312 - Correct difference analysis of arbitrary merge sessions When performing an arbitrary merge from one branch to another, the difference analysis was not always able to determine conflicts properly, resulting in missed conflicts and eventually a failed merge session. This has been fixed. You can use Arbitrary merge sessions to migrate a branch with changes into a freshly made new branch. This essentially rebases your branch, and allows the origin model version to be up-to-date.   IAM 2025.1, 2024.320250313 - Copy classic user-defined prefilter states When copying an application in IAM, you can copy the user preferences of the copied application to the new one. However, the default states of user-defined prefilters were not copied properly resulting in these prefilters being turned off. This has been fixed.

Hello everyone,In this release, we have fixed an issue with the error reporting during import operations.You can read more about Indicium's features in the Indicium user manual.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 features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2025.1.11 here. ContentsAbout Indicium Minor fixes and tasks Questions or suggestions?Minor fixes and tasksWe have fixed an issue that would report the importing of a record as being successful when in fact it failed. This issue would occur when the import failed due to certain types of database-level errors. When this happened, Indicium would incorrectly report the result of the row import as successful, leading to a mismatch between the displayed import result and the actual import result.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: SF & IAM 2025.1Cubes20250303 - Modify create_cube enrichment after Cube refactor After the Cube refactor, the enrichment to create a cube was affected and could raise an error when used. This has been fixed. 20250306 - Cube categories drag-drop correction It was impossible to use drag-drop to change the order of Categories / Rows in the Cube set-up panel. This has been fixed. Action bars20250305 - Prevent syncing custom actions for removed custom action bar It was possible for removed custom action bars to leave behind custom actions that were set up prior to the removal of the bar. These leftover actions were then synchronized to IAM which caused the Windows GUI to raise an error. This has been fixed.   20250307 - Modify create_breakpoint_screen_types enrichment with ActionBar With the introduction of the Action bar, the old Toolbar has been removed. Any references to the toolbar have been changed to the Action bar for this enrichment.

Hello everyone,As of this release, we have introduced several new solutions to the Thinkstore. Furthermore, we have restructured and enhanced a large number of other solutions. ContentsContents About the Thinkstore New and changed in the Thinkstore models Standard http queue with system flow (API) Columnstore index and AI search Add index temporal table Email system flow Maps and Routes Renamed 'Using OAuth to get data from external applications' Default tooltip Make sure your display values are unique Turn off enable tab task when empty Find a certain char in a string Generate a unique randomized token Thinkwise Guideline Validations Check constraint for easy user input validation Difference in data between two databases Friendly error msg for databaseconnector Date prefilters Questions or suggestions? About the ThinkstoreThe Thinkstore is a fully integrated way for downloading and installing ready-made solutions directly into your models right from the Thinkwise IDE. It contains a collection of scripts and samples to help you get the most out of the Thinkwise Platform. You can find the Thinkstore in the Software Factory, in the menu Enrichment > Thinkstore.The Thinkstore only contains solutions specifically for the Software Factory version you are using. Therefore, the Thinkstore will be cleared before every platform upgrade. After the upgrade, if you open the Thinkstore in the new Software Factory version, it will initiate a refresh and retrieve all the available solutions for that version. This process runs in the background. It can take up to ten minutes before the solutions are available.You can read more about the Thinkstore in the Thinkstore guide. New and changed in the Thinkstore modelsStandard http queue with system flow (API)newWe have introduced a new solution in the Thinkstore: Standard http queue with system flow (API). This solution provides a queue table with all the input and output variables of a HTTP connector process action.A system flow executes HTTP calls and stores the response data into the table. This allows both users and the system to process the retrieved information.Columnstore index and AI searchnewThis new solution contains an example of how to use a columnstore index in the Software Factory, combined with AI search.The data model consists of a product table that can compare itself to other products within that table and provide a matching score. A higher score indicates that the product is more similar to the selected product.The columnstore index ensures that this functionality is extremely fast. Columnstore indexes store data by column instead of row, offering significant data compression and reducing storage needs. This leads to faster queries because less data is accessed during query execution.More general information about columnstore indexes: Microsoft More information about columnstore indexes in the Software Factory: IndexesAdd index temporal tablechangeThe model Add index temporal table has been changed because of the introduction of the Non-clustered (history) index in the Software Factory.Add index temporal table now contains a dynamic model. When the tag add_history_index is added to a table, the dynamic model creates an index on the history table based on the primary key of the original table.This index helps when you have included the Thinkstore solution Logging data available in the GUI in your model or when you query your history table with the original primary key.Email system flowchangeThe Email system flow has been completely restructured for improved efficiency and reliability. This update streamlines email handling and ensures a more scalable and robust solution for managing email workflows.Key changes include:New email table: We have introduced an email table with a status field, serving as a queue table for email processing. Background process: A new system flow, email_read_next_queue_id, has been implemented to manage queued emails. It identifies and picks up the next email to be sent automatically. Subflow execution: The system flow triggers a subflow that sends emails using the Email connector.The Example email module has been deprecated as the newly updated Email system flow now provides a more comprehensive and efficient alternative.Maps and Routeschange Universal GUIThe models Maps (mymappi) and Google Maps have been merged into a new model named Maps and Routes. This new model serves the purpose of teaching how to work with the Maps component in the Universal GUI. It also uses two Web connection endpoints for retrieving the GPS coordinates and routes.You need to get your own API key from Google and enter it in the Web connection.The model includes a menu for addresses and routes:Adding an address initiates a process flow that uses the Web connection to retrieve and display the GPS coordinates on the Maps component. Once you have at least two addresses, you can add a route. The Web connection retrieves and displays the fastest route on the Maps component.Renamed 'Using OAuth to get data from external applications'changeThe model Using OAuth to get data from external applications has been renamed to Using OAuth to get data from Exact Online. In addition:The MS Graph connection has been removed. This will be a separate Thinkstore model. Instead of an HTTP connector, a Web connection is now used.Default tooltipchangeThe model Default tooltip has been updated:The generation strategy has been changed to Fully Controlled. The code has been changed so the trace columns are updated. The code has been changed so the tooltip translation is also updated when the translation is updated.Make sure your display values are uniquechangeThe generation strategy has been changed to Staged.Turn off enable tab task when emptychangeThe generation strategy has been changed to Fully Controlled. The code has been changed to a where not exists. The code has been changed to create the tag when it does not exist yet.Find a certain char in a stringchangeWe have added a table valued function so the functionality will be easier to use.Generate a unique randomized tokenchangeWe created a subroutine (procedure) for the functionality. Previously, it was only an example script.Thinkwise Guideline ValidationschangeWe renamed the validation column_name_starts_with_the_table_name to tsf_guideline_column_name_starts_with_the_table_name. This is to be in line with the rest of the naming of the validations. In the validation tsf_guideline_column_name_starts_with_the_table_name, the like missed the '%', this has been corrected. tsf_guideline_domain_which_contains_the_name_of_an_rdbms_datatype now only checks for the RDBMS type of the model. All the validations that use a cursor with a table variable have been changed to a temporary table to improve performance and stability. See this Community post.Check constraint for easy user input validationchangeWe changed the strategy for the meta control procedure "check_constraint_message_add" from delete to staged.For more information about the custom check constraints, see the blog Check constraints using the Software Factory.Difference in data between two databaseschangeWe removed unnecessary parts of the model, reducing the size of the export file model.dat, without any other changes.Friendly error msg for databaseconnectorchangeWe changed the strategy for the meta control procedure database_connector_process_action from delete to fully controlled. We also modified the insert statement for the table process_action_output_parmtr to include the column output_parmtr_type with a value of fixed_option.We changed the strategy for the control procedure error_log_code from delete to staged. We also removed the parameter @error_log_code from the error handling code in the template error_log_code, as it was not declared.Date prefilterschangePreviously, this model included a table named date_of and a prefilter group called date_filters with 4 prefilters. Now, it only contains a meta control procedure tab_date_prefilter that adds the prefilter group and prefilters to all tables linked with the tag tab_date_prefilter. In the tag value, you must specify a column with a domain of data type DATE, DATETIME, or DATETIME2.The 5 prefilters created are:Current week Year to date (new compared to the previous model) Current month Current quarter Current yearThese prefilters can be adjusted within the dynamic code if you desire more or fewer prefilters, or if you wish to modify any details of the prefilters. We set the strategy for the meta control procedure tab_date_prefilter to fully controlled, giving you the freedom to change the details after creation. Note that changes to the dynamic code will not modify the already created prefilters.You have to get your own API key from Google and enter it in the web connection.The model includes a menu for addresses and routes.Adding an address initiates a process flow that uses the web connection to retrieve and display the GPS coordinates on the maps component. Once you have at least 2 addresses, you can add a route. The web connection will then retrieve and display the fastest route on the maps component.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have added support for a number of new features that have become available with the Thinkwise Platform release 2025.1. These features include the formalization of action bars, the assignment of actions to screen areas, and the support for default expand grouped grid.We have also implemented the new UI styling for the action bar and grid rows. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.10For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.10 here ContentsDemo Universal GUI version 2025.1.10 Contents Breaking Thinkwise Container images New and changed Action bars formalized Screen areas to assign actions to screen components Support for default expand grouped grid Support for disabling multirow selection Support for collapsible form sections Support for calculated cube fields Row visibility in the grid Security update Minor fixes and tasks Questions or suggestions?BreakingThinkwise Container imagesIf you use a container image from the Thinkwise Container Registry, the default port has changed from 80 to 8080.For more information, see the blogpost Thinkwise Container images breaking change. New and changedAction bars formalizednewAs of Thinkwise Platform release 2025.1, the Universal GUI uses Action bars and Custom action bars. The screen component Toolbar is no longer available as of this platform version. When starting this Universal GUI version against an older platform version such as 2024.3, the Toolbar will still be displayed.The new action bars offer you more flexibility in their content and appearance. For more information about configuring the (Custom) action bars, see User interface - More control over action bar placement in the Universal GUI in the Thinkwise Platform 2025.1 release notes.The following features are available in the new action bars:New styling for prefilter, CRUD, and task/report buttons as described in the blog post Styling update of the Universal GUI. In Comfortable mode, the buttons are bigger and have more space around them. This mode is mainly used on mobile devices, and is now more suitable for touch devices. The reintroduction of task and report group dividers, once temporarily introduced in the Universal 2024.3.12 release candidate. Extended display types for table tasks, table reports, prefilters, and cube views, which override the default display type for the action bars. For more information, see Display types in the Thinkwise Platform 2025.1 release notes. A more even distribution of space between buttons. The (Custom) action bars try to keep as many buttons visible as possible. If an action bar is configured with, for example, many Icon + text (> text > icon) buttons, it will first collapse all buttons to Text, then to Icon, and finally to the overflow, from far to near. Contrary to the Toolbar, the (Custom) action bars do not display prefilters both in the bar and in an overflow to the right of the prefilters. This saves screen space. However, it is possible to place prefilters in the overflow menu. Note that the prefilter overflow menu has been removed, there is only one overflow menu at the far end of the action bars.Custom CSS changedThe new action bars come with changes to your custom CSS; the styling has been improved, possibly making your custom CSS obsolete.Note that the HTML structure, CSS classes, and data test IDs have changed, making your CSS selectors mostly unusable for the action bars. This applies to all parts of the selector, for example: div[data-testid=”toolbar”] > div > .icon > svg.We recommend using the default styling.For an overview of the changes:Differences between the test IDs for toolbars and the new action bars: Area Toolbar test ID Action bar test ID Notes General toolbar actionbar     start-toolbar -     - actionbar-near     - actionbar-far     toolbar__overflow-menu -     toolbar__overflow-menu__button actionbar__overflow-menu__button The action bar has only one overflow menu. It is located action bar-far for far buttons, or else in action bar-near. Search search-toolbar__search actionbar__search__input   Prefilters prefilter-toolbar-group-0__<prefilter id> prefilter-actionbar-group-0__<prefilter id> The number (index) differs based on the button visibility   prefilter-toolbar-section -   CRUD crud-toolbar__add actionbar__add     crud-toolbar__copy actionbar__copy     crud-toolbar__edit actionbar__update In action bars, Edit buttons are always hidden in ​​default editable subjects   crud-toolbar__delete actionbar__delete     crud-toolbar__save actionbar__save In action bars, Save buttons are always available in default editable subjects    crud-toolbar__cancel actionbar__cancel In action bars, Cancel buttons are always available in default editable subjects    crud-toolbar__refresh actionbar__refresh   Tasks Reports task-toolbar-section report-toolbar-section -     toolbar__task__<task id> toolbar__report__<report id> actionbar__task__<task id> actionbar__report__<report id>   Cube views cubeview-toolbar-section -     toolbar__cubeview__<cube view id> actionbar__cubeview__<cube view id>   Extra actions in the overflow menu - actionbar__overflow-menu__context     toolbar__overflow-menu__item__quickfilter__icon actionbar__quick-filter     toolbar__overflow-menu__item__filter actionbar__filter     etc. etc.           Note: hidden buttons are no longer rendered. This is not relevant for styling but is relevant when test IDs are used in automated tests. For example, when adding rows is forbidden in the subject, the Add button was available in the Toolbar, but not shown. In the (Custom) action bars, the button is not in the DOM (Document Object Model) at all. *The new Action bar; on the left shows more buttons on the same screen size than the old Toolbar; on the right* Screen areas to assign actions to screen componentsnew changeAs of Thinkwise Platform release 2025.1, Detail groups have been renamed to Screen areas.You can use these Screen areas to assign actions to Action bars and Custom action bars and mark them as fallbacks for all unassigned actions. This allows you to divide actions across multiple bars or make the most important actions stand out in a screen type. You can assign a screen area to the following types of actions in the (Custom) action bars:Tasks Reports Cube views PrefiltersIn the screen type, you can assign the same screen area to task and report tiles, and to task, report, prefilter, and cube view bars. Here, you can also select whether the tiles or bars should be used as fallbacks. You can reuse a screen area multiple times in a screen type, allowing tiles and buttons to be available more than once on a screen. This also applies to the fallback mechanism: a table task, table report, cube view, or prefilter can fall back to multiple bars or tiles.Screen areas remain available for details, the only difference is that a detail tab is placed on a subject only once, whereas actions can be duplicated.For more information, see Screen areas also for tiles and bars in the Thinkwise Platform 2025.1 release notes. Support for default expand grouped gridCommunity idea newIt is now possible to set a grouped grid to be default expanded. When the setting Default expanded has been enabled, you can set the level of groups that will be expanded by default (menu User interface > Subjects > tab Default/Variants > tab Settings > group Grid). For example, if you enter '3', three nested groups deep will be expanded by default.Note that the group and all its parents containing the active row are always expanded, even if the expansion level is set to '0'.For more information, see User interface - Setting for expanding grouped grid in the Thinkwise Platform 2025.1 release notes. Support for disabling multirow selectionnewA new setting is available for enabling or disabling the possibility for users to select multiple rows in the grid. The setting is called Multirow selection enabled and is available in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab General.Disabling multirow selection ensures that the following actions are performed on a single row: Task, Mass update, Delete, Export.For more information, see User interface - Multirow selection in grid in the Thinkwise Platform 2025.1 release notes. Support for collapsible form sectionsnewIn the Universal GUI, form tabs are not implemented because forms can extend indefinitely vertically. Instead, new tabs are interpreted by the Universal GUI as new sections. For example, the Trace info in the Software Factory is displayed as a tab in the Windows GUI, but in the Universal GUI, it is implemented as a section.For all supported Thinkwise Platform versions, the form sections can now be collapsed or expanded by users.As of Thinkwise Platform version 2025.1, you can use the Software Factory setting Default Expanded to specify whether a section should be expanded or collapsed by default. For this setting to work, the first column in a section must have the setting Field on next tab page enabled.Sections without a Tab page label to explain the information available in the section cannot be set to default collapsed, neither in the Software Factory nor via user preferences.For more information, see User interface - Collapsible sections for Universal GUI forms in the Thinkwise Platform 2025.1 release notes.Check the test ID for `<section>`For custom CSS, the data test IDs are unchanged.Note that the <section> element with the editors in it is now wrapped with some additional <div> elements brought up by the collapse panel. You may need to update your selectors for that.The test ID for the <section> element is form-section__<first editor column name>. Support for calculated cube fieldsnewCalculated cube fields are fields that are not directly available in the database but are calculated based on other cube fields. They are evaluated on cells and (sub)totals after intervals have been applied to dimensions and after values have been aggregated.In the Software Factory, you can now create calculated fields by selecting the aggregation type SQL Expression (menu User interface > Cubes > tab Tables > tab Default/Variants > tab Values > tab Form). The Universal GUI will fetch and display these fields in pivot tables and charts like any other aggregation type.For more information, see User interface - Calculated cube fields in the Thinkwise Platform 2025.1 release notes. Row visibility in the gridchangeWe have enhanced the way active, selected, and hovered rows are displayed in the grid:Row highlighting - The active, selected, and hovered row colors now use a gradient based on the main color selected for your theme in the Software Factory instead of a gray shade. Error indicators - Cells with errors are now more clearly highlighted for better visibility. Active row design - The indicator at the beginning of the active row has been removed for a cleaner look.*The new row highlighting in the Universal GUI**The new error indicator in the Universal GUI* Security updatenewWe have fixed the following security advisory: GHSA-mmhx-hmjr-r674.This resolves a security issue affecting some areas where HTML is displayed in the Universal GUI, including:HTML control (view-only mode) Preview component displaying an HTML field Prefilter, task, and report button tooltips Column, report, and task column tooltips Tooltips for grid headers Maps marker popupsIf a malicious actor were to inject an HTML value into one of these areas, such as through the Indicium API, this vulnerability could be exploited. In such a case, if a user had one of these elements visible, the attacker's JavaScript payload could be executed. In the worst-case scenario, the attacker could execute Indicium requests using the victim's credentials.Thanks to Indicium's Content Security Policy, the risk of exploitation was low. In addition, we strongly recommend always configuring Security headers. Minor fixes and tasksFor hierarchical trees without grouping, the conditional layouts were not applied the first time the user entered the screen. This has been fixed. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have improved a setting for OAuth server client credentials and made several improvements to our Oracle Database support.You can read more about Indicium's features in the Indicium user manual. 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 features such as system flows and OpenID. Download Indicium Basic release 2025.1.10 here.Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2025.1.10 here. ContentsAbout Indicium Contents Breaking OAuth server client credentials setting Thinkwise Container images New and changed Oracle database support improvements Questions or suggestions? BreakingOAuth server client credentials settingIn the Software Factory, it is possible to configure the Send client credentials for OAuth servers. This setting did not work as intended and always used the As basic Auth header option instead.Most OAuth servers support both options, so in most scenarios, this should not be a real problem. However, some OAuth servers only support one of the two options.Validate that the OAuth server is working after the upgrade to this release (menu Integration & AI > OAuth servers). If it is not working, change the mode to As basic Auth header if it is configured as In request body.Check the OAuth server client credentials Thinkwise Container imagesIf you use a container image from the Thinkwise Container Registry, the default port has changed from 80 to 8080. For more information, see the blogpost Thinkwise Container images breaking change. New and changedOracle database support improvementsnew changeIn this release, we have made several improvements to our Oracle database support:Table-valued functions We resolved an issue that affected the execution of subroutines returning a table (table-valued functions). Data type support We added support for the data types boolean and XML, expanding the range of data types you can work with. Note that before Oracle version 23c, the boolean data type only works for parameters in stored procedures and not for columns. User-raised errors We have resolved an issue with user-raised errors and how they impact the user flow in the Universal GUI. This will now work the same way as for SQL Server. Stability enhancements This release includes various bug fixes that improve the stability of Oracle applications.  Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone!In this release of the Thinkwise Platform, we have significantly improved the configuration of action bars for the Universal GUI. You now have more control over the placement of action bars on a screen and can manage their content and appearance more flexibly. In addition, the new UI Styling has been applied to the new action bars.We have also added a number of other new user interface features for the Universal GUI, such as collapsible sections for forms, a relative setting for the form column width, and expanding settings for grids.Cubes are now more user-friendly to set up as well. We have redesigned the cube screen and added support for editable pivot grids and calculated cube fields in the Universal GUI.The most significant new feature in IAM is the ability to schedule the clean-up of applications, branches, and models. You can set up a process to help you keep your IAM environment tidy by automatically removing applications, branches, and models that are no longer in use.With this release, we also introduce the first official version of the Windows GUI (3-tier) via Indicium, making Indicium Basic end-of-life. This year (2025) is the last year the 2-tier architecture is supported. Note that the Windows GUI (3-tier) is a backup plan if moving to the Universal GUI directly proves problematic. It is only available for those participating in the early-adopter program. The 3-tier architecture is much more secure and stricter regarding the quality of your model, so to prepare for the transition to the Universal GUI or to the Windows GUI (3-tier), we recommend fixing all findings in validations and smoke tests.This release contains 25 Community ideas representing a record of 588 votes. The most popular ideas were:This post highlights the key features of the release. For detailed release notes, visit the Thinkwise Documentation.ContentsContents User interface - More control over action bar placement in Universal GUI User interface - New features for the Universal GUI Cube enhancements Translations - Generate alternative translations for objects Some other new features Questions or suggestions? User interface - More control over action bar placement in Universal GUIchange Universal GUIIn this release, we have significantly improved the configuration of screen types for the Universal GUI. Some of the most important changes are in the configuration of Detail groups:The setting Detail groups has been renamed to Screen areas. Fallback groups have also been renamed, from Fallback group to Fallback area. You can now assign a screen area not only to details but also to task and report tiles, and to task, report, prefilter, and cube view bars. Assigning screen areas to tiles and bars allows you to place buttons for table tasks, table reports, prefilters, and cube views in different locations on a screen. You can reuse a screen area multiple times within a screen type, allowing tiles and buttons to be available more than once per screen.As a result, you have more flexibility in positioning bars within a screen type. Previously, the Universal GUI would automatically place action bars in screens. Now, two types of action bars are available, and you can define their content and appearance in more detail:The Action bar follows the default configuration defined for a branch. Changes to this default configuration affect all screens with Action bars. At the screen type level, you can include and exclude actions. In a Custom action bar, you can include or exclude actions, and change their order, default display type, screen area, and fallback settings. You can use screen areas to assign table tasks, table reports, prefilters, or cube views to a Custom action bar.Custom action bar configuration User interface - New features for the Universal GUInew Universal GUIIn addition to the improvements to the action bars, we have added some other new user interface features for the Universal GUI:Collapsible sections for forms. By default, all sections are expanded, showing all columns inside them. A Form column width factor setting to adjust relative form column width sizes. The Max. form-col space shows the form column space as a percentage of a form field, report parameter, or task parameter. Multi-row selection for grids. Hierarchical grouping of resources in a Scheduler. A maximum size limit for modal documents. Cube enhancementsCommunity idea new changeWe have enhanced a number of cube-related screens to improve clarity and usability. These changes will help you configure your cube views more efficiently. Some of the most important changes are:In the menu group User interface, the menu item for cubes is now called Cubes instead of Business intelligence. Instead of a single tab for Cube fields, there are now two separate tabs for Dimensions and Values. The new Cube set-up panel allows you to configure the cube view fields visually, similar to how you would create a cube view in your application. Settings specific to the cube view type are now available in vertical detail tabs: Pivot settings, Chart settings, Filter and Sort.For the Universal GUI, we have added support for editable pivot grids. For the Windows GUI, the extender default_editable_cube remains available but is no longer necessary if you are transitioning to the Universal GUI.Another new feature for the Universal GUI is the ability to create calculated cube fields of the type Value. You can set the Aggregation type to SQL expression and enter an expression. For the Windows GUI, the checkbox Calculated field has been replaced with Aggregation type Formula (deprecated). If you are transitioning from the Windows GUI to the Universal GUI, you can add both settings to your cube view. Aggregation type will be ignored by the Windows GUI, and Aggregation type Formula (deprecated) will be ignored by the Universal GUI.The new cube setup panel Translations - Generate alternative translations for objectsCommunity idea new Universal GUI Windows GUI (3-tier)In the Thinkwise Community, a highly requested feature was the ability to create alternative translations for objects. This feature is now available, allowing you to generate an alternative translation label for table (variant) columns, task (variant) parameters, and report (variant) parameters. It enables you to keep generic column names while customizing translations in your applications based on context or specific use cases.Add an alternative translation Some other new featuresFor models, you can now limit branch access for users to prevent accidental changes to a branch. This is especially useful for the MAIN branch, where changes are typically not made directly but instead added through merging. A new file storage type is available: SFTP. It can be used to access files on an SSH FTP server, which is useful for secure file transfers. For variants, we have added a new screen that shows an exact overview of how the variant differs from the default. In addition, variants are now also displayed in the Usage tabs, indicating that an object is used in a variant. For Oracle, we have added: Support for sequences in models Unit tests Smoke tests We enhanced validations by adding tasks that affect all messages for a validation at once and improving descriptions. We also added several new validations. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

This is an additional release for the Universal GUI version 2024.3.15. This release contains a fix for the prefilters:After turning off/on a prefilter, the hidden prefilters were shown (unwanted).This has been fixed.These issues were introduced in the 2024.3.15.0 release.The 2024.3.15.1 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements: SF & IAM 2024.320250212 - Next col field positions further fix When one field was placed in a next column (field_in_next_col), any fields within that form-column using a value of 0 for the Field no. of positions further setting would not be placed where intended. This has been fixed.

February 12, 2025Full release 2024.3.15 (from release candidate 2024.3.15) We have added some additional fixes to this version: When a user worked in a detail subject, a bug caused it to stop refreshing when its parent subject was auto-refreshing. This occurred, for example, when a user triggered a refresh at a specific moment, such as after executing a task on a detail subject where the entire document is refreshed after completion of the task. We have fixed this. The detail subject will now refresh correctly, and the auto-refresh will be paused until the next cycle. When expanding a domain with elements on an alphanumeric field, the pivot incorrectly generated a filter query using the translation instead of the domain element value, leading to an empty result. This has been fixed. Hello everyone,In this release, we have focused on resolving issues and improving the appearance and usability of the Universal GUI. We have made styling improvements to the sidebar of the Universal GUI and improved the target area for resizing in the Scheduler. We have also fixed some issues in Cube views, process flow actions, and improved the Suggestion type lookup editor.DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI.Universal GUI version 2024.3.15For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.3.15 hereContentsDemo Universal GUI version 2024.3.15 Contents User interface - Sidebar styling improvements User interface - Improved target area for resizing in the Scheduler Minor fixes and tasks What we will be working on next sprint Questions or suggestions?User interface - Sidebar styling improvementschangeWe have made some styling improvements to the sidebar in the Universal GUI:The menu switcher button is now square when the menu is collapsed. Menu item alignment and icon sizes have been adjusted for a more uniform design. The left corner radius of the workspace has been modified for better visual balance.Sidebar styling improvementsUser interface - Improved target area for resizing in the SchedulerchangeIn the Scheduler, the resource column or area was too small, making it difficult for users to resize it. We have enlarged the target area that users can hover over to make resizing easier. In addition, the resized area will be remembered on their device.Minor fixes and tasksWe have fixed the following two issues in Cube views (menu User interface > Business Intelligence > tab Tables > tab Cube views): When a Dimension was sorted by a Value that had the aggregation type min or max with the Sort by cube field setting, the sorting was incorrect When a Dimension was sorted by another Dimension with the Sort by cube field setting, the setting was ignored. In a cube, when a group was created with items like year(date) and quarter(date), and the year was added as a dimension in the Software Factory, the rest of the group would not expand when starting. When this same group was added in the pivot table editor, the groups would expand, but when another item was added behind it, it would appear inside the group. Both issues have been fixed. We have improved the Suggestion type lookup editor. When a user types a new criterion, a new set of options is loaded. However, depending on the network latency, the response to a previous search would sometimes arrive later than the response to the last one. We have fixed this so that the list of options always matches the latest search criteria. The process flow action Clear filters did not clear predefined and user-defined prefilters. We have fixed this. All active prefilters will now be cleared except for locked or hidden ones. When a detail tab was not activated, the process flow action Activate detail opened the detail subject, but reported the status as unsuccessful, causing the flow to follow the red arrow for an unsuccessful action. In addition, the continuation of the flow did not wait for the detail subject to load its data. Both issues have been fixed. We have fixed an issue where executing a process flow that disabled all active prefilters would cause hidden prefilters to become visible. Canceling changes in a record in a default editable grid caused the Form tab to be activated. This has been fixed. When editing a grid's cell value and navigating to another cell, the cursor would sometimes unexpectedly jump to another component (such as a form or filter form). We have fixed this so the cursor now stays within the component that is being edited. The date picker would always select the day part, even when clicking on the month or year. This has now been fixed and the appropriate part will be selected when clicked on. Saved date-type prefilters that used empty or not empty operators were resulting in a bad-request error. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Support for the Thinkwise Platform version 2025.1 Restyling of the grid/pivot table MaintenanceQuestions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have fixed some minor issues for Oracle databases and improved the automatic login behavior for password managers.You can read more about Indicium's features in the Indicium user manual.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 features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2024.3.15 here. ContentsAbout Indicium Minor fixes and tasks Questions or suggestions?Minor fixes and tasksWe have fixed an issue where password managers would try to automatically log in when the username and password were known. This automatic login would sometimes result in unexpected results. We have fixed this issue, and automatic login should now work as expected. We have resolved an issue that could occur when generating count queries for Oracle databases. In a few rare scenarios, a column alias could be missing, leading to an error when executing the query.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  ​

Hi everyone!Last week, we’ve released the following platform improvements: SF 2024.3, 2024.2, 2024.1, 2023.3, 2023.220250129 - Process flow assignment fix The determination of which static assignments needed to be updated or removed during the renaming of a process flow is based on the process flow name. However, if a process flow name was a subset of another name with an additional suffix, this led to assignments being incorrectly included. This issue has been resolved by improving the comparison logic to ensure only exact matches are processed, preventing unintended changes.

This is an additional release for the Universal GUI version 2024.3.14.In the upcoming 2025.1 release of the Thinkwise Platform, the generic toolbar that the Universal GUI normally adds to your screens will be added to each screen type in the Software Factory. This change will give you more control over where the toolbar is placed.To prepare for this change, we have improved the merging of a single toolbar placed underneath the generic toolbar, ensuring the same user experience as before.This change ensures that the toolbar now adheres more closely to the screen type design in the Software Factory.As as result, the toolbar placement for more complex screen types has slightly changed.For example, when a screen type starts with a tab panel containing component tabs directly below a bar, the generic toolbar would previously be placed inside the component tabs. Now the generic toolbar will also be placed above the tabs. Tip:Check your custom screen types in a situation like the one mentioned above.The 2024.3.14.1 release is now available for download in TCP.

January 20, 2025Full release 2024.3.14 (from release candidate 2024.3.14) Solved the following issues found in the release candidate: When the user added or removed series, categories, or values in the cube editor, the chart would not immediately respond to these changes. The user had to refresh manually to view changes. This is now fixed. In version 2024.3.13, we optimized the process of opening a lookup pop-up from a read-only subject. In specific cases where the representation of a lookup record (display value) was not unique between records, the pop-up would not open the correct record. This has been fixed. We have also optimized the requests for loading data in the pop-up. If the filter column is a lookup field (resolved lookup), the data is now filtered based on the key instead of the display value from another table. This improves the performance of the pop-up. In version 2024.3.11, we introduced the new date picker. In it, the buttons Clear and Today were omitted. They have been added back. Hello everyone,In this release, we have added support for editable pivot tables and filtering multi-line type-domain controls. We have also fixed some minor issues and tasks. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.14For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, such as a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory instances you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2024.3.14 here ContentsDemo Universal GUI version 2024.3.14 Contents New and changed Support for editable pivot tables Support for filtering multi-line type domain controls Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedSupport for editable pivot tablesnewAvailable as of Thinkwise Platform release 2025.1The Universal GUI now supports editable pivot tables. 'Editable' means that users can change the value of cells in the pivot table. They can navigate through the cells by using the arrow or tab keys. Pressing Enter brings the cursor into the editor to change the value. Changes are directly saved to the table behind the pivot table after leaving the cell by either using the mouse or the keyboard.To make a pivot table editable, the following conditions must be met:The user must have permission to manipulate data in the table by selecting the option Update. The column type must be set to Editable. The summary type of the cube field must be min, max, avg, or sum. The count of the summary type must be 1 (exactly one row behind the aggregation). For example, the sum of Ben's (47) and Anna's (30) ages equals 77, with a count of 2 (derived from two rows, which cannot be changed). If you add "person" as a dimension, you get Ben (47, count = 1) and Anna (30, count = 1); these counts can be adjusted since they correspond to individual rows.If a user edits a pivot table, the Universal GUI applies the setting for the refresh After update. However, it is advised not to set this to Document, as it may cause the pivot table to re-render.It is not necessary to enable the subject to be editable by default, to enable autosave, or to show an action bar when no form is present for the subject behind the pivot table.Editable pivot table Support for filtering multi-line type domain controlsnewWe have added support for filtering multi-line type domain controls. Both the filter pop-up and the inline filter form support this now. Minor fixes and tasksFor grids and forms:When selecting multiple rows with conditional layouts in a grid, only the active row was highlighted as selected. The conditional layout would override the styles (row background color) of the other selected rows. This has been fixed. On a slow network, selecting a value for a lookup editor from a pop-up could occasionally cause a crash. This issue has now been fixed. Inserting records in a grouped grid subject was not working as expected. Grid columns are grouped when the checkbox Group until is selected in the Software Factory (menu User interface > Subjects > Default/Variants > tab Data > tab Sort). To insert the added record in the same group, the grouped columns should also be marked with the checkbox Include in insert (menu User interface > Subjects > Default/Variants > tab Columns). Previously, the group values were not filled in the form after pressing Add. This has now been fixed. Note that a form is required to insert a record (the grid itself cannot add a record).For the date picker:The date picker would only show days belonging to the current month, leaving empty spaces before and after. These spaces will now be filled with adjacent days from the previous or next month. The date picker would always show Sunday as the first day of the week. It has now been updated to set the first day of the week based on your browser's locale language setting. For example, if the language is set to English US, the first day of the week will be Sunday; if set to English UK or Dutch, the first day of the week will be Monday.Other:In some cases, the background of a cube field was not shown in the field selection panel. Now, it is always shown. The tooltip of an open document shows details about the selected record of the document. For a few releases, this tooltip has been showing details of the active document on inactive documents, which was confusing. For example, when 'Projects' was active and you hovered over 'Employee', the tooltip of 'Employee' would show the active project details. This has been fixed, so the 'Employees' tooltip shows the active employee again. What we will be working on next sprintThe next sprint we will be working on:Support for the Thinkwise Platform version 2025.1 Cell selection in pivot grids for task execution or showing detail data Maintenance 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 2024.320250117 - Only add parameters to existing program object items When upgrading a system-versioned table, in some cases it was possible that a parameter was generated for a program object item that did not exist. This has been resolved. IAM 2024.3 ⭐ 20250117 - Improve performance of process flow schedule log We have added an index to the process_flow_schedule_log table that enhances the performance of starting in system flow instances.