Product Updates

Hello everyone,In this release, we have improved a couple of models and removed models that had become obsolete. 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. ContentsAbout the Thinkstore Improved Improved the model Logging data available in the GUI Improved the model "Trace tasks" Improved the model "Illegal XML characters" Improved the model "Facts" Improved the model "Logging data available in the GUI" Improved the model "Auto create a function for system versioning" Improved the model "Working with dates in SQL" Improved the model "Getting domain elements in SSMS shortcut" Improved the model "Extract a file name from a file path" Improved the model "Translating model objects in business logic" Combined and improved the models "Convert UTC marked dates to locale dates" and "UTC and local time conversion" Removed Removed the model "Auto refresh" Removed "Auto generate reports" Removed the model "Knowledge application" Removed the model "Change detection" Removed the model "Replace HTML font family" Removed the model "Change font of html fields from Segui ui to Arial" Removed the model "Session variables" Removed the model "Default error handling on SQL Server" Removed the model "Drag and drop between subjects example" Fixed Fixed the model "SAP API stock, consumption and production booking" Fixed the model "Multi lang data" Questions or suggestions? ImprovedImproved the model Logging data available in the GUIchangeWe have updated the Thinkstore model Logging data available in the GUI to improve performance and readability.The control procedure that generates tables, columns, and references no longer uses temporary tables.It now uses staged tables.Improved the model "Trace tasks"changeWe have made the following changes:Adjusted the dynamic model "Trace tasks" to be fully controlled. Added "where not exists" to the columns. Changed that the table and columns are no longer set as "generated". Changed the strategy to "Staged". Changed the order of the assigning. We now weave the functionality into the program object in step 3 instead of step 2. If a task has a transaction, the code is now within the transaction.Improved the model "Illegal XML characters"changeWe have made the following changes:Adjusted the dynamic model "Illegal XML characters" to be fully controlled. Added "where not exists" to the subroutine and parameters. Changed that the subroutine is no longer set as "generated". Changed the strategy to "Staged".Improved the model "Facts"changeWe have added roles for each base table to the model "Facts". We have also created unique indexes for the names per table.Improved the model "Logging data available in the GUI"new changeIn the model "Logging data available in the GUI", we have created the needed domains in case they are not yet in the model via the dynamic model code.We have also added the following fixes:There was an issue with the row_number when determining the conditional layout code values. This has been fixed. If the total length of combined tab_ids exceeds 1000, the extended property will now give an error since this column is a varchar(1000). If there is a reference on the computed column, the ref was deleted from #ref but not #ref_col, which would give an error. This has been fixed.Improved the model "Auto create a function for system versioning"changeFor the model "Auto create a function for system versioning", we have made the following improvements:Changed the dynamic model strategy to 'staged'. Added the creation of the domain. Aligned the code with our Code guidelines. Changed the control_procedure strategy to 'staged'.Improved the model "Working with dates in SQL"changeFor the model "Working with dates in SQL", we have made the following improvements:Revised the table and removed some columns. Changed the control procedure to 'staged' so the assigning will be done automatically. Changed the code for the insertion of the date_helper to be able to update and insert new records where needed. Note: Feel free to add extra columns and functionality where needed, for example:is_working_day / production_week / number_of_days_in_month This is merely a first setup for a date_helper table.Improved the model "Getting domain elements in SSMS shortcut"changeWe have made the following improvements to the model "Getting domain elements in SSMS shortcut":Changed the control_procedure strategy to 'staged'. Changed the dom_id domain to varchar(128) (was 200) to be aligned with the dom_id of the Software Factory. Changed the template with all the domains to contain elements from the Software Factory instead of checking IAM, which is not desirable and costs more performance.Improved the model "Extract a file name from a file path"We have made the following improvements to the model "Extract a file name from a file path":Added 2 domains and a function. Changed the control procedure strategy to 'staged'. Added 2 unit tests. Fixed that an error would occur when a file path without a backslash ('') was given as input.Improved the model "Translating model objects in business logic"We have made the following improvements to the model "Translating model objects in business logic":Added the function get_dom_elemnt_id to be able to retrieve the element_id of a domain value. For example: order_status with database value 1 can be retrieved with select dbo.get_dom_elemnt_id('order_status',1). Added some more examples of type_of_objects in the control procedure code.Combined and improved the models "Convert UTC marked dates to locale dates" and "UTC and local time conversion"changeWe have merged the models "Convert UTC marked dates to locale dates" and "UTC and local time conversion" into one model.The resulting model has only one function, with an input date time, from_time_zone, and to_time_zone.This way, you are flexible in how you use the function.When you are always in the same timezone, you could create your own function:convert_local_to_utcconvert_utc_to_localYou can then define your own timezone as convert_local_to_utc and convert_utc_to_local. RemovedRemoved the model "Auto refresh"changeWe have removed the model "Auto refresh". Auto refresh can be done by an extended property.For more information, see the Extended properties,RefreshOnDocumentSwitch and RefreshOnTabSwitch.Removed "Auto generate reports"changeWe have removed the model "Auto generate reports".In version 2022.1 of the Thinkwise Platform, we introduced the generate report connector. See Generate report.This connector covers the functionality of the model that was removed.Connecting it to a write file / SMTP connector is explained in this Community post.Use these resources for creating a system flow.Removed the model "Knowledge application"changeWe have removed the model "Knowledge application" from the Thinkstore.Removed the model "Change detection"changeWe have removed model "Change detection". The documentation has the same example: https://docs.thinkwisesoftware.com/docs/sf/business_logic#change-detectionRemoved the model "Replace HTML font family"changeThe model "Replace HTML font family" is outdated and no longer relevant, so we have removed it.Removed the model "Change font of html fields from Segui ui to Arial"changeWe have removed the model "Change font of html fields from Segui ui to Arial". This model did not add anything functional. It only replaced a tag with another span tag that included a font in HTML.Removed the model "Session variables"changeWe have removed the model "Session variables".See the documentation for how to use the session variables:Extended propertiesGenerated session variableshttps://learn.microsoft.com/en-us/sql/t-sql/functions/session-context-transact-sql?view=sql-server-ver16Removed the model "Default error handling on SQL Server"changeWe have removed the model "Default error handling on SQL Server" because the Software Factory handles the most common errors with atomic transactions.See the documentation:Atomic transactionsWeave code into atomic tasksRemoved the model "Drag and drop between subjects example"changeWe have removed the model "Drag and drop between subjects example" which demonstrated drag and drop between subjects.In version 2024.2 of the Software Factory, an enrichment is available to create a drag-and-drop task between two subjects.See Available model enrichments. FixedFixed the model "SAP API stock, consumption and production booking"fixWe removed broken prefilters from the model "SAP API stock, consumption and production booking" and fixed some broken prefilter queries missing the t1. prefix.Fixed the model "Multi lang data"fixWe have changed the error handling. Before, if the table was not in the model, there would be an error.Now, the code will not be executed in that case. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,This release includes a breaking change: Indicium has been updated to use the ASP.NET Core 8 Runtime. 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.2.10 here. You can read more about Indicium's features in the Indicium user manual. Contents About Indicium Breaking Update to .NET 8 Questions or suggestions? BreakingUpdate to .NET 8Indicium has been updated to use the ASP.NET Core 8 Runtime.When running Indicium on a local/internal IIS server, ensure the ASP.NET Core 8 Hosting bundle has been installed. When running Indicium on a cloud platform such as Azure/AWS, ensure you are using a base environment that has .NET 8 installed.See also the prerequisites for Indicium. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

