Product Updates

Hello everyone,in this sprint, we improved the import functionality and updated the Thinkwise Reporting Service. Moreover, it is now possible to simulate a user. This can be a powerful tool for testing the access control or debug an issue with a specific user.You can read the Indicium user manual to read about Indicium's features.We'll keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.3.10 here. Download Indicium Basic release 2021.3.10 here. Indicium Universal Importing subjects with untranslated lookupsIt is now possible to import into a subject that contains untranslated lookups. Multiple results from a single query in the application connectorThe application connector can now retrieve multiple result sets from a single query. If multiple result sets are detected, the application connector will retrieve them and put them in a single JSON file. This can be used for a stored procedure that you want to use in the application connector, returning multiple result sets. User simulation in IndiciumAs of version 2021.3 of the Thinkwise Platform, which will be released very soon, it is possible to simulate a user if you are an administrator or a simulation administrator. User simulation can be a powerful tool for testing the access control or debug an issue with a specific user. It is also available in IAM.With the proper rights to simulate a user, you see a new link on the root page of Indicium: User simulation.New link: User simulationWhen you click the User simulation link, you navigate to the page where you select the user you want to simulate from the drop-down list. Then, press Simulate.The user simulationWhen you're ready with the simulation, press the Stop simulation button.It is visible on the root page of Indicium that you're impersonating a user:The user simulation in the root pageIt is also possible to simulate a user via the API by using the following call. It will return the user you're simulating. If you're not simulating, it will return the status code NoContent.GET account/api/usersimulationThis call will start the simulation for the selected user and return the status code Ok when the simulation succeeds. If not, you will receive a badRequest with the error message.PATCH account/api/usersimulationRequest body:{"simulated_user": "{username you want to simulate}"}To stop the user simulation, send the following command:DELETE account/api/usersimulation Disable "Forgot your password"From now on, it is possible to disable the Forget your password? link on the Indicium login page by adding the following JSON property to your appsettings.json."LoginOptions": { "AllowPasswordForget": false }When the AllowPasswordForget property is set to false, the Forget your password? link is disabled. Also, the Forget your password page or API cannot be used any longer. Thinkwise Reporting Service version 5We also released a new version of the Thinkwise Reporting Service, version 5. It contains some improvements and bugfixes:For Crystal Reports, the Thinkwise Reporting Service can now detect and use any 64-bit service pack (so, also service pack 26 and higher). For DevExpress Reports, we updated libraries to enable parameters for data sources using stored procedures. We also fixed that a parameter dialog appeared if not all parameters had received a value from rpt_get_parmtrs. Finally, DevExpress is now an accepted value (instead of TR) for report_type in rpt_get_reports. Two general settings are available now: PrinterNameCaseSensitive: sets whether printer names should be case sensitive. PrinterTrayCaseSensitive: sets whether printer tray names should be case sensitive. .NET Framework 4.8 is the new prerequisite for the Reporting Service. For more information on the new and changed prerequisites, configuration, logging, installation, and upgrading, see Reporting Service. Changes Minor fixes and tasksOn some occasions, an OpenIDConnect provider can throw an error. These errors are now correctly handled by Indicium, so a message is shown on the login page. It won't give away details as it might contain sensitive information. Logging in to an IAM user without a configured password would show an HTTP error instead of a message. This has been fixed. The maximum file size in a storage configuration for files over 2GB didn't work correctly. This has been fixed.  

 September 24, 2021:Changed beta release to full version: 2021.3.10: Fixed a bug where the checkbox would always be center aligned in the gridSeptember 29, 2021:Fixed a bug where Universal would crash when logging out or clearing the cache while working on HTTP. This has been released as 2021.3.10.2 and can be downloaded here.Hello everyone,In this sprint we implemented support for unavailable domain elements in combo boxes and added the release date to the About box. We also made some changes to existing features and functionality. But most of all, we solved a lot of minor issues.As always, we've 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.10Like with every blog, we've released a version so you can test the Universal GUI out for yourself. Don't 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. Furthermore, 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.10.2 here Breaking Default form field background color changedWe changed the default value of config.json setting useFormFieldBackgroundColor, which turns on background colors of editors. It was false, now it is true. When you're keeping your previous config.json file, there is no impact.See Form field background color. New Support for unavailable domain elements in combo boxesIn release 2021.2, the Software Factory introduced an option for marking domains as 'unavailable'. See Making a domain unavailable. Now, this setting also applies to the combo boxes in the Universal GUI, both textual and image variants.As a bonus, we fixed combo boxes in the editable grid to send value changes directly to Indicium after choosing them. In the form, it already worked this way. Release date in the About boxThe About box (under User Preferences) now also contains the date that the Universal GUI version was released.Universal GUI release date in the About box Changed Spin loader when deleting a recordPreviously, when deleting a record took a while, e.g., in a large data set, no indication was available that records were being deleted. Deleting a record twice resulted in an "action not allowed" error.Now, a loading panel will come up until the operation is carried out on the database, so the user will not continue working with the deleting record. Button visibility of task and report parameter popupsThe Universal GUI now listens to the layout application logic for the button visibility in task and report parameter popups. The confirm_button_type and cancel_button_type parameters can now be used to disable or hide one of the buttons. See Business logic. Minor fixes and tasks Fixes in process flows We fixed a crash that occurred when a process flow was running on a detail subject, and the user closed the document. The Open document process flow action, with use an existing document enabled, now skips the already opened (zoomed) detail documents of the same subject. The Go to row process actions (including next, previous, last, and first) previously did not work outside the page. Now, they work regardless of the page you are on. We fixed the Start task process action causing a crash at various events. Also, we fixed scenarios in which a crash could occur when the user started a task before the task definition was loaded. The scenario below would not behave correctly. After the Edit Row in the root subject, the Go to first row process action that was supposed to execute in the detail, was executed on the root subject. Additionally, the dataset refresh after the Edit row would come after the Go to first row, resulting in the Go to first row having no effect. Example scenario Small styling improvementsFixed the height of the top tab bar in opened documents to match the menu Search control again. Fixed the height of the application menu in comfortable mode. Aggregation values are aligned better now with the grid's headers and column data. Fixed the size of generated icons in action bar buttons. We solved a lot of little alignment issues with controls in both the grid and the form. Fixed the padding at the bottom of the toolbar in comfortable mode. Fixed the padding around images in the grid and centered them correctly.Known issue: the grid column values do not always have the desired padding yet. The solution for this is planned for a later date. Fixes for lookup controlsWith the latest version of Indicium, the lookup controls would stop working and give no result. This has been fixed. (Suggestion) lookups were not aligned properly. When no icon was shown, the text in the form would be over the label. Now, in grid edit mode, the whole control is shifted down and to the right. We fixed that lookup controls were being cleared by the default application logic. Previously, it was not possible to select another value afterward. Fixes for paginationDeleting the last record of, e.g., page 5, resulted in the Universal GUI going back to the first record of the first page. This has been fixed. Now, the Universal GUI will go to the last record of the previous page. Transitioning between pages will look more fluid now. OtherThe colored bitmap and vector images now get grayed out when the button (e.g., a task) is disabled. When a hidden HTML field was made read-only by the layout, it would not show data. This has been fixed. We fixed filter form combo boxes still displaying a value after clicking Clear all filters. (Quick) filters were not applied to the grid summary totals, which caused them to be bigger than the visible dataset. This has been fixed. We fixed strange behavior in the formatting of received data, where a textual value with a date was replaced with a date-only value. When a login options error occurred, the application would refresh and you would not be able to see the error. This has been fixed. We fixed a problem with the screen type breakpoint on mobile devices after opening a subject. We fixed the use of the Cortex scanner control on an offline executed task. What we will be working on next sprintThe next sprint we will be working on:Grid temporary auto-edit mode - When the Autosave property is enabled, the grid wil stay in autosave/edit mode until an explicit Save or Cancel. And again, we will solve issues and technical debt.

