Product Updates

Hello everyone,We have released version 2022.1.12 of Indicium Universal, which contains two hotfixes. If you are on platform version 2021.3 or above and you are not targeting a DB2 database server, then you can ignore this release and await our next feature release on Friday.Task confirmation messagesThis hotfix applies to platform versions 2021.2 and below. When a task was configured to have a confirmation message, an error would occur when attempting to execute the task from the Universal GUI. This error was caused due to a mismatch between supported versions for confirmation messages. The Universal GUI supported this feature on every platform version, whereas Indicium Universal only supported it from version 2021.3 onwards. Important: this hotfix also requires the latest SF and IAM hotfixes to be installed, otherwise it will not work.Layout procedures on DB2This hotfix only applies when Indicium’s appsettings.json is configured to use the iSeries mode, not the Core mode. It fixes an error regarding the procedure parameters that could occur when calling the layout procedure. Version 2022.1.12 of Indicium Universal can be downloaded here. Our apologies for any inconvenience caused by these issues.

Hello everyone!We’ve released the following platform improvements this week: SF and IAM 2020.2 and up20220225 - Match checkbox and element filter and search conditions The database values for default filter and search conditions for checkboxes and elements are different from the default filter and search conditions (equals, starts with etc) of all other control types. The i_ui_gui_appl view will now convert these database values so they match the other control types. 20220225 - Remove grid text scaling for Universal GUI With the introduction of Compact mode and with the changes in font-size, automatic scaling of text in the grid is no longer needed. The scaling was originally in place to ensure no unnecessary whitespace or margin was left. Due to it no longer being needed, it has been removed. SF and IAM 2020.2, 2021.1 and 2021.220220222 - Added confirmation message value to i_core_task Due to the confirmation message value being present in the GUI, but not in the values returned to Indicium a 400 error occured in Universal. This has been hotfixed in the 2020.2, 2021.1 and 2021.2 version of the Software Factory and IAM by adding the value of the confirmation message to the information returned by i_core_task. SF and IAM 2021.3 and 2022.120220224 - Maps i_ui improvements Some improvements have been made in the data mapping, base layer and overlay interface views to Universal (i_ui views) for Maps. It is not possible anymore that values are retrieved while the 'Show' setting is empty. It is not possible anymore that too many values are retrieved because of an incomplete join. SF 2022.1 20220225 - Invisible table tile images restored Due to a missing line of code, table tile images were not available for the Universal GUI to show. This has been fixed.    Please note: Some files are currently being processed by our production pipeline and will become available at a later time today.

Hello everyone!We’ve released the following platform improvements this week: SF 2020.2 and up20220215 - Removed session properties from i_ui_extended_property The session properties have been excluded from the i_ui_extended_property. This has been changed in every version of the Software Factory that is currently supported. In the 2022.2 version of the Software Factory an extra property will be added (Expose to front-end) to the extended properties that allows the developer to mark specific extended properties as allowed to be exposed to the front-end. SF 2021.3 and 2022.120220214 - Unit test datatype usage fix Some data types used in the Unit test process had an insufficient width causing errors in situation where the used parameters were larger than 100 characters. This has been fixed. 20220218 - Writing of messages Execute source code performance improved fix The processing of returned messages during the executing of code files has been improved upon, resulting in a significant performance boost. SF and IAM 2020.2 and up20220214 - Add UI and core views for drag-drop information In preparation for drag-drop functionality in Universal, both Indicium and Universal GUI will obtain the model information. SF and IAM 2021.2 and up20220216 - Added additional OAuth2 prompt options The available OAuth2 prompt options has been made editable and has been expanded with the prompt options login, select account and none.  

