Product Updates

Hi everyone! We’ve released the following platform improvements this week: SF 2024.3 20250117 - Only add parameters to existing program object items When upgrading a system-versioned table, in some cases it was possible that a parameter was generated for a program object item that did not exist. This has been resolved. IAM 2024.3 ⭐ 20250117 - Improve performance of process flow schedule log We have added an index to the process_flow_schedule_log table that enhances the performance of starting in system flow instances.

Hello everyone, We have become aware of issues with DevExpress reports in Indicium in the last release. If you use DevExpress reports, we recommend updating to version 2024.3.14.1 The 2024.3.14.1 release of Indicium is now available for download in TCP. Our apologies for any inconvenience caused by this issue.

Hello everyone, In this release, we have fixed some issues. You can read more about Indicium's features in the Indicium user manual. About Indicium Two types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.3.14 here. Contents Hello everyone, About Indicium Changed in Indicium Improved debugging of 'Web connections' in the Process Flow Monitor Minor fixes and tasks Questions or suggestions? Changed in Indicium Improved debugging of 'Web connections' in the Process Flow Monitor change We have improved the debugging experience of Web connections in the Process Flow Monitor by including additional debug data regarding the actual request data that was sent. This should make it significantly easier to identify why a Web connection is not working as expected. Minor fixes and tasks The mass update functionality did not take the dependent lookup fields into account when trying to translate the display value to a data value. This could result in an error, because the display value is sometimes only unique in the context of the other filters. This has been fixed. We have fixed an issue that caused requests for lookup sets to partially omit context filters, outside of edit mode, when a parent level was empty, but the top level parent was not. Requests will now always result in an empty lookup set. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

December 23, 2024 Full release 2024.3.13 (from release candidate 2024.3.13) Solved the following issues found in the release candidate: Occasionally, the lookup pop-up in edit mode was not filtered based on the partially typed value. This has been fixed. In the release candidate of this version, we introduced a new styling for the menu. For the full release, we have made some extra changes to the styling: Improved the vertical alignment of items Added more rounded corners Ensured that when the scrollbar appears on collapsing a menu group, the menu content no longer moves Hello everyone, This release contains the first part of the styling update proposed by our UI/UX designer. As a first step, the menu component has been updated to give the Universal GUI a fresh new look. We have also added support for field width in cubes, and users can now reorder columns in grids by dragging column headers. Additionally, we have changed the casing of tab header labels, improved the filtered lookup pop-up, and fixed several minor issues. We have updated data test IDs to improve compatibility with testing solutions like Cypress. Note that this change may break your tests if they rely on the previous data test IDs. Demo As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.13 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, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium. Download the Universal GUI version 2024.3.13 here Contents Demo Universal GUI version 2024.3.13 Contents Breaking Updated data test ids New and changed Menu styling updated Casing of tab header labels Reorder columns in grids Support for field width in cubes Filtered lookup pop-up Minor fixes and tasks What we will be working on next sprint Questions or suggestions? Breaking Updated data test ids change Many data test ids were identical and overlapped on a single page. The following changes have been made to better facilitate your testing solutions: Controls that are part of the grid can now be identified by grid-cell__colId__... as opposed to form-field__colId_... to better separate them. Grid cells now show as grid-cell-row-X__colId as opposed to grid-cell__colId to be identifiable individually. Grid renderers now show as grid-cell-row-X__colId__renderer. We added data test ids to some renderers that did not have them yet. Listbar items in an expanded group now show up as listbar__groupId__item__groupIndex as opposed to listbar__groupId__item to differentiate between listbar items. We added data test ids to the pivot grid field list editor cancel button chips cubeFieldId__return. Check your tests Check your tests and update the data test ids accordingly. New and changed Menu styling updated change On the Community, the styling update proposed by our UX/UI designer has been a popular topic. In this release, we have implemented the menu component of this styling update, which gives the Universal GUI a fresh new look. In future releases, we will continue to implement other parts of the styling update. We also plan to introduce an indicator (a colored dot) on menu groups to show that there are items with badges within those groups. Updated menu styling Casing of tab header labels change community idea Previously, the casing of the component and detail tab labels were always in uppercase. The community requested the possibility of using case-sensitive headings instead. We have made sure the casing of component and detail tabs now use the casing as specified in the translation. If you want to retain the uppercase, add the following CSS to custom.css: .tabstrip__button__title { text-transform: uppercase !important;} Reorder columns in grids change You can now allow users to reorder columns in grids by dragging column headers. The column order is persisted as user preference: if the user logs out and logs in again, the column order will be the same as they left it. To allow users to reorder columns, you must authorize them in IAM by selecting a configuration in the menu Authorization > Users > tab Form > group User preferences > field Configuration for which the following user preferences are enabled: Column order - allows the user to change the column order in grids. Number of locked columns - allows the user to lock columns by dragging them into the locked column area at the left. If this option is not selected, the user can only reorder locked columns within the locked column area. To configure the default grid settings in the Software Factory, see Grid settings for subjects. Reordering columns in a grid Support for field width in cubes change The Universal GUI now supports the setting Field width (px) for cube view fields in a pivot grid. It can be set in the Software Factory in the menu User interface > Business Intelligence > tab Tables > tab Cube views > tab Cube view fields. Without a field width explicitly set, the following applies: If the field is a category, the column width is auto-sized based on its content. If the field is a series, the column width is set to 110px. Additionally, column resizing has been enabled for all pivot columns, the minimum width is 50px. Filtered lookup pop-up change When a user opened a field's lookup pop-up, it previously displayed all data. Now, if the user types a search string in the field before opening the pop-up, only matching items are loaded. This improves performance and enhances usability. Minor fixes and tasks We have fixed conditional layouts not working in tasks and reports. A process flow could get stuck on the Refresh action when a subject was edited. We have fixed this by ensuring the process flow will now follow the red arrow and continue onto the next step that should be followed after an unsuccessful step. Previously, SVG files were not cached but were always fetched from the server. This has been fixed. We have fixed an issue where pasting an image copied from the Snipping Tool or from disk into the HTML editor did not work. When users applied a filter in a detail subject, the loading indicator would not spin. This has been fixed. When updating multiple records (also known as 'mass update'), the lookup editor for selecting constant values showed only the values already used in the current table. This issue has now been resolved. Previously, setting the Page size to 0 or less (such as, -1, -2) while leaving Max no of records empty would still apply pagination to the subject. This has been changed so that setting Page size to 0 or less will now always disable pagination. To improve performance, count requests are no longer made for subjects with pagination disabled. When a task was executed on an empty subject, the Universal GUI would not communicate the subject variant to Indicium. This situation could cause unexpected behavior, such as Indicium rejecting task execution because it used the wrong task variant. Also, some data requests would be blocked unexpectedly. This issue has been fixed. What we will be working on next sprint In the next sprint, we will work on maintenance; due to the holidays, we will have limited capacity. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hi everyone! We’ve released the following platform improvements this week: SF 2024.3 20241216 - Include Endpoint request header table in Merge base models Due to an oversight in the task code generation, the table Web connection endpoint request header was missing from the task. This resulted in the base model data not being copied from the base model into the work model. This has been fixed. IAM 2024.3 20241219 - Added allow_create_pat field to Import AD group task The task to import users from a given Active directory group was missing a field, causing an error when using the task. This has been resolved.

