Product Updates

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

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

Hi everyone!We’ve released the following platform improvements this week: SF 2023.3 & 2024.1 20240205 - Allow loading of runtime configurations on SF meta source A column was missing for the Windows GUI to load all active runtime configurations for the given user when starting with the meta source SF. Due to the absence of this column, the GUI did not want to load. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week: SF 2024.1 20240130 - Change default backplate of Thinkwise theme We accidentally supplied a placeholder backplate in the default theme supplied by the DEFAULT_THEMES base model. This has been fixed. If you use this theme in your models, please generate their definition. IAM 2024.1 20240203 - Universal cube UP An issue in writing back user preferences has been resolved in preparation of custom cube view user preferences in Universal. 

Hello everyone,In this release, we have solved a problem. GUI freeze in model enrichmentsA problem occurred in the model enrichment screen that was recently introduced in the Thinkwise Platform version 2024.1. The user interface froze after running an enrichment. This has been solved.  

Hi everyone!We’ve released the following platform improvement this week: IAM 2022.2 and up 20240122 - Improve performance for role reference checks In rare occasions, SQL Server uses a query plan that is highly inefficient in calculating source and target object reference rights. This causes a very slow login process and results in a timeout. This improvement resolves this issue.

Hello everyone,As of this release, data verification is available in the Thinkstore instead of in the Software Factory. We have also enhanced the functionality for Trace fields, Logging data available in the GUI, and Active prefilter. 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 Contents New, changed, and fixed in the Thinkstore models Data verification moved to the Thinkstore Trace fields Logging data available in the GUI Active prefilter Questions or suggestions? New, changed, and fixed in the Thinkstore modelsData verification moved to the ThinkstorenewThe base models SQLSERVER_VERIFICATION, ORACLE_VERIFICATION, and DB_VERIFICATION have been relocated to the Thinkstore. Previously, they were included in the initial installation of the Thinkwise Platform.If you need an update for these models, download a new version from the Thinkstore. Trace fieldsWe have converted the Trace fields functionality to align with the latest version of the Dynamic model.new changedThe script now uses a temporary table to identify the set of tables for which you want to generate the trace fields. This change significantly enhances the script's maintainability. The script now has settings at the top for the names of the trace columns. Note: If you change the name of a trace column, you must also adjust the template in the control procedure. The script now generates the tag automatically if it does not exist. Use this tag to exclude trace columns from a specific table. The script now creates the necessary domains automatically if they are not already present. The strategy is now set to Staged, which means trace columns are no longer deleted and re-generated when created. The insert user and insert datetime columns now have a default expression that automatically gets an insert from the database if you do not specify them. This change simplifies the insert statements. The DATETIME domain control now uses the Time zone setting Local to store the trace information in UTC format. You can manually adjust this in the scripts to store the DATETIME control as non-UTC. Note: if you are already using a DATETIME control and the script is not in charge of that domain (i.e., the Generated by control_proc_id is not the same as from the dynamic model trace_fields), this will not be set automatically. Instead of tsf_user(), we now use tsf_original_login() to represent who changed or inserted data, even when user simulation is used. See also User name. The template no longer sets the update trace functionality when adding a record. These lines are now in a comment. You can uncomment them if you wish to keep this functionality. Data sensitivity is now automatically applied to the add and update user columns. The data will be replaced by Added user and Updated user. This prevents showing user names to third parties. The date fields are set to Not sensitive. Data sensitivity is a setting at the top of the script; set it to 0 if you do not want it to be set automatically. We have introduced the Use for optimistic locking setting for the update_date_time trace field. This is a setting at the top of the script; set it to 0 if you do not want to use optimistic locking on the trace field.fixedThe missing commas in the template functionality, which caused the script to break, have been corrected. The length of the user_name domain is now set to 128 to match the tsf_original_login. Logging data available in the GUInewNew settings are available:Exclude trace cols - You can exclude 4 trace columns (by default, insert_user, insert_date_time, update_user, and update_date_time) if you prefer not to show them in your history views. view_suffix- Specify your desired suffix for the history view. Note: the suffix cannot be _history as this is reserved for temporal tables. Previously, it could be a prefix or suffix, but now only a suffix is allowed. show_as_detail - Indicate whether the history should be shown as a detail of the subject. Set it to 0 if this is not required. setup_roles- Set up roles based on the base tables. force_recompile_extended_property_id - In the views, the query hint "Use force recompile" is used now. This hint is beneficial when the view is used as a screen in your application. SQL server uses it to optimize the query plan.changedWe have updated the names of the generated views to history_overview to align them with our naming guidelines. In addition to the regular primary keys, we have added valid_from and valid_to as primary keys to the generated views. We have changed the default sort order to only sort based on the valid_from and valid_to columns. Optimistic locking has been deactivated for all columns in the generated views. The use of handlers has been disabled for the generated views. Previously, this information was derived from the base table for which the view was generated.fixedThe naming of the created references was not always correct. This has been adjusted. The column generated_by_control_proc_id was not correctly filled in every place. Note: when this model causes generation errors, update the objects with the correct generated_by_control_proc_id or remove the existing views and generate them again. The value of the conditional layout has been changed from grid_order_no to abs_order_no since the abs_order_no is always unique within the table. Active prefilternew changedWe have revised the code for creating active prefilters.This dynamic model is based on the strategy Delete because it only assists in creating prefilters and does not maintain them. Once the prefilters are created, you can modify their settings without being overwritten by the dynamic model.Settings in the scripts are available for adjustment to your preferences. It is now possible to use an icon. First, upload it to the icon table. A tag is now available to exclude a prefilter from a table. If you add the tag when the prefilter has already been added, you must manually delete the prefilter. The prefilter is now column-based instead of query-based. You will no longer get a prefilter for generated tables (for example, history views). Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