Hello everyone!We’ve released the following hotfix this week:IAM 2021.220210903 - OAuth server with multiple applications When multiple applications use the same model with an OAuth server configuration, the Windows and Web GUI's would fail to start. This has been resolved.

Hello everyone,in this sprint, we've built that your selection in a grid is retained after an auto-refresh. We also fixed some issues for auto-refresh.We're still working on making the Oauth 2.0 connectors in process flows available for the Web GUI. So, these aren't available yet in this release.You can read the GUI user manual to read about the Windows and Web GUI's features. We'll keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.2.18 here. Download Web GUI 2021.2.18 here. New features Row selection retained after auto-refresh (Windows GUI)Now, when a grid row or tree node is selected, it will stay selected after a refresh or auto-refresh action. This applies to both single and multi-row/node selections. Or course, when a row or node is no longer available after the refresh action, it won't be selected any longer. Minor fixes and tasksWe've fixed an issue where auto-refresh would keep refreshing when a user switched to a different document. We've also fixed an issue where auto-refresh continued after you entered edit mode. Now, auto-refresh will pause after you enter edit mode and only continue when you leave.

2021, September 3:Full release 2021.2.16 Fixed since the 2021.2.16 beta: Lookups without popup icon were not aligned properly. The value would be overlapping the label in the form. In grid edit mode the whole control was shifted down.Hello everyone,in this sprint, we've added support for working with tasks when you're offline. In addition, we added a 'compact' mode with less space since more data on the screen could make an application easier to scan, view, and compare. And in the Resource scheduler, you can now switch between two timescales: days and weeks.As always, we've 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'll keep you updated regularly about Universal's progress. Universal GUI version 2021.2.16Like with every blog, we've released a version so you can test the Universal GUI out for yourself. Don't forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, eg 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. Furthermore, 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.2.16 hereNew Compact modeAmple whitespace is necessary in an application. It improves, e.g., comprehension, legibility, and focus, and it guides the user through the interface. However, some applications are less suited for the default data density that is currently used (supplied by Material-UI). A denser UI could make data in your application easier to scan, view and compare. For this reason, we’ve implemented a compact mode.You can add a default for your users to the config.json, with:"spacingMode": "compact"The options for spacingMode are compact and comfortable. Depending on the goal of your application, you may want to use a more compact or a more comfortable UI. If you do not set this property explicitly, it will default to compact for desktop and comfortable for touch devices.The user can override this option in the User preferences if they prefer a different density:Settings for density in the User preferencesBesides adding a compact density mode, we made a few changes that impact the comfortable density mode.Reduced font size  We’ve reduced the base font size from 16px to 14px in both compact and comfortable modes. Since text takes up less space, components get a tad denser. We use the base font size as a measurement for the size of some components, not just the size of the text content. So, reducing the font size makes components denser by default, even in the comfortable mode.Reduced grid row height We’ve also reduced the grid rows to 44px (from 48px), which ensures that more data is visible on the screen in both modes.Spacing in compact mode Compact mode reduces the spacing in the Universal GUI by half (4px rather than 8px). This spacing comes back in the margins outside components and the entire screen, but also inside components. After reducing the spacing, we checked where the components in the Universal GUI needed tweaking. We tightened the components where necessary and reduced the density if a part became too dense and compromised legibility.This gif shows what has changed. It moves twice from the old situation to the new compact mode, and finally back to the comfortable mode: Offline tasks from the menuAvailable only from release 2021.2.Universal now supports offline tasks from the menu.Previously, the Universal GUI did not respond properly to a failing network connection. A lot of error messages would pop up, and parts of the screen remained empty. Also, planned offline operations were impossible, e.g., for a maintenance engineer working in a basement or a ship crew at sea.Now, while still online, the requests to start the GUI are cached and persisted as long as the definition doesn't change. And when the connection is lost, the user is requested to close their work to work in offline mode. Switching between online and offline mode will reset the GUI.Warning that you're about to go in offline modeAt the same time, the menu is disabled, and tasks flagged as Offline executable become available. An indicator next to the user menu shows the state of the connection. Status: offline.Status: online without changes.Status: online with pending changes.There are some restrictions when working in offline mode:The tasks cannot (yet) contain lookups/domain/file controls. The tasks will check for mandatory fields but make no other validations. The tasks will not execute application logic for parameter input. Indicium will do this later when you're online again. The task control procedures should accept all input and not relay errors since the user cannot fix these when syncing. We plan to add relay or export options later on.After a connection has been restored, Universal will not reconnect automatically but stay offline. So, the user needs to 'Reconnect'. This option becomes available by clicking on the offline indicator.ReconnectAt that moment, all executed tasks and their input will be synchronized, including canceled task actions. While syncing, this progress page is shown and afterward, the GUI comes up from scratch.Uploading the changes that have been made offlineThis feature sets a base for more offline logic to come. We have plans for opening subjects with pre-fetched datasets, manipulate data in them, and maybe even some basic offline logic to guide the user through the process. Zooming out to weeks in the Resource schedulerIn the Resource scheduler, you can now switch between two timescales. The scheduler will start on a time scale with a granularity of days. You can zoom out to weeks. The default view is days. Minor fixes and tasksWe fixed a crash that occurred when you scrolled and clicked in the list bar menu. We fixed three different causes for crashes that could occur in process flows. The following popup didn't show when pagination was turned on for a subject. This has been fixed.   What we'll be working on next sprintThe next sprint we'll be working on:Resolving issues and technical debt.