February 18, 2022:Changed beta release to the full version: 2022.1.11 Hotfixes for issues found in the previous beta release: In non-edit mode, conditional layouts did not work. This has been fixed. Some mandatory fields no longer had a mandatory asterisk. This has been fixed. When a process flow with a Start table task process action was executed, the application could become unresponsive. This has been fixed.  Hello everyone,In this sprint, we added two extended properties that can be very useful when executing a task offline. And when importing, you can now also update the existing matching rows. Furthermore, we added change detection for auto-refresh, and form controls in edit and non-edit mode now have the same style.More new functionality and improvements are listed below.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress. Universal GUI version 2022.1.11Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation  and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.1.11 here  Contents of this releaseUniversal GUI version 2022.1.11 New Hiding read-only task parameters when offline Repeat offline executable tasks Update Existing rows Grouping by a time interval in cube charts Splitter position preserved Changed Process flows with multiple start actions New Change detection performance setting for auto-refresh Same styling for form controls in edit and non-edit mode Minor fixes and tasks What we will be working on next sprintNewHiding read-only task parameters when offlineWe added a new extended property HideOfflineTasksReadonlyParameters. This property hides all read-only task parameters when offline. This way, you don't have to create a duplicate task for offline use that does not contain these read-only task parameters. This Application property just needs to be present, no value is necessary.Repeat offline executable tasksYou can now configure a task to repeat after execution in offline mode. For example, to scan an entire store stock very quickly with a barcode scanner. In future platform releases, this will be a task-level setting in the Software Factory. For now, this can be enabled by setting the new Extended property RepeatOfflineTasks. This will only be applied to tasks marked as "Offline executable".Update Existing rowsThe Import dialog now also includes an Update existing rows checkbox. To import new rows and also update the existing matching rows, select the Update existing rows check box.The import dialog for the Projects screenGrouping by a time interval in cube chartsUniversal cube charts now support the following time intervals: Date, Year, Quarter, Month, and Week of year.Splitter position preservedWhen a splitter was moved, and the user changed tab pages or changed documents and then reopened it, the new position was not remembered. This has been changed. Now the splitter position is preserved.ChangedProcess flows with multiple start actionsThe Universal GUI now supports process flows with multiple start actions modeled after the start flag. For example: running the same flow both after opening a document for the first time and after reactivating it. Example of a process flow with multiple start actionsNew Change detection performance setting for auto-refreshThe logic concept Change detection that is available as of Thinkwise Platform release 2022.1 can now be applied before an auto-refresh on a subject takes place. Before the auto-refresh starts, this logic concept checks whether or not a subject has been changed. This prevents unnecessary auto-refresh actions and works especially well when the refresh is a bit 'heavy'.The Change detection setting can be specified in menu User interface > Subjects > tab Default > tab Settings > tab Performance. New Change detection settingSame styling for form controls in edit and non-edit modeIn a previous release, we changed the style of form controls in edit mode by adding a background color. Now we applied this style to non-edit mode too, which makes the positioning of controls clearer and provides a better indication of their boundaries. The transition from non-edit to edit mode is now smooth and less "jumpy". The label and data value stay at the same position with and without the new style.Note: If you have set the useFormFieldBackgroundColor setting in config.json to false, the default background color for form fields is not used. Same styling for form controls in edit and non-edit modeMinor fixes and tasksWhen editing a Formlist field, the tooltip displayed the previous value instead of the new value. This has been fixed. Primary key columns with a Datetime domain were not parsed correctly resulting in errors. This has been fixed. When switching chart views or opening a new chart after a failed network request to get the chart data, the charts stopped working. This has been fixed. When moving a splitter in a screen that also contained (for example) a preview component or HTML editor, the splitter did not move correctly. When a mandatory field with control Checkbox, Combo, or File link was not filled in, no error was shown under the appropriate field. In a selection control (lookup), when clearing the field by pressing backspace, the default procedure was executed immediately. As a result, the previous default value was immediately refilled. This has been fixed. The lookup now first sends data to Indicium when leaving the field. When selecting a record in an auto-refresh screen, the top row was selected first and then the original row. This has been fixed. When loading a screen, the profile picture could disappear for a short time. This has been fixed. In a screen containing a map, when the domain element of a custom marker did not have an image, the application could stop responding. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Grid column label grouping - Use grouped header labels. Scheduler time period configuration - The ability to change the displayed time period in the resource scheduler. Filter form conditions - The ability to use several filter conditions in the Universal GUI defined in SF → Subjects → Data → Filter conditions (with some exceptions). Action bars positioning - The ability to position action bars with tasks anywhere on the screen. Technical design for storing local user preferences.

Hello everyone,In this sprint, we solved some issues.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.1.12 here. Download Web GUI 2022.1.12 here.Minor fixes and tasks(Web GUI) When closing a lookup popup dialog, an incorrect value was returned into a form field when the item contained a non-unique translation. This has been fixed. (Windows GUI) When opening the Windows GUI and the cached get_gui_map value was a decimal number instead of an integer, an error message occurred. This has been fixed. (Windows GUI) When switching subjects from a form or grid, the application could become unresponsive. This has been fixed.

Hello everyone,In this sprint, we made it possible to authenticate personal and work accounts separately with Microsoft Azure Active Directory using tenants. Furthermore, Indicium now supports authentication by Amazon Simple Notification Service (Amazon SNS for short) to receive messages published by Amazon SNS. Finally, we support a new quarter standard computation.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.11 here.Contents of this releaseBreaking changes Windows users can no longer be impersonated as Database Pool User Indicium Universal Authenticating users in Microsoft Azure Active Directory using tenants Amazon SNS authentication support New: quarter standard computation Minor fixes and tasks Breaking changesWindows users can no longer be impersonated as Database Pool UserIn this version, it is no longer allowed to configure a Windows account as Database Pool User in the appsettings.json configuration file. This support is removed because it caused performance issues and is considered a potentially dangerous security practice. You can easily circumvent this by configuring the IIS Application Pool Identity property, or by configuring an RDBMS user as a Database Pool User. See also: Configuring pool users . Indicium UniversalAuthenticating users in Microsoft Azure Active Directory using tenantsOne of the limitations of our support for authenticating against Microsoft Azure Active Directory via OpenID was that each configuration would only work on one specific tenant. In the case of multiple tenants, you would need to configure multiple OpenID servers, which would also result in multiple login buttons. In addition, the common (all Microsoft accounts) and organizations (all work and school accounts) tenants were not supported at all. In this Indicium Universal release, we have added two new settings for OpenID server configurations that enable the use of these two global tenants. You can now define multiple valid tenants within your organization. Furthermore, you can now completely disable issuer validation. This allows you to use the common and organizations tenants to accept logins from Microsoft accounts that do not belong to a tenant under your control.When using Microsoft Azure Active Directory to authenticate your users, it is now possible to explicitly specify one of the following:Both personal Microsoft accounts and work or school accounts can log in to the application. Only users with work or school accounts can log in. Only users with personal accounts can log in (this was already possible in earlier versions by using the consumers tenant) User accounts in a specific tenant can log in (possible in earlier versions).In all cases, the Microsoft account that tries to log in must already be available in IAM. Otherwise, Indicium will not accept the authentication. We will be working on a user provisioning feature that removes this necessity in the near future by creating IAM accounts for unknown users automatically.Aside from each company-specific tenant identified by a GUID, Microsoft defines the following 'global' tenants:organizations (this is an umbrella tenant for all organization tenants) consumers (this can be seen as a singular company-specific tenant where the company is Microsoft and it encapsulates all personal accounts) common (all organization tenants and Microsoft's tenant for personal accounts)For more information, refer to the Microsoft OpenID Connect documentation.The base configuration for OpenIDConnect for Microsoft is:"Microsoft": { "MetadataEndpoint": "https://login.microsoftonline.com/<tenant>/v2.0/.well-known/openid-configuration", "ClientId": "client-id", "ClientSecret": "client-secret", "ButtonIcon": "windows_64px.png", "ButtonText": "Sign in with Microsoft", "SignOutButtonIcon": "windows_64px.png", "SignOutButtonText": "Sign out of Microsoft", "IncludeEmailScope": true,} To support the common and organizations tenants:If you want to allow everyone with a Microsoft account to log in, specify common for <tenant>. If you want to allow all work and school accounts to log in, specify organizations for <tenant>. In both cases, disable the issuer validation because the tenant that issues the token is not known in advance:"ValidateIssuer": false If your organization has multiple Azure AD's but you want a single sign-in button then you can also use the organizations tenant, but you don't need to turn issuer validation off. Instead, you can use the ValidIssuers settings to supply a list of tenants corresponding to all of your Azure AD's. This way, accounts of other organizations will not be able to sign in."MetadataEndpoint": "https://login.microsoftonline.com/organizations/v2.0/.well-known/openid-configuration","ValidIssuers": [ "https://login.microsoftonline.com/<tenant-one>/v2.0", "https://login.microsoftonline.com/<tenant-two>/v2.0"] To enable users to sign in with personal accounts, specify consumers for <tenant>. ValidateIssuer does not need to be turned off for this to work.Amazon SNS authentication supportIndicium now supports authentication by Amazon Simple Notification Service (Amazon SNS for short) to receive messages published by Amazon SNS. To use Amazon SNS to send notification messages, subscribe to Amazon SNS topics on one or more HTTPS endpoints. You still need to confirm your subscription by going to the SubscribeURL, either with the HTTP Connector or manually from the browser.The endpoint can for example be an Indicium Process Flow API endpoint. This makes it possible to create custom logic to handle the message.Please refer to the Amazon documentation for full details on how to subscribe New: quarter standard computationIndicium now supports a quarter standard computation. This computation calculates the quarter of the year (1, 2, 3, or 4).Syntax: $apply=compute(quarter(*column name*) as *alias*))Minor fixes and tasksWhen uploading a file with an extension that was not allowed, the readability of the error message was poor. The file extensions are now separated by slashes and displayed without single quotes. We fixed an issue with document preview in combination with an Excel file in the Windows Server 2019 Datacenter Edition. The $apply operation could return an empty object ( {} ). These records will now be removed from the result. When calling a task or report in the context of a table that uses context logic, the call failed if the context logic output parameter for that task or report was disabled. This has been fixed and also fixes some issues with calling certain Software Factory tasks via the API, such as the task to copy a project version.