An additional release is available to Universal GUI 2024.1.10. It contains one change. Changed handling of OpenID provider informationThe Universal GUI depends on Indicium to receive information about the usage of OpenID providers. This information determines whether the GUI should redirect to a provider.In poor network conditions, the request for this information might be lost, and the Universal GUI would show its login page instead. This could lead to errors when local login was disabled in IAM.Now, if the Universal GUI does not receive information from Indicium but has a `loginAuthProviderHint` in the `config.json` file, it will not show the username and password fields. The 2024.1.10.1 release is now available for download in TCP.

Hello everyone,In this sprint, we have added support for standard keyboard shortcuts, word wrap in grids, opening a document in a modal popup, and more. Read on to see all the new features and fixes. 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.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.1.10 here ContentsDemo Universal GUI version 2024.1.10 New and changed Select or deselect translation in import popup User preferences - Sorting Support for standard keyboard shortcuts Word wrap support in grids Workaround for Universal Firefox showing a black screen Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changed Select or deselect translation in import popupnewIn the import wizard, you can now specify whether the file to import (Excel or CSV) contains human-readable or database values. This is similar to the option that we added to the export wizard in the previous sprint.We will explain this with help of the screenshot below. For example, you have a manager named Hans with ID 12. If your import has the value Hans, the system needs to determine that you mean the manager with ID 12 and then insert that. What if there is another Hans with ID 15? Which one should be inserted? When exporting and importing, it is often much easier to directly use the database value of 12 rather than the translated value of Hans.Indicium version 2023.3.13 is required for this feature.The import popup with the option to select or deselect translationUser preferences - SortingnewWhen a user sorts a grid by clicking the headers, the sorting is now saved and restored when the component loads again. Support for standard keyboard shortcutsnewYou can use keyboard shortcuts to launch toolbar actions for quick and easy editing. Previously, these shortcuts were only available in forms. Now, they are available in every part of the application. You can use the following keyboard shortcuts:Add: Ctrl + + or Ctrl + = Cancel: Esc Copy: Ctrl +  Alt + + or Ctrl + Alt + = Delete: Ctrl + - Edit: Ctrl + E Save: Ctrl + Enter or Ctrl + SFor example, Ctrl + + creates a new record in your last focused table or grid. Pressing Ctrl + Alt + + copies the active record. The application performs checks at the following moments to determine on which grid, form, tree, etc., it should set the focus:Opening a document sets the focus to the main table. Switching tabs sets the focus to the main table. Editing the form or grid automatically sets the focus on the element that is being edited. Word wrap support in gridsnewIn the grid, a text field now displays multiple lines if the word wrap setting is turned on in the Software Factory. You can enable this feature for a domain using the control Multiline in the menu Data > Domains > tab Form > tab Domain > group User Interface. This means that you can scroll through the entire text in the grid.When you are editing the grid, the old styling is still used.The column's content does not influence the height of grid rows. You can adjust the Row height setting of the subject in the Software Factory. Workaround for Universal Firefox showing a black screenDuring this sprint, we investigated an issue when using the Firefox browser on Android. On some occasions, after switching to different apps and coming back to Firefox, the Universal GUI would be shown as a black screen. We found a Firefox bug report. It is not something we can fix on our side; it occurs on multiple websites. The workaround, for now, is to change the battery restrictions from 'restricted' to 'Optimized' or 'Unrestricted.' To do this, open the Settings application and open the Battery section. Click Battery optimization and find the Firefox application. Here, you can change the battery restrictions. Minor fixes and tasksIf you added a new record to a table and one of the fields was a lookup, that field remained empty. The field is now correctly filled with the lookup value. Previously, when you clicked a row in the tree with autosave on, the Universal GUI did not autosave and move to the new row. This has been fixed. There used to be an extra empty column in the grid. It was intentionally added for grids that did not have enough columns to fill the full width of the grid. This way of filling the grid is no longer necessary, so this space-filling column has been removed. Switching to a different item in a tree in auto-edit mode would sometimes cause the application to hang. This has been fixed. If you open the Advanced Filter popup, its title contains the table name. This table name was automatically converted to lowercase. Since this was not always the desired behavior, the table name is no longer changed. The Excel-style filter popup would sometimes not show all available options. This has been fixed. We have fixed five different scenarios where domain elements either would not be displayed or would be displayed untranslated in the Chart component. When a domain element was untranslated, the user would see "false" instead of "No", or "1" instead of "Concept". If you opened and closed the filter option dropdown of a column header, the filter marker would be shown. The reason for that was that the filter checkboxes in the Excel style filters were selected by default, even if no selection had been made. Now, filter checkboxes in the Excel style filters are no longer selected by default. In some cases, the custom tooltip on a grid header was cut off on the edges of the grid. The issue was introduced in version 2023.3.13 and has been fixed now. When, for example, Subprojects would be opened from the menu and would then be opened a second time by clicking a detail tile or double clicking a detail tabpage in for example Projects, reactivating Subprojects from the menu would result in the zoomed document to be wrongly opened. Universal would open the second instance from Subprojects that was opened from Projects. It now opens the first instance from Subprojects, the one opened from the menu, as it should. What we will be working on next sprintThe next sprint we will be working on:Open document window as a modal from process flow Grid double click task on cell double click Commit after patch Save a user defined cube view Save a user defined pre-filter Lift the grid edit mode line height restriction Store more existing user preferences to IAM FormList Look-ups Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! (Opens in new window or tab).