Hello everyone,This release is a little different from our normal releases. Due to some compatibility issues between the Universal GUI and Indicium Universal 2021.2.16 and 2021.2.17, we are rolling back some changes from these releases to ensure stability. If you are not experiencing any issues, then it is not necessary to replace your Indicium. However, if you are experiencing requests that produce 500 errors, then we recommend to install this version of Indicium to fix these problems.You can read the Indicium user manual to read about Indicium's features.We won't release a new version of Indicium Universal this sprint, to make sure that Indicium Universal and the Universal GUI are fully compatible again in the next release (September 17th). A new version of the Universal GUI will be released at the end of this sprint, but remain compatible with this version (2021.2.18) of Indicium Universal.Download Indicium Universal release 2021.2.18 here.This release of Indicium is the same as version 2021.2.15, plus the changes listed below.ChangesDefault values (including default expressions) are now applied to imported rows.Minor fixes and tasksFixed an issue that caused Indicium to return records in a different order despite the $orderby parameter being the same. This could occur when the values of the sorted columns were not unique within the table for view. This has been fixed by appending the primary key to the end of the order by clause to make the sorting deterministic.

Hello everyone,in this sprint we fixed a couple of issues in web and also changed Windows GUI behavior when connected to indicium.You can read the GUI user manual to read about the Windows and Web GUI's features. We'll keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.2.17 here Download Web GUI 2021.2.17 hereWindows GUI will not send unnecessary requests after a 401 Unauthorized responseThe Windows GUI will not send unnecessary requests anymore after a 401 Unauthorized response. A message will be represented after an unauthorized request to ask the client to login again.This scenario could've happened when an indicium was restarted or in some instances when a laptop user would put his laptop in sleeping mode.Other fixes:Web GUI: Domain with type uniqueidentifier now supported in lookup. Therefore it is now possible to select value from the drop down list on lookup with uniqueidentifier domain type. Web GUI: SVG icons in the Web GUI were displayed incorrectly. It seemed like the icons were disabled whereas they were enabled.