May 21, 2024:Release 2024.2.10 This release is the same as 2024.1.14.0May 13, 2024:Full release 2024.1.14.0 We have solved the following known issues in the release candidate: The image combo would erroneously show text in the grid when no image was available. The grid had empty space at the bottom. The chart would not respond to size changes. Fixed: When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours. Hello everyone,In this sprint, we have added the possibility to resize the width of the vertical tab panel, new keyboard shortcuts, the ability to display domain element translations as values in the pivot grid, and more. Continue reading to see what else is new and what we have fixed in this release. 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.2.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, e.g., 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. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. 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.2.10 here ContentsDemo Universal GUI version 2024.2.10 New and changed Resize vertical tab panel Added "Max no of records" indicator, page size, and pagination Drag and drop in the sort pop-up Shortcut support in filter pop-up Navigate with "Enter" in Filter form component 'Remember me' on login page renamed to 'Stay signed in' F5 / ALT+F5 shortcut keys to refresh data Pivot grid supports displaying domain elements Export wizard - visible columns Added element name to tooltip Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedResize vertical tab panelnewUsers can now resize the width of the vertical tab panel by dragging its edge sideways. This makes it possible to view detail tabs with longer names. The width of the vertical tab panel is remembered between sessions. Added "Max no of records" indicator, page size, and paginationnewWhen the setting Max no of records is specified on the subject, and more records than the maximum are available, an indicator is displayed to let the user know there are more records. Also displayed are the number of records per page and the pagination.If no Max no of records is specified, the indicator will not be shown, but the page size and pagination details will still be available. Drag and drop in the sort pop-upnewThe user can now drag and drop an item from the left to the right and vice versa in the sort pop-up. In addition, the user can use drag and drop to rearrange the position of items within the list on the right.Drag and drop in the sort pop-up Shortcut support in filter pop-upnewWe have added support for keyboard shortcuts in the filter pop-up. Users can use Enter or Tab to navigate to the Operator or Value fields.If the extended property Keybindings=classic is enabled for the application (classic mode), you can use Enter for navigation. If the extended property Keybindings=classic is disabled for the application (modern mode), you can use Tab for navigation.In addition, for both keybinding modes, we have changed the initial focus to the first Value field.Filter pop-up with keyboard shortcuts Navigate with "Enter" in Filter form componentnewIf you use the classic keybinding in the Filter form component, Enter now moves to the next filter form field. 'Remember me' on login page renamed to 'Stay signed in'change'Remember me' on the login page has been renamed to 'Stay signed in' to prevent any confusion about this functionality. This functionality is for preventing the user from being logged out, not for remembering login details. F5 / ALT+F5 shortcut keys to refresh datachangeInstead of loading the entire web application, users can now refresh the data in the current view by pressing the F5 or Alt+ F5 keys.If the extended property 'Keybindings’ is set to 'classic’, the refresh shortcut key is F5. If the extended property 'Keybindings’ is set to 'modern’ or not set at all, the refresh shortcut key is Alt+F5.This change means that the F5 / Alt+ F5 keys now have the same behavior as clicking Refresh in the action bar. Pivot grid supports displaying domain elementschangeThe pivot grid can now display domain element translations as values. If no domain element is defined for a value, the original value is displayed. Export wizard - visible columnschangeThe export wizard showed subject columns that were marked as hidden on the subject or its variant in the Software Factory. These are now hidden from the wizard, except for the primary key columns. This is because the primary key columns are needed to re-import the modified Excel sheet later. Added element name to tooltipchangeWe have added element names to the tooltips of tasks, reports, buttons, and tiles. If you hover your cursor over, for example, a task, the tooltip shows the task name, its shortcut, and its information text. The tooltip shows the task name, shortcut, and information text Minor fixes and tasksIn some cases, hovering over a screen with a chart could cause errors. These errors were ignored, but could be seen in the browser development tools. They no longer occur. Fields on the same line would always equal 100% even when the field width would indicate otherwise. We removed this limitation, allowing fields on the same line to exceed 100% of the available width. This allows the Universal GUI to better scale sets of fields. You can set the Field width in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > group Form. When using a Filter form on a screen that did not allow searching, the Filter form would not show up at all. This has been fixed. A bad request error was displayed when pagination was combined with the maximum number of records and the active record would fall outside of the maximum number of records. This has been fixed. The user is now asked whether they want to open the active record on a separate screen. Click "Show" to open the row on a separate screen Previously, you could not save your report with a custom name. Now, you can give your report a custom name by including a report parameter with Property set to Export path (menu Processes > Reports > tab Report parameters > group Model settings). When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Fixes for grid and form:A combo box with the bit datatype would not display the expected values in both the grid and form. This issue has been resolved, so now domain elements can be used in place of Boolean values. In a read-only grid, the summary row would be cut off if the row height was set too low. Now, it will always have a minimum height of 44, and appear correctly regardless of the row height. When a hidden column was used in the grouping of a grid, its values were visible to the user. Now, the hidden column is still used, but no longer visible. In some cases within the Formlist screen component, the fields would be slightly misaligned if an auto-complete combo control was present. This has been fixed. Navigating over editable datetime controls using the Tab or Enter keys without changing its value caused the field to PATCH its value and the record to get marked as changed. This is now prevented. Navigating over datetime controls in the editable grid by arrow keys without making changes caused the field to PATCH and the record to save. This was especially undesirable on mandatory fields since it made the previous record red because it could not be saved. This is now prevented. If you typed a dot as the first character in a numeric field, then a dot again to reach the decimals, and then added some numbers, only the first number entered was displayed as a decimal. After typing the first decimal, the cursor would jump to the beginning of the field and add the next numbers at the front. This would turn 0.1200 into 2.1000, for example. This has been fixed. When navigating through records in the editable grid using ↑ or ↓, the value of the previous record that was just changed was not always processed correctly, especially on date/time type columns. This has been fixed. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours. What we will be working on next sprint The next sprint we will be working on:Performance improvements (including grid default edit mode performance) Support report generation action dropdown Breadcrumb update on detail subject navigation More shortcut support Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,This release features the further integration of AI-powered model enrichments in the Software Factory. We have added more generic model enrichments, and model enrichments specifically designed for a seamless migration to the Universal GUI. Many of the new and existing model enrichments have also become available as tasks on the screens where they can be of immediate use. The AI code review has been improved, and is now also available as a task so you can request it manually.An important visual change is that we have restructured the default menu in the Software Factory. It now contains a new menu group, Integration & AI, that allows easy access to screens that were previously only available as a tab in a branch.Another new feature in the Software Factory is the columnstore index support. A columnstore index offers substantial data compression, resulting in improved query performance. A powerful use case for columnstore indexes is storing LLM embeddings.This release also includes 9 Community ideas.In this summary, you will read about some of the key features of this release. Read all the detailed release notes in the Thinkwise Documentation. ContentsContents Highlights of this release Further integration of model enrichments in the Software Factory Enhanced screen layouts and a new menu group Columnstore index support in the Software Factory Some other new features Questions or suggestions? Highlights of this releaseFurther integration of model enrichments in the Software FactoryThis release contains further integration of (AI-powered) model enrichments in the Software Factory.You can now use prompt chaining in AI-powered model enrichments. This allows for more sophisticated prompting techniques and breaking down complex tasks into manageable steps. Five more model enrichments have been added, for example, one to generate application logic based on natural language business rules. Sixteen new model enrichments have been added to support the migration of your application to the Universal GUI. To improve the usability of the model enrichments, many are now accessible as tasks within the Software Factory interface. We will continue this integration in future releases. When objects or code are generated using the AI-powered features of the Software Factory, the field Modified by is now set to "Generative AI". This makes it clear that the object or code was generated by AI. The AI code review has been improved and is now also available as a task. Enhanced screen layouts and a new menu groupIn both the Software Factory and IAM, we have enhanced the layouts for several screens.In IAM, we have enhanced the layout of the screen Applications (menu Authorization).In the same way, we have changed the layout of the screen Branches in the Software Factory (menu Models).In addition to this, the Software Factory now has a new menu group, Integration & AI. It is home to the following menu items:Web connections Email providers File storage locations OAuth servers Generative AI AutoML (the menu group Machine Learning has been removed)These features remain available in the screen Branches in the Software Factory, but are more easily accessible this way. Columnstore index support in the Software FactoryWe have enhanced the Software Factory's support for creating indexes by introducing the option to generate columnstore indexes.What is a columnstore index?A columnstore index is a type of index used in relational database management systems (RDBMS) to optimize the storage and retrieval of data in tables. Unlike traditional row-based indexes, which store data in rows, a columnstore index stores data in columns. They offer substantial data compression, leading to a significant reduction in required storage space. This results in improved query performance due to reduced I/O requirements when executing queries that involve scanning and aggregating large volumes of data. This is typically done in analytical and reporting workloads.A columnstore index can be clustered or non-clustered. You can find both options as two new index types when creating an index in the Software Factory, in the menu Data > Data model > tab Tables > tab Indexes. Some other new featuresA new process flow connector: Web connection. It is an enhanced and reusable version of the HTTP connector. Public OpenID Connect clients - In IAM, you can now mark a client application as a public client. This feature allows two types of OpenID clients: confidential and public. Merge changes into an arbitrary branch - In the Software Factory, you can now start merge sessions with source and target branches that are not the origin branch. You could use this, for example, when you are developing two different releases (each with their own release branch and develop branches) and need to merge changes from one release into the other. Tree-based menu designer - To make the Software Factory suitable for use with the Universal GUI, the menu designers (known as modelers) have been replaced with a Tree component. As a result, menus can be visualized and maintained once the Software Factory uses the Universal GUI. Jump to model rights - You can now navigate from various objects, such as a table, menu, or process flow, to the Model rights overview. Jump to objects - From the tab Deploy in Functionality, you can now jump easily to tasks, the data model, process actions, subroutines, and reports. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