Hello everyone, In this release, we have made an improvement to the Scheduler and fixed some issues. You can read more about the Windows GUI's features, in the user interface guide. Download Windows GUI 2024.3.13.1 here. Contents Contents New Refresh Scheduler via task Minor fixes and tasks Questions or suggestions? New Refresh Scheduler via task new It is now possible to refresh the entire Scheduler via a task, ensuring that not only the visuals but also the resources are up to date. This is useful when you configure a process flow with multiple actions and want to refresh the scheduler at the end. Previously, refreshing was only possible for specific tasks such as drag-drop, resizing, or double-clicking. You can configure this refresh by creating a table task that is linked to the appointment table and setting the option Refresh after execute to Document (menu Processes > Tasks > tab Table tasks > tab Form). (fixed in 2024.3.13.1) Minor fixes and tasks We have fixed an issue where changing the column width was not being saved as a user preference. This issue only occurred when the grid had group headers. (fixed in 2024.3.13.0) We have fixed an issue where dragging and moving a floating document caused the active pinned document to switch to the first visible document. (fixed in 2024.3.12.1) We have fixed an issue where, after startup, the Windows GUI switched to the first visible document and displayed a grey box in front of it. (fixed in 2024.3.12.1) This happened only if start objects (either user-specific or group-specific) were present. We’ve fixed a null-reference error when opening a document from a process flow (fixed in 2024.3.13.1) Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Release notes Indicium 2024.3.13 Hello everyone, In this release, we have made a change where process variables with very large text values will now be shortened before they are sent to the process flow monitor. Read the full release notes below. You can read more about Indicium's features in the Indicium user manual. About Indicium Two types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.3.13 here. Contents Release notes Indicium 2024.3.13 About Indicium Contents New and changed Questions or suggestions? New and changed change Process variables with very large text values will now be shortened before they are sent to the process flow monitor. Large binary values were already shortened but it was still possible for hundreds of megabytes of text data to be sent to the process flow monitor. This could result in errors and memory problems. Large text values will now be shown as: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent feugiat lorem in odio laoreet tincidunt. Vestibulum ante ipsum primis in porta ante... (15340629 more characters) 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 2024.3 20241125 - Fix reapply of retention setting When changing the retention period of a system-versioned table, the upgrade script didn't re-apply the new setting properly. This has been fixed.