This area contains the release notes and hotfixes for our products.Check out the product filter below: select a product to get a good overview of all its release notes and hotfixes. Do not forget to Subscribe to this area with the button at the top right of this screen.

Hello everyone!We’ve released the following platform improvements this week:SF 2022.120220201 - Conditional layout validation corrections Two validations regarding invalid values ​​for conditional layout, could result in validation messages outside the project/project version context. This has been corrected. SF 2020.2 and up20220204 - Fix platform default theme in i_ui_global_settings It is now possible to run Universal against a clean SF when there are no default themes selected for platforms Upcycler20220202 - Upcycler - Import data run schedule The Upcycler Workbench now automatically runs the import data run on the correct schedule. It is no longer required to enable this schedule manually in IAM.    

We are very excited to announce version 2022.1 of the Thinkwise Platform. It is available for download in TCP now!Here, we would like to highlight two features: the full integration of the Thinkstore into the Software Factory and the redesigned deployment processes.For an overview of everything new, improved, and fixed in this release, please consult the release notes in the Thinkwise Docs.  Thinkstore fully integratedLet's start with the Thinkstore. Perhaps you have tried it already in the Community? It has been fully integrated into the Software Factory to improve its ease of use.What is the Thinkstore?The Thinkstore is already available in the Community. It contains a collection of scripts and samples to help you get the most out of the Thinkwise Platform.In the Community, solutions can only be downloaded and installed manually. To improve this, you can now access the Thinkstore in the Software Factory from the menu Enrichment > Thinkstore. Here, you can select, download, and install samples and models right from the Thinkwise IDE into your projects. You can install a solution multiple times under different project names and project versions.Thinkstore fully integrated into the Software Factory Redesigned deployment processesIn the previous release (2021.3), we have redesigned the Creation process. In this release, we have continued improving the entire Deployment process. In the Creation process, writing program objects to disk is available again in the Generate source code step. In the Execute source code step, we have improved the information on the user input that is sometimes required when the execution is aborted. The icons for the available tasks to continue the execution have also been improved. New in the Execute source code step is the possibility to determine the error handling behavior in API calls via Indicium for the tasks Connect to database and Execute source code. Finally, we have improved the error log when the source code is executed via the user interface or Indicium's API.As a follow-up to the redesigned Creation process, the Deployment processes Synchronization to IAM and Deployment package have also been redesigned. Both the processes now run through Indicium, so automation via the Indicium API is possible.In the task Synchronize to IAM, you no longer need to enter a host, database, or authentication. Instead, you only need to select a Target IAM (as set in menu Maintenance > IAM configurations). In the task Synchronize to disk (previously: Write to disk), you no longer need to enter a file location. A location field is displayed on the screen. You can easily navigate to this file or folder using the buttons next to it. In both tasks, the new Note field allows you to place a comment, like the reason for synchronizing. This comment is visible in the History tab's grid.Synchronization to IAM redesignedIn the Deployment package process, you no longer need to enter a file location. After a successful run, all deployment package files are written to the project folder. A field containing the exact location appears on the screen. You can easily navigate to this folder using the button next to it. The new Note field allows you to place a comment, like the reason for creating the deployment package. This comment is visible in the History tab's grid.Deployment package redesigned Other highlightsOf course, this release brings many more new features and changes. Some other highlights are:Expandable validation messages in the tree - Now, validations only show the first 25 messages. This benefits the performance and overview of the screen. When there are more than 25 messages, a node to expand the validation is added to the tree. Import and export projects for reuse - You can now share a project between different environments by exporting it. This is a fast and easy way to enrich your projects. A new logic concept: Change detection - This logic concept allows you to inform the user interfaces during certain events whether or not a subject has been changed and needs a refresh. Task to copy user and group preferences - In IAM, it is now possible to copy all preferences to selected users or user groups.   