May 13, 2024:Full release 2024.1.14.0 We have solved the following known issues in the release candidate: The image combo would erroneously show text in the grid when no image was available. The grid had empty space at the bottom. The chart would not respond to size changes. Fixed: When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours. Hello everyone,In this sprint, we have added the possibility to resize the width of the vertical tab panel, new keyboard shortcuts, the ability to display domain element translations as values in the pivot grid, and more. Continue reading to see what else is new and what we have fixed in this release. 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.1.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, e.g., 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. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. 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.1.14 here ContentsDemo Universal GUI version 2024.1.14 New and changed Resize vertical tab panel Added "Max no of records" indicator, page size, and pagination Drag and drop in the sort pop-up Shortcut support in filter pop-up Navigate with "Enter" in Filter form component 'Remember me' on login page renamed to 'Stay signed in' F5 / ALT+F5 shortcut keys to refresh data Pivot grid supports displaying domain elements Export wizard - visible columns Added element name to tooltip Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedResize vertical tab panelnewUsers can now resize the width of the vertical tab panel by dragging its edge sideways. This makes it possible to view detail tabs with longer names. The width of the vertical tab panel is remembered between sessions. Added "Max no of records" indicator, page size, and paginationnewWhen the setting Max no of records is specified on the subject, and more records than the maximum are available, an indicator is displayed to let the user know there are more records. Also displayed are the number of records per page and the pagination.If no Max no of records is specified, the indicator will not be shown, but the page size and pagination details will still be available. Drag and drop in the sort pop-upnewThe user can now drag and drop an item from the left to the right and vice versa in the sort pop-up. In addition, the user can use drag and drop to rearrange the position of items within the list on the right.Drag and drop in the sort pop-up Shortcut support in filter pop-upnewWe have added support for keyboard shortcuts in the filter pop-up. Users can use Enter or Tab to navigate to the Operator or Value fields.If the extended property Keybindings=classic is enabled for the application (classic mode), you can use Enter for navigation. If the extended property Keybindings=classic is disabled for the application (modern mode), you can use Tab for navigation.In addition, for both keybinding modes, we have changed the initial focus to the first Value field.Filter pop-up with keyboard shortcuts Navigate with "Enter" in Filter form componentnewIf you use the classic keybinding in the Filter form component, Enter now moves to the next filter form field. 'Remember me' on login page renamed to 'Stay signed in'change'Remember me' on the login page has been renamed to 'Stay signed in' to prevent any confusion about this functionality. This functionality is for preventing the user from being logged out, not for remembering login details. F5 / ALT+F5 shortcut keys to refresh datachangeInstead of loading the entire web application, users can now refresh the data in the current view by pressing the F5 or Alt+ F5 keys.If the extended property 'Keybindings’ is set to 'classic’, the refresh shortcut key is F5. If the extended property 'Keybindings’ is set to 'modern’ or not set at all, the refresh shortcut key is Alt+F5.This change means that the F5 / Alt+ F5 keys now have the same behavior as clicking Refresh in the action bar. Pivot grid supports displaying domain elementschangeThe pivot grid can now display domain element translations as values. If no domain element is defined for a value, the original value is displayed. Export wizard - visible columnschangeThe export wizard showed subject columns that were marked as hidden on the subject or its variant in the Software Factory. These are now hidden from the wizard, except for the primary key columns. This is because the primary key columns are needed to re-import the modified Excel sheet later. Added element name to tooltipchangeWe have added element names to the tooltips of tasks, reports, buttons, and tiles. If you hover your cursor over, for example, a task, the tooltip shows the task name, its shortcut, and its information text. The tooltip shows the task name, shortcut, and information text Minor fixes and tasksIn some cases, hovering over a screen with a chart could cause errors. These errors were ignored, but could be seen in the browser development tools. They no longer occur. Fields on the same line would always equal 100% even when the field width would indicate otherwise. We removed this limitation, allowing fields on the same line to exceed 100% of the available width. This allows the Universal GUI to better scale sets of fields. You can set the Field width in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > group Form. When using a Filter form on a screen that did not allow searching, the Filter form would not show up at all. This has been fixed. A bad request error was displayed when pagination was combined with the maximum number of records and the active record would fall outside of the maximum number of records. This has been fixed. The user is now asked whether they want to open the active record on a separate screen. Click "Show" to open the row on a separate screen Previously, you could not save your report with a custom name. Now, you can give your report a custom name by including a report parameter with Property set to Export path (menu Processes > Reports > tab Report parameters > group Model settings). When a page size is defined, we now ignore the setting *Max. no. of records*. If you use paging, you will never get the indicator that the maximum number of records is reached. If you do not want pagination, you should explicitly set the setting *Page size* to ‘-1’. Both settings can be found in the menu *User interface* > *Subjects*. Fixes for grid and form:A combo box with the bit datatype would not display the expected values in both the grid and form. This issue has been resolved, so now domain elements can be used in place of Boolean values. In a read-only grid, the summary row would be cut off if the row height was set too low. Now, it will always have a minimum height of 44, and appear correctly regardless of the row height. When a hidden column was used in the grouping of a grid, its values were visible to the user. Now, the hidden column is still used, but no longer visible. In some cases within the Formlist screen component, the fields would be slightly misaligned if an auto-complete combo control was present. This has been fixed. Navigating over editable datetime controls using the Tab or Enter keys without changing its value caused the field to PATCH its value and the record to get marked as changed. This is now prevented. Navigating over datetime controls in the editable grid by arrow keys without making changes caused the field to PATCH and the record to save. This was especially undesirable on mandatory fields since it made the previous record red because it could not be saved. This is now prevented. If you typed a dot as the first character in a numeric field, then a dot again to reach the decimals, and then added some numbers, only the first number entered was displayed as a decimal. After typing the first decimal, the cursor would jump to the beginning of the field and add the next numbers at the front. This would turn 0.1200 into 2.1000, for example. This has been fixed. When navigating through records in the editable grid using ↑ or ↓, the value of the previous record that was just changed was not always processed correctly, especially on date/time type columns. This has been fixed. Opening a lookup pop-up while adding data another lookup pop-up caused unexpected behavior in the last opened pop-up. The CRUD buttons were gone and the form did not show because there was no record selected in the open pop-up. This has been fixed. A case where this could happen was when adding a project address and an address (base table of project address) while booking hours. What we will be working on next sprint The next sprint we will be working on:Performance improvements (including grid default edit mode performance) Support report generation action dropdown Breadcrumb update on detail subject navigation More shortcut support Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this sprint, we have added the new Live Error Log, improved the performance of query generation, solved an issue with double logging, and we have changed Indicium's behavior regarding default logic to match the behavior of the Windows GUI.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.1.14 here . ContentsAbout Indicium New and changed Added Live Error Log Query performance improvements Minor fixes and tasks Fixed double logging of first process action in process flow monitor Fixed small incompatibility regarding default logic compared to the Windows GUI Questions or suggestions? New and changed Added Live Error LognewWe have introduced a new feature called the Live Error Log. The purpose of this feature is to improve the experience for developers when trying to troubleshoot issues.All users who have access to downloading Indicium's error log will also have access to the new Live Error Log page, which can be found at the same location as the regular error log - on Indicium's landing page. In the future, the Universal GUI will also add a link to the Live Error Log to the menu. Indicium landing page menuThe screenshot below shows what the Live Error Log looks like. When opening the page, it shows the last 100 (configurable) log entries that you would also see in the error log file.If web sockets are enabled on the web server, the Live Error Log will maintain an open connection with Indicium and new log entries will be added automatically as they occur. If web sockets are not enabled, the page can simply be refreshed to see the latest log entries.The Live Error Log allows for text-based filtering, and you can indicate a minimum error level (for example, errors only), which makes it much more useful than the error log file. Finally, when Indicium is horizontally scaled, and Redis is configured for state management, the Live Error Log will show the log entries of all Indiciums simultaneously, rather than just the Indicium you're connected to. Live error logAnother addition to the Live Error Log compared to the regular error log is that, when applicable, log entries will include the request URL that caused the error, as shown in the image below. Expanded entry in the live error logIf you want to change the number of log entries that Indicium will keep track of for the Live Error Log, you can do so by adding the configuration settings shown below inside of the Logging:ErrorLog section of the appsettings.json."LiveErrorLog": { "MaxTailLength": 100}The purpose of these changes is to make the error log much more digestible.The next version of Indicium will most likely contain similar improvements for the Database Event Log and the Process Flow Monitor. In the near future, we will also look into the possibility of deep linking from error messages in the Universal GUI to entries in the Database Event Log and/or the Live Error Log, so we look forward to those changes! Query performance improvementschangeWe have improved the performance of the queries generated by Indicium in two specific situations:All platforms When using a CHAR, NCHAR or GRAPHIC datatype for a key column of a lookup subject. Because these data types can have trailing spaces, Indicium applies an RTRIM to them to remove these trailing spaces from the result. However, Indicium did this in a subquery on the JOIN clause, causing the index to be unusable for the join. This has been changed, greatly improving the performance of joins on these lookups to resolve display values. Oracle and DB2 only When sorting on any alphanumeric column that is indexed. Indicium would apply an UPPER function to the column in order to ensure consistent results on case sensitive platforms. The usage of this UPPER function can decrease the performance of the sorting operation when that column is indexed, as the index cannot be utilized effectively. When the domain is configured as "Upper case", the UPPER function will no longer be applied as the data is assumed to be in uppercase already. If you have columns with uppercase data, it will be beneficial to mark the domain as "Upper case". Minor fixes and tasks Fixed double logging of first process action in process flow monitorWe have fixed an issue that caused the first process action of a process flow to be logged twice in the Process Flow Monitor in some cases.Fixed small incompatibility regarding default logic compared to the Windows GUIWe have fixed a small incompatibility regarding the default input and default output settings compared to the Windows GUI (menu Models > Model content > tab Columns > tab Form > tab Performance).When the settings were applied as illustrated below: Default input/output settingsIndicium would interpret this as the property neither triggering the default logic nor supplying the value for that property when another property triggered the default logic. Since no value was supplied for the parameter but Default output was turned on, this would cause the property to be nulled when not explicitly set within the default logic.The Windows GUI still supplies the value for the property if another column triggers the default logic as long as Default output is also turned on, causing properties to retain their value when not explicitly set within the default logic.Since this behavior was a breaking change compared to the longstanding behavior of the Windows GUI, we have decided to change it. Indicium will now also supply the value to the default logic if Default input is turned off but Default output is turned on. In the future, a more clear distinction between 'trigger' and 'value input' will be made for the checkbox Default input in the Software Factory. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this sprint, we have added support for placing the filter and toolbar components vertically and upgraded our DevExpress reporting component.You can read more about the Windows GUI's features, in the user interface guide.Download Windows GUI 2024.1.13 here. ContentsNew and changed Upgraded DevExpress reporting component Filter and toolbar components can now be placed vertically Questions or suggestions? New and changed Upgraded DevExpress reporting componentnewWe have upgraded our DevExpress reporting component in the Windows GUI to support the latest DevExpress reporting features. These can be configured in the 1.70 version of our DevExpress report designer.Filter and toolbar components can now be placed verticallychangeIn the screen type designer, you can now add filter and toolbar components vertically to your screen type. Note that actually displaying these components vertically is only supported in the Universal GUI. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this sprint, we have added support to the Web GUI for the 2024.1 and 2024.2 versions of the Thinkwise Platform, and we have fixed an issue with closing an application after switching between applications with different menu types.You can read more about the Windows GUI's features in the user interface guide .Download Windows GUI 2024.1.14 here . Download Web GUI 2024.1.14 here .ContentsNew Support for Thinkwise Platform versions 2024.1 and 2024.2 Minor fixes and tasks Closing application not possible after switching between IAM applications Report export file path parameter name null Questions or suggestions? New Support for Thinkwise Platform versions 2024.1 and 2024.2Web GUIAs promised during our developer event, we have added support for the 2024.1 and the upcoming 2024.2 versions of the Thinkwise Platform. This will make it easier to transition from the Web GUI to the Universal GUI. Minor fixes and tasks Closing application not possible after switching between IAM applicationsIn some cases, closing an application was not possible: after switching between applications with different menu types (tiles versus list), without opened documents (none opened yet or all already closed). This has been fixed. Report export filepath parameter name nullIn Windows GUI version 2024.1.12.0, functionality was added based on the export filepath parameter name. Because of this, a user could sometimes encounter the error 'name' argument cannot be null. This has been fixed. 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: IAM & SF (All supported versions) 20240426 - Aggregation expression dependency Aggregations derived from expression columns were disappearing after filters were applied to the grid. This has been fixed so that the behaviour of the aggregations are consistent. IAM 2024.1 20240423 - Migrate classic user preferences It was possible for the migration to fail when if multiple applications for the same model and branch are present and users of these applications have user preferences for cubes. This has been fixed. SF (All supported versions) 20240430 - Lock branch whilst merging base models into work models When a base model supplied a table and a column and had the look-up display column set up for a reference, the trigger code would set the look-up display column of the table before the actual column was added to the work model. This has been corrected. SF 2023.2 and up 20240501 - Only check running jobs before locking branch When jobs were queued in succession, an error could occur during the Generate definition process. This has been fixed.