November 25, 2024 Full release 2024.3.12 (from release candidate 2024.3.12) Solved the following issues found in the release candidate: In the release candidate, we introduced taskbar dividers for the toolbar. However, we decided not to include them in the full release because we want to improve them. We have fixed bad_request errors from cubes containing dates. This problem was introduced in the release candidate. Activating a detail tab from a process flow did not work in a specific case where the detail tab was hidden within nested component tabs. This issue has been fixed. In the new HTML editor options, the default font family could not be selected from the dropdown. This option has now been added. Additionally, the default font size was not available in the HTML editor dropdown. The dropdown has been replaced to provide more control over font size. Select the font size Solved the following urgent issues that didn't make the release candidate: A crash that occurred when opening the tree on a touch device has been resolved. Opening lookup pop-ups from an empty subject sometimes showed unfiltered data. This issue occurred when the lookup field value depended on the value of another lookup field. For example, when booking hours, the subproject depends on the selected project. Previously, the pop-up would show all possible subprojects, even those not associated with the user’s project. Now, in such cases, the pop-up opens empty. When editing a lookup, the available options sometimes were not limited by the prefilters with the Default prefilter state set to On . In some cases, this caused a slowdown in loading the options or even in the Universal GUI itself due to a large number of options being loaded. This issue has been resolved. Editing a lookup field sometimes changed the value of other fields unexpectedly. This issue has been fixed. When two process flows are running on the same subject, the first one is aborted. In some cases, this flow would continue sending follow-up requests to Indicium, causing 404 statuses. This is now prevented. A process flow starting with an Activate document process action was started twice. Now, it is started only once. We identified a situation where the task trigger Refresh active row stopped the process flow. This problem occurred when a task was removed from the table and a detail tab showing a table with related data for that row was open at the same time. The row would remain visible and the process flow would stop. In the Network tab in DevTools, server requests would return HTTP 404. Now, the row is visually removed and the process flow continues. Hello everyone, In this release, we have added support for Windows authentication, multi-row deletion, and advanced sorting in cubes. We have also extended the HTML editor pop-up with more options and improved the breadcrumbs to show the location of your most recent action. Demo As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.12 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, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium. Download the Universal GUI version 2024.3.12 here Contents Demo Universal GUI version 2024.3.12 New and changed Support for Windows authentication Support for multi-row deletion Support for advanced sorting in cubes Support for HTML forms in Preview More options in the HTML editor pop-up Context-sensitive breadcrumbs Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changed Support for Windows authentication new The Universal GUI now supports Windows authentication. For a smooth login experience, the Universal GUI now redirects users to the Indicium login page when Windows authentication is enabled for Indicium (menu Authorization > Users > tab Form > group Authentication). The login page of Indicium allows users to log in without re-typing their domain account credentials. For more information, see Windows authentication. Support for multi-row deletion new In the Universal GUI, you can now delete multiple selected records at once in a grid. Note: it is not yet possible to delete records across pages when pagination is enabled. In the GIF below, you can see how multiple records are deleted. In this example, "Slow 4G" network throttling is used to show the progress indicator. This progress indicator is not shown if deletion is completed within 200 milliseconds. Deleting multiple records in a grid Support for advanced sorting in cubes new We have added support for advanced sorting in cubes: Sorting a cube view on a domain with elements now follows the setting Sort order of elements, (Translation or Order no) in the menu Data > Domains > tab Form > tab Domains. In the tab Elements, this setting is available as Sequence no. You can now sort a cube view dimension by a cube field that is not present in the cube view itself (menu User interface > Business Intelligence > tab Tables > tab Cube views > tab Cube view fields > tab Form > tab Cube view field > setting Sort by cube field). Support for HTML forms in Preview new Previously, HTML forms embedded inside a webpage that used the Preview screen component were not allowed to be submitted. You could recognize this situation in the browser's developer tools by the message 'Blocked form submission to [your website]'. Now, it is possible to allow HTML forms to submit by setting the extended property UnsafePreviewAllowForms to true or yes. Enable this feature only when you trust the contents of all web pages you intend to embed. HTML forms lack the Cross-Origin Resource Sharing restriction that is otherwise standard for ways to perform web requests. This makes it possible to access external websites that normally disallow such requests. More options in the HTML editor pop-up new We have added more options to the HTML editor pop-up: Font size Font family Text style and alignment Table Links Image upload Context-sensitive breadcrumbs change Previously, the breadcrumb in the top bar of an open document showed the selected record of the main subject or, in the case of a zoomed-in detail document, it also showed the path to the parent subject. We have extended the breadcrumbs with nested detail navigation. They now show the location of your most recent action. For example, if you are working in Project > detail: Subproject > detail: Activities, the breadcrumb now shows: V.C. Partners > Development phase 2.0 > Analysis. This enhancement is particularly useful when your parent subject is hidden in an inactive tab, as it helps you track the project and subproject on which you are currently working. Minor fixes and tasks Generic: We have fixed an issue where the subject could get unresponsive after dragging a splitter to resize its components. Tooltips are now shown at the top end instead of the beginning. This change reduces the chance of overlap with previous elements. For grids and forms: The HTML control did not display pasted text if other text was already selected in the control. This issue has been fixed. Previously, when opening the lookup pop-up of an empty field, users would see the form with the details of the first item in the lookup table. Now, the list of lookup items is shown instead. This change prevents confusion by showing an unrelated item as if it were selected. For cubes: Domain elements were not translated in the x-axis and legend of a chart, and in the pivot grid. The displayed values were the raw database values instead of the translated ones. This issue has been fixed. We have improved the date/time notation in pivot grids and charts. All types are now formatted based on the browsers' local settings. When data in a category (row) contained a quote ', a bad request message was displayed when the category was expanded. This issue has been fixed. When a pivot grid was part of a nested subject, the deep link would try to use the parent subject as the domain, resulting in bad request errors. This issue has been fixed. For process flows: In some cases, the Activate detail tab process action did not work. Especially when it was located in nested component tabs or when jumping back to the first tab page. This has been fixed. For session expiration: Sometimes, switching to a different application when the session expired resulted in an application error. This has been fixed. When the session expired, multiple session-expired pop-ups were displayed instead of just one. This has been fixed. In some cases, when the session expired, an infinite loop was running in the background, triggering API requests. This has been fixed. What we will be working on next sprint The next sprint we will be working on: The styling update, starting with the menu and global frame of the application (we expect the styling update to take multiple sprints) Editable pivot grid Grid column reordering including saving this to User preferences Casing of tab header labels, to solve this community idea. 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 a digital signature to the report viewer for DevExpress reports. You can read more about the Windows GUI's features, in the user interface guide. Download Windows GUI 2024.3.12 here. Contents New Block unknown certificates in the GUI Questions or suggestions? New Block unknown certificates in the GUI new To ensure the integrity of our software, we added a digital signature to the Thinkwise.DevExpress.ReportViewer.exe (to preview the generated report). A digital signature attached to a file positively identifies the distributor of that file and ensures that the contents of the file were not changed after the signature was created. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone, In this release, we have improved the query speed of cubes and solved some issues with the LLM Chat completion connector and the Indicium log. You can read more about Indicium's features in the Indicium user manual. About Indicium Two types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.3.12 here . Contents About Indicium Contents Breaking LLM Chat completion connector with history parameter New and changed Improved cube query performance Minor fixes and tasks Questions or suggestions? Breaking LLM Chat completion connector with history parameter fix The process flow connector LLM Chat completion did not work correctly when the history parameter was provided as specified in the documentation. It would result in the error Error converting value 'User' to type 'Microsoft.SemanticKernel.AI.ChatCompletion.AuthorRole'.. This has been resolved. The connector now functions correctly only when the history parameter is provided as specified in the documentation: see Example customer support with LLM chat completion. In addition, we have added a new status code -4 Unsuccessful (Invalid chat history). It is returned when the chat history format is invalid. If you use the LLM Chat completion connector with the history parameter, validate that the input is correct. New and changed Improved cube query performance change We have improved the query speed of cubes. The number of unnecessary conversions has been reduced, resulting in faster queries and less overhead for the database server. Minor fixes and tasks The Indicium log would sometimes contain an error message about a ProcessFlowMonitorWorkItem being modified while it was not allowed. This has been fixed. We have fixed the error that would occur when assigning one column to multiple task parameters. This problem was mentioned in this Community topic. We have fixed the issue that the back button on various debugging pages would redirect the user to the root of the web server (which is often where the Universal GUI is located) instead of the root of Indicium (which is often something like /indicium). This problem was mentioned here. 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 2024.3 20241113 - Correct global session expiration settings We have introduced settings in 2024.3 to configure the default and extended session expiration. These settings influence how long a session is kept alive without any user interaction. We have resolved an issue where the extended session expiration was incorrectly set after the upgrade to 2024.3. This platform improvement will not affect your settings if you have already changed the extended session expiration settings.

This is an additional release for the Universal GUI version 2024.3.11. This release contains the following fixes for the lookup editor: A crash occurred when opening the dropdown if the lookup display column has a domain with elements. Furthermore, the representation would also be incorrect in this case. The translation was incorrect when the database value was 0. These issues were introduced in the 2024.3.10 release. The 2024.3.11.2 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2024.3.11. This release contains the following fixes: If the user was typing in an HTML input field, focused another application or browser tab, returned to the HTML field and typed some more, the second part that was typed would not be saved when saving the record. This is fixed now. When "Refresh after update" was set as "Row" and the user edited the row, the preview component would wrongly display just "No preview available". This has been fixed. The 2024.3.11.1 release is now available for download in TCP.

