Product Updates

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.220240701 - Improvement in determining the exported branch for usage metrics In some situations, the determination of which branch is most relevant for sending anonymized usage metrics to Thinkwise was incorrect. This resulted in no data being sent. This has been resolved.  IAM 2024.2, 2024.120240702 - Check classic user preference table for modified prefilter In a hybrid environment where the Universal GUI and Windows GUI are used alongside, there is specific scenario in which modifying user defined prefilters in the Windows GUI would cause an error. This has been resolved.

Now that customer success is the focus of the Universal GUI, we can prioritize User Experience too.This blog is the first step, introducing quick win UI Styling updates that require no Model changes or changes in User Experience. Later, we'll introduce and discuss Data Density improvements and more comprehensive UX & Universal Theme implementations.In the past years a lot of features have been added to the Universal GUI, but in the meantime the visual side of this interface hasn’t changed a lot. Comparing our Universal GUI to other enterprise applications, we do notice that our interface lacks a little conviction. We want to improve on this together with you, to ensure that our ideas support you and your users. So please, join in the conversation and let us know what you think.We took the Insights application as a benchmark.The Projects screen in the current Universal GUIThere is a lot going on in this screen, which means our users have a lot of elements to visually look through.We think we can do better.Based on the Material UI components and the 10 Usability Heuristics we altered the UI styling, bringing us to the following design:Styling update of the Universal GUIThis is the same Projects screen in the Insights application, with only visual alterations. Let us take you through it, so you know what is going on.Styling update with subject indicators Menu Currently, the background color in the menu has the same color as the general background of the rest of the application, which can distract the user in their navigation through an application.Menu designWe want to introduce the primary color as background of the menu.This provides a better visual hierarchy and helps the user focus on the data. With this change, we also introduce a lot more color in the application.We also want to change the alignment of the Open Documents (aligned with the submenu items) and the badges in the menu (make them stick to the right). Prefilter buttonsThe current setup of the Prefilter buttons is based on an icon, with a primary-colored underline when the prefilter is active.Prefilter buttons with solid background Like you, we think this can improved by making the Prefilter button a more distinctive button, by introducing a solid background in a round shape.When the prefilter is active, the background could get the primary color or secondary color. Which do you prefer, the primary or the secondary color for active prefilter?  CRUD and Task/Report buttons Like with the prefilters, we introduce a solid background for the CRUD and Task/Report buttons.By making these button backgrounds square, they are better distinguishable against the round prefilter buttons.Default CRUD and Task/Report button styling Also, we would like to know what your stance is on introducing the primary/secondary color to the Task buttons to make it a clear Call To Action button.Concept of button with color What do you think of introducing the primary or secondary color to the CRUD and Task/Report buttons? Conditional layoutThe current setup of the Conditional layout colors the entire cell. We want to improve on this visual cue, highlighting the text only.Conditional layout around text With text fields and an icon, we could encapsulate the icon with the text highlight:Icon in Conditional Layout highlight Or we could give the icon the conditional layout color (if it’s an SVG icon of course) and place it outside the text highlight.Icon in Conditional Layout color Which one do you prefer?  Lookup controlEspecially in read-only Grids, the lookup control needs a little love.To make the Universal GUI more consistent with other controls like the email, map, URL or phone number control, we want to change the current lookup control into a hyperlink. This way we follow behavior the users expect from other platforms.Evergreen, Kim Wilde, Country building and Budget office are the Lookups in this image. In this idea, the underline in the grid is only shown on active row/hover, to prevent a grid full of underlined data. Column headersVertical space is a great challenge in the Universal GUI.The grid headers now demand a lot of vertical room compared to the rows, and the styling of the header text make them fall into the background.In this design, we want to introduce a lower header bar and a bold font style. Subtle vertical dividers between the columns in the header and the active row are also added to emphasize column width.Column headers design What do you think of this Column headers design? Form fields – Outlined styleOne of the major elements in this design is changing the Filled style to the Outlined style form fields.We think the Outlined style holds a lot of answers for data density, control alignment, conditional formatting, visual hierarchy, focus indication, etcetera.To give you an impression, we put the current Filled style next to an Outline style setup. The field content and setup are the same.On the left the current Filled Form Field styling, on the right the Outlined Form Field style Because this will be a major change, this is not exactly a ‘quick win’. We want to get rid of the Form field background color setting and implement this idea. This also means that forms in non-edit mode have no background nor outline.Forms in non-edit mode without background color What do you think of the Outlined Style for Form fields replacement? Active row colorUniversal uses grayscales to draw the attention of the user, we think that color is a better guidance and looks nicer.While using a hint of the primary color (a pass through of 12% to be precise), the active row would stick out a lot more.Active row indication in Primary colorWhat do you think of coloring the active row? ConclusionAs stated in the intro, these Design changes are predominantly focused on visual changes. They will have an impact on how the Universal GUI looks and feels, but not on its behavior.To react to the designs, use the number of the subject and place your comment next to it, so we know which subject you are referring to.We look forward to your opinions!  