Hi everyone!We’ve released the following platform improvement this week: IAM 2022.2, 2023.1, 2023.2, 2023.3 20240415 - Corrected effective variant rights Indicium did not always received the correct rights for a variant with a different form layout then its base. This has been corrected. For IAM 2023.2, an additional hotfix came out to resolve an issue: 20240417 - Remove label width and field width from col form function SF 2023.1 20240419 - Correct deletion of delete strategy program object When combining the staged and delete strategies, there was a small chance that program objects were not set stale upon generating definitions which could lead to code being omited from a generated code file. This has been fixed.

April 15, 2024:Full release 2024.1.13 Fixed: Pressing Alt + Enter when using the `classic` key binding in a multiline control, would not insert the enter at the caret position, it was always added at the end. This has been fixed. While using 'classic' key bindings, there was an issue navigating through grid records in a default editable grid. When the arrow keys were used to leave a record, the changed value wasn't always saved. This has been fixed. A bad request error occurred in both key binding modes when leaving an empty text field using arrow key navigation in the default editable grid. This has been fixed. We fixed a bug in the release candidate where some bars (like tasks, reports, prefilters, cube views, search) were erroneously removed from the screen. We fixed an issue in the release candidate where the cube view bar buttons sometimes were too big when the bar was placed vertically. Hello everyone,In this sprint, we added support for user-defined prefilters, improved the screen component bars, and more. Read on for the full list of changes. 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.1.13For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., 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. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. 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 2023.1.13 here New and changedUser preference - User-defined prefiltersNewUsers can now save their custom filters as a prefilter with the new Save as new prefilter button that is available at the bottom of the filter dialog. When saving a filter as a prefilter, they must provide a unique name.After saving, the prefilter is automatically updated and becomes available in the toolbar for the specific subject. In the overflow menu, with the option Own prefilters, users can add, delete or edit their own prefilters. Edited prefilters can be saved as a new prefilter with a different name.For IAM administrators, the user-defined prefilters are located in the menu Authorization > Users > tab User preferences > vertical tab Prefilters. These options are only available for the Thinkwise Platform version 2024.1 and up.Save as prefilter User preference - Remember prefilter statusnewThe Universal GUI can now remember and apply a user's preferred state for a prefilter (activated or de-activated). A prerequisite for this feature is that in the Intelligent Application Manager, the setting Prefilter status is enabled in the Advanced menu > Master data > UP availability.For example, if a user deactivates a prefilter that was initially activated, and returns to that screen, the prefilter will automatically be deactivated by default. Enhanced filter from grid column headersnewWe have further enhanced the column header filter functionality in the grid, specifically for lookup-type columns. Users can now select multiple lookup values in the pull-down filter on a grid column header. This update is designed to make data filtering more intuitive and efficient for users.The column header filter in a grid now includes the following features:More comprehensive filtering options: when you open the column header filter on a lookup column, a pull-down appears with a list of options. It takes into account all relevant subject filters, except the one on the column you are currently filtering. This means you have access to all relevant options within your current context. Checkbox selection: each option in the list is preceded by a checkbox. Select the checkboxes for the items you want to include in your filter. Limit on filtering options: to ensure optimal performance and usability, the list of options is limited to 25 items. If the list exceeds this limit, a search/suggestion field is shown to find and select specific options in the extensive list. To customize the limit, use the extended property called LookupGridHeaderFilterOptionsLimit. When you re-open the filter pull-down, any active filters are checked, making it easy to see your current filter settings. IN operator filter functionality: the selected options are added to the IN filter. This gives you more control over your data and makes it easier to customize your view. Dropdowns in the filter pop-up from the toolbar allow multi-item selection and the IN operator, to present the filter at both ends.Checkbox selection in a column headerA search field when the number of items exceeds the limit Screen component bar improvementsnewWe have made the following changes to improve the screen component bars:We have added support for the following screen components: Search Cube view bar Prefilter bar Report bar You can now position screen component bars vertically. This includes the Task bar and Action bar screen components. To include a bar into the action bar, you can add the AlwaysMergeToActionBar screen component property to any bar. It will stay in place in the Windows GUI. Screen component bars now listen to their alignment/dock properties. Task tiles are now removed if no tasks have been defined. Show grand total of a rownewIn the Software Factory, the cube view setting Show row grand total adds a row containing the rows' summed values to the pivot. You can configure this row to appear at the top or the bottom of the pivot.You can define the settings for the grand total of a row in the menu User interface > Subjects > tab Components > tab Cube > tab Cube views > tab Form:Show row grand total - Select to add a row containing the summed-up values of the rows Total position - Select the position of the row: Far: the row will be shown at the bottom of the pivot. This is the default behavior. Near: the row will be shown at the top of the pivot. The row grand total, set to position "Far" Change pivot settingsnewUsers can now change the pivot settings. When a pivot is available, users can open the Pivot settings pop-up from the overflow menu. Here, they can enable totals for rows or columns. They can also choose where to display the grand total. Cube view sortingnewUsers can now set the sorting of the dimensions through the overflow menu of the cube view: Sort. The dimensions can be sorted Ascending or Descending on their own display value or on a value present in the cube view. Mass update on lookupsnewIn release 2024.1.12, we introduced a feature allowing users to update multiple records simultaneously through the Mass update functionality. It had a known limitation: it did not allow updating lookups. Mass update now supports updating lookup fields. Conditional layout for progress bars the same in grids and formschangeThe form progress bar was displayed according to the conditional layout settings. Still, the grid progress bars displayed the default style with the conditional layout behind it on the grid cell. Now, the grid and form progress bars look the same. A progress bar in the cardlist component now also displays conditional layouts.All three (form, grid, and cardlist) now apply the text color setting to the percentage. Make sure that there is enough contrast with the background color(s).Progress bars now have a uniform look Search bar translationchangeIf you are using the Software Factory version 2024.1 or older, and upgrade to version 2024.1.13 of the Universal GUI, you will see Filter instead of Search in the search bar. If you do not want this, you can change the translation. In the menu User interface > Translation, filter for the Translation object combined_filter and change its translation.As of Software Factory version 2024.2, the translation will be Search again by default.The translation object 'combined_filter' Minor fixes and tasks Fixes for HTML fields:We have fixed the following security advisory: https://github.com/advisories/GHSA-5359-pvf2-pw78. This fixes a security issue in the HTML editor in case the HTML data would have a malicious SVG in an <embed> or <object> tag. Adding an SVG in this way is not possible through the Universal GUI or Windows GUI, so in normal usage, this problem couldn't occur. If an HTML field was able to be filled by a malicious actor, for example, directly through the Indicium API, this vulnerability would become relevant. In that scenario, if a user would go into edit mode on a HTML control, the attacker's JavaScript payload inside the SVG file would be executed. In the worst case, if the SVG file was served from the same origin as Indicium, the attacker would have been able to execute Indicium requests under the victim user's credentials. Links added to HTML fields will now properly open in a new tab. Previously, the HTML control text could overlap with the action button. This has been fixed.Fixes for display and usability:If you do not declare a page size in the Software Factory, the table only displays the first 100 rows. We have added pagination so you can still navigate to the rows after row 100. When opening a lookup popup, the correct page is now activated to show the currently selected record. If you used dark mode and collapsed the sidebar and expanded it again, a brief white flash would show on the right-hand side. This has been fixed. The dropdown scrollbar on mobile devices was only visible when scrolling. It is now always visible. The dropdown is configured to display all items regardless of the dimensions of the device on which it is being viewed. Group headers in a form are now placed lower to show they are connected to their group. Some users experienced continuous resizing of tiles paired with the appearance and disappearance of a scrollbar. This would happen if multiple tiles were stacked vertically, and the list was just long enough to make a scrollbar appear and also narrow enough that any less space would cause the tiles to shrink. In applications with multiple menu options (on the Windows platform), closing a document in the tile menu sometimes automatically selected the next open document. This has been fixed. We fixed a bug in the release candidate where some bars (like tasks, reports, prefilters, cube views, search) were erroneously removed from the screen. After a user saved a cube view, the order of the series or category fields was sometimes not maintained correctly. This has been fixed. We fixed an issue in the release candidate where the cube view bar buttons sometimes were too big when the bar was placed vertically.Fixes for grid and forms:In an auto-editable grid, users should be able to switch records without saving if no changes have been made. However, if they switched records after selecting a date-type cell, the grid would always behave as if changes had been made, even if only the focus had been set. It caused validation errors if the record had unfilled required fields. This has been fixed. Pressing Ctrl + Enter now only saves the record and does not navigate to the next field. After saving a form, the focus always moved to the first field of a form, although it should remain on the last field edited, or in case of an error, on the first field that contained an error. This problem has been fixed. The active record of all parent subjects is refreshed while working in a detail subject. While the lookup data of a grid column was loading, a loading indicator was shown which was not aligned correctly. This has been fixed. Subjects with auto-save enabled would sometimes make multiple requests to Indicium to delete the staged resource. Only one request would succeed, the others would return a 404, which could be observed in browser development tools. This has been fixed. If the parent subject had no record, the Universal GUI used to make detail tabs and detail tiles of unrelated details read-only, so they could not be clicked. This was wrong because unrelated details do not need a parent record and should therefore remain clickable. This has been fixed. Occasionally, when a user pressed Shift to select something in the browser, the grid or tree could enter a state that prevented the selection of rows. This has been fixed. Using the arrow keys to navigate through checkbox cells in a grid would be very inconsistent. This has been fixed. While using "classic" key bindings there was an issue navigating through the grid records in a default editable grid. When a record was left by the arrow-keys the changed value wasn't always saved. This has been fixed. Pressing Alt + Enter when using the “classic” key binding in a multiline would not insert the enter at the caret position. It was always added at the end. This has been fixed. In both key binding modes, a bad_request error occurred when leaving an empty text field using arrow-key navigation in the default-editable grid. This has been fixed. Pressing Alt + Enter when using the `classic` key binding in a multiline control, would not insert the enter at the caret position, it was always added at the end. This has been fixed. While using 'classic' key bindings, there was an issue navigating through grid records in a default editable grid. When the arrow keys were used to leave a record, the changed value wasn't always saved. This has been fixed. A bad request error occurred in both key binding modes when leaving an empty text field using arrow key navigation in the default editable grid. This has been fixed.Fix for reports:Exporting a report to PDF would open the PDF in a new tab in preview mode. Now, the PDF will be downloaded directly, based on the configuration in the Software Factory.Fixes for import:When using the Import wizard, a problem could occur if you went back one screen and then continued with the wizard. If you selected how to import the data, went to the next screen, and then went back to change that selection, your updated selection would not be registered at the Indicium API side. The wizard would appear to have the correct option selected, but the actual import would be performed using your original selection. This has been fixed. We found an issue when importing .csv files in Firefox. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Shortcut support in pop-ups Technical and functional 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 relaxed the rules for duplicate site bindings when creating a new site, and we have fixed how Universal GUI deployments are handled for version 2023.3.12.0 and up.Download the Thinkwise Deployment Center 3.2.0 here. ContentsChanged Relaxed rules for duplicate site bindings when creating a new site Fixed Fixed Universal GUI deployments for version 2023.3.12.0 and up Questions or suggestions? Changed Relaxed rules for duplicate site bindings when creating a new sitechangeWhen deploying the Universal GUI or an Indicium Service Tier to IIS, users can also create a new site. The screen where this is done tries to detect if the bindings to be added conflict with ones that already exist on the server. Bindings used to be considered duplicates if the port number was already in use.Starting from this version, they are now only considered duplicates if they match another binding exactly. As long as a different hostname, IP address, or port is used, the deployment flow will continue. Fixed Fixed Universal GUI deployments for version 2023.3.12.0 and upfixStarting with the 2023.3.12.0 release of the Universal GUI, the sample configuration file has been renamed from config.json to config.sample.json. The Deployment Center will now attempt to read from config.sample.json and fall back on config.json when loading the base configuration from the package. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this sprint, we have updated the DevExpress Reporting library updated to version 23.2.5.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.1.13 here. ContentsAbout Indicium New and changed DevExpress Reporting library updated to version 23.2.5 Questions or suggestions? New and changed DevExpress Reporting library updated to version 23.2.5changeWe have updated our DevExpress Reporting library from version 21.2.10 to version 23.2.5. This updates includes various new features such as the ability to add multiple watermarks to a report. More information about new features can be found on the DevExpress website.Due to a change in the cross platform drawing engine the following setting has been removed:Reporting:DevExpress:UseCrossPlatformRendererWindows and Linux will now always select their preferred engine. See Use Reporting on Linux and macOS for more information. 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 improvement this week: SF 2023.3 20240322 - Enhance used separator for AI code review There's a small chance where the used file encoding interferes with a separator used in code. When running the AI code review platform improvement, this could cause an issue in one of the procedures. This has been improved to prevent the issue.