October 28, 2024: Full release 2024.3.11 (from release candidate 2024.3.11) Solved the following issues found in the release candidate: The date control flashed when choosing a different date from the one already set. This is fixed now. When updating the date, two PATCH requests were sent to Indicium. This is now a single request. Once a record was dropped into the grid, the records could not be dragged again. This is fixed now. In charts, Domain element translations were only shown for multi-series. Now also single-series are included. We improved tooltip behavior to hide it once the element is left by the mouse cursor. This way the user can't unexpectedly click a button by clicking its tooltip. We have fixed an issue where the subject could get unresponsive after dragging a splitter to resize its components. Hello everyone, In this release, we made sure users are always working on the latest deployed version when the Universal GUI is started. Besides, we added support for the conditional layout setting 'Apply to' and for multi-record selection in the default editable grid. For the barcode control, we introduced the option to suppress the on-screen keyboard on mobile devices. We also improved the date input and added week numbers to the date calendar on desktop. Additionally, we resolved several minor issues and tasks. Demo As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.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. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium. Download the Universal GUI version 2024.3.11 here Contents Demo Universal GUI version 2024.3.11 Breaking Support for Thinkwise Platform releases 2022.1 and 2022.2 has ended New and changed Now always using the latest version when loading Universal Date picker and date field changes Support for conditional layout setting 'Apply to' Support for multi-record selection in a default editable grid Support for the Between/Not Between operator in the Filter form component Button to open preview in a new tab Barcode control - Suppress on-screen keyboard Minor fixes and tasks What we will be working on next sprint Questions or suggestions? Breaking Support for Thinkwise Platform releases 2022.1 and 2022.2 has ended In accordance with our Lifecycle Policy , the Universal GUI support for Thinkwise Platform releases 2022.1 and 2022.2 has ended. Upgrade to at least the Thinkwise Platform release 2023.1. New and changed Now always using the latest version when loading Universal change We have made sure users are always working on the latest deployed version when the Universal GUI is started. This is a long-awaited feature on the community with a lot of upvotes (59!). This also fixes issues where it was not possible to log in to an application after a platform upgrade because the cache was not yet refreshed. The cache is now refreshed before the login page is shown. Going forward, a user should only get messages about a new version when the model is updated while the user is active in the application. Note that this solution is only applicable from this version onwards. Date picker and date field changes change On desktop, we have replaced the date picker component (used for Date and DateTime controls). This fixes some issues and allows us to now show week numbers. This was a highly requested community idea with 37 upvotes. In addition, the keyboard input has improved using input masks. For example, typing the year as '24' will now become 2024 instead of the input becoming empty after leaving the field. Besides this, in some browsers, when using the calendar to pick a date in a Date or Datetime control, we have fixed the field value being updated immediately after a user selected a different month. This fixes prematurely triggering the layout and default logic. Week numbers in the calendar Support for conditional layout setting 'Apply to' new In the Software Factory, you can specify to which components a conditional layout should apply. We have now added support for this setting in the Universal GUI. It is available in the Software Factory in the menu User interface > Subjects > tab Default/Variants > tab Data > tab Conditional layout > tab Form > tab Conditional layout > field Apply to. The following options are available: Grid, Form and Edit - The conditional layout is applied to grid and form, in both read and edit modes. Grid and Form - The conditional layout is applied to the grid and form, only in read mode Grid only - The conditional layout is applied to the grid, only in read mode Form only - The conditional layout is applied only the form, only in read mode Additionally, we have solved a problem where using the same style for different conditional layouts would only apply to the last conditional layout. Support for multi-record selection in a default editable grid change Previously, it was only possible to execute a task or Excel export on a selection of records when the grid was not editable. In particular, in a default editable grid, these features excluded each other. Now, multi-record selection is available in a default editable grid as well. Support for the Between/Not Between operator in the Filter form component new Users can now apply the Between/Not Between operator in the *Filter To enable this, they must first select the Between/Not Between operator in the Filter pop-up from the toolbar and enter the desired values. You can also set the default operator to Between in the Software Factory menu User interface > Subjects > tab Data > tab Filter. Then, the chosen field in the inline Filter form will show two input fields that the user can adjust as needed. Button to open preview in a new tab new Due to CORS and the way browsers work, the Universal GUI cannot always show URLs in preview components. For that reason, we have added a button to preview components to open the previewed content in a new tab. This button is also shown when the file can be shown, which has the advantage of showing it larger in a separate browser tab. Button to open preview in a new tab This is opt-in, so the button only appears if you add the Screen component property showPreviewOpenButton to the Preview component in the menu User interface > Screen types > tab Screen components > tab Screen component properties. Screen component properties Barcode control - Suppress on-screen keyboard new You can now suppress the on-screen keyboard for the barcode control on mobile devices by adding the extended property SuppressBarcodeKeyboard. Set the value to yes. This feature is useful when using a barcode scanner that automatically enters the barcode value into the control. Minor fixes and tasks For cubes and charts: If a cube field was configured with a specific number of decimals, the chart would previously show only 2 decimals. Now, it respects the setting configured in the Software Factory. Domain elements were not translated in the x-axis and legend of a chart, and in the pivot grid. The displayed values were the raw database values instead of the translated ones. This has been fixed. Cells with NULL as a value in a pivot grid were displayed as 0.00. This has been fixed. For grids and forms: When a user used a task to add a record to a table detail, the badge for the detail would not update. The same issue occurred if the user refreshed the table with the Refresh button. This issue has been fixed. The Not equal to layout condition was incorrectly applied to cells that had no value. This has been fixed. The conditional layout is now only applied to cells that have a value. For grouping in grids: The rules for enabling grouping in grids were not applied correctly. The behavior has been adjusted to work like this: Non default editable grid: If not in edit mode, grouping is enabled If in edit mode and auto-save is enabled, grouping is enabled If in edit mode and auto-save is disabled, grouping is disabled. Default editable grid: If auto-save is enabled, grouping is enabled (regardless of whether the user has changed a record in the grid) If auto-save is disabled and no records have been changed, grouping is enabled If auto-save is disabled and a record has been changed, grouping is disabled Previously, when grouping by a column in the grid and changing the active record, the grouping would be removed. This issue has been fixed, and grouping now persists across row changes. Group columns were not always added to locked columns. This issue has been resolved, and group columns are now correctly displayed within the locked columns area. What we will be working on next sprint The next sprint we will be working on: Finishing context-sensitive breadcrumbs Multi-record delete Editable pivot grid (we expect this to take multiple sprints) Pivot grid column width Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hi everyone! We’ve released the following platform improvements this week: SF 2024.3, 2024.2, 2024.1 20241024 - Temperature input parameter for LLM connectors We have added a new input parameter to the LLM connectors. Temperature controls the creativity of responses. Originally added in 2023.3 via hotfix, but new installations and upgrades that moved past 2023.3 missed this parameter. This has been resolved now. SF 2024.3, 2024.2, 2024.1, 2023.3 20241022 - Improve determination of origin model version in revert branch In a specific scenario, it was possible for the Revert branch task to revert the branch to a state before its origin model version, and updating that model version to an unrelated model version. This could lead a future merge session to compare to a point-in-time where the Origin and the Branch were not the same, potentially causing all kinds of merging issues. This has been resolved.