Hello everyone,We are happy to announce the release of the Thinkwise Platform 2024.1.The most important new feature of the Software Factory is the introduction of model enrichments, which are actions that automate parts of your manual workflows. Other highlights in the Software Factory include branch protection, reciprocal merging, and screen configuration preferences for the Universal GUI. We also added support for cell-based double-click tasks, a popular community idea.In the Intelligent Application Manager, we have introduced a new way of storing user preferences.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 Enrichments Protected branches Reciprocal merging Screen configuration preferences for the Universal GUI Cell-based double-click tasks User preferences in the Intelligent Application Manager Questions or suggestions? Highlights of this releaseEnrichmentsThis release of the Thinkwise Platform features the introduction of model enrichments. Model enrichments are actions that automate parts of your manual workflows. You can use an enrichment instead of a dynamic model if you do not want your actions to be executed during every generation.The Software Factory comes with a number of ready-made model enrichments. Over 20 enrichments are already available for areas like the data model, functionality, user interface, unit tests, the transition to the Universal GUI, and the Upcycler. More will be added in the future. In addition, you can build your own model enrichments.Model enrichments can be model-driven, data-driven, or AI-powered. Or a combination of those. A model-driven enrichment will query the model and then create (potential) model updates. It can be used to check, for example, the consistency of your application. You can re-run it on demand. A data-driven enrichment will prompt you for a runtime configuration when you start it. It queries the database to load the information required to present the model updates. Examples of this type of enrichment include generating missing indexes, creating mock data based on table content, and deriving control types and elements from data in the database. An AI-powered enrichment will use the configured generative AI provider of the Software Factory to retrieve information from a large language model. Examples include generating descriptions, translations, comments, etc.  Protected branchesWe have also introduced branch protection. It prevents branches from being archived or deleted. This feature is especially useful for managing branches with indefinite lifespans, like release branches. Temporary branches, such as feature branches, should keep the ability to be archived or deleted after merging.When a branch is protected, a lock icon will be displayed in the branch diagram, making it easy to identify protected branches.Upon upgrading to this version, the branches named MAIN, RELEASE, and DEVELOP will be automatically protected. A branch will also automatically become protected when it is used as an origin for another branch. You can remove its protected status after all its branches have been deleted.Branch protection Reciprocal mergingAnother new feature for branches is reciprocal merging. Previously, after merging a branch to its origin, you would have to manually merge the origin back to the branch to continue working in the branch. Now, we have integrated this reciprocal merging into the merging process. When you create a merge session, you will get the choice of how to continue with the branch after merging it to its origin.A reciprocal merge Screen configuration preferences for the Universal GUIFor the Universal GUI, we have added support for screen configuration preferences. Users can now, for example, select another screen type and reorder or hide detail screens. You can read more about this in the Universal GUI release notes (2023.3.13 and 2024.1.10) in the Thinkwise Community. Cell-based double-click tasksThis release also includes 10 Community ideas representing 123 votes. One community idea that received many votes requested a double-click task that is bound to a specific column. This enhancement significantly improves the user experience because it allows each column in a grid to start a different process or handle specific data. User preferences in the Intelligent Application ManagerWe have introduced a new way of storing user preferences for the Universal GUI in the Intelligent Application Manager. For older user interfaces, user preferences are stored per path in the UI. Now, for the Universal GUI, they are stored per model object or model object variant.A one-time migration of the classic structure to the new structure will be performed automatically during the IAM upgrade. A main administrator can repeat this migration process later if you are still using a previous-generation UI.User preferences in IAM 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 some new model settings that are introduced in Thinkwise Platform release 2024.1. We have also fixed an issue with grid navigation.You can read more about the Windows and Web GUI's features, in the user interface guide (Opens in new window or tab).Download Windows GUI 2024.1.10 here (Opens in new window or tab). ContentsNew Compatibility with 2024.1 model settings Minor fixes and tasks Grid navigation col order wrong Questions or suggestions? New Compatibility with 2024.1 model settingsnewThe Windows GUI is compatible with the new model settings that have been introduced in the Thinkwise Platform version 2024.1. Double-click tasks for grid columns are supported. Minor fixes and tasks Grid navigation col order wrongWhen using the up and down arrow keys to navigate vertically in the grid, the selected column jumped all over the place. This problem has been solved. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! (Opens in new window or tab).