Hello everyone,In this sprint we have fixed a few minor issues, which are outlined below.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.2.12 here.  ContentsAbout Indicium Breaking Support for Thinkwise Platform release 2022.2 has ended Changes Security enhancements Minor fixes and tasks Questions or suggestions? BreakingSupport for Thinkwise Platform release 2022.2 has endedIn accordance with our Lifecycle policy, we no longer support the Thinkwise Platform version 2022.2 as of this release. ChangesSecurity enhancementsAs part of our ongoing effort to maintain the highest security standards and protect your data, we have implemented several security enhancements that improve the overall safety and resilience of our platform.We recommend all users upgrade to this version as soon as possible to take advantage of these improvements and enhancements. Minor fixes and tasksWhen you are using a case-sensitive filesystem, the process flow monitor did not work. The JavaScript could not be loaded, due to a difference in the file name case. This has been fixed. The initial setup for two-factor authentication would only work if the setup was completed within one minute. This has been fixed. Our OData metadata document was missing the field PreviewContentType. This caused issues with certain integrations. This has been fixed. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

This is an additional release for the Universal GUI version 2024.2.11. It contains one change:In specific and rare circumstances a default editable grid caused a crash when opening a detail tab. This has been resolved.The 2024.2.11.2 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements this week: IAM 2024.220240614 - Limit returned application data for references When having multiple IAM applications sharing the same model and branch, there is the possibility that the Windows GUI would not return any data in table, task and report look-ups. This has been resolved.  SF & IAM 2024.1 and below (including 2022.2)20240617 - Always return percentage for field sets When using Universal GUI version 2024.1.13 and below, having multiple fields on a single line could cause all but the first field to be invisible to the user. Using TAB, the user could see and fill in the focused field but this is suboptimal. This has been resolved for all supported versions including 2022.2. Platform version 2022.2 is no longer supported but does receive this improvement. It is advised to upgrade.

This is an additional release for the Universal GUI version 2024.2.11. It contains one change:The theme background was not displayed. This has been resolved.The 2024.2.11.1 release is now available for download in TCP.

We have a challenge for you!We are in the midst of designing the Universal GUI version of filtering within the Pivot Table. We've made a prototype to let you experience the Universal GUI version of this feature and we would like to hear your opinion.Please leave your comments in the comment section below.You will see:A new expandable/collapsable panel, where the user can find the Pivot Table Editor and Pivot Table Filter. Filter Dimension only as a top row drop zone for Dimension Values A new Filter Tab in the expandable/collapsable component to see all used Dimension ValuesWe give you 3 assignments to go through this prototype:Use Dimension Value ‘Invoice status’ for the Filter Dimension (this prototype doesn't support Drag and Drop, clicking on the element is enough). Set the filter of ‘Invoice Status’ to only ‘Paid’ (clicking on any checkbox will directly set this filter correctly for this prototype)  Set the filter of ‘Sub project’ to Exclude ‘Braggs apts’ from the data  Reset ‘Sub project’ with the RESET button. Set filter ‘Invoice status’ so that all checkboxes are checked (again, clicking one checkbox in this prototype activates them all again) Set ‘Sub project’ to Include the value ‘Boardwalk center’ in the dataClick here to open the Prototype.Use password ‘pivot filter’ to access the design.Use ‘R’ to restart from the beginning of the prototype if you are stuck.  