Hello everyone, In this release, we have improved the query speed of cubes, added a new setting to disable cache clearing on startup, and made some visual improvements to the Database event log and Live error log. We have also fixed two issues related to sending emails with attachments and SMTP configurations. You can read more about Indicium's features in the Indicium user manual. About Indicium Two types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.3.11 here. Contents About Indicium Contents New and changed Improved cube query performance Disable cache clearing on startup Log readability improvements Minor fixes and tasks Questions or suggestions? New and changed Improved cube query performance change We have improved the query speed of cubes. The number of unnecessary conversions has been reduced, resulting in faster queries and less overhead for the database server. Disable cache clearing on startup new We have introduced a new setting in the appsettings.json file for the FileCache feature: FileCache:ClearLocalCacheOnStartup. If this setting is set to false, Indicium will not automatically clear its cache folder at startup. Instead, you need to manage this manually. If the setting is not added to the configuration, or if it is set to true, the default behavior is applied, and Indicium will automatically clear the cache folder at startup. This option is especially useful in environments where multiple instances of Indicium share the same FileCache folder, such as when running multiple app service instances on Azure. It helps prevent scenarios where one instance clears the cache while another is trying to access files, avoiding potential conflicts. Log readability improvements change We have made some visual improvements to the Database event log and the Live error log. Both now have a grid layout with a header at the top and evenly spaced columns to improve readability. In addition, the Database event log also has a new column called Type. It shows the type of database event (such as Query, Layout, Default, Insert, Task, Model reader). The settings at the top now also offer a new option to filter by any or all of these database event types. New layout for the Database event log and new column: Type Filter options for the Database event log New layout for the Live error log Minor fixes and tasks We have fixed two issues that could occur when using the Email connector process action or the IAM Email provider (for 2FA, password reset, etc.). These issues were introduced after a recent update to a new email library. Sending emails with attachments sometimes failed if the receiving mail server did not support the BDAT command (this usually happened with SMTP servers). This resulted in the error message 550 5.6.11 SMTPSEND.BareLinefeedsAreIllegal. SMTP configurations with Use SSL turned off sometimes failed. If the SMTP server supported Start TLS but there was no valid certificate, the connection to the SMTP server would fail. This happened because Indicium would attempt to use Start TLS whenever available, regardless of the Use SSL setting. This behavior has now been reverted. 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 & IAM Upgrade to 2024.3 (particular to 2024.2.13) Renaming of roles to adhere to new naming convention There was a possibility where renamed roles could lead to duplicate in both the current as well as the history data. We revised the way that this rename is done to ensure any new upgrades to 2024.3 can no longer run into this issue. We resolved an issue in regards to leftover role rights of a non-existing model in IAM. Note: these changes do not affect installations already upgraded to 2024.3 IAM 2024.3 20241017 - PAT button translations in English With the introduction of Personal access tokens, two global translations of the Confirm and Cancel buttons were not translated in English. This has been resolved. IAM 2024.3, 2024.2 20241014 - Resolved tenancy filter not applying for dbo users We resolved a situation where users with db_owner rights did not have the tenancy filter applied to them.

Hello everyone, This release features a new model in the Thinkstore: the Thinkwise Reporting service. It replaces the Reporting service that was available for Windows. Thinkwise Reporting Service new Universal GUI The Thinkwise Reporting Service is a powerful system flow designed to automate your reporting process. It fully integrates with your existing Thinkwise application, and ensures seamless interaction with predefined reports, printers, and file storage locations. This solution streamlines your reporting workflows, making it easier to manage your reporting needs. This model replaces the Reporting Service, which is End-of-Service Life in accordance with our Lifecycle Policy. The key features of the Thinkwise Reporting Service include: Automatic processing - Reports are automatically processed, ensuring timely generation and delivery. Flexible output - Reports can be printed or saved to file storage locations. Scalable processing - Control the number of instances that simultaneously process reports. The new Reporting Service reads and processes entries from the table reporting_service_queue. Based on the specified actions, it generates reports, prints them, or writes them to file storage locations. For more detailed information on configuration and usage, see the Reporting Service documentation.