Hello everyone,In this sprint, we have fixed two issues regarding performance on first sign in and application claiming.You can read more about Indicium's features in the Indicium user manual (Opens in new window or tab).We will keep you updated regularly about Indicium's progress. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID.Download Indicium Basic release 2024.1.10.0 here (Opens in new window or tab) Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2024.1.10 here (Opens in new window or tab).  ContentsAbout Indicium New and changed Improved error message for successful OpenID login without valid user Minor fixes and tasks Questions or suggestions? New and changed Improved error message for successful OpenID login without valid userchangeIn Indicium, the error message for a successful OpenID login with an unfound or invalid IAM user has been changed. Instead of just stating that the user was not found in IAM, it now also states that the user's expiration date may have passed. Minor fixes and tasksWe have fixed a rare performance issue that could occur upon a user's first sign-in (after an Indicium restart or a model change) for any given role set. It could happen that Indicium would load the internal application model two or even three times instead of just once. This issue had no functional consequences. We have fixed an issue that, in rare situations, could cause a single user session to trigger multiple application claims in IAM. This issue could cause the Max. # sessions per account to be violated erroneously, causing users to see messages like "Unable to claim the application". Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! (Opens in new window or tab)

Hi everyone!We’ve released the following platform improvement this week: SF 2023.2 & 2023.3 20231221 - Correct model settings history When the Floating label strategy was introduced, an incorrect default value was placed in the history of the table. This would cause an error when attempting to revert to a point-in-time where this value was present. This has been corrected. SF 2023.3 20231222 - Enhance used separator for AI code review There's a small chance where the used file encoding interferes with a separator used in code. When running the AI code review platform improvement, this could cause an issue in one of the procedures. This has been improved to prevent the issue.  🎄 Happy holidays everyone! 🎄