Hello everyone!We’ve released the following platform improvements this week:SF and IAM 2020.2 and up20220128 - Azure engine edition update Installing Software Factory and Intelligent Application Manager databases on Azure Managed Instances will no longer cause errors regarding ALTER Database statements. Likewise, products built using the Software Factory will no longer cause this error on deployment when deploying the database on an Azure Managed Instance. SF 2021.320220128 - i_ui views performance optimizations This service update provides optimizations that improve the performance for 3 i_ui views: i_ui_col_form, i_ui_task_parmtr and i_ui_report_parmtr. When starting an end product created with the Thinkwise Platform, the model must be loaded. For the Universal GUI, this is done by using so-called i_ui views. These views load the data in the most efficient way, which is a challenge because the model and amount of data can differ enormously per customer. We always strive to offer a solution that works as well as possible for everyone. 20220128 - Execute source code improvements Some improvements have been made to inform the user about the status of the database connection.

January 28, 2022:Changed beta release to the full version: 2022.1.10 Hello everyone,In this sprint, we finished the FormList component in a basic form, and added some CSS styling classes for custom.css. Also, you can now execute a task on multiple rows in a grid in combination with a Popup for each row. And when importing rows, you can now download the rows that were not imported successfully.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress. Universal GUI version 2022.1.10Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation  and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2022.1.10 here  Contents of this releaseUniversal GUI version 2022.1.10 New FormList component Execute a task for multiple rows with a popup for each row CSS styling classes for custom.css Download failed rows Changed Hide actions bar buttons when there are no editable components on the screen Marker popup in the maps component contained too much padding Minor fixes and tasks What we will be working on next sprintNewFormList componentThe Universal GUI now supports the FormList component in a basic form. In a FormList, each record in a dataset is represented as a separate form. This form looks and feels like a default-editable autosave form. Using a FormList, you can create a dynamic form without the need to re-generate your Software Factory projects.This first, basic support is targeted at making questionnaires. Suppose a survey contains multiple questions with different types of answers. For example, a full name (string), a birth date (DateTime), and a Yes/No checkbox that indicates whether the end-user wants to receive commercial emails or not. But you could also think of a five-point scale that measures user satisfaction. Using a FormList, this survey would look like this:  Example of a FormListIn this example, a Layout control procedure in combination with an answer type field can be used to show the correct answer field for the related question. The corresponding stored procedure is then executed to determine the visibility of each control.Using a Group label control type in a Form or FormList component results by default in a bold (group) label. See the labels Full name, Birth date and Allow communication in the image above.The Universal GUI supports the following control types: Default, Multiline, Numeric, Currency, Date, DateTime, Time, Checkbox, and RadioButton.HTML, file, and lookup controls are not yet supported. The component and fields are always in edit mode. There can only be one form column. Multiple form columns are not supported yet. For adjacent fields, the width is evenly distributed over the available width, regardless of the settings in menu User Interface > Subjects -> tab Components -> tab Form. When grouping controls for a single record, the field in next group and field in next tab options are not supported. FormList is default editable and works around the subject editing mechanism. Without any other editable components, like form or grid, CRUD buttons are hidden on the action bar. FormList patches directly to the table just after changing a value. To keep the editing experience fast and smooth for now, no data is refreshed and field visibility has not been updated yet. The layouts are not re-fetched after a patch. The dataset is not re-fetched after a patch. As layout mode, only the navigation layout mode can be used.Execute a task for multiple rows with a popup for each rowIn the Universal GUI, you can now execute a task on multiple rows in a grid with a Popup for each row. With this general task setting enabled the GUI displays a popup for each row to give the user the opportunity to give input to the task execution.Currently, a popup will be displayed for all rows. In the Universal GUI, it is not yet possible to abort this flow.Until now, tasks with a Popup for each row could only be executed for a single row.CSS styling classes for custom.cssWhen using custom CSS to enhance theme settings, you can now specify style sheet rules that are specific for light or dark mode, and for comfortable or compact mode. You can use the following classes:.light{ } .dark{ } .comfortable{ } .compact{ }Download failed rowsWhen importing rows, you can now download failed rows using the DOWNLOAD FAILED ROWS button in the summary dialog. Example of a dialog with a 'Download Failed Rows' buttonChangedHide actions bar buttons when there are no editable components on the screenIf a screen does not contain any editable components, the action bar now no longer contains buttons for adding, editing and copying. These buttons are not necessary when viewing a cube or chart, for example.Tip: you may also be interested in hiding the toolbar .Marker popup in the maps component contained too much paddingIn the Maps component, the marker popup was not displayed correctly, it contained too much whitespace. This has been corrected.Minor fixes and tasksWhen the browser autofills the username/password dialog, the Login button would remain disabled until the user clicked somewhere on the page. This was unintended behavior. The Login button is now always available. If the user clicks on the button with an empty username, it will disable and focus the username field. In a tree component, icons were not displayed correctly in compact mode. This has been fixed. When a screen with detail tab pages with badges was opened, and the dataset took a while to load, a 400 network error would occur. This has been fixed. Badges showed a 0 (zero) when there were no rows or when a row was added. This was unintended behavior. Now, the badge will be hidden in these cases. In dark mode, the font color used for text on colored backgrounds was inconsistent. This has been fixed. The HIDE_TOOLBAR screen component property now works correctly regardless of its value. In a Preview component, when a search returned no results, the default text No preview available was aligned at the top left instead of the center. This has been corrected. After changing the password from the user preferences menu, or when changing an expired password after login, the Universal GUI browser tab was not immediately displayed in front. This has been corrected. When a screen contained both a form and a grid, the grid component could become editable, even if this was not configured in the Software Factory. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Non-edit mode filled style - The ability to have the filled style displayed in non-edit mode. Repeat offline tasks - All tasks that are flagged as offline will repeat. This behavior will be added as an option in the Software Factory in the future. Hide read only parameters in offline tasks - Parameters the user cannot fill in an offline situation will be hidden. Continue improving grid performance and make it less flickering. Continue automatic testing. 