Hello everyone, In this release, we have added one new model, called Columnstore index and AI search. We also merged two existing models, Maps (mymappi) and Google Maps, into a new model called Maps and Routes. Fourteen models have been updated, and one model has been removed. The changes in this release are available for Thinkwise Platform version 2024.3 and higher. About the Thinkstore The 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. Contents About the Thinkstore Contents New Thinkstore models Columnstore index and AI search Maps and Routes Updated Thinkstore models Currencies API Check constraints for easy user input validation Differences in data between two databases Friendly error msg for database connector Date prefilters RDW car info / KVK info / Webservice example to retrieve address info from zip code Using OAuth to get data from external applications Default tooltip Make sure your display values are unique Turn off enable tab task when empty Find a certain char in a string Generate a unique randomized token Thinkwise Guideline Validations Removed models Use T-SQL OPENJSON for accessing JSON data Questions or suggestions? New Thinkstore models Columnstore index and AI search new This new solution contains an example of how to use a columnstore index in the Software Factory, combined with AI search. The data model consists of a product table that can compare itself to other products within that table and provide a matching score. A higher score indicates that the product is more similar to the selected product. The columnstore index ensures that this functionality is extremely fast. Columnstore indexes store data by column instead of row, offering significant data compression and reducing storage needs. This leads to faster queries because less data is accessed during query execution. More general information about columstore indexes: Microsoft More information about columnstore indexes in the Software Factory: Indexes Maps and Routes new Universal GUI The models Maps (mymappi) and Google Maps have been merged into a new model named Maps and Routes. This new model serves the purpose of teaching how to work with the Maps component in the Universal GUI. It also uses two Web connection endpoints for retrieving the GPS coordinates and routes. You need to get your own API key from Google and enter it into the Web connection. The model includes a menu for addresses and routes: Adding an address initiates a process flow that uses the Web connection to retrieve and display the GPS coordinates on the Maps component. Once you have at least two addresses, you can add a route. The Web connection retrieves and displays the fastest route on the Maps component. Updated Thinkstore models Currencies API change We have removed the currency tables because this solution only provides a web connection and a task to start the API call and show the response. If you want to process the JSON response, this blog post with JSON examples might be useful. Check constraints for easy user input validation change We changed the strategy for the control procedure check_constraint_message_add from delete to staged. For more information about the custom check constraints, see the blog Check constraints using the Software Factory. Differences in data between two databases change We removed unnecessary parts of the model, reducing the size of the export file model.dat, without any other changes. Friendly error msg for database connector change We changed the strategy for the meta control procedure database_connector_process_action from delete to fully controlled. We also modified the insert statement for the table process_action_output_parmtr table to include the column output_parmtr_type with a value of fixed_option. We changed the strategy for the control procedure error_log_code from delete to staged. We also removed the parameter @error_log_code from the error handling code in the template error_log_code, as it was not declared. Date prefilters change Previously, this model included a table named date_of and a prefilter group called date_filters with 4 prefilters. Now, it only contains a meta control procedure tab_date_prefilter that adds the prefilter group and prefilters to all tables linked with the tag tab_date_prefilter. In the tag value, you must specify a column with a domain of data type DATE, DATETIME, or DATETIME2. The 5 prefilters created are: Current week Year to date (new compared to the previous model) Current month Current quarter Current year These prefilters can be adjusted within the dynamic code if you desire more or fewer prefilters or if you wish to modify any details of the prefilters. We set the strategy for the meta control procedure tab_date_prefilter to fully controlled, giving you the freedom to change the details after creation. Note that changes to the dynamic code will not modify the already created prefilters. RDW car info / KVK info / Webservice example to retrieve address info from zip code change We have replaced the last message with a task pop-up to make it easier to show the given JSON and process the information. Using OAuth to get data from external applications change The model Using OAuth to get data from external applications has been renamed to Using OAuth to get data from Exact Online. In addition: The MS Graph connection has been removed. This is a separate Thinkstore model. Instead of an HTTP connector, a Web connection is now used. Default tooltip change The model Default tooltip has been updated: The generation strategy has been changed to Fully Controlled. The code has been changed so the trace columns are updated. The code has been changed, so the tooltip translation is also updated when the translation is updated. Make sure your display values are unique change The generation strategy has been changed to Staged. Turn off enable tab task when empty change The generation strategy has been changed to Fully Controlled. The code has been changed to a where not exists. The code has been changed to create the tag when it does not exist yet. Find a certain char in a string change We have added a table-valued function, which makes the functionality easier to use. Generate a unique randomized token change We created a subroutine (procedure) for the functionality. Previously, it was only an example script. Thinkwise Guideline Validations change We renamed the validation column_name_starts_with_the_table_name to tsf_guideline_column_name_starts_with_the_table_name. This is to be in line with the rest of the naming of the validations. In the validation tsf_guideline_column_name_starts_with_the_table_name, the like missed the '%', this has been corrected. tsf_guideline_domain_which_contains_the_name_of_an_rdbms_datatype now only checks for the RDBMS type of the model. All the validations that use a cursor with a table variable have been changed to a temporary table to improve performance and stability. See this Community post. Removed models Use T-SQL OPENJSON for accessing JSON data change The model "Use T-SQL OPENJSON for accessing JSON data" has been removed from the Thinkstore. This blog post with JSON examples should give you enough information to work with JSON in T-SQL. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