December 21, 2023Full release 2023.13 Fixed: We have fixed a bug where the application crashed and displayed a 'submit crash' pop-up when adding a new entry in the grid of the lookup pop-up. Includes: A prior solution for the chart component incorrectly displaying as 'trial' despite proper functionality and licensing. See Extra release 2023.3.12.1.  Hello everyone,In this sprint, we have added a number of options for users to adjust their screens to their own preferences. In addition, we have made several improvements to the action bar and the task bar. We have also enhanced the way tasks are managed.These are only a few of the many improvements we have made. Read on to learn more about all the new features and improvements 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 2023.1.13For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in the appsettings.json file. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2023.1.13 hereThis is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Monday. ContentsDemo Universal GUI version 2023.1.13 New and changed Screen configuration for users Action bar and taskbar improvements Task improvements Elements filter for domain controls Check for Software Factory and IAM support Config.json file caching strategy Reduced size of Universal GUI Cube support Support for controls Multi-select retained Tooltip position Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedScreen configuration for usersnewWe have added a lot of options for users to adapt their screens to their own preferences. Most of these settings are available in the overflow menu of the taskbar.To configure the availability of these options for your users, see Configure user preferences.Screen type - Available as of Thinkwise Platform version 2024.1 With the option Screen type, users can select another screen type. In the pop-up, they can select a screen type from the dropdown menu. The screen will refresh, and the screen type will be applied to the current subject. For the configuration of the available screen types, see Available for user preferences.Users can select another screen typeDetails - Available as of Thinkwise Platform version 2024.1 With the option Details, users can reorder and hide detail screens. In the pop-up, they can reorder the detail screens by dragging them to another position in the list. They can hide a detail screen by deselecting its check box. The screen will refresh, and the changes will be applied to the current subject. This configuration affects the displayed details in the tabs and in detail tiles.Users can select another screen typeChart - Available now With the option Chart, users can change the chart settings. They can adjust the chart type and the legend. If no legend is available, only the chart type can be adjusted.For the legend, the following settings are available:- Horizontal alignment (left, center, right)- Vertical alignment (top, center, bottom)- Legend direction (left to right, right to left, top to bottom, bottom to top)Group in grid - Available now In addition to the settings in the overflow menu, the Universal GUI now also supports grouping in a grid. Users can change the grouping by dragging a column header to a group box. Note that the grouping is not remembered when the screen is refreshed. See also Grouping in a grid.To enable this feature, two settings in the Software Factory are required:Select the Group checkbox in the menu User interface > Subjects > tab Settings > tab Permissions. Select the Group box visibility checkbox in the menu User interface > Subjects > tab Settings > tab General. The possible values are: Always - The group box is always visible, and it is possible to drag grid columns into it. When grouped - The group box is shown only when a group exists in the model. Never - The group box is never shown, and it is not possible to change the grouping of the grid. Users can change the grouping by dragging a column header to a group box Action bar and taskbar improvementsnew changeWe have made several improvements to the action bar and the taskbar.The action bar is the one on top that has search, prefilters, CRUD, etc. If you use a Taskbar screen component, the task buttons will be moved from the action bar to the taskbar.The first change is that we have moved all the unrelated items from the prefilter overflow menu to the general overflow menu (next to Export and Import). This change means that the overflow menu of the prefilters will disappear if there are no prefilters. The following items have been moved:Quick filter Filter Clear all filters Restore sort order Expand/collapse all (for the tree)Another change is that you can now place both a taskbar and a task tiles component on a screen. Previously, the taskbar would be removed. Multiple taskbars on one screen are also possible.If you place the taskbar at the top of the screen, it will become part of the main action bar. In that case, it will never be removed from the main action bar, even if the screen contains another taskbar or task tiles component.A new feature is that you can now reposition the items in the action bar. You could, for example, place the tasks on the left and the search field on the right. You can do this by adding a screen component property called toolbar_order to the top screen component in the screen tree. In the menu User interface > Screen types > tab > Screen components > tab Form > tab Screen component properties, you can enter a Screen component prop (toolbar_order) and Value in JSON format:{ "start": [ "Extra", "Crud" ], "end": [ "Reports", "Prefilters", "Tasks", "CubeViews", "Search" ]}This JSON object has two properties, "start" (the items on the left) and "end" (the items on the right).Both properties are arrays that can hold the following values:"Search" "Prefilters" "Crud" "Tasks" "Reports" "CubeViews" "Extra"Most of these are self-explanatory. "Extra" holds the items in the overflow menu like Import, Export, Filter, Restore sort order, etc.When we implement vertical bars, "start" will correspond to the top, and "end" will correspond to the bottom side of the bar. Task improvementsnewWe have enhanced the way tasks are managed, resulting in the following improvements:Timeouts are no longer an issue. Each task now features a progress bar, with a spinner visible until the initial message appears. Messaging has been improved.In the Software Factory, you can configure the task progress and feedback. The following options are available in the menu Processes > Tasks > tab Setting > tab General > field Await result:Yes: Users have to await the result; a progress indicator is shown, and the GUI is blocked. Yes (no progress bar): Users have to await the result; no progress indicator is shown, and the GUI is blocked. No: Tasks are executed in the background, allowing users to continue working; no progress bar is shown. Refreshing or executing a process flow is not possible. The task may be part of a process flow. Optional: Combines the previous options. The progress bar is visible, but users can cancel it. The subject is not refreshed.You can enrich the SQL logic of the task by sending progress messages. For more information, see Display progress from a stored procedure. Users will receive these messages immediately, while the progress indicator is visible in the GUI. In this way, you can inform them about the progress of a long-running task.Known issues:When a task is executed on multiple rows ("pop-up for each row"), a request to insert parameters for the next task only appears after the previous task has been executed. This might take some time, depending on the task logic. Long-running tasks are bound to the subject on which they are initiated, and the subject should remain open until the task is completed. Users will receive a message when they try to close the document.The progress bar in the task, with progress messages Elements filter for domain controlsnewThe Software Factory includes domains that may have elements. You can add elements in the tab Elements tab (menu Data > Domains). You can use this, for example, to add statuses like Approved or In progress to an Invoice column.Now, if a column holds a domain with elements, its grid header features a new filter for these elements. This is similar to the filter in Microsoft Excel, where all values for a column are accessible in the column header. In other filters and filter forms in the Universal GUI, the elements will be accessible in a dropdown field.The elements filter in the grid header Check for Software Factory and IAM supportnewIf a user attempts to log in to an unsupported version of the Software Factory or IAM, the Universal GUI will now attempt to update itself and perform a hard refresh. It will then try to log in again to check if the version is now supported. Only if the version remains unsupported, a 'version not supported' message will be displayed on the login screen. Config.json file caching strategychangeIf a network is available, the config.json file is now cached using a 'network-first' strategy to ensure it always picks up the latest changes. We maintain a caching strategy to enable Universal GUI usage even when offline. Reduced size of Universal GUIchangeWe reduced the disk size of the Universal GUI by approximately 66%. Users now need to download less when using this GUI, resulting in a better experience with faster loading times. The functionality of the Universal GUI remains the same. We removed, for example, compatibility with older browsers, saving a significant amount of space. The Universal GUI still adheres to the lifecycle policy. Cube supportnewWe have added support for the default cube view type. When a user selects a cube view, the type that you configured in the Software Factory will be shown. For example, if you have configured a cube and a chart on different tabs, the default cube view type determines which one is shown.You can configure the type in the menu User interface > Business intelligence > tab Tables > tab Cube views > tab Form > field Def. cube view type.In addition, the active cube view is now remembered if the user changes the cube view. Support for controlsnewWe now support the domain controls CODE EDITOR and SQL EDITOR. These controls are used, for example, in the Software Factory. They highlight the syntax for SQL, JSON, or XML formats. Multi-select retainedchangeWhen you selected multiple rows and waited for a few seconds for auto-refresh, the selection would not be held by the Universal GUI. Now it will.You can auto-refresh on a subject in the Software Factory, see Auto-refresh. Tooltip positionchangeWe have changed the tooltip position in various places, including the form and grid. It is now located above the cursor for improved legibility of the screen elements. Minor fixes and tasksTree icons will now refresh properly when editing an item detail. When selecting four random rows in the grid and attempting to export them, the pop-up initially displayed the correct number of selected rows. However, after a few seconds, this number would update to 1 due to the grid auto-refreshing. The problem has been resolved, and now the number of selected records remains consistent. If auto-save and auto-edit were enabled, row refresh was not working in some cases when navigating to different rows using the up/down arrow keys. This has been fixed. We have fixed some issues with the snack bar. It now has a show more button when there are more than 3 messages; otherwise, it displays them in individual snack bars. We have also added space between messages in the Show more pop-up. The text in a tile will now continue on the next row if it is too long to fit on one row, ensuring complete visibility of the text. In charts with multiple axes, the domain elements on the categories were not translated, and the database value was displayed. This issue has been resolved. We have fixed a bug where the application crashed and displayed a 'submit crash' pop-up when adding a new entry in the grid of the lookup pop-up. What we will be working on next sprintThe next sprint we will be working on:User screen configuration - Remember sorting Support for default CRUD shortcuts anywhere on the page Open document as a modal Grid multiline field appearance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,We have fixed an issue that was introduced in Indicium version 2023.3.13.0. This issue could cause a query syntax error on query's with SQL prefilters on platform versions 2023.2 and below. Platform version 2023.3 was not affected by this issue. This issue has been resolved in Indicium version 2023.3.13.1, which is available for download in TCP.Our apologies for any inconvenience caused by this issue.