Release notes Windows GUI and Web GUI (2022.1.10)Hello everyone,In this sprint, we solved some issues.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.1.10 here. Download Web GUI 2022.1.10 here.Minor fixes and tasks(Web GUI) On small monitors, e.g. a 14-inch display, HTML popup text editors were not fully displayed. This has been fixed. Now, HTML popup text editors have been changed to dynamically fill 50% of any screen. (Web GUI) When clicking a cell in a grid, the horizontal scroll bar moved. This has been fixed as it is not the intended behavior. (Web GUI) When previewing a report or exporting a report to PDF, this file was exported to the temp folder location of the local environment instead of the (intended) app_data folder of the Web GUI. This has been fixed.

Hello everyone,In this sprint, we have added a /refresh_model API endpoint. Furthermore, PDF and HTML files now open in a new browser tab. Finally, we added a temporary solution that allows you to write files to file storage configurations using the Write File connector process action.You can read more about Indicium's features in the Indicium user manual .We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.10 here . Download Indicium Basic release 2022.1.10 here . Table of contentsIndicium Universal New refresh_model endpoint Print previews from a report open in a new browser tab Extended file storage support using Write file Minor fixes and tasks  Indicium UniversalNew refresh_model endpointThe Refresh model functionality that can be accessed from the Developer ribbon in the Software Factory is now also available as an API endpoint in the Indicium Universal application tier.To reload (refresh) the model, send a POST request to one of these URLs:<web_app_root_url>/sf/<appl>/refresh_model <web_app_root_url>/iam/<appl>/refresh_modelPrint previews from a report open in a new browser tabWhen opening a print preview from a report, this preview now opens in a new browser tab instead of being presented as a download, unless the browser cannot open this file type.Extended file storage support using Write fileIn this release, we added a temporary solution that allows you to write files to file storage configurations using the Write File connector process action. This particular solution is temporary because we want to provide an easier and richer solution in a future version of the Thinkwise Platform, after which we will automatically upgrade this temporary solution to the new solution.To take advantage of this new temporary solution, perform the following steps: Create a process variable and let the process variable ID end with a double underscore __ followed by the ID of the intended file storage location. Note that this does not work for database storage locations, only for File System, FTP, Azure and AWS storage locations.  Example of a file storage process flow In the Write File connector process action, use this process variable for the File path input parameter. The value of the process variable must be the name of the file, as it will be written to the storage location. It can also be a relative path that ends with a file name. In that case, the relative path is created with the storage location as the base path, and the file is written there. Valid examples are:my_file.txtmy_sub_folder\another_sub_folder\my_file.txtThe rest of the Write File connector process action works as usual. The data provided in the File data input parameter is written to the storage location.Minor fixes and tasksIn the Indicium OData API, when you use the \$apply standard computation (e.g. $apply=compute(year(date_of_birth) as year)) within a chained transformation, all other columns from the corresponding entity were no longer selected. This has been fixed. Lookup columns were sometimes exported to Excel/CSV with a column header that used the translation of the lookup display column instead of the lookup column itself. For example, a project_id lookup column could have the column heading 'Name' instead of 'Project'. This has been fixed.

January 7, 2022:Changed beta release to the full version: 2021.3.15. Hotfixes: On a mobile device, when an inactive tab contains a form, this form was not activated when a new row was added. This has been fixed. In this example layout procedure, the manager_id field is hidden when not being edited, and it is made editable when editing or adding: In this case, the "Select" button in the lookup popup of the manager field remained disabled. This has been fixed.  Hello everyone, In this sprint, we added a visibility setting for the HTML editor popup button, and fixed some issues. Also, we started implementing the FormList component. We expect to finish this component as part of the next sprint.As always, we have made a demo for you: try it here . Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual  to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress. Universal GUI version 2021.3.15Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation  and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2021.3.15 here  Table of contentsUniversal GUI version 2021.3.15 New Visibility of HTML editor popup button Changed Clear error messages Grid-based export as default Minor fixes and tasks What we will be working on next sprint NewVisibility of HTML editor popup buttonFor an HTML field, the visibility of the lookup button next to this field can now be set. In the previous version, this lookup button was always displayed.To change the visibility:In the Software Factory, select Data > Domains. Select the appropriate domain with an HTML control. Set the Show action button attribute to one of the following values: Never: the lookup button is hidden. When editable: the lookup button is only displayed if the HTML field is editable. Always: the lookup button is always displayed. Show action button attribute ChangedClear error messagesSome error messages that may be displayed in the snackbar at the bottom of the screen have been changed, and now contain fewer technical details. For example:"Staged edit failed. Error: Action not allowed" => "Action not allowed""Continue failed. Error: Data no longer available" => "Data no longer available."Please note that if you report error messages in the snackbar, include a HAR file. This way, we know which network request caused the error message. Grid-based export as defaultWhen exporting the contents of a grid, all columns were exported, including the non-visible columns.Now, only the primary key columns and all visible columns in the grid are exported (in the order they are displayed).If the current screen does not contain a grid, the export falls back on the previous full export. Minor fixes and tasks When config.json had a wrong encoding or invalid JSON, the Universal GUI used to show just a white screen. Now, the (Universal) GUI shows the login page with an error, to help you solve this problem. Example: Login page with error message  In a grid, image icons were not correctly right-aligned and left-aligned. This has been fixed. In a Datetime control, the date and time parts are two separate fields. Procedures that act on a Datetime control, for example, to set a default value or to perform layout logic, were unnecessarily triggered. This happened when the user tabbed through these two fields, or focused on a field without changing the value. This has been fixed. These procedures are still called when navigating through months and years in a calendar control in a web browser. This is due to technical limitations of the native date picker controls that are used in most web browsers. We fixed a problem with a faulty timezone correction when the date was filled in by default on editing. Entering a search condition that contained a special character, for example, a single or double quote, resulted in an error. This has been fixed. Now, all special characters can be searched. In a grid, progress bars were not correctly vertically aligned. This has been fixed. When the model inspector  was used in the Universal GUI, default editable autosaved checkboxes were not functioning. When clicking such a checkbox, nothing would happen. This has been fixed by excluding such a grid column from the model inspector. All other scenarios will continue to work. Two problems have been solved for the auto-save functionality. Previously, in a parent-child relationship, when editing a child record in a grid, and then selecting another parent record, only the current child record was saved. The other parent record was not displayed. Also, sometimes an error occurred. Now, the current child record is saved and the selected parent record becomes available. When changing the value of a task or report parameter resulted in an error, the corresponding error message and its details were not displayed. Instead, an unexpected error occurred. This has been fixed.  What we will be working on next sprintThe next sprint we will be working on:Embed and complete the first version of the FormList. Provide the option to update existing rows when importing a .csv or Excel file. After importing, provide a feedback dialog on the import process, and provide the ability to download failed rows. On a screen that only contains for example a chart, the add, edit, and other navigation buttons should be hidden. In progress: several technical user stories to enhance grid performance. In progress: automatic testing. In progress: UX/UX design of the action bar as a screen component.