September 30, 2024: Full release 2024.3.10 (from release candidate 2024.2.15) Solved the following issue found in the release candidate: Pivot grids with an axis based on a group interval like 'year(date)' would give a bad request error when the drill-down pop-up was opened by double-clicking. This has been fixed. Hello everyone, In this release, the FormList component has been improved with support for comboboxes, more refresh options, and an active record that moves with the editor. We have also added support for the property Show grid header in the screen type modeler. The performance of editing and task/report execution has been further optimized. Demo As always, we have made a demo for you; try it here. Before trying it out, press 'Clear Cache' on the login screen. Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2024.3.10 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.3.10 (release candidate) here This is a release candidate that you can use to test the new features. It is not suitable for use in a production environment. The full release 2024.3.10 will be available next Monday. Contents Demo Universal GUI version 2024.3.10 Contents New and changed FormList - Support for lookup comboboxes FormList - More refresh support FormList - Active record and breadcrumbs Performance - Editing and task/report execution Security update Support for Show grid header in screentype modeler Deep links to log files Row selection in grid Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changed FormList - Support for lookup comboboxes new In a previous release, we added support for lookup editors in the FormList component. At that time, we chose not to support comboboxes because a combobox would load its list of items after the editor appeared on the screen. Since the FormList displays an editor for each record, this would trigger many list requests and load unnecessary data. Instead, the lookup editor was always presented as a suggestion control in which the user had to search for options. The disadvantage of this approach was that the user has to know what values to search for. Especially for a small list of options, a combobox is more user-friendly. We have improved the combobox to load options after it is opened for the first time. This means that the use of comboboxes in a FormList is now supported. Whether it becomes a suggestion control or a combobox depends on the selected control type on the lookup reference in the Software Factory. FormList - More refresh support change We have improved how data is refreshed after changing a field value in the FormList component. Previously, only refreshing a Subject was supported. Now, we have added support for refreshing a Document (from a detail subject) and a Row. You can find these options in the menu User interface > Subjects > tab Default > tab Settings > tab Performance > group Refresh > field After update. We recommend refreshing the subject only when necessary, as the FormList displays editors for every record in the set and re-renders the layout for each row. See also Refresh behavior in the Software Factory documentation. FormList - Active record and breadcrumbs change In the FormList component, the active record now moves with the editor on which a user focuses. Previously, the first record remained the active record no matter what a user did in the FormList. This offers new possibilities for combining the FormList with other components, such as a detail tab subject to present detail data of the active record. In addition, the breadcrumb now shows the active record, and you can delete the active record. Performance - Editing and task/report execution change We have further improved the performance of the Universal GUI by combining and saving requests for editing and task/report execution. The actions for Add, Copy, and task/report execution now combine the staging request with getting the result of the layout and default application logic. A lookup editor previously made an extra "translation" request after editing started. As the display value is already known, these requests (one per editor) no longer occur. This saves a lot of requests, especially when the subject is default editable. Skipping these requests saves waiting and processing time, and server-side resources for Indicium. Security update new We have fixed the following security advisory: GHSA-mmhx-hmjr-r674. This resolves a security issue affecting some areas where HTML is displayed in the Universal GUI, including: HTML control (view-only mode) Preview component displaying an HTML field Prefilter, task, and report button tooltips Column, report, and task column tooltips Tooltips for grid headers Maps marker popups If a malicious actor were to inject an HTML value into one of these areas, such as through the Indicium API, this vulnerability could be exploited. In such a case, if a user had one of these elements visible, the attacker's JavaScript payload could be executed. In the worst-case scenario, the attacker could execute Indicium requests using the victim's credentials. Thanks to Indicium's Content Security Policy, the risk of exploitation was low. In addition, we strongly recommend always configuring Security headers. Support for Show grid header in screentype modeler new We have added support for the property Show grid header in the screen type modeler (menu User interface > Screen types > tab Design). If this setting is set to false, the grid header will be hidden in the Grid screen component. Show grid header in the screen type modeler Deep links to log files new Database and server error messages now include a deep link to the indicium log files. This feature is only available for users with the role developer. Requests that produce a database error message include a deep link to the database event log Requests that produce a server error include a deep link to the error log This makes it easier to find the cause of the error and resolve it. An error snackbar with both deep links. Row selection in grid change A selected record in a grid can be no longer available because of several reasons, for example: A user deletes the record A user edits the record and the record no longer meets the filter criteria A user deletes a record with a task, or edits a record with a task and the record no longer meets the filter criteria A user adds or copies a record but the record does not meet the filter criteria Previously, the grid would refresh and the first row would be selected. Now, the next record after the one that was removed is selected, which is more consistent with the expected behavior. For an add or copy action, this is still the first row. Minor fixes and tasks For pivot grid and chart When a pivot grid had a related parent subject without any records, the pivot grid would still show data. This has been fixed. We solved the following issues in the pivot field list editor, the pivot grid, and the chart when multiple cube fields had the same source field: When you configured a column as both a dimension and a value When you configured multiple group intervals, like year, month from the same date When you configured multiple aggregations, like sum and average, for the same columns This could lead to: Dimensions disappearing in the editor when re-ordering them Values disappearing after dropping them into the editor Categories changing when switching between the pivot and chart tabs Charts with no y-axis Date interval dimensions showing the wrong interval, for example, year when month was configured In some cases, actually crashing the GUI For form and grid When a user selected a grid cell and pressed CTRL+C to copy, the Universal GUI would copy the whole grid row to the clipboard. Now, it only copies the selected cell. We have fixed an issue where in some cases, dragging a row over a drag/drop grid, would not indicate the rows being dragged over. When you grouped columns that render images inside grids, the images were scaled up in the group column. This has been fixed. When switching between open documents, some forms in the screen would flicker briefly. This should no longer happen. When a default editable subject was saved using auto_commit , it would not return to edit mode automatically. This has been fixed. Default editable details would not always go into default edit mode, for example, when executing a Zoom detail process action for the second time. This has been fixed. Numeric input would remove the minus sign, for example, when a user entered -0.5. This has been fixed. Additionally, a user can no longer add negative numbers if the Min. value (menu Data > Domains) in the Software Factory is 0 or higher than 0. For tasks Task execution was not halted after user input was marked as invalid by domain input constraints. This has been fixed. What we will be working on next sprint The next sprint we will be working on: Grid multi-select in edit mode (continued) Calendar component: We will begin fixing the issue where the calendar component fills in the date during navigation. (continued) Force Universal GUI update Context sensitive bread crumbs - Breadcrumbs showing navigation to detail subjects Maintenance Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone! This release contains a great new feature to enhance security in your applications: Personal Access Tokens (PATs). PATs are a secure way for users to allow external parties to connect with your application. We are also introducing environment interaction logs in IAM. These logs help detect issues such as malfunctioning external services, disks and printers, application landscape connectivity problems, and provider misconfiguration. Additionally, security checks have been added to IAM. These checks can be used to ensure that users are not authorized to access more data than intended. They can be configured for a user and focus on specific domains within an application. We also introduced custom reports. You can configure custom reports in IAM by overriding the default report file for an application or, in the Software Factory, by using a report file stored in the file system. Lastly, we implemented many changes and features to improve developers' workflows. Some of these quality-of-life improvements are also listed in this blog. This post highlights the key features of the release. For detailed release notes, visit the Thinkwise Documentation. Contents Contents Highlights of this release Personal access tokens Monitor your environment in IAM Security checks in IAM Custom reports Some quality-of-life improvements Questions or suggestions? Highlights of this release Personal access tokens new Universal GUI Security is a key aspect of any system, which is no different for the Thinkwise Platform. To further enhance security, we are introducing Personal Access Tokens (PATs) as another type of authentication. Personal Access Tokens are a secure way for users to allow external parties to connect with their application. Users can create their own tokens and assign them a limited set of application permissions. If a PAT is leaked, the token can be revoked by the user or an IAM administrator without the need to change the user's password. Or, from a technical point of view: PATs are a way for external parties to log in to the Indicium API with a token instead of basic authentication. This token can be scoped to only access the necessary resources within the rights of the user. User credentials are not shared. Users can create PATs in the application in their profile menu. They need to select an application, add a name, and select the permissions they want to assign to the token. The expiration date can be set from one day to one year. With a PAT, users can achieve features in an application without waiting for others to implement them. Examples in applications: Set up webhooks (for example, with a service like If This Then That (IFTTT)) that perform actions on the user's behalf or poll the user's data in a Thinkwise application, such as: Synchronizing appointments between a Thinkwise application and their personal Google or Apple calendar Synchronizing data between a Thinkwise application and another application, such as a Finance or CRM application, on behalf of the user Setting up an automated process to receive an email or text message when the status of a task, order, invoice, transaction, project, or ticket changes Starting a long-running process flow at night, such as importing data or generating invoices on behalf of the user Setting up an AI Assistant to answer questions about the data in a Thinkwise application Examples in Indicium administration: Integrating Indicium health checks into load balancer decision making Verifying Indicium and database health after running a CI/CD pipeline You can follow this flow diagram to decide if using PATs is the best solution or whether another way of authentication would be better (click to enlarge): When to use PATs Monitor your environment in IAM new 3-tier main administrator application administrator You now have access to environment interaction logs in your production environments. The primary goal of these logs is to detect malfunctioning external services, disks and printers, application landscape connectivity problems, and provider misconfiguration. The logs are created when the Indicium service tier interacts with the application environment. The interaction done by the 2-tier Windows GUI will not generate any logs. Available log sources: The following log sources are available for each application (menu Authorization > Applications > Environment monitoring): Application-related logging Application database logs - These do not log all actions to access the database but can be used to detect application database connectivity problems Provider-related logging Web connection logs Email provider logs File storage provider logs OAuth server logs Generative AI provider logs Printer logs Process action-related logging HTTP connector logs SMTP connector logs Disk file logs (non-file storage) FTP connector logs (non-file storage) Application connector logs Database connector logs (not yet available) Monitor your environment with environment interaction logs Log analyses are also available, globally and per application. These analyses are based on the last 30 days, as this is the minimum log retention time. Analyze the environment interaction logs Security checks in IAM new main administrator The data that is accessible to an end user depends on the configuration of various actors and settings in IAM, the Software Factory, and the end application data. To ensure that users are not authorized to access more data than intended, IAM now offers security checks to assert the correct configuration. These assertions are called Security checks. A security check is configured for a user and revolves around specific domains in an application. The checks are verified by simulating the user with the application data and the current configured rights. Examples of security checks: The user b.hanssen may never see columns with the value j.vandyk@competitor.com using the domain email in application 395 - myproduct. The user s.harris may only see records with values 5, 6, and 7 for columns using the domain customer_id in application 395 - myproduct. The user s.harris may not see records with values concept or null for columns using the domain invoice_status in application 395 - myproduct. You can schedule security checks to be executed a number of times per day but you can also run them manually. Security check configuration Custom reports new Reports can now be customized in two ways: Override the default report file for an application - The default file for a report is configured in the Software Factory. You can now override this default file for an application in IAM. You can upload a different file or change the file path for the selected application. You can use this, for example, to use a different logo in the report for a specific application. Previously, you had to switch the logo within the report. Use a report file stored in the file storage - Previously, it was not possible to show a different report based on the data when a report was stored in the file storage. For example, if you wanted to show different reports for large orders and for small orders. To solve this, we have added a new report property (Report file) to the Software Factory. You can use it for storing report files in your storage location and supplying them in a report parameter with the required data using a default procedure. Some quality-of-life improvements Performance - We improved the performance of the platform in several areas, for example: Synchronization to IAM - The effective rights are now calculated more efficiently. The tsf_optimize procedure -This procedure can speed up SQL Server performance when many indexes are fragmented and statistics are outdated. Now, you can run it in a system flow. Merging - We have made several improvements to the merging process: It is now easier to view errors, if any, in the latest merge session, which is especially useful for scheduled merge sessions. When merging branches, it is crucial to ensure the merge session data is up-to-date. We have added the task Check merge session to see if the merge session is still up-to-date for the branches involved. Usually, you want to merge everything from a branch to the main model, solve conflicts, and then execute the merge. However, sometimes, you want to exclude certain actions from the merge execution. You can now exclude delta actions from a merge session with the new task Exclude merge action. Unit tests - We have made several improvements to the unit tests: The unit test screens have received a mostly visual but partly functional update. Unit tests now support table-valued functions. We have improved the screen Mock data by adding additional information about the data. Code search - We have made several improvements to the code search: Code search results are now displayed in a hierarchical tree format. We have introduced a new task, Hide search result. It allows you to hide specific items from the code search results that are of no interest to you. Groups - You can now add object groups through dedicated tabs displayed next to the object itself in several locations. Previously, you had to open the lookup pop-up and add the group there. Storage - We have added several new settings to manage the retention of historical data: System versioning - to specify a retention period for historical data. Session log retention - to specify a retention period for user session logs. Archived branch retention - to specify a retention period for archived branches and their history data. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