Hello everyone,In this sprint, we have improved query generation when SQL prefilters are involved. We have also fixed an issue with requesting the scope of a custom resource of a client applicationYou can read more about Indicium's features in the Indicium user manual (Opens in new window or tab).We will keep you updated regularly about Indicium's progress.About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support 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 2023.3.13 here (Opens in new window or tab).  ContentsAbout Indicium New and changed Improved query generation when SQL prefilters are involved Minor fixes and tasks Questions or suggestions? New and changed Improved query generation when SQL prefilters are involvedchangeQuery generation has been improved for situations where SQL prefilters are used. Previously, Indicium did not know which columns were used by the SQL expression, so when a sub-query was required, it would select all columns in the sub-query to satisfy the prefilter on the outer query.Now, it will only select the necessary columns. This makes these queries easier to read and, in the case of expression columns, will improve performance somewhat.This change only applies to platform version 2023.3. Minor fixes and tasks We have fixed an issue that would occur when requesting the scope of a custom resource of a client application (OpenID Client). Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community! (Opens in new window or tab)

Hello everyone,It has come to our attention that the chart component of the Universal GUI shows up as a trial version. This affects all Universal GUI versions up to 2023.3.12, used with applications that leverage the chart component.SymptomsWhile the application or the chart will not cease functioning in any way, a FusionCharts Trial indicator is visible to the end-user.Chart showing the trial indicator in the bottom-leftSolutionWe have remediated this problem immediately. You can update your Universal GUI to version 2023.3.12.1, which is available for download in TCP and the container repository.Updating to 2023.3.12.1 not possible?If you are still using an older version of the Universal GUI, you may not be ready or able to update to version 2023.3.12.1.This can be due to backwards compatibility restrictions with Indicium or your Thinkwise Platform model version.Please get in touch with your Thinkwise representative with your current Universal GUI version or submit a ticket in TCP and we will provide a hotfix version based on your current Universal GUI version. We apologize for any inconvenience this may cause. We are investigating the root cause of this incident further, as the component license itself is in order.

Hello everyone,We have fixed an issue that was introduced in Indicium version 2023.3.12.0. This issue caused an error to occur when trying to send an email for two-factor authentication and password reset tokens. This issue has been resolved in Indicium version 2023.3.12.1, which is available for download in TCP.Our apologies for any inconvenience caused by this issue.