June 10, 2024:Full release 2024.2.11We solved two issues that had been introduced in the 2024.2.11 release candidate: The pop-up of a marker in the Maps screen component would not show up properly, especially after switching documents. This has been fixed.  An issue could occur in some specific scenarios, such as applying sorting in a grid within a document but also in some other scenarios. After closing the document, the application would stop working, and the user would be presented with a crash report submission form. This has been fixed. Now, the user can continue using the application normally after closing the document. Hello everyone,In this release, we added the ability to start a process flow from within a custom component. We also made some performance improvements, added general keyboard shortcuts for pop-ups and a confirmation when closing a lookup or pop-up. Lastly, we solved some issues. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to familiarize yourself with the GUI. Universal GUI version 2024.2.11For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, 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.11 here ContentsDemo Universal GUI version 2024.2.11 (release candidate) Contents New and changed Start process flow from within a custom component Performance improvements General keyboard shortcuts for pop-ups Confirmation when closing a lookup or pop-up Minor fixes and tasks What we will be working on next release Questions or suggestions? New and changedStart process flow from within a custom componentnewYou can now start a process flow from within a custom component by sending an instruction to the Universal GUI. For example:window.parent.postMessage({ type: 'startProcessFlow', processFlowId: 'refresh_document_detail_from_component', dataParams: {}}, '*');The process flow needs to be a deeplink process flow. See Deep linking in a process flow. The Universal GUI allows origins from the same master domain, for example, *.thinkwise.app.WarningIf you introduce custom screens or custom components into your application, you will also introduce a piece of traditional programming. If you are making changes to your model, the Software Factory will not alert you about the use of process flows and their parameters in your custom components. It is your responsibility to put a change process in place for this. For more information, see Custom screens. Performance improvementschangeWe have upgraded our general component library, which has resulted in performance improvements.Actions that triggered multiple re-draws of the interface now update the interface once. We also expect an improved grid edit-mode experience, although we have planned more improvements in this area in the upcoming sprints.Also, switching between documents and tabs looks much calmer now. Forms position their editors directly in the right place now. The same goes for (detail) tiles. General keyboard shortcuts for pop-upsnewYou can now use the following keyboard shortcuts when interacting with a pop-up:Esc - Cancel Ctrl + Enter - Confirm Confirmation when closing a lookup or pop-upnewPreviously, when users edited a record and clicked on one of the buttons, the lookup or pop-up would close without any confirmation. This could result in them losing their changes. Now, when users edit a record and try to close it, they are asked if they want to discard their changes or return and finish editing. Minor fixes and tasksIf the page size was set to -1, paging would incorrectly be presented by the Universal GUI. This has been fixed. If the checkbox Allow sort was cleared, users were unable to manually change the column width in the grid. This has been fixed. A lookup editor in an editable form or as a task parameter was emptied when the value was entered before the dropdown list options were loaded and the control was left. For example, when copy-pasting or barcode scanning. Now, the value remains and is matched once the dropdown list options are received. We have fixed an issue in the form where any field with Field number of positions further = 0 would disappear if placed directly after a file upload field. The Max no. of records indicator was not translated. Now, the indicator will display "There are more records than can be displayed". An issue could occur in the card list when the page size and the maximum number of rows were set to zero or a negative number. This has been fixed. With these values, there will be only one page with all the records.Fixes for process flows:A process flow that starts with activating a detail tab would sometimes start multiple times. This has been fixed. When a task had Await result set to No and a process flow would use this task as Start table task, the process flow would not continue after executing the task. This has been fixed.Fixes for slower connections: Sometimes, especially on slower connections, quickly changing the active row would cause the detail tab to break and no longer show data unless manually refreshed. This has been fixed. On a slower connection, the data on a detail grid could be out of sync when switching between multiple records. This has been fixed. On a slower connection, detail tab data could be out of sync after switching to the parent record and back. This can be fixed by adding the following option to config.json: "disableTabPageCaching": true, Only use this option when you experience the mentioned issue since it lowers performance.  What we will be working on next releaseThe next release will be about:Solving issues - For the status of your own issues, please refer to TCP. Improved default edit mode - Closing a document will allow the user to cancel their current changes and errors. Performance improvements. Set filter from process flow - The filter form in a process flow was no longer displayed as a user filter. We will address this issue. HTTPS Security warning - When the Universal GUI is started over plain HTTP, it will give a warning that the connection is not secure. 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.2 20240605 - Enrichment improvementsWe made several improvements to enrichments themselves and the enrichment execution mechanism: Enrichment: Add a table description with AI Exclude generated tables in AI completion prompt for enrichment Enrichment: Create prefilters for checkboxes Exclude generated columns in Model update query and change instructions accordingly Suggest the to be created prefilter groups to be nonmandatory by default instead of mandatory Use the 'is_truthy' function to validate truthy input for the parameter @mand_grp in the enrichment templates 'create_prefilter_grp' and 'create_prefilters' Enrichment: Create prefilters for image combos Exclude generated columns in Model update query and change instructions accordingly Suggest the to be created prefilter groups to be nonmandatory by default instead of mandatory Use the 'is_truthy' function to validate truthy input for the parameter @mand_grp in the enrichment template 'create_prefilter_grp' Enrichment: Include every lookup column in the search Ensure that the enrichments not only supports tables but also table variants Rename template 'include_in_global_filter' to 'include_in_filter_tab' Add new template 'include_in_global_filter_tab_variant' to support table variants Task code: Generate model updates (technical: task_add_job_to_run_enrichment) Add enrichment title + parameters as job parameters