September 30, 2024: This release is largely the same as release 2024.2.15 Extra fix in this release: We have fixed an issue that could occur when using the AWS Secret Manager for Data Protection. If the number of keys stored in the AWS Secret Manager exceeded 10, Indicium would stop working. Hello everyone, This release contains a breaking change about mandatory prefilter groups. We also fixed two minor issues. You can read more about Indicium's features in the Indicium user manual. About Indicium Two types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Download Indicium Basic release 2024.3.10 here. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.3.10 here. Contents About Indicium Contents Breaking Mandatory prefilter groups Minor fixes and tasks Questions or suggestions? Breaking Mandatory prefilter groups change Previously, if the following conditions were met, a mandatory prefilter group was no longer treated as mandatory: The prefilter group was marked as Mandatory All prefilters in this group were Off by default The prefilters were Hidden from the user through role permissions This behavior has been changed. Now, all data remain hidden under these conditions. Review any mandatory prefilter groups that meet these conditions, and decide what behavior you want (menu User interface > Subjects > tab Data > tab Prefilters). If you want users to receive data, they must be able to see and activate the prefilters or the prefilter group should not be mandatory. Minor fixes and tasks When external users canceled the external authentication process, the authProviderHint parameter was forgotten. This would confuse users. Now, the authProviderHint parameter persists even if the external authentication is canceled, prompting users to use external authentication again. We have fixed an inconsistency between the process action SMTP connector and the SMTP email provider. The SMTP email provider required a username and password, which is incorrect because it is possible to configure your SMTP server without authentication. It should be up to the SMTP server to enforce authentication or not. Now, the process action SMTP connector and the SMTP email provider are consistent, it is no longer necessary to enter a username and password. We have fixed an issue that could occur when using the AWS Secret Manager for Data Protection. If the number of keys stored in the AWS Secret Manager exceeded 10, Indicium would stop working. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone, In this sprint, we resolved an issue. You can read more about the Windows GUI's features in the user interface guide. Download Windows GUI 2024.3.10 here. Minor fixes and tasks We have fixed an issue in the Windows GUI when used with Indicium Basic. A screen with change detection would freeze if minimized for some time. This issue has been resolved. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone, This release contains a breaking change about mandatory prefilter groups. We also fixed two minor issues. You can read more about Indicium's features in the Indicium user manual. About Indicium Two types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2024.3.10 here. Contents About Indicium Contents Breaking Mandatory prefilter groups Minor fixes and tasks Questions or suggestions? Breaking Mandatory prefilter groups change Previously, if the following conditions were met, a mandatory prefilter group was no longer treated as mandatory: The prefilter group was marked as Mandatory All prefilters in this group were Off by default The prefilters were Hidden from the user through role permissions This behavior has been changed. Now, all data remain hidden under these conditions. Review any mandatory prefilter groups that meet these conditions, and decide what behavior you want (menu User interface > Subjects > tab Data > tab Prefilters). If you want users to receive data, they must be able to see and activate the prefilters or the prefilter group should not be mandatory. Minor fixes and tasks When external users canceled the external authentication process, the authProviderHint parameter was forgotten. This would confuse users. Now, the authProviderHint parameter persists even if the external authentication is canceled, prompting users to use external authentication again. We have fixed an inconsistency between the process action SMTP connector and the SMTP email provider. The SMTP email provider required a username and password, which is incorrect because it is possible to configure your SMTP server without authentication. It should be up to the SMTP server to enforce authentication or not. Now, the process action SMTP connector and the SMTP email provider are consistent, it is no longer necessary to enter a username and password. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!