Hello everyone,In this sprint, we have changed the background coloring of the out-of-office hours in the Resource Scheduler, and we solved some issues.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.3.18 here. Download Web GUI 2021.3.18 here. Changed Resource Scheduler behavior and background color settingsIn the Resource Scheduler, out-of-office hours (8 pm - 6 am) are now disabled. The background color of the corresponding time cells will not be changed anymore. All background color settings can now be defined in the worktime table/view or via the default settings in the Software Factory (menu Projects > Full model > tab Extender properties). Minor fixes and tasks(Windows GUI) When the tsf_send_message procedure was triggered to display an error message, this message was displayed correctly, but also an unnecessary second error message (500 Internal Server Error) was displayed. This has been fixed. (Web GUI) In a lookup, values that contained special characters (e.g. a single quote used as an apostrophe) were not shown correctly in the Web GUI. This has been fixed.

Hello everyone,In this sprint, we have improved our support for OData's $expand query options. It is now possible to include 1:N references. We also improved the performance of the Application Connector.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.18 here. Download Indicium Basic release 2021.3.15 here. Table of contentsIndicium Universal Improved support for OData's $expand query options Improved performance of the Application Connector Minor fixes and tasks  Indicium Universal Improved support for OData's $expand query optionsOData's $expand query option allows you to include related entities in the response within a single request. We already supported this for 1:1 references, such as look-ups, to fetch the display value. Now, we also support this for 1:N references. This is especially interesting for retrieving the detail records for each parent record.To expand a detail within the context of a parent, the request should look like this:<indicium_base_url>/<meta>/<application>/<parent_entity>?$expand=detail_<ref_id>For example:https://server/indicium/iam/appl/sales_order?$expand=detail_ref_sales_order_sales_order_line Most of the regular OData query options, such as $select and $filter, can be applied to the expanded detail as well. They can be added as a semicolon-separated list between parentheses.For example:https://server/indicium/iam/appl/sales_order?$expand=detail_ref_sales_order_sales_order_line($select=sales_order_id,sales_order_line_id;$filter=sales_order_line_cost gt 10) Improved performance of the Application ConnectorThe performance of the Application Connector has been improved by loading only the relevant model information, instead of the entire application model. Minor fixes and tasksWe fixed that a user could not give consent to OpenID offline access. Because of this, Indicium could not hand out refresh tokens when consent was required. We fixed that ongoing process flows were aborted after a tsf_send_message (or raiserror) from a trigger or a stored procedure. We fixed an issue that caused the process flow API to be case-sensitive. With this fix, the casing of the request URL is no longer relevant. 

Hi everyone!On this last day of the year, we’ve released the following service update: IAM 2020.2, 2021.1, 2021.220211231 - Fix for copying user with user preferences When copying users with user preferences, some preferences could not be copied due to identity values being different after insertion, resulting in referential errors with details of preferences. This was already solved in IAM 2021.3, but we decided to also provide this as a service update for other supported IAM versions. Hope you all have a great New Year's Eve. Enjoy, stay safe, and see you all next year! Thinkwise Product Development team

Hello everyone!We’ve released the following hotfix this week:SF and IAM 2021.320211222 - Remove any schedules for subflows Being able to schedule subflows is not supported at the moment. Therefore, any existing schedules will now be removed when converting a process flow to a subflow.

Hello everyone,A hotfix for the issue described here has been made available in TCP with the version number 2021.3.17.This build of Indicium Universal is the 2021.3.16 release + the hotfix for this specific issue, it does not contain any other changes that we are working on in this sprint. Those changes will be released according to our normal schedule.The hotfix can be downloaded here.Our apologies for any inconvenience caused by this issue.

Hello everyone!We’ve released the following hotfixes this week:SF 2021.320211216 - Fix unit test system flow duplicate result parameters A select statement in the code may cause duplicate result parameter records. This situation led to an error in the unit test system flow without notice. The duplicate records will now be deleted and an assertion error message will be shown as the result of the unit test to prevent false positive unit tests runs.