November 27, 2023Full release 2023.3.12 Fixed: The user no longer gets an error when logging in with an email address. Hello everyone,Some of the new features in this release are the added support for several cube features and the Calculator domain control. We have also further enhanced the functionality for filtering, the action bar, and the task bar.This release contains two breaking changes. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2023.3.12For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, 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 the appsettings.json file. The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2023.3.12 here ContentsDemo Universal GUI version 2023.3.12 Breaking Support for Thinkwise Platform releases 2021.2 and 2021.3 has ended Moved config.json file New and changed Support for cube features Support for Calculator domain control Filtering further enhanced Select or deselect translation in export pop-up Scheduler sliding window HTML control in a grid Multiline control in a grid No more keyboard for lookup with combo control Data no longer reverted in a field with an input constraint Minor fixes and tasks What we will be working on next sprint Questions or suggestions? BreakingSupport for Thinkwise Platform releases 2021.2 and 2021.3 has endedIn accordance with our Lifecycle Policy, the Universal GUI support for Thinkwise Platform releases 2021.2 and 2021.3 has ended.UpgradeUpgrade to at least the Thinkwise Platform release 2022.1. Moved config.json filePreviously, a downloaded Universal GUI contained a preconfigured config.json file. However, this file could be easily overwritten if you replaced the GUI with a newer version. For this reason, we have removed the preconfigured config.json file and added an example version: config.sample.json.Check your configurationFor a new deployment, rename config.sample.json to config.json and add your preferred settings. You can find all the settings and their options at Configuration settings for the Universal GUI For existing deployments, you can keep your original config.json file. This change saves you a manual step or one in your CI/CD pipeline  New and changedSupport for cube featuresnewWe have added support for the screen component Pivot table fields. To display this component in the Universal GUI, select the checkbox Dragging fields in a cube (menu User interfaces > Subjects > tab Components > tab Cube). This feature allows users to modify a cube's series and categories and create a customized overview of the pivoted data.The setting Sort by cube field is supported, too (menu User interface > Business intelligence > tab Tables > tab Cube fields > tab Cube view fields > tab Form). The prerequisites for this setting to work are:The Cube field type is Value (menu User interface > Business intelligence > tab Tables > tab Cube fields > tab Form) And: the field is part of the cube view. A user cannot sort by values they cannot seeCube features support Support for Calculator domain controlnewThe Universal GUI now supports the Calculator domain control, allowing users to perform calculations using on-screen buttons or their keyboard. The decimal separator is automatically determined based on the user's region, using either a comma or period.The Calculator domain control in the Universal GUI​​​​ Filtering further enhancednew fixIn this release, we have further improved the Universal GUI's filtering capabilities.In the filter forms, we have expanded the support for filter conditions with the following operators:Is empty Is not Empty Does not contain Does not end with Does not start with Between Not betweenIn addition to this, the Universal GUI now supports filtering for the date, time, and datetime fields. You can use these filters in filter forms and quick filters (filtering on the selected grid cell).The advanced filter form (using filter expressions) has been introduced in the previous release, 2023.3.11.We have also fixed a problem with filters on a checkbox with 0, empty, or false values. The filter icon was not displayed on the grid column header in these cases. This issue occurred, for example, when using a quick filter on an empty checkbox, making it difficult to notice that a filter was active on this column. We have resolved this problem. Now, the filter icon will be visible in these cases. Select or deselect translation in export pop-upnewIn the export pop-up, when choosing which columns to export, a new option is available: Export headers and data translated and localized.For example, when exporting employee_id, the default behavior is that the connected name is passed. Now, if you deselect the new option, Indicium will export the raw data.A new option: Export headers and data translated and localization Scheduler sliding windowchangePreviously, when using the Scheduler with a sliding window and a top timescale set to years, the Scheduler would display only a part of the current month in the past. This potentially caused users to lose oversight of events that began earlier. To improve this, the Scheduler now starts a month in the past. HTML control in a gridnewThe HTML control now has an icon to open the popup in an editable grid. This is similar to the HTML control in the form. In the grid, a user can change the contents of the control only through the pop-up. Multiline control in a gridnewThe Universal GUI now supports editing multiline controls in grid edit mode. A user can edit these controls directly within the grid or open them in a popup for editing. The popup button is also available for a multiline control in the form.During grid editing, this button will also appear on the active record in the grid. It respects the setting Show action button found in the Software Factory menu: Data > Domains > tab Form > tab Domain. No more keyboard for lookup with combo controlchangePreviously, when opening a lookup with a Combo control on a mobile device, a keyboard would appear. Now, this behavior has been removed.If you prefer the previous behavior with the keyboard, you can enable it by adding the extended property disableKeyboardForAutoCompleteCombo: false to your config.json file.Note that if a lookup has a Default control with a suggestion (as configured in the menu User interface > Subjects > Settings), the behavior remains the same, and a keyboard will still open when accessing the lookup. A suggestion type control will display a maximum of 8 results based on the typed search criteria.You can base the choice between these options on user preference and the number of items expected in the (unfiltered) dropdown. Data no longer reverted in a field with an input constraintchangeIn a field with input constraints, the data entered would be reverted to a previous value if the input breached the constraints. This could potentially lead to a user saving incorrect data. To prevent this, we have removed this behavior. Now, saving is no longer possible if input constraints are breached. Minor fixes and tasksWe have improved the alignment of elements in the export wizard in Comfortable mode. We fixed an issue where, in specific cases like editing an autosave-enabled grid with a form component, the checkboxes' values in the active grid row would not be restored correctly after clicking cancel. Upon closing and reopening a default editable document, the document would no longer automatically enter edit mode. This has been fixed. We fixed an issue where the tree would incorrectly expand when Default Expanded is set to false. We resolved a problem where certain SVG icons in the tree and form were not displayed correctly. When updating a tree icon through a task, the icon failed to refresh, persisting with the original one. Now, the tree icon will correctly refresh. We have fixed an error that occurred when a task with a HTML parameter was opened from the tiles menu. On the current application page, clicking the application switcher would display nothing if the user lacked rights to other applications. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:SQL/Code editor Grid grouping by dragging headers Chart user-defined legend position User preference screen type User preference detail show/order Excel style filter on domain controls Task progress report Toolbar improvements Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvement this week: SF 2023.3 20231124 - Rights on menu items While trying to modify a menu group, an error could occur because of existing role rights, hindering the group change. This service fix will ensure that these role rights remain intact when changing a menu group using the form. They are automatically applied to the new combination of group and item.   In the 2024.1 it will also be possible to use the Design tab to modify the menu group without any errors. This was not something we could easily include in this service fix. We mentioned this part as a known issue for the 2023.3 platform release.