Hello everyone,In this sprint, we have updated a number of Thinkstore models with the new Web connections .The changes in this release are available for Thinkwise Platform version 2024.2 and higher. 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 New, changed, and fixed in the Thinkstore models Updated the model "Currencies API" Updated the models "RDW car info", "KVK info", and "Webservice example to retrieve address info from zipcode" Removed the model "Use T-SQL OPENJSON for accessing JSON data" Questions or suggestions? New, changed, and fixed in the Thinkstore modelsUpdated the model "Currencies API"changeWe 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. Updated the models "RDW car info", "KVK info", and "Webservice example to retrieve address info from zipcode"changeWe have replaced the last message with a task pop-up to make it easier to show the given JSON and process the information. Removed the model "Use T-SQL OPENJSON for accessing JSON data"changeThe 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!

Hello everyone,In this sprint, we have changed the error handling for system flows. We have also fixed an issue that could occur when importing files that contained lookup translations.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.2.11 here. ContentsAbout Indicium New and changed Changed error handling for system flows Minor fixes and tasks Questions or suggestions? New and changedChanged error handling for system flowschangeIf multiple Indiciums are running against the same database, they will all try to execute the system flows. Only the first one will execute the system flow and the others will receive an error. These errors ('system_flow_already_running') would be logged to Azure Application Insights. Now, they are no longer logged. Minor fixes and tasksWe have fixed an issue that could occur when importing files that contained lookup translations. It would occur when the lookup reference had more than one column and the filter columns of the reference (i.e. all but the last reference column) had different IDs on the target and source sides of the reference (e.g. sub_project.project_id <-> project.id). The issue would not occur if data values were used for the import instead of translations or if the reference columns had the same ID in both tables. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,In this sprint, we have solved some minor issues and tasks.You can read more about the Windows GUI's features, in the user interface guide.Download Windows GUI 2024.2.11 here. ContentsContents Minor fixes and tasks Report export file Devexpress reports exporting bugs Questions or suggestions? Minor fixes and tasksReport export fileA report export file could not be created when a user canceled the selection of a new file name. This has been fixed. Now, the export file will be created. Devexpress reports exporting bugsWe have resolved some issues with Devexpress reports. Errors occurred while exporting to docx and to PDF. These issues were originally hotfixed in versions 2024.1.14.2 and .3, but had not yet received release notes. 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 (All supported versions)  20240527 - Merge reference and look-up display col In some extraordinary situations, during the merge process one of the following messages could occur: - 'Cannot delete this row due to related 'References'. Please update or delete these 'References' and try again' - 'Cannot delete this row due to related 'Task references'. Please update or delete these 'Task references' and try again' - 'Cannot delete this row due to related 'Report references'. Please update or delete these 'Task references' and try again' This situation could occur when a new column would be introduced in a branch and set as look-up display column at the same time for a table which existed in the source branch and has look-up, task or report references in the source branch. SF 2024.2 20240527 - Fix code search trigger When upgrading to the 2024.2 the trigger for the code search is wrongly dropped. This hotfix will recreate the trigger.

Hello everyone,We have fixed an issue with loading 2024.2 application models that contain web connector process actions. Updating to this version is only necessary if you have already upgraded to platform version 2024.2 and you intend to use the new web connector feature.Our apologies for any inconvenience caused by this issue.

 May 21, 2024:Release 2024.2.10 This release is the same as 2024.1.14.0 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!  

Hello everyone,In this release, we have solved some issues.Download the Thinkwise Upcycler 2024.2.10 here.RequirementsSoftware Factory 2024.2 or higher is required.ContentsRequirements Minor fixes and tasks Identity columns without valid seed Default value of columns and domains Questions or suggestions? Minor fixes and tasksIdentity columns without valid seedIt was possible for an upcycled identity column to not have a seed. The extracted data did not supply a value. Now, if an identity column is upcycled, the seed will automatically be set to 1 if not provided by the model extraction.Default value of columns and domainsDuring upcycling, default values for columns and domains are extracted from the technology. However, the values could be the literal 'NULL' which would then be set as the default value for this column or domain. Now, the literal 'NULL' is translated to be NULL so the default value is empty.Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have improved a 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.