December 17, 2021:Changed beta release to full version: 2021.3.14. Added fix: We fixed that process flows sometimes crashed on continue.Hello everyone,In this sprint, we have added, among other things, support for zoom levels in Maps, improved the look-up popups, and added a shortcut for opening a look-up from the grid. And you can now hide the Remember me option from the login screen.As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.We will keep you updated regularly about Universal's progress. Universal GUI version 2021.3.14Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal.Download the Universal GUI version 2021.3.14 here Contents of this releaseUniversal GUI version 2021.3.14 Changed The confirmation of tasks can now show the value of hidden task parameters Resetting the dataset will spin the refresh icon in the toolbar New Support for Zoom level in Maps Improved look-ups New setting to hide "Remember me" option from the login page Improved loading performance of model icons by caching them Minor fixes and tasks What we will be working on next sprint Changed The confirmation of tasks can now show the value of hidden task parametersAs of this release, confirmation messages can show the value of hidden task parameters since Indicium now handles the translation for the Universal GUI.This change makes this Universal GUI version only compatible with the latest Indicium version: 2021.3.16. Resetting the dataset will spin the refresh icon in the toolbarNow, after resetting the dataset, the Refresh icon will spin in the toolbar to indicate that the Universal GUI is processing the change. The dataset is reset when you apply a filter or prefilter or change the sorting. New Support for Zoom level in MapsThe Universal GUI now supports the initial Zoom Level for Maps in the Software Factory.At the moment, only a zoom level with a value between 2 and 19 is supported. A value higher than 19 (for example, 23) will be set to 19. A value lower than 2 (for example, 1) will be set to 2. Improved look-upsNow, you can use the Ctrl+Alt+P shortcut to open the look-up for the selected field in a grid in a non-editable subject. Note that this shortcut only works when the focus is on the grid component. Alternatively, you can use the "Show look-up" options from the toolbar.After opening, we have improved the look-up popup in cases where the requested record does not exist in the current data set when it is opened. The Universal GUI validates whether the record is available. If so, the set is filtered, without prefilters, to show it. If not, a snack bar message will inform you something else is selected: "The desired data cannot be found because of the active filters."Note: this is only available when you open a look-up popup from a non-editable editor. When editable, we expect that you open the popup to select something else.Related to this, a look-up will now activate a tab with a grid (or card list) if the parent is editable. This allows you to pick a different record. If the parent is not editable, it will activate a tab with a form to show more details about the current value.When the record is filtered out after adding/editing it inside the look-up popup, you will get a message with the question to open it in a new document to continue working on it: "The just saved data cannot be displayed on this screen because of active filters. Would you like to open it in the background?". New setting to hide "Remember me" option from the login pageYou can now configure the Universal GUI to hide the "Remember me" option from the login page by adding "loginRememberMeHidden": true, to the config.json. This option allows users to remain logged in for 14 days instead of 30 minutes. Remaining logged in is not always desired, for example, when tablets are shared between multiple users. Improved loading performance of model icons by caching themWe are now fetching icons from the i_ui_views of the meta model in a different way so the browser can cache them. This has resulted in slight performance improvements when, for example, logging in or opening a screen for the second time in the same browser instance. Minor fixes and tasksWe fixed that the Universal GUI would crash when opening a startup document that had never been opened in a process flow. When uploading a file that is not whitelisted as a file extension, for example, a .png file while only .jpg is whitelisted, the Universal GUI displayed "Stage patch failed. Error: bad_request". It also crashed sometimes. The crash has been fixed, and we now display "The used file extension, .png, is not allowed, only the following file extensions are allowed: '.jpg" instead of the technical error message above. We fixed that, after editing, a date field changed spontaneously due to the browser's time zone. Deleting records in details will no longer result in a progress popup that freezes the GUI. The previewer is now also refreshed after a document or subject is refreshed manually from the toolbar. A Refresh document process flow action in a detail no longer crashes the Universal GUI. The Maps component no longer crashes on invalid data. Previously, when the user was on a tab with a grid, the Universal GUI would wrongfully switch to a form tab. Now, if Edit is allowed in the grid, it will stay on the grid tab (menu User interface > Subjects > tab Settings). This makes more sense because the user already has an editable component available, so there is no need to switch to a Form tab. We fixed that process flows sometimes crashed on continue. What we will be working on next sprintThe next sprint we will be working on:Export using grid columns - Exports just the visible columns in the grid. If no grid is available, all columns will be exported. Task popup for each row - When multiple rows are selected, a task popup is available for each row. Form list - We will also work on a POC (proof of concept) for the form list. General maintenance.