This is an additional release for the Universal GUI version 2024.1.12. It contains one change.Lookup dropdowns were not (always) filtered by the active prefilters of the lookup subject. This caused dropdowns to offer too many items, even the ones the user was not allowed to see. This has been fixed.The 2024.1.12.2 release is now available for download in TCP.We strongly advise updating to this version if your product uses Universal GUI releases 2024.1.12.0 or 2024.1.12.1.

March 18, 2024Full release 2024.1.12. In the Release Candidate, we added support for user-defined prefilters. However, we had to make the decision to postpone that feature due to unexpected issues. We expect to release it again as part of the next release. Several fixes Hello everyone,In this sprint, we have added a large number of user preference features to the Universal GUI. Users can now, for example, save custom cube views, show or hide columns, and save their custom filters as a prefilter. To improve the migration from the Windows GUI to the Universal GUI, we have added Windows GUI-like navigation options for editable fields in forms and grids. Additionally, we have further enhanced the Formlist component and the pivot grids. For custom CSS, we have added more options.We have also done some minor fixes and tasks. DemoAs always, we have made a demo for you: try it here . Before trying it out, Select Clear Cache on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.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, 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. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. 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.1.12 here ContentsDemo Universal GUI version 2024.1.12 New and changed User preference - Save custom cube view User preference - Show or hide columns User preference - Remember prefilter status User preference - Sort & group Changed filtering in lookup-type columns Windows GUI-like navigation option for editable fields in form and grid Formlist - Lookup editors Formlist - more enhancements Grid - Update multiple records Custom CSS - More control over combo and suggestion controls Custom CSS - Classes for identifying mandatory fields in a grid Import - Asynchronous import function on Azure Pivot grids - Conditional layout Pivot grids - Access underlying cell data Pivot grids - Collapse/expand nested series Minor fixes and tasks Fixes in full release 2024.1.12 What we will be working on next sprint Questions or suggestions? New and changed User preference - Save custom cube viewnewUsers can now save custom cube views by selecting Save as cube view from the overflow menu. They can enter a name and select the default type.Save as cube viewThe saved cube view will show next to the model cube views.A custom cube view next to the model cube views To delete it, users can select Delete cube view [name] from the overflow menu. User preference - Show or hide columnsnewUsers can now show or hide grid columns in read-only grids. This option is available in the overflow menu of the grid. Additionally, they can change the Lock columns until setting.To configure the availability of these options for your users, see Configure user preferences .Show or hide grid columns in read-only grids User preference - Remember prefilter statusnewThe Universal GUI can now remember and apply a user's preferred state for a prefilter (activated or de-activated). A prerequisite for this feature is that in the Intelligent Application Manager, the setting Prefilter status is enabled in the Advanced menu > Master data > UP availability. For example, if a user deactivates a prefilter that was initially activated, and returns to that screen, the prefilter will automatically be deactivated by default.In this release candidate, the status for user-defined prefilters is not yet remembered. User preference - Sort & groupnewUsers can now change the sort order in a grid if the permission Allow sort has been selected for that table (menu User interface > Subjects > tab Settings > tab Permissions > group Data).With this permission enabled, a user's changes in the sort order and grouping will be saved, and the next time they log in, their preferences will be applied to the table.If a user selects the option Sort... in the menu, the Sort popup will appear. Here, a user sees the current status of the table: the columns on which the grid is sorted, the order of the sorted columns, and the direction in which the data in every column is sorted. If the Group permission has been selected in the Software Factory, a user also sees the Group button and if the data in the table is grouped by column(s).In the Sort popup:To sort data, users can select column(s) on the left and use the >> button to add and sort columns in ascending order. To exclude columns from sorting, users can select column(s) on the right and use the << button to move the columns to their default position on the left. To group columns, users can select columns on the right and then select the Group button. If the selected column has been grouped already, the columns will be ungrouped. To move all the columns from the right to the left, users can select the Clear button. If OK is selected, all the groups and sorting will be removed. To return to the default settings as set in the Software Factory, users can select the Default button. To change the column order on the right, users can select a column and the Up button. If the column above is grouped and the selected one is not, the selected one becomes grouped, too. Users can use Down to move columns down in the same way. To change the sorting direction in a column, users can select a column at the right and the button Direction.Known issue:When a column that is not visible in the grid is added to the sorting, it will be temporarily visible. Refreshing the Universal GUI, going into edit mode, closing and reopening the document, or switching pages in pagination will hide the column. Then, it will no longer become visible.The Sort popup Changed filtering in lookup-type columnschangeTo enable further development of filtering from grid column headers, we have changed how other column filtering methods like filter forms and quick filters work.Multiple records may have the same display value, like two employees with identical names. When filtering by that name, we now show all matching records for both individuals. This means we filter by the display value and duplicate names appear only once in the dropdown list.However, column filters applied through the Change filter process flow action filter by key. These filters are treated as system filters and no longer visible in the filter form or grid header. Users can add more filters to the column to refine their filtering. System filters are automatically cleared using the Clear filters option from the toolbar because system filters may be applied to hidden columns.Once a column is filtered, the in-line filter form dropdown shows all relevant options. Previously, the dropdown was filtered by its filter value, resulting in a single option being shown. Windows GUI-like navigation option for editable fields in form and gridnewUsers can now use Windows GUI-like navigation through the editors of editable components in the Universal GUI. This can be helpful if you migrate from the Windows GUI to the Universal GUI.We have added the extended property KeyBindings to support changing how you navigate your application with the keyboard. You can configure it per application or model in the Software Factory. Choose the value "Classic" for Windows GUI-like navigation or the default value "Modern" for the standard Universal GUI navigation.The keyboard shortcuts are as follows:Navigation Classic Modern Move to next editable control in form/grid Enter Tab Move to previous editable control in form/grid Shift + Enter Shift + Tab Open the file explorer from the file editor Alt + Enter Enter We have added new keyboard shortcuts to avoid conflicts if you choose to use "Classic" navigation.You can create a new line in a multiline editor by pressing Alt + Enter instead of Enter. You can open a dropdown list by pressing ↓.The following editors do not support "Classic" navigation:Label Group header label Group header icon Signature Image upload Image blob Image link Video link HTML (in grid) Formlist - Lookup editorsnewWe have added support for lookup editors in the Formlist screen component. Previously, it only showed a loader and no editor.Now, the editor is shown, and the selected value is saved right after the user selects an option, just like the supported types of editors already do.Note:Related lookup editors are not yet supported. For example, booking hours: the selected project filters the subproject field with the subjects that belong to the selected project. The pop-up button is not available. We aim to keep the Formlist simple, so there is no option to look up or select a record from the pop-up. The configuration of a lookup relation in the Software Factory knows different control types. In a Formlist, comboboxes will become suggestion controls. Comboboxes (dropdowns) have the disadvantage that the list of options is loaded directly. This would result in many requests for options on initial load or data refresh. Suggestion controls load a limited number of options and only when working on the field. Formlist - more enhancementsnewIn addition to the support for lookup editors as described above, we have added even more functionality to the FormList component:In a default procedure, the Formlist will now correctly apply new values, also to other columns than the edited column. For a layout procedure, the layout will be applied after a value has been changed. For the following setting, the Formlist rows will be refreshed after a value has been changed: menu User interface > Subjects > Settings > Performance > group Refresh > field After update > select Subject. Note: if refreshing is not strictly necessary, select None since refreshing slows down performance. Grid - Update multiple recordsnewUsers can now update multiple records ('mass update') in tables at once, by selecting the Update option from the overflow menu. They can select the fields to update and enter a new value for each of themAfter the update, a message appears, showing the number of records updated and any errors found.Updating lookups directly is not supported. This feature will be included in a future update. Mass update is unavailable while the subject is in edit mode.Update multiple records in tables Custom CSS - More control over combo and suggestion controlsnewWe support two different types of combobox controls: the Combobox (dropdown list) and the Combobox with a suggestion. Previously, these types shared the same CSS styling.We have added new CSS classes to make it possible to use different CSS styling for each type of combobox:'combo-select' applies to the Combobox (dropdown list) control 'autocomplete-select' applies to the Combobox with a suggestion controlYou can now visually distinguish between the controls if needed. Custom CSS - Classes for identifying mandatory fields in a gridnewThe grid now includes classes on each cell to show the column's state. This allows you to hook into these classes in your custom CSS. You can find these classes on the .conditional-layout-container. Use this option to make certain types of cells stand out more, for example, if they contain an error.The classes are:.mandatory for cells with a mandatory field .readonly for cells with a disabled field .has-error for cells with a field that has an error Import - Asynchronous import function on AzurechangeThe import function on Azure now runs asynchronously to avoid timeouts. This ensures the file imports are completed regardless of their duration. This feature requires WebSockets. The system will fall back to the synchronous method if WebSockets are not configured.For more information on the configuration of WebSockets, see Enable WebSockets in Azure. This also applies to the Universal GUI. Pivot grids - Conditional layoutnewWe have added support for conditional layouts for pivot grid fields (menu User interface > Business Intelligence > tab Cube views > tab Conditional layout). This allows you to draw a user's attention to specific fields.Situations where the conditional layout is useful:In standard cube views (not custom cube views) In basic conditional layouts. A cube view can have multiple conditional layouts. For grand totals and nested fields (categories) Pivot grids - Access underlying cell datanewIt is now possible for a user to double click a pivot grid cell to open a pop-up with a grid containing the underlying data for that specific cell. This new grid is read-only and adheres to any filters set on the pivot grid. Pivot grids - Collapse/expand nested serieschange newNested series (columns) in pivot grids are no longer default expanded, but users can still expand them manually. This is now similar to the categories (rows).For both series and categories, we have added support for the setting to expand them by default. It is available in the menu User interface > Business intelligence > tab Tables > tab Cube fields > tab Cube view fields > tab Form > checkbox Expand. Minor fixes and tasksA layout can change from mandatory to non-mandatory. Saving an empty non-mandatory field that was previously saved as mandatory resulted in the error cannot_save_document_field_error. This has been fixed. Non-existent data was incorrectly displayed as 0 in the chart. Now, the chart no longer draws these absent data. We have resolved two issues that incorrectly positioned tasks in the action bar, even though they were located elsewhere on the screen. This has been fixed. Sometimes, the overflow menu did not appear in the action bar on mobile phones. This has been fixed. Now, when space is limited, the CRUD buttons will collapse individually into the overflow menu. It was possible to use the CRUD buttons while an operation was already in progress, resulting in an error. This is no longer possible. When the process action Activate detail was used as a starting point, a 'bad request' error would appear. This has been fixed. In some cases, the pinned cell within the grid that shows the sum aggregation of data showed a non-numerical element like a checkbox instead of a number. Now, it always shows a number if a sum value can be calculated. In grids with the option Auto-save enabled, manually saving a record left the grid in edit mode. This has been fixed. Now, the grid exits edit mode automatically after saving. Editing shortcuts are now limited to components on the screen that allow add, copy, and edit actions. Lookup pop-up buttons did not always open the pop-up on the first click. This has been fixed. If a user opened a lookup pop-up and clicked the Add button quickly enough, the pop-up would occasionally not switch to the tab where the data for the new item could be inserted. This has been fixed. If you used the filter form with numeric or date/time controls, this could result in a bad request network error, causing empty controls on dropdowns. This has been fixed. Fixes in full release 2024.1.12The value "Classic” of the KeyBindings extended property that was added to the release candidate was case-sensitive. We have fixed this, so it is no longer case-sensitive, and the value "classic" now also works. Filtering a dropdown using the IN operator was not applied since the last release candidate. This is fixed now. On both numeric controls and dropdowns (data value), filters on value 0 are now applied. We have fixed an incorrect translation in the new Mass update feature. The default width of fields in filter forms has been reduced to 250px, just like fields in the regular form. As part of the release candidate of this version, we introduced the concept of system filters. These are filters from the change filter process flow action. We decided not to show system filters to the user anymore. It turns out that some of our customers used these filters as initial input for the filter form, where users can modify it to see another set of data, for example, to show all data from the current year 2024 initially. It is now possible again to filter on these columns from the filter form. The system filters are still not displayed to the user. They will be replaced when the user filters for a different value/criteria in the same column. What we will be working on next sprintThe next sprint we will be working on:Grid header filtering for look-up-type columns Pivot row (category) grand totals Mass-update lookup-type columns Pivot grid sorting improvement Pivot grid total positioning user preferences Vertical bars Freely positionable prefilter, cube view, report and combined filter (search) bar Action bar content alignment Questions or suggestions?Do you have any 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: IAM & SF 2024.1 20240313 - Universal cube view field sorting Categories and series in cube views will now be properly sorted descending when configured as such. Previously, this would only work when the dimension was sorted on another cube field, such as a total. When a category or series was defined as sorted descending, this would not be picked up by the GUI. The category or series would be sorted ascending. This has been resolved for cube views which are part of the model as well as user-defined custom cube views.