Hello everyone,In this sprint, we have fixed two grid issues.You can read more about the Windows GUI's features in the user interface guide.Download Windows GUI 2023.3.12 here.ContentsMinor fixes and tasks Editable grid as a detail Keyboard navigation in the grid Questions or suggestions? Minor fixes and tasksEditable grid as a detailWe resolved a problem in the default editable grid where, in some instances, the grid failed to enter edit mode when clicking on a new row. This issue could occur when the editable grid serves as a detail of another document. Keyboard navigation in the gridWe have fixed a problem in the Windows GUI's grid where navigating via the keyboard would not scroll the cell into view. 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 possibility to filter within the open API document. We have also made Indicium more robust against missing decryption keys.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support 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 2023.3.12 here.  ContentsAbout Indicium New and changed Filter in open API document Start and load with missing decryption keys Minor fixes and tasks Questions or suggestions? New and changedFilter in open API documentnewWe have added the possibility to filter within the open API document. This can be a powerful method to reduce the document size, resulting in faster loading times, or to selectively show specific entities.The following query string parameters have been added:entities - A single entity or a comma-separated list of entities. The entities can be tables, reports, and tasks. Example:iam/<appl>/openapi?entities=employee,employee_hour,project include_lookups - A boolean (true or false) that indicates whether the lookups need to be included in the document. Example:iam/<appl>/openapi?include_lookups=true include_details - A boolean (true or false) that indicates whether the details need to be included in the document. Example:iam/<appl>/openapi?include_details=true include_table_tasks - A boolean (true or false) that indicates whether the table tasks need to be included in the document. You can filter normal tasks with the entities' query string parameter. Example:iam/<appl>/openapi?include_table_tasks=true include_table_reports - A boolean (true or false) that indicates whether the table reports need to be included in the document. You can filter normal reports with the entities' query string parameter. Example:iam/<appl>/openapi?include_table_reports=true Start and load with missing decryption keyschangeWithout access to the required decryption keys for the application model or IAM configuration, Indicium will now still start and load these application models. Only the features related to the encrypted settings will not work. Minor fixes and tasksWe have extended the lifespan of the cookie that stores the redirect URL or return URL. Previously, this cookie had a lifespan of only 3 minutes, meaning that if users opened the page and remained inactive for 3 minutes, the cookie would expire, and the return URL would be lost. To address this issue, we have increased the cookie's lifespan to 10 minutes. We have fixed an issue that prevented the drag-drop links from being provided as input parameters for the task's default procedure. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,You may have already noticed some changes in the Thinkwise Documentation, but perhaps you haven't seen everything yet. Here’s an overview of all the structural changes and enhancements that we have made in the last few months. ContentsContents General documentation features New tiles Let us know what is helpful Enlarge images Content enhancements IAM - Roles better explained Software Factory - Improved task setup guide Software Factory - Generic features Restructured content  General documentation featuresNew tilesThe most recent and most visual change is that we refreshed the tiles on the documentation's home page. They are now more in line with the Thinkwise products.New subjects on the landing page are Artificial Intelligence and the Thinkstore. We want to highlight these subjects because they can be a great help in developing your applications. They replace the Knowledge base and User interface guides. Of course, both guides remain available through the menu and Search. Let us know what is helpfulAt the bottom of each page, you can now let us know whether the information on that page was helpful or not. We use this feedback to decide which pages need improvement, to set priorities, and to know which pages are good and useful. So, you can help us further enhance the documentation by using the Yes and No buttons.We are looking into extending this feature with a feedback field, so you can let us know what's good and what can be improved.Let us know what you think!Enlarge imagesSome of the screenshots in the documentation are large and contain a lot of information, which makes them sometimes hard to read. It is not always possible to make them smaller because too much information would be lost. Instead, you can now click on an image to enlarge it. When you hover over a screenshot, a magnifying glass appears as an indication that the screenshot can be enlarged. Click to enlarge, and click again to zoom back out.Enlarge a screenshotContent enhancementsIAM - Roles better explainedTo resolve some confusion about the available roles in IAM, we have improved the descriptions of these roles. You can find the descriptions in the Administrator roles guide. For a better overview, we have added some tables to this guide that enable comparison between roles, see the chapter Role overview.In addition, we have added the minimum roles required for each feature in IAM.Roles in IAM better explained Software Factory - Improved task setup guideWhen you are new to the Software Factory, one of the more complicated processes might be setting up a task. To support you in this, we have added a clear walkthrough to guide you through the process. See Set up a task. This information may also be useful for setting up the drag-drop functionality.How to set up a task Software Factory - Generic featuresSome features are generic throughout the entire Software Factory but were nowhere clearly explained. Until now. In the new guide Generic features, you can read everything about features like Go to tasks, trace fields, and generated objects.We will continue to extend this guide.Generic features Restructured contentA guide with a clear structure makes it easier and faster to find what you are looking for. For this reason, we have restructured some large guides:The IAM guide - We restructured the entire IAM guide. Previously, it included an Administrators’ guide and a Managers’ guide, but so many features have been added to IAM in recent years that this format is no longer useful. Now, the functionality in IAM is directly visible in the menu. The Models and branches guide - The information has been restructured, with a clearer division between both.  The Universal UI guide - This guide now consists of three parts. Within these parts, the information has been restructured.  Basics Screen components Controls

Hi everyone!We’ve released the following platform improvements this week: SF 2023.3 20231108 - Field positioning using field sets We now set the "field no. of positions further" to 1 when a field in a form or task/report pop-up is part of a new field set.  A field set defines which fields belong to each other and should be displayed next to each other. Example: Field A Field B - Field C If field B is hidden in the model or due to authorization, field C must not be shown next to field A because it has a different field set.  SF & IAM 2023.2 and up 20231107 - Set client secret not null When trying to encrypt the client secret from oauth server you will get a error which causes that the client secret isn't encrypted. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week: SF 2023.3 20231030 - Prevent lock during archiving Archiving the current user branch after executing a merge session or manually archiving the current user branch will prompt the user to select a new branch. A previous hotfix ensured the branch currently being archived would not be selected. However, this caused waiting times in certain situations, when the asynchronous archiving would already be running. This situation has been resolved. A different method is now used to prevent that the archiving branch will be chosen as target branch on the switch branch task.