Hello everyone,In this sprint, we have added support for double-clicking a task in screen types that contain a tree. In addition, you can now link a task to deleting an appointment in the Resource Scheduler. We have also solved a lot of issues.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.3.17 here. Download Web GUI 2021.3.17 here. New Double-click task support for tree screen types(Windows & Web GUI) As of this version, it is possible to add a double-click task to screen types that contain a tree. Resource Scheduler: new extended property for a task after deleting an appointment(Windows & Web GUI) In the Resource Scheduler, it was already possible to link tasks to actions, for example, double-clicking, moving, or resizing an appointment.You can now also link a task that has to be executed when an appointment is deleted with the Delete key, with the new extended property DeleteAppointmentTaskScheduler. For example:DeleteAppointmentTaskScheduler = "scheduler_delete_appointment". Minor fixes and tasks(Windows GUI) For images that were uploaded using the AWS file storage system, the file name was displayed instead of the image. This has been fixed. Now, image uploads via AWS appear as images in both the grid and the form. (Windows GUI) We have fixed a bug in the OAuth connector that resulted in a blank login screen. Also, we have added some extra debug logging for the OAuth connector. You can find these log messages in the Debug screen (Developer ribbon). (Windows GUI) Previously, when the value of a variable contained more than 43,500 characters, the Windows GUI showed a blank value in the Process flow monitor (Developer ribbon). Now, it shows a notification that the value is too long. You can copy the value to the clipboard by double-clicking on the text box. (Windows GUI) When a group header contained only one visible column, and this column was hidden using the User Preferences ribbon in your end-application (Subject configuration > Grid), the column was removed, but the group header remained, along with a dummy empty column underneath it. This has been fixed. Now, the entire group header is removed when no underlying columns are visible. (Windows GUI with Indicium (Basic)) We fixed a look-up with suggestion control that resulted in a query error. (Windows & Web GUI) If the name of an uploaded file already existed in the AWS file storage, the file was replaced. This has been fixed. Now, the name will be made unique automatically. (Windows & Web GUI) Now, the maximum value that can be set in the Software Factory domains will be enforced in the Windows and Web GUI. (Web GUI) In a task form, when a file upload field was filled by a default stored procedure, a form refresh would clear the field. This has been fixed. (Web GUI) Previously, when inserting the first record into a grid, the look-up dialog would not show when it was openend from the context menu or CTRL+L. This problem has been fixed. (Web GUI) Now, the Web GUI will ask the client to refresh the GUI to prevent that a timeout occurs. (Web GUI) We have fixed a bug in the DevExpress reports error logging that caused high CPU usage in Azure environments. This bug occurred when a report could not find any row in its source tables.

Hello everyone,In this sprint, we have added support for deep-linking in a process flow, so you can use values from variables to start a process flow. We have also updated the DevExpress Reporting library and changed the OpenID behavior when signing in and out.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.16 here. Contents of this releaseBreaking Invalid input parameters values will now stop the process flow in Indicium Universal Indicium Universal Deep link support for process flows Changes Update DevExpress Reports Changed OpenID behaviour Minor fixes and tasks  Breaking Invalid input parameters values will now stop the process flow in Indicium UniversalFrom now on, process flows will stop when the data types of an input parameter and the process variable do not match.When this happened in previous versions, Indicium would continue with a null value since it could not convert the value into the expected data type. This could result in unwanted or unexpected behavior.Now, when a process variable has datatype varchar(12), its default value is "Hello Indicium", and it's passed to an input parameter that expects an Int, it will result in an exception. Indicium Universal Deep link support for process flowsIf deep-linking is enabled in a process flow, you can now post process flow variables with their values to start the process flow with those values. Previously, these values had to be set with a task. This feature will be available as of IAM version 2022.1. Changes Update DevExpress ReportsIn this version of Indicium, the DevExpress Reporting library is updated to a newer version (21.1.6). Changed OpenID behaviourWe changed the behavior of Indicium when signing in and out.In the appsettings.json, we added a new property to OpenIDConnect named AlwaysPromptLogin. This is a boolean field, its value by default is false.When it is set to true and you sign in using that OpenID Provider, the login screen will always appear.If the specified OpenID is the only login option available and the value of AlwaysPromptLogin is false, Indicium will automatically log you out when pressing the button to go to the logout page.Also, if logging in with local accounts is disabled, then the logout button for local accounts will no longer be available. Minor fixes and tasksWe fixed the issue that the uploaded files of a staged resource were deleted when a commit failed. Now they will remain in the temp folder until the staged resource is committed or canceled. When staging a task or report in the context of a table, Indicium will now copy all parameter values that have been linked from the table context row. Previously, file columns linked in this way did not provide a download link for the file. This made it impossible for clients to show, for example, image previews since they did not receive a file from the link in the staged resource response.

Hello everyone!We’ve released the following hotfixes this week:SF 2021.320211202 - Ensure last agent check in only has one record When multiple instances of Indicium were present, it would in rare occasions occur that the table logging Indicium's last check-in contained multiple records. This would lead to an error in the creation screens, and has therefore been fixed. 20211130 - Function to get linked objects optimizations Due to some optimizations in the get_linked_objects function, it is now possible again to export your SF or IAM 2021.3 database from an Azure environment. IAM - All supported versions20211202 - i_ui views performance optimizations​​​​​ This service update provides optimizations that improve the performance for 3 i_ui views: i_ui_col_form, i_ui_task_parmtr and i_ui_report_parmtr. When starting an end product created with the Thinkwise Platform, the model must be loaded. For the Universal GUI, this is done by using so-called i_ui views. These views load the data in the most efficient way, which is a challenge because the model and amount of data can differ enormously per customer. We always strive to offer a solution that works as well as possible for everyone.

Hi everyone!We’ve released the following hotfixes this week:SF 2021.320211123 - Correction to sort Unit test data properly In rare occasions it would be possible that Unit test data was incorrectly sorted, causing the data to be inserted into the wrong column. This has been fixed. 20211124 - Corrections in creation process In some occasions the Execute source code log would show the incorrect message in the Log screen. This has been resolved and now all returned messages are shown. The Complete creation task would show an informational message about it being queued after a job the task created. This has been fixed and the task will only show the message once the first job is queued after another job. IAM 2021.320211123 - Validation tree refresh frequency In the 2021.3 version of the SF, jobs are no longer performed by a client (the GUI) but instead by Indicium. To keep track of the progress, the creation screens are periodically auto refreshed. This means that the data in the screen must be retrieved again.  This also applies to the validation screen. When a large amount of validation messages were unsolved, it could occur that not all data was retrieved before the next auto refresh. The screen could then not be used properly.  We now changed the frequency of the auto refresh in IAM. As a result, you will be kept informed less regularly about the progress during validation. However, this does solve any performance issues you might experience. Of course, this optimization for dealing with a large amount validation messages, does not change anything in our advice to always solve your validations. Hope you all enjoy your weekend!