Hello everyone,In this sprint, we have added an error message and status indicator for when WebSockets are disabled on the web server hosting Indicium.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.1.12 here. ContentsAbout Indicium New and changed Error message when WebSockets are disabled Questions or suggestions? New and changedError message when WebSockets are disablednewWe have included an error message for when WebSockets are disabled on the web server hosting Indicium. If the process flow monitor page is opened and WebSockets are not enabled or cannot establish contact, you will see an error message with helpful steps instead of a blank page.Additionally, we have added a status indicator to the top bar displaying Connected or Disconnected.Both the error message and status indicator aim to enhance the user experience by providing more information about the status of the connection to the server. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this sprint, we have added an extended property to improve the visibility of drag-drop tasks, and we have fixed a few minor issues.You can read more about the Windows GUI's features in the user interface guide.Download Windows GUI 2024.1.12 here. ContentsNew Extended property for drag-drop task visibility Minor fixes and tasks Changes in the grid not always saved Template history would not open Questions or suggestions? NewExtended property for drag-drop task visibilitynewTo determine the task visibility, the Windows GUI uses the display type set in the Software Factory (menu Processes > Task > tab Table tasks > tab Form > field Display type).However, drag-drop tasks were always hidden regardless of their display type. To inform the Windows GUI to use the display type for drag-drop tasks, you can now add the extended property UseDragDropTaskDisplayType to your model and set the value to "True".As of the Thinkwise Platform release 2024.2, the display type will always be used to determine the visibility of the task. Minor fixes and tasksChanges in the grid not always savedWe have fixed a problem where the grid would not save changes in some cases. This issue could happen when editing a single value and saving with Ctrl + Enter without leaving the cell. Template history would not openWe have fixed the template history in the Software Factory. If you open a template's history with Ctrl + H you can go back in time to a previous version of the template. Previously, the generated file would contain invalid characters in its name and not open. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