Hello everyone,This sprint, we have made some big changes to Indicium's query generation in order to better support OData's $apply function and we have worked towards improving the developer experience. Aside from that, we have also solved some issues.In addition to these features that are directly visible in Indicium, we have been working on enhancements for the Universal GUI and the next Thinkwise Platform release as these also contain an Indicium component.You can read the Indicium user manual to read about Indicium's features.We'll keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.2.16 here. Indicium Universal BREAKING. As of this release of Indicium Universal, it is mandatory for the Application Pool user to have read and write access to Indicium's Cache folder, including permissions to create it if it does not exist. Previously, Indicium would show and log an error message if the Cache folder could not be created. The absense of the Cache folder can cause a multitude of other issues, which have led us to make it so that Indicium no longer starts without it, to make it more clear what the actual issue is. Improved support of OData's $apply featureOver the last few weeks we have worked on enriching Indicium Universal's support of OData's $apply feature. It was already possible to do a single compute, groupby, aggregate, groupby+aggregate or filter transformation in the $apply clause, but as of this release it is possible to chain them indefinitely, with each transformation applying to the result set of the previous transformation.To illustrate this, the URL below selects all customers for which more than 5 projects were done in the year 2021./project?$apply=compute(year(project_date) as project_year) /filter(project_year eq 2021) /groupby((customer_id), aggregate(project_id with count as count)) /filter(count gt 5)&$select=customer_id  Configuration option to disable scheduled system flowsIn this release we have added an Agent:Enabled setting to the appsettings.json. The default value of this option is true.Setting this options to false will turn off all background operations that are managed by Indicium Universal and IAM. Currently, the only example of such a background operation is the scheduling of system flows.Example{ "Agent": { // Skip registering this Indicium instance as an agent on IAM. // Also disables adding all agent related services such as the scheduled system flow runner. "Enabled": false }} Disable Scheduled License Update ChecksIn this release we have added an Licensing:ScheduleUpdate setting to the appsettings.json. The default value of this option is true.Normally, Indicium Universal performs a license check on startup in order to obtain a new, updated license, if necessary. This check then recurs periodically in order to keep the license valid. When this option is set to false, Indicium will not perform this check.Example{ "Licensing": { // Only check and potentially update the current license once on startup and skip scheduling further checks from being run in the background. "ScheduleUpdate": false }} ChangesDefault values (including default expressions) are now applied to imported rows. Minor fixes and tasksVarious improvements have been made to Indicium's error logging. Some errors lacked the necessary information to troubleshoot them easily and in this release we have improved many of these error messages. We will continue to work on this in the future. Fixed an issue that caused Indicium to return records in a different order despite the $orderby parameter being the same. This could occur when the values of the sorted columns were not unique within the table for view. This has been fixed by appending the primary key to the end of the order by clause to make the sorting deterministic. Indicium would apply percent-encoding to file names, causing spaces to be returned as %20 for example. This has now been fixed.

2021, August 13:Full release 2021.2.15 No changes have been made since the betaHello everyone,in this sprint, we've finished the last process flow actions, implemented starting with no records until a filter has been set.As always, we've 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'll keep you updated regularly about Universal's progress. Universal GUI version 2021.2.15Like with every blog, we've released a version so you can test the Universal GUI out for yourself. Don't forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, eg 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. Furthermore, 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.2.15 hereNew Prevent document showing data before a filter has been setIn some use cases the document should not show any data until the user searches or sets a filter. Changing a prefilter does not trigger showing the records.If a subject has no filter component, the focus is set to the search field upon opening the document. If a subject has a filter component, the focus is set to the first field in the filter component.Records will be shown after the user enters a search of a filter. When clearing the filter/search, the records will be cleared.For more information, see Start empty with filter. Process actions Activate grid / Activate formWhen a process flow action 'Activate grid' or 'Activate form' is returned from the process flow, the UI will find and select the tab that has either the Form or the Grid component. Process action Default prefiltersIn Universal GUI version 2021.2.12, support for the "Change Prefilters" process action was added. Now, we have added support for the "Restore default prefilters" process action, which restores the prefilters to the same state as when the screen was opened. Open document process action opens document that is not in the menuUniversal already supported the 'Open document' process action, but when the document wasn't present in the users’ menu it would not do anything. This behaviour has now been implemented. Minor fixes and tasks1468S - Resource Scheduler group until column sort order descending not workingThe resource scheduler works on the group until field, but this also has sort order and Universal was ignoring this setting. This has now been fixed.2074S - Wrong badge is shownUnder some circumstances batches on nested subjects were showing the value of the parent or not showing a value at all. What we'll be working on next sprintThe next sprint we'll be working on:Compact mode Zooming out the timescale of the Resource Scheduler Finishing up offline tasks

Hello everyone!We’ve released the following hotfixes this week:SF 2021.220210806 - Updating theme font and color settings caused error When using the update font and color tasks in Themes, an error would occur causing the task to fail. This has been fixed.

Hello all,Advance notice for everyone still using SQL Server 2016. Mainstream support by Microsoft has ended last July. As per our lifecycle policy, official support for this version will be discontinued in a future release.As it stands, Thinkwise Platform 2022.1, to be released early next year, will no longer officially support SQL Server 2016 and will require SQL Server 2017 or higher.Note that the upcoming release of the Thinkwise Platform (version 2021.3) will still support SQL Server 2016.Impact on the platform databasesThe Software Factory (SF) and the Intelligent Application Manager (IAM) are planned to leverage T-SQL language features exclusive to SQL Server 2017 and up. The Deployment Center will prevent installation or upgrade of an SF or IAM to version 2022.1 when the SQL Server version is below 2017 or the database compatibility level is below 140.Impact on product databasesSQL Server product databases running on SQL Server 2016 do not have to be upgraded directly on release of Thinkwise Platform 2022.1.There are no concrete plans for the runtime components interacting with the product database to leverage new T-SQL language features in the forseeable future. However, runtime components with version number 2022.1.* and higher may start using SQL Server 2017 language features on a moment’s notice.Furthermore, Software Factory version 2022.1 may not be able to upgrade, deploy or test product databases using SQL Server 2016. To be able to continue development on the product, upgrading to SQL Server 2017+ will be required. The changes in SQL Server version support will be reflected in the lifecycle policy.

Hello everyone!We’ve released a service update for the 2021.2 IAM version. This service update provides optimizations that improve the performance on larger datasets for several get_gui views.When starting an end product created with the Thinkwise Platform, the model must be loaded. For the Windows and Web GUI, this is done by using so-called get_gui 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.

Hello everyone!We’ve released the following hotfixes this week:IAM and SF 2021.220210723 - Fix form_field_in_next_grp 2 Hotfix to solve issue where field_on_next_tab would always lead to field_in_next_grp.

Hello everyone,in this sprint we improved logging for DevExpress reports and fixed an issue.You can read the GUI user manual to read about the Windows and Web GUI's features. We'll keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.2.16 here. Download Web GUI 2021.2.16 here. New features All log file are now based on severity level (Web GUI)In the Web GUI, when extended properties WriteLogToFile and LogSeverity are used, log files will be created based on the severity level (info/warning/error). Minor fixes and tasksWindows GUI & Web GUI: The model cache sometimes didn't update properly, which caused the GUI to reload the model on every start instead of using the cached model. This issue has been fixed. Windows GUI: We fixed an issue regarding auto-refresh. It also refreshed the subject while the tab was inactive.

Hello everyone,As of this sprint, the logo and background image as set in IAM will also be visible in Indicium's login pages. We also added support for translating the OpenIDConnect "Consent" page. And as always, we solved some issues.In addition to these features that are directly visible in Indicium, we have been working on enhancements for the Universal GUI and the next Thinkwise Platform release as these also contain an Indicium component.You can read the Indicium user manual to read about Indicium's features.We'll keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.2.15 here. Download Indicium Basic release 2021.2.14 here. Indicium Universal Login page logo and backgroundThe logo and background image, set in IAM, will now be visible on all Indicium pages involved with logging in. You can set the logo and background image in the IAM menu Settings > Global settings.Example of a customized background and logoSupport for translating the OpenIDConnect Consent pageWe added support for translating the OpenIDConnect "Consent" page. It is possible to overwrite the default translations of the standard scopes (OpenID, profile, etc.), and the custom resources that you can add in the Intelligent Application Manager (IAM). Changes  Export to Excel for Date and Time controls (Universal GUI) - From now on, when exporting to an Excel file, the control format is respected. DATETIME_SHORT and TIME_SHORT will no longer show seconds, and a DATE control will no longer show the time. This is similar to how the Universal GUI shows the information of those control types. Styling improvements for landing page - Indicium's landing page is now styled to look like the other Indicium pages. Restyled Indicium landing page Minor fixes and tasksDatabase storage with a mandatory BLOB column showed an error when saving the record. This has been fixed. In previous versions, the errors for Process procedures weren't logged, which made it difficult to find out why a system flow didn't work as expected. This has been fixed.

2021, July 27:Full release 2021.2.14Added fixes: You can now enter a date/time without dividers You can now enter a date/time with 'wrong' dividers (/ rather than -) We now use the browser’s preferred language to determine date/time formatting Fixed a bug where the wrong badge would be shown Fixed alignment of grid editors Hello everyone,As announced in the previous release, we completely renewed the Date, DateTime, and Time editors in the form component. To offer you the best solution, we decided to build an entirely new control that is pretty much state-of-the-art.Furthermore, in this sprint, we've added more awesome features like support for the Maps component, a quick filter in the grid, and the possibility to use customized CSS. Also, we've added refresh options for tasks and records and support for yet another process action. And developers in the Software Factory can now use the new Model inspector for a better overview of the tables, columns, and fields they are working with.As always, we've 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'll keep you updated regularly about Universal's progress. Universal GUI version 2021.2.14 Like with every blog, we've released a version so you can test the Universal GUI out for yourself. Don't forget the documentation and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, eg 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 the appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Furthermore, 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.2.14 hereThe deployment package contains a lot more files than usual. This won't affect the functioning of the Universal GUI, only deploying may take longer. We aim to have this optimized in the next release. New Customized CSSIt's now possible to use custom CSS in the Universal GUI. A custom.sample.css file is included in every Universal GUI download. For each Universal GUI installation, you need to rename this file once to custom.css even if you don't use the custom styles. Renaming ensures that custom styles aren't overwritten when updating the Universal GUI. If you do not rename this file, you'll see a 404 error in the browser console.We'll release a separate blog post for detailing this feature with examples. Refresh options for tasks and recordsThe Universal GUI now supports refresh options after executing a task, and saving or deleting a record.The refresh options for a task are available in the menu Processes > Tasks > tab Default/Variants > tab Table tasks > tab Form > tab Table task. The refresh options for a record are available in the menu User interface > Subjects > tab Default > tab Settings > tab Performance.Refreshing 'Row' is not fully supported yet, this option refreshes the entire subject. Process action: Close DocumentWe now support the Close document process action. In a process flow, an open document can be closed with this process action. You can use the Document input parameter to decide which document gets closed.In addition to this process action is the Document input parameter now also supported for other document-related process actions. Grid quick filterWe've added a Quick filter to the overflow menu. When you click a cell now, you can easily filter on a specific value in the grid. To turn off the filter, select the same cell in the grid and press the Quick filter button a second time. You can use the Clear all filters button to quickly clear your current filters.Both filters are combined with the filters set in the filter form and the Change filter process action.If the quick filter is disabled, this can be caused by any of the following reasons:You didn't select a cell. You are currently editing a record. The selected control is not supported. Unsupported controls are: Columns with data type 'Binary'. Columns with these domain Control types (as set in the menu Data > Domains > tab Form > field Control): Date, DateTime, Time, Label, Group header label, Group header icon, HTML, RTF, SQLeditor, Multiline, Image link, Image upload, Image BLOB, File, File upload, Signature, Video link. If the Clear all filters button is disabled, you currently have no filters set.Quick filter in the overflow menu Renewed date and time editorsAs announced in the previous release, we completely renewed Date, DateTime, and Time editors in the form component. Earlier, we had some inconsistenties between the values in other components, like the grid and card list. To offer you the best solution, we decided to build an entirely new control that is pretty much state-of-the-art.It has complete native browser editor support and will choose the date/time format based on the preferred language as configured in the browser.As a result, the date and time-related controls are now consistent in their displayed values. Besides, they can be cleared all at once. It's also possibile to clear the controls in iOS.A change is, that the time controls are no longer filled with a default value, like 12:00:00. Instead, it is left empty, as it should be.In addition, we've added support for the controls DATETIME_SHORT and TIME_SHORT. These can be used in domains (menu Data > Domains > tab Form > field Control). The controls show a DateTime or Time without seconds. For example, 16:33 instead of 16:33:33.New controls for DATETIME_SHORT and TIME_SHORTFinally, date and time editors are now available in the editable grid. They work the same as in the form.Known issues in the form or grid:In iOS, it's not possible to select seconds in the time picker. In Android, seconds are only available when filled with the time picker. When edited, they change to .00 and will be ignored (so, they disappear). Android, Edge: the time header/label remains orange in edit-mode, even when the focus is in another field. Firefox for desktop doesn't support the time dialog. Firefox for mobile does. Tabbing in the date section of the DateTime control in the editable grid sets the focus to the next column rather than the time part. Model inspector for software developersIt is now possible for Software Factory developers to inspect the model using ALT+F1 in the Universal GUI. To use this feature, you need to add to the config.json: "debugMode": true,When you start the Universal GUI after this setting has been added, the Model inspector screen will open automatically at the bottom right. When no screen is opened, and no column or screen is focused, the Model inspector screen is empty, like this.Empty model inspectorWhen focusing on a column, it shows the following information:Model inspector with dataThe Model inspector can be helpful if you need to know which column, table, and variant you're currently looking at. It can be closed by clicking on the cross and be opened again by pressing ALT+F1. You can move the Model inspector by clicking and dragging it:Column, table, and variant in the Model inspector Maps component supportedIn the Software Factory, a Maps component can be created by the Model Extender. This component can now also be used by the Universal GUI. It supports multiple tile-based layers and markers, polylines, polygraphs, and circles.Limitations are:Tile layers can only be configured using x,y,z URLs. Library scripts are no longer supported. Custom marker icons and overlays are not yet supported. Selecting a marker in the map doesn't select the corresponding row in, for example, the grid. The opposite is possible, though: selecting a row does select the corresponding marker on the map.To use Maps in the Universal GUI, you first need to install hotfix 20210715 - Maps i_ui views for the platform.Later this year, in the next platform release, Maps will be available as a full component instead of a Model Extender component. This upgrade is also supported by the Universal GUI.An example of the Maps componentAnother example of the Maps component​​​​​​ Changed Updated submit button translationInfo messages are triggered after, e.g., submitting a task. Previously, the Submit button for Info messages contained the "Cancel" translation. Now, we've changed the translation to "OK". For users, this is a more logical response to an Info message. Badge updated after a task has finished runningBadges elsewhere in the GUI but belonging to the same subject will update instantly now after the related subject is updated by a task, edit or delete action. Thus, badges for open documents and menu items will be updated instantly. Minor fixes and tasks Executing a table task will now also start a process flow if the subject is empty. Read-only lookup values disappeared when adding a new record. This has been fixed.We've also fixed several issues in the form:Fields placed side-by-side did not work correctly: The new platform version 2021.2 is hotfixed to support side-by-side fields in the Universal GUI. After the hotfix, the checkbox and radio button controls ignored the Software Factory's configuration. This is fixed now. The labels of text fields that are placed side-by-side, received extra padding to the left, which misaligned them with the rest of the control. This is fixed now.  What we'll be working on next sprint The next sprint we'll be working on:Offline task execution - execute a task while being offline (task input can be synced after re-connect). With this, we hope to finish the entire Offline task execution feature. Start empty without filter - Allows for the subject to be empty until the user enters a search filter. Process flow actions: Activate form - Follow-up action to activate the form component. Activate grid - Follow-up action to activate the grid component. Open a document not visible in the menu. Restore filters. Default prefilters. And of course, we'll solve some issues.

Hello everyone!We’ve released the following hotfixes this week:IAM 2019.2 and up20210715 - Set GUI cache task datetime2 precision datediff check too precise A change was made in the GUI to make use of the datetime2 data type. This impacts the check that is done in the set GUI cache task. The date difference check in this task is too precise and needs to be changed to accommodate for the change.

Hello everyone!We’ve released the following hotfixes this week: SF 2021.220210705 - Import base data for default themes base project In a previous hotfix the base data import procedure for default themes had been altered but was not executed to ensure the base data was corrected. This hotfix will execute the procedure to update the base data.

Hello everyone!We’ve released the following hotfixes this week: SF 2021.220210629 - Gradient color columns incorrectly excluded from default themes base project Fixed an issue where gradient columns were incorrectly excluded when importing default themes. SF 2021.2 and IAM 2021.220210702 - Fix form_field_in_next_grp Fixed an issue for Universal where fields could incorrectly end up in the next group.  

Hello everyone,in this sprint we solved some issues for the scheduler and for two-factor authentication.You can read the GUI user manual to read about the Windows and Web GUI's features. We'll keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2021.2.15 here. Download Web GUI 2021.2.15 here. Minor fixes and tasks Two factor authentication: invalid 'code sent' message (Web GUI)A user could force a 'verificationcode send' message when they repeatedly tried to log in after already receiving an error message. However, the Web GUI did not actually send a verification code.This is been fixed. Now, the Web GUI will repeat the original error message and never show the 'verificationcode send' message. Scheduler (Windows GUI & Web GUI)Some minor fixes for the scheduler have been made:The active menu incorrectly changed to the list bar menu when the scheduler was opened in a floating document. Now, it keeps the opened tiles menu as it is. Resizing an appointment in the Web GUI no longer causes an unhandled exception. The header color of inactive scales no longer uses the grid header font settings. The date picker no longer crashes in the Web GUI when navigating to dates.

Hello everyone!We’ve released the following hotfixes this week: SF 2019.2 and up20210622 - Start merge session missed specific conflicts During Merging, the Software factory is searching for conflicts and marking them for the developer to resolve. When the SF was looking for indirect conflicts, in rare situations it would look in the trunk project instead of the branch project and therefore not find any conflicts. This has now been fixed. SF 2021.2 20210621 - Fix process variable tasks A reference was missing between process variable and process action output parameters. This resulted in corrupted data when using the rename or delete task for variables. This hotfix will delete the corrupted situations and fix the tasks. 20210623 - Sequences without cache resulted in cache 0 This hotfix will ensure Sequences can be created without cache.

Hello everyone,In this sprint, we've added standard computations and the possibility to change log file names. We also made a minor change to the system flow's end date.You can read the Indicium user manual to read about Indicium's features.We'll keep you updated regularly about Indicium's progress.Download Indicium Universal release 2021.2.14 here. Download Indicium Basic release 2021.2.14 here. Indicium Universal Edit logfile name and levelCommunity ideaIt is now possible to edit the log file name and the path. This can be useful if you are running multiple instances of Indicium next to each other or if you don't like the current name.To change a log file name, add the PathFormat to the Logging:ErrorLog segment in Indicium's appsettings.json:{ "Logging": { "ErrorLog": { "PathFormat": "YourOwnName-{Date}.txt", "LogLevel": { "Default": "Error", } } }}Replace the content of FileName with a name of your own choosing (YourOwnName). If no {Date} is specified, Indicium will add it. If file extension .txt is not specified, Indicium will add it.We also introduced the possibility to edit the minimal log level. The default log level is 'Error'. This feature can be useful if you need more information.The log level of other logging namespaces can be overridden by adding a key and value to the Logging:ErrorLog:LogLevel section. Some keys cannot be modified and will always be set to level 'Information'.{ "Logging": { "ErrorLog": { "LogLevel": { // Log Information level messages to the error log. "Default": "Information", // Log Debug level messages if the namespace of the logger starts with 'Microsoft'. "Microsoft": "Debug" } } }} DB2 iSeries data providerIt turned out that, compared to the old iSeries driver, the new DB2 .NET Core driver has compatibility issues with certain column types. These column types are:XML DBCLOB.Both these column types throw errors about not being able to perform the required CCSID conversion.While we still recommend using the newer driver over the iSeries driver due to vast performance improvements, for customers encountering this issue, we are introducing a way to run the iSeries driver using the plugin system that certain report types also utilize.Please note that since this means data now needs to travel between process boundaries from the plugin to Indicium, this method might degrade performance in some situations compared to Indicium versions that previously used this driver directly. The most noticeable situations are:Selecting large data sets. Downloading file data stored in a database storage column.To switch to the old iSeries driver, set the DataProviders:DB2:Mode configuration setting to iSeries. The number of plugin workers spawned can be modified using the DataProviders:DB2:WorkerCount setting. The default number is 3.For example, using appsettings.json:{ "DataProviders": { "DB2": { // Switch to using the old iSeries driver. "Mode": "iSeries", // Only spawn one plugin worker process instead of 3. "WorkerCount": 1 } }} Getting the number of rows without dataWith this release it is possible to do a $top=0&$count=true OData query. This makes it possible to get the number of records in a table without getting actual data. Application id and alias in the session contextCommunity ideaThe application ID and application alias (available from IAM version 2021.1 or higher) are now available in the session context. If you want to know the application alias or application ID in the database, you can use the following statements:To retrieve the application ID:select SESSION_CONTEXT(N'tsf_appl_id') To retrieve the application alias (available from IAM 2021.1 or higher):select SESSION_CONTEXT(N'tsf_appl_alias')This will return the application ID or application alias that was called. Standard computationsStandard computations are a great way to extract data from a column without the need to store them in a different column with a default expression.For example, if the computation Year is called, the computation will return the year of the supplied dates. Or, if you want to get a part of a column value, you can use Substring to retrieve it.The following computations are added:Computation Input Output Example Date Date DateTime Date $apply=Compute(Date(columnname) as Alias)) Time Time DateTime Time $apply=Compute(Time(columnname) as Alias)) Isoweek Date DateTime Int $apply=Compute(Isoweek(columnname) as Alias)) Weekday Date DateTime Int $apply=Compute(Weekday(columnname) as Alias)) Year Date DateTime Int $apply=Compute(Year(columnname) as Alias)) Month Date DateTime Int $apply=Compute(Month(columnname) as Alias)) Day Date DateTime Int $apply=Compute(Day(columnname) as Alias)) Hour Time DateTime Int $apply=Compute(Hour(columnname) as Alias)) Minute Time DateTime Int $apply=Compute(Minute(columnname) as Alias)) Second Time DateTime Int $apply=Compute(Second(columnname) as Alias)) Ceiling Int Numeric Decimal Int $apply=Compute(Ceiling(columnname) as Alias)) Substring Varchar Nvarchar Char Nchar Varchar $apply=Compute(Substring(columnname, Startindex, Length) as Alias)) Concat Varchar Nvarchar Char Nchar Varchar $apply=Compute(Concat(FirstColumn, SecondColumn) as Alias))  ChangedThe end date of a system flow is now always filled in, regardless of whether the flow failed or succeeded. This way, the freed-up slot is available for a new instance of the system flow. The log is available in IAM, in the menu Analysis > Scheduled system flows > tab Schedule log. 

2021, July 2:Full release 2021.2.13 Added fix: New translation for an Info message’s Submit button. Hello everyone,in this sprint, we've added pagination for grid and cardlist components. We've also added support for the Cortex barcode scanner, an alternative to the regular barcode scanner and free to use with the Universal GUI. On top of that, we've changed some small functionality, and of course, we solved some issues.As always, we've 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'll keep you updated regularly about Universal's progress. Universal GUI version 2021.2.13Like with every blog, we've released a version so you can test the Universal GUI yourself. Don't forget the documentation and keep the following in mind:A modern browser is required to access the Universal GUI, eg 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 the appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Furthermore, 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.2.13 here New Pagination for grid and cardlist componentsWe've implemented pagination to avoid the use of the top-statement on a subject. The top-statement could suggest that, for example, 100 records are all available data in a table, when in fact, there is more.The paging mechanism can be enabled by entering the number of rows on a page in the field Page size. The default is set per project version, in the menu Projects > Project overview > tab Project versions > tab Form. The default is overridden by the Page size field in the subject, in the menu User interface > Subjects > tab Default > tab Settings. 0 or -1 disable paging for the specific subject. Paging is also disabled while editing the subject/document.The page navigation is shown at the bottom of multi-record components, like the grid and the card list. The active record always remains on the active page, so it navigates with you between pages.For now, in detail subjects the GUI may show to many pages. Our Indicium team will fix this as part of the 2021.2.14 release.Pages in the Universal GUIWhen using pagination, keep in mind that the Go to row process flow actions can only navigate to a row within the current page. Later on, we will improve these actions, to make jumping to the next, previous, or a specific page possible. Support for licensed Cortex barcode scannerWe've added support for the Cortex barcode scanner. This is a more powerful alternative to the default barcode scanner for the Universal GUI. To use the Cortex barcode scanner, you need a license from the manufacturer. For more information, see https://codecorp.com/products/web-sdk.Note: When using Google Chrome on iOS, both the regular and Cortex barcode scanners only work on iOS 14.3 and higher due to vendor limitations.To use Cortex in the Universal GUI, configure CORTEX_DECODER as the domain control (menu Data > Domains). Then, in the Universal GUIs configuration file config.json, add the license like this:“cortexLicense": "your-license-key-here”To improve the scan performance, you can configure only the symbologies you need:"cortexEnabledSymbologies": ["Code128", "EAN8", "EAN13", "UPCA"]By default, Cortex scans the following symbologies: Aztec  UPCA  UPCE PDF417  Interleaved2of5 Code93  Code128  Code39 QR  EAN8 EAN13  DataMatrix  DotCode GS1Databar14   Cortex supports a lot more symbologies, though. This is the full list: AustraliaPost MSIPlessey Code128 Plessey EAN8 CanadaPost MicroPDF417 Code49 Straight2of5 GridMatrix Code11 Pharmacode DataMatrix UPCA IATA2of5 Code39 RoyalMail EAN13 USPSIntelligent KoreaPost CompositeCode Trioptic GoCode BC412 Maxicode DutchPost UPU HongKong2of5 CodablockF PDF417 GS1Databar14 USPSPostnet JapanPost Code32 QR HanXinCode Aztec Matrix2of5 Code93 Telepen Interleaved2of5 Codabar NEC2of5 DotCode UPCE USPSPlanet          Renewed date and time editorsWork in progressWe're still working hard on solving some issues with the Date, DateTime, and Time editors in the form component. The same value disappeared in other components, like the grid and card list. To offer you the best solution, we decided to build an entirely new control that is becoming pretty much state-of-the-art.It has complete native browser editor support and will choose the date/time format based on a combination of the browser language and the Windows OS regional settings. Which one is leading depends on your OS and browser.Since we're still testing the new control, it's not yet available in this release. It will be available in an extra release. Changed Improved color schemeIn form controls with conditional layouts, we improved the readability. When choosing a dark color in light mode, or a light color in dark mode, the labels and icons became unreadable. From now on, the UI will always select a contrast color.This is not yet available for the hovering colors (following soon). It is a known issue that the date and time icons do not work correctly yet. At the moment, we're overhauling the Date/Time/DateTime controls. We'll fix the issue after the overhaul. Minor changesA button or link in an HTML file, shown in the preview component, now opens its target in a new window. Items in the Universal GUI are no longer translated by the browser. Since the Thinkwise Platform has its own translation tool, this prevents unwanted and wrong translations. To improve performance, we stopped refreshing detail subjects that are unrelated to their parent (no reference columns are part of the reference between both tables). The ShowMessage process action now shows a default OK button if none is configured. Previously no button was shown. Minor fixes and tasksWhen navigating away from an unchanged editable row with Autosave activated, it would not end the edit mode. This has been fixed. We fixed that messages were hidden behind dialogs (tasks, reports, lookups, progress). Cursor_to_col_id didn't work on opening a task parameter dialog. It always navigated to the first control instead of the selected control. That's fixed now. When you performed an Activate detail process action, the process flow continued in that detail, even though you added a table to a process step to indicate where the action should be performed. We fixed that the process flow erroneously continued in the detail instead of in the parent table. We fixed a problem where filtering with double spaces resulted in a bad_request. A task variant not visible in the menu wasn't found in a process flow, causing a "Cannot find transl of undefined" error. The task/report parameter input validation crashed after the dialog was committed for the second time. E.g., because a mandatory parameter wasn't filled in. This caused a "Cannot find askConfirmation of undefined" error. "500" errors are handled correctly now. The task/report dialog will close, and a subject will leave edit mode. Also, a running process flow will continue executing the red arrow. Previously, the Submit button for Info messages contained the "Cancel" translation. Info messages are triggered after, e.g., submitting a task. Now, we've changed the translation to "OK". For users, this is a more logical response to an Info message.  What we'll be working on next sprintThe next sprint we'll be working on:Quick filter - Filter quickly using the currently selected value in the grid. Maps - Basic maps component to visualize geographical locations. Pivot grid enhancements: Collapse/expand rows (for all aggregation types). Nested series (columns). Grid date(time) editor - Editable datetime type editors. Process flow actions: Restore prefilters - Follow-up action to restore the default prefilters. Close document - Follow-up action to close a previously opened document. And of course, we'll solve some issues.Work in progress:Offline task execution.

Hello everyone!We’ve released the following hotfixes this week:IAM 2020.2 and up20210615 - Start-up performance multi-appl The start-up performance for all UI's and Indicium has been improved for scenario's where multiple applications have been configured for the same project version in IAM.

Hello everyone!We’ve released the following hotfix today:SF 2021.220210614 - IAM sync checked for incorrect version The previous hotfix "20210602 - DNS suffix Azure when use current_server host name” was using an incorrect version inside the procedures. This new hotfix makes sure the correct version number is used.