This is an additional release to Universal GUI 2024.1.11. It contains one change.On a slow or unstable connection it may happen that the task or report tile buttons were not loaded. This has been fixed.The 2024.1.11.1 release is now available for download in TCP.

February 19, 2024Full release 2024.1.11 In the Software Factory, we have the concept of unrelated details. Tables are linked but no columns are linked to each other to bind them. We have fixed an issue where an action was executed from an unrelated detail, causing the parent subject to be emptied. In that case, the detail was cleared too, which was unexpected. Hello everyone,In this sprint, we have added support for features that have been introduced in the Thinkwise Platform 2024.1 release, such as tying a column to a double-click task and auto_commit for default logic. We have also improved the task shortcuts and the preview component. Additionally, we have added a new extended property to lift grid row height safeguards and another one to open lookups full-screen. We have also made some minor fixes 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.1.11 For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., 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. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. 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.1.11 here ContentsDemo Universal GUI version 2024.1.11 Contents New and changed Support for tying a column to a double-click task Support for auto_commit for default logic Shortcut support Task shortcuts available in every context Preview component PDF enhancements Extended property to lift grid row height safeguards Active cube view retained Handling OpenID provider in poor network conditions Logout button when application or platform is not available Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedSupport for tying a column to a double-click tasknewIt is now possible to tie a double-click task to a column, as introduced in the Thinkwise Platform 2024.1 release.This feature allows each column in a grid to start a different process or handle specific data. For more information, see Configure a double-click task. Support for auto_commit for default logicnewThe Universal GUI now supports the auto_commit feature introduced in the Thinkwise Platform 2024.1 release. This feature makes it possible to automatically save the record after filling in a field. This opens up new possibilities, such as, after receiving input, starting a process flow for validations and automatically returning to edit mode. For more information, see New parameter for default logicThe Universal GUI supports this for:Editing a new or existing record after changing a value Directly after add/copy Changing a parameter value of a task or reportNot yet supported:In combination with auto-edit and auto-save The 'confirm update' confirmation on tables The 'ask' confirmation for tasks A task without tsf_send_progress does not show progress Shortcut supportnew changedIn addition to the shortcuts that we have added in the previous sprint, we have added some new options and made a change in behavior: Ctrl + R opens the advanced filter pop-up. For iOS, we have added Cmd key support since this is used more often than Ctrl. If you add your own shortcut for a task, Ctrl will be replaced by Cmd. You can add your own shortcuts for your application in the menu Processes > Tasks > tab Settings > tab General. After opening a new subject, the detail subject was activated for shortcuts. However, this differed from the Windows GUI where the main subject is activated. Therefore, we have changed this behavior, now, the Universal GUI also activates the main subject. You can switch between subjects to activate its shortcuts by: navigation between tabs focusing a form control activating a grid cell (new) Task shortcuts available in every contextnewTask shortcuts now function in every context, including detail subjects and subjects opened in a pop-up. Previously, they only executed tasks on the main subject.See, for example, the lookup pop-up in the screenshot below. When editing the Employee field in the Hours subject and clicking the zoom button behind the field, the pop-up opens with tasks in the taskbar. Now, you can do the same using keyboard shortcuts.Determining which subject is triggered follows the same logic as the CRUD shortcut keys introduced in the previous sprint. Additionally, the active subject is now also determined when a grid is activated, so the tasks with a shortcut are immediately available. Previously, the active subject was only determined when navigating to another subject, limiting the ability to return to a parent subject to execute shortcuts.Opening a pop-up using keyboard shortcuts Preview component PDF enhancementschangePreviously, when the Preview component showed a PDF file on Chrome on Android, the user had to open it in a PDF app to see its contents. On iOS, the preview would only show the first page and no toolbar. To address these issues, we now use an alternative way to display PDFs.NoteUse iOS version 15.4 and up. Use a recent version of Chrome (as required by the Lifecycle policy). Older versions like Chrome 114 do not work well with this new way of showing PDFs.This new way of previewing PDFs also fixes password protection and enables the use of links and forms in the PDF preview on iOS.To implement this solution, you need to configure two more MIME types on your web server. The web.config file included with this Universal GUI release already contains this configuration, so it can handle it for the IIS. Other web servers need the additional configuration:Extension MIME type .mjs application/javascript .ftl application/octet-stream Extended property to lift grid row height safeguardsnewIt is already possible to set the row height in the grid. The Universal GUI will mostly adhere to the set height but does add some safeguards to:Ensure the tap targets are large enough Ensure controls fit in the cells in edit modeIn some instances, you may want to remove these safeguards. This is now possible with the following extended property: DisableGridRowHeightSafeguards: trueNote:When you disable the safeguards, it is your own responsibility to ensure all the content in the grid fits and looks good. This setting also affects the values at the bottom of the grid. Another height may be necessary to ensure the values are visible. Check this carefully when testing this setting. Extended property for opening a pop-up full-screennewA new extended property, 'OpenLookupsFullScreen', is now available. By setting it to 'true', all lookup pop-ups will open at a larger size, around 90% of the screen. The size is not entirely full-screen to maintain recognition as a pop-up. Active cube view retainednewThe active cube view will now be retained when opening the same screen on different devices or in different browsers. Handling OpenID provider in poor network conditionschangeThe Universal GUI depends on Indicium to receive information about the usage of OpenID providers. This information determines whether the GUI should redirect to a provider. In poor network conditions, the request for this information might be lost, and the Universal GUI would show its login page instead. This could lead to errors when local login was disabled in IAM.Now, if the Universal GUI does not receive information from Indicium but has a loginAuthProviderHint in the config.json file, it will not show the username and password fields. Logout button when application or platform is not availablechangedWhen an application or platform is unavailable, users previously received one of the following error messages:'This platform isn't available for the application. 'This application is not available. Contact your administrator.' 'No applications available. Contact your administrator.'Now, a logout button appears adjacent to the login button in such situations. This prevents users from being unable to perform any actions due to user authorization failures. Minor fixes and tasksA few months ago, we changed the default position of tooltips from the bottom to the top. However, at specific heights, when the tooltip reached the top of the window, it would start flickering. This problem was partially resolved in the last sprint. Now, we have addressed the remaining occurrences. Tooltips will still be displayed at the top by default, but if they are too large, they will be shown at the bottom. We have solved some issues with the styling of the progress bar. The cut off label has been fixed and the alignment has been improved. The Formlist component disappeared after clicking the refresh button on the main subject. This has been solved. It was possible to use the CRUD buttons while an operation was already in progress, resulting in an error. This is no longer possible. We have fixed an issue that, some specific cases, a record was auto-saved directly when it was added or copied. This would lead to a validation warning. The labels in a chart were displayed in datetime format even though the datatype was date. This has been fixed. Previously, a horizontal scrollbar appeared in a filter as long as there was a filter condition. Now, it will no longer appear as it is unnecessary. What we will be working on next sprintThe next sprint we will be working on:Save and delete a user defined cube view. This allows a user to save a cube view they made with the pivot field editor. Save and delete a user-defined pre-filter. This allows a user to save a filter they created with the filter form as a pre-filter. Formlist improvements Excel-style filter look-up control Sort- and group pop-up Cube view pivot conditional layout Open drilldown from cube view pivot grid 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.1 and up 20240215 - Sync fix for double aliases Some synchronization scripts contained a double alias in a join. This has been fixed. SF 2024.1 20240215 - Deployment package manifest version When creatiing a deployment package the manifest contained the wrong version number. This has been corrected. Upcycler 2023.1 and up 20240216 - Temp db collation Sometimes the collation of the temp database can be different than the collation of the Upcycler database. This could cause a collation conflict. This has been fixed.

Hello everyone,We have fixed an issue that caused the ‘guid’ and ‘tsf_use_log_session_id’ session variables to be NULL for users with authentication type ‘External’, that logged in via an identity provider. This issue was introduced in Indicium version 2024.1.10.0. If you are currently using Indicium version 2024.1.10.0 or 2024.1.11.0 and you have one or more identity providers configured in IAM, then we recommend updating to version 2024.1.11.1. Please note that after updating Indicium, it may still be necessary for users to log out and log back in before the issue is resolved.Our apologies for any inconvenience caused by this issue.

Hello everyone,In this sprint, we have added new ways for clients to specify values for lookup columns and columns with elements when directly POSTing/PATCHing to table, task, and report endpoints.Note that we have also made a possible breaking change to how the OAuth server scope is applied. Please check the breaking changes section for more information.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.1.11 here. Contents About Indicium Contents Breaking OAuth server scope now applies to OAuth server login connector New and changed Added ways to choose Minor fixes and tasks Questions or suggestions? BreakingOAuth server scope now applies to OAuth server login connectorchangeThe OAuth server login process flow connector did not use the Scope setting of the corresponding OAuth server configuration when the scope input parameter was not assigned. This has been fixed.In addition, we have made a minor change to the OAuth user login connector. If this connector had an assignment for the Scope input parameter, but the value of the assignment was empty, it would erroneously fall back to the Scope setting of the OAuth server configuration. This should not happen because the existence of any assignment to the Scope input parameter should always lead to ignoring the Scope setting of the OAuth server configuration.As of this release, any assignment to the Scope input parameters for the OAuth server login and OAuth user login connectors takes precedence over the Scope setting for the OAuth server configuration. So, even if the input parameter is assigned to a process variable with no value, the OAuth server configuration scope will be ignored. However, if the input parameter is not assigned at all, the OAuth server configuration scope will be used instead in both cases.Note that both fixes have a small possibility of being a breaking change.For the OAuth server login connector, this change can be breaking when both of the following conditions are met:The OAuth server login connector has no assignment for the Scope input parameter. The corresponding OAuth server does have a Scope configured.In this case, Indicium would previously not send a scope to the OAuth provider, but as of this release, it will send the scope defined in the OAuth server configuration.For the OAuth user login connector, this change can be breaking when both of the following conditions are met:The OAuth user login connector is assigned to a process variable, and the value of this process variable may be empty. The corresponding OAuth server has a Scope configured.In this case, Indicium would previously send the scope defined in the OAuth server configuration to the OAuth provider, but as of this release, no scope will be sent.Check your process flow connectorsCheck the connectors that meet the criteria outlined above.For both cases, if the conditions are met, it will depend on your specific situation whether it will be an issue. New and changedAdded ways to choosenewWe have added new ways for clients to specify values for lookup columns and columns with elements when directly POSTing/PATCHing to table, task, and report endpoints.The first one is choose. Use it to choose a lookup value by providing the primary key values of the lookup source. This can be useful if the client knows from which source record to select the target value, but the foreign key from the target to the source is not part of the source's primary key.POST <metasource>/<application>/<target_table>{ "<target_FK_column>": { "choose": { "<source_PK_column>": "36724a01-521a-4b4a-b51f-30d943f9a0d0" } }}The second one is choose_by_display. You can use it to choose a lookup value by providing the value from the column configured as the display column.Note:The display value must resolve to a unique record in the source. When the display column has domain elements, the given value must correspond to the database value of an element instead of the translation. Use choose_by_element instead when selecting based on element translation values.For example, if the model contains a project table:project_id project_name 1234 Example project And a sub_project table that has a sub_project.project_id -> project.project_id lookup which is configured to display the project.project_name. Then Indicium allows the following when adding a new sub_project:POST <metasource>/<application>/sub_project{ "project_id": { "choose_by_display": { "display_value": "Example project" } }}Which, in the example above, would resolve to 1234 as the value for project_id for the new subproject.The third way is the choose_by_element translation. Use it to choose the database value for a column configured with elements based on the translation value of an element.Note:Use this for both regular columns and lookups that have configured a display column with elements. When used with a lookup, the value must resolve to a unique record in the source, just like when using choose_by_display.For example, in a model containing a domain example_domain configured with the following elements:element_id element_value example_element_1 0 example_element_2 1 example_element_3 2 And element translations:element_id lang_id transl_value example_element_1 EN Element one example_element_2 EN Element two example_element_3 EN Element three example_element_1 NL Element één example_element_2 NL Element twee example_element_3 NL Element drie Then Indicium will allow a column using this domain to be posted or patched like this:POST <metasource>/<application>/example_table{ "some_element_column": { "choose_by_element": { "element_transl": "Element two" } }}PATCH <metasource>/<application>/example_table(1234){ "some_element_column": { "choose_by_element": { "element_transl": "Element three" } }}By default, this feature uses the session user's language to match the translations or the application's fallback language if the application does not contain translations for the user language. The above example assumes this to be English (EN) for the user making the example request. You can overwrite this behavior by providing a language_hint value with the column. For example, to use Dutch instead of English in the previous example, specify the following:POST <metasource>/<application>/example_table{ "some_element_column": { "choose_by_element": { "element_transl": "Element twee", "language_hint": "NL" } }}If the language for the language_hint cannot be found, the application's fallback language will be used instead. Minor fixes and tasksWhen shutting down or restarting, Indicium attempts to wait for all running system flows to finish before ending the process. Although this functioned correctly, it sometimes generated error messages in the error log. This issue has been resolved. 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.3 & 2024.1 20240205 - Allow loading of runtime configurations on SF meta source A column was missing for the Windows GUI to load all active runtime configurations for the given user when starting with the meta source SF. Due to the absence of this column, the GUI did not want to load. This has been fixed.

Thinkstore model updates (2024.2)

Release notes Indicium (2024.2.10)

Release notes Universal GUI 2024.2.10

Thinkwise Platform release 2024.2

Release notes Universal GUI 2024.1.14

Release notes Indicium 2024.1.14

Release notes Windows GUI 2024.1.13

Release notes Windows GUI and Web GUI 2024.1.14

🚀 Platform improvements for week 17

🚀 Platform improvements for week 16

Release notes Universal GUI 2024.1.13

Release notes Thinkwise Deployment Center 3.2.0

Release notes Indicium 2024.1.13

🚀 Platform improvements for week 12

Extra release - Universal GUI 2024.1.12.2

Release notes Universal GUI 2024.1.12

🚀 Platform improvements for week 11

Release notes Indicium (2024.1.12)

Release notes Windows GUI (2024.1.12)

Extra release - Universal GUI 2024.1.11.1

Release notes Universal GUI 2024.1.11

🚀 Platform improvements for week 7

Hotfix release - Indicium 2024.1.11.1

Release notes Indicium (2024.1.11)

🚀 Platform improvements for week 6

Filter by product