Product Updates

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.

 Hello everyone,in this sprint, we added a new connector process action, as an addition to the OAuth connector that was recently released.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 GUIs progress.Download Windows GUI 2021.2.13 here. Download Web GUI 2021.2.13 here. NewA new connector process action (Windows GUI)A new connector process action has been added: the OAuth refresh token connector. You can use it to request a new access token for OAuth if the old one is expired.It can be used, for example, to leverage the Microsoft Graph API (Azure, Office 365, Microsoft 365) on behalf of a user instead of a service account. For this process action, input and output parameters are added.This connector process action is an addition to the OAuth connector that was recently released.New connector proces action: OAuth refresh tokenIt needs an OAuth server configuration to work:OAuth serverThis server can be configured in the menu Projects > Project overview > tab Project versions -> tab OAuth servers.OAuth server configurationIt is possible to override these settings for development/testing purposes in the runtime configuration (menu Deployment > Runtime configuration > tab OAuth servers).It is also possible to override the configuration settings in IAM (menu Authorization > Applications > tab OAuth server configurations). Minor fixes and tasksThe input field validation (for example, the input must be bigger than 0) in a default editable multi-page grid was not working as it was supposed to. This has been fixed.

Hello everyone,in this sprint, we've improved the login flow and added immediate redirection after an expired password. Also, we've added a new process action, and support for tasks with logic type 'None'. You can read all about it below!You can read the Indicium user manual to read about Indicium's features.We'll keep you updated regularly about Indicium's progress.June 9, 2021:New Indicium (Universal) has released: 2021.2.13 An issue regarding system flows was found in this release of Indicium Universal. This issue caused some system flows to fail when they should not have. This issue has been hotfixed in version 2021.2.13 of Indicium Universal.  Indicium Universal Breaking Improved Indicium's login flowIn this version of Indicium Universal, we have improved Indicium's login flow. We removed the  DefaultIdentityProvider setting and improved the user experience.When multiple options are available for logging in, e.g., with a local account against IAM, through IIS with integrated Windows authentication, or via external Identity Providers, Indicium will show the following page:Improved login flowThis page has a Remember my choice checkbox that sets a cookie for the user to skip this page the next time. This way, each user can make their own choice.If only one option is available, this page will not be shown at all, and the option will be handled as the default option. To this end, we have added the following configuration setting that allows you to disable the Sign in with local account option if, for instance, you only want to allow users to log in using an external Identity Provider like Azure AD:"LoginOptions": { "AllowLocalAccounts": false} New Platform version visible on Indicum main pageThe platform version is now also visible on Indicium's main page, underneath Indicium's version. This makes it easier to find the Intelligent Application Manager's (IAM) version. Platform version in Indicium's main page New process actionIt is now possible to renew access tokens with the new OAuth refresh connector. When you want to call external APIs from Indicium, it is sometimes necessary to refresh the access tokens. Since access tokens have a short lifetime, it can be useful to obtain a fresh one in the background. To use this new system flow action, select the OAuth refresh connector in a process action.An OAuth Server is required, and the action requires a mandatory input parameter Refresh token. This input parameter can, for example, be obtained by using the process action OAuth login connector. Note that you only need to refresh the access token when it is almost expired. It is not necessary to do this before every API call.The process action has several output parameters:Access token = New access token issued by the OAuth Server that can be used to call an API. Expires in = The lifetime of the new access token in seconds. Granted scopes = The scopes returned by the OAuth Server. Refresh token = Potentially a new refresh token when the provided OAuth Server only allows to refresh a token one time. Token type = The type of token. Most of the time it contains the value "bearer". Redirection after expired passwordIn the 2021.2 Thinkwise Platform release, we added a password expiration policy. To support this feature, Indicium will now automatically redirect a user to the Change password page once their password has expired and force a password change before access to the application is granted. Support for tasks with logic type 'None'In this version of Indicium Universal, we have added support for the Task logic type 'None' in the Software Factory, including support for output parameters. Previously, using this logic type would result in an error upon executing the task.Task logic type ‘None’ represents a dummy task that can be used in a process flow or to display a form. It can be found in the Software Factory, in the menu Processes > Task > tab Settings. Minor fixes and tasksWe have fixed an issue that occurred when using multi-row tasks in the Universal GUI. When the task execution couldn’t be started on of the selected records, for instance, due to a context procedure, the entire set would fail. Indicium will now ignore such errors, just like the Windows and Web GUIs do. We fixed an issue that caused an infinite login loop when a DefaultIdentityProvider was configured in the appsettings.json and logging in failed because the user could not be matched with a valid user in IAM. Tasks with a mandatory MultiSelectParameterId parameter would show an error. This has been fixed. Indicium treated all error messages coming from the database server as fatal errors, causing the Universal GUI to be unable to continue editing a record or entering task parameters and retrying. This included situations that were not fatal and could be resolved by the user, such as tsf_send_message and raiserror calls or constraint violations. As of this version, Indicium will treat all user-defined errors such as raiserror and all constraint violations (PK, FK, CHECK, UNIQUE, and NOT NULL) as non-fatal, allowing the user to correct their input and try again.  

Hello everyone!We’ve released the following hotfixes this week:SF 2021.2 & IAM 2021.220210602 - DNS suffix Azure when use current_server host name When using current_server as server name inside IAM and/or SF, the conversion did not add the needed suffix for SQL Azure (.database.windows.net). This has been fixed, so using current_server as server name no longer causes problems when connecting to SQL Azure databases. IAM 2021.220210603 - Rename task error when message returned Tenant Rename tasks in IAM returned an error when Tenant was included in the message as this is an integer. Because tenant is not needed in the message, it has been excluded from the message and the error no longer occurs.

Release notes Universal GUI 2021.2.12 2021, June 11Changed beta to full release (2021.2.12). Added two fixes: An asterisk was shown inside the grid editor if it was a required field. This was unintended since the asterisk is shown in the grid header already. This has been fixed. The percentage control was misaligned between edit and non-edit, causing it to move when you switched. This has been fixed.  Hello everyone,in this sprint, we've added another process action. Moreover, we extended the refresh and auto-refresh capabilities of the Universal GUI, and we improved the conditional layout in grids.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.12Like 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.12 hereThis is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Friday. New Support for 'Change prefilters' process actionIt's now possible to use the Change Prefilters process action in the Universal GUI. With this process action, you can enable or disable prefilters that aren't hidden or locked. When trying to change a locked or hidden prefilter, the process action will follow the red arrow. Support for refresh subjectPreviously, when changing rows after editing a row in an auto-saving default editable grid, the subject wouldn't refresh. This improved the performance of the default editable grids.Now, we've added support for refreshing the subject. This can be configured by setting the option Refresh after update to "Subject" or "Document". It is possible to disable refreshing after updating by setting Refresh after update to "None".This option is available in the menu User interface > Subjects > tab Default > tab Settings > tab Performance. Support for auto-refresh subjectIt's now possible to use auto-refresh in the Universal GUI. When configured, the Universal GUI will refresh the subject according to the chosen interval. Auto-refresh only has an effect when the subject is not in edit mode. When an auto-refresh subject has children, these will be refreshed as well at each auto-refresh cycle.The auto-refresh setting is available in the menu User interface > Subjects > tab Default > tab Settings or tab Variants > tab Settings. Changed Change in conditional layout in gridWe've changed the way conditional layouts are shown in the grid. Now they fill the entire cell, rather than just the value with a 5px padding. This means that empty cells with a conditional layout will also be entirely colored. Besides, the text color set in the conditional layout is applied correctly now. Improved error handling when trying to save or execute a taskPreviously, when editing or executing a task, the Universal GUI assumed an error would always be "a mandatory field is empty". Our Indicium team has improved the error handling, which allowed us to do the same. Rather than a generic validation error, we will now show the TSFMessage. This improvement leads to more specific errors. Minor fixes and tasksWe've fixed a bug where you couldn't activate a numeric or combo control by clicking on the placeholder. In a form, fields were not placed side-by-side when they were supposed to. This has been fixed. We fixed an issue with an optional lookup field in the filter form. The column was filtered with an invalid value, while no filter value was specified yet. The Refresh button was not animated when it was pressed manually. This has been fixed. We fixed some possible crashes after task executions from the menu or hidden task executions triggered by a process flow. The crashes occurred when the user input triggered validation messages. An asterisk was shown inside the grid editor if it was a required field. This was unintended since the asterisk is shown in the grid header already. This has been fixed. The percentage control was misaligned between edit and non-edit, causing it to move when you switched. This has been fixed.  What we'll be working on next sprintIn the next sprint, we'll be working on:Pagination - The ability to paginate through large recordsets. Quick filter - Quickly filter using the currently selected value in the grid. Cortex barcode scanner - Implement the Cortex barcode scanner to support more barcode formats. Additional license required. Process flow action: Restore prefilters - Follow-up action to restore the default prefilters. And of course, we'll solve some issues.Work in progress:Offline data Excel style filter Solving date/time control issues (eg, settings, display, default values) Pivot grid field list

Hello everyone!We’ve released the following hotfixes this week:SF 2021.220210517 - Sort order index columns Fixed an issue with the new calculations of sorted indexes in 2021.2 where the indexes that were created for sort orders only included the sorted columns but did not take into account the sort order of these columns. 20210517 - Reference on delete set null Fixed an issue with references in 2021.2 where the option "set null" for "on delete" was not implemented correctly. IAM 2021.220210518 - Get_gui_oauth_server rights Added rights for end users and for indicium to access get_gui_oauth_server. This feature is supported by the Windows GUI as of version 2021.2.12. SF and IAM 2021.2 20210519 - Indicium requests Changes to some interface views with Indicium to support development of new and/or improved features.

Hello everyone,here's another release from the Universal GUI team. We've added a first version of the form conditional layout, and a lot more.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.May 21, 2021:Updated beta version is available in TCP:  2021.2.11-b2May 26, 2021:Changed beta release to full version: 2021.2.11 Fixed bug in the beta where the mandatory asterisk would not be visible if the label was empty Fixed bug in the beta where date/time/datetime controls could not be activated properly if they were empty Fixed bug in the beta where fields would not be placed next to each other in non-edit mode Fixed bug in the where the contents of lookup fields would be empty in edit modeUniversal GUI version 2021.2.11Like with every blog, we've released a version to 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.11 hereNew Redirection after expired passwordIn the 2021.2 Thinkwise Platform release, we added a password expiration policy. To support this feature, Indicium will now automatically redirect a user to the Change password page once their password has expired, and force the password to be changed before access to the application is granted. Filled form fields and form conditional layoutIn this sprint, we've added a first version of the form conditional layout. To make this possible, two problems had to be solved first:With the current way form fields were styled it was not clear what exactly would get the background color. Besides, it was hard to discern where a form field starts and ends, especially when a field spans multiple rows and the colored bottom border falls outside of the form's visible part.To solve these issues, we’ve decided to implement filled form fields. These give more space to the content so you can apply color to the background. Applying a default color makes it easier to see where the form fields start and end.Since this is a major change, we've decided to make the color optional, so that's disabled by default. To enable it, you have to set useFormFieldBackgroundColor to true in the config.json. The spacing difference is still available to accommodate form conditional layouts.The conditional layout does not yet support the following controls:Radiobutton. Signature. Checkbox. HTML.This is what the filled form fields look like:Filled form fieldsThis is an example of the form conditional layout: Bold/italic conditional layout for the resource schedulerIt is now possible to use bold and italic conditional layouts in the resource scheduler. "Remember me" checkbox in the login pageIt's now possible to stay logged in for two weeks by enabling the *Remember me* checkbox in the login page:Remember me (for two weeks) Grid: double click task executionNow the Thinkwise Platform version 2021.2 has been released, task execution by double-clicking a grid record is available. In the Software Factory, use the checkbox Grid double click in a table task to enable this. This checkbox can be found in the menu User Interface > Subjects > tab Subjects > tab Links > tab Tasks. See the Thinkwise Platform 2021.2 release notes. The Universal GUI will choose the first enabled task to execute. This is the same as in the Web GUI, as explained in this blog. Lookup values in the filter formIn the filter form, lookup controls are now enabled. The dropdown field in the filter form will sum up all separate translations of the lookup column available in the current (pre)filtered data set. Dependent lookup columns could be filtered separately but will reduce each other's options, too, when combined. Directly submit a task while scanning barcodesThe barcode scanner control as a task parameter now contains some exclusive logic when it is the last control in the dialog. When the code is scanned and the control receives a Tab key, the task is submitted directly. This can be used to make barcode scanning very fast in a production environment using physical scanners. Changed Autosave is triggered in a parent subject if a child is refreshed manuallyAuto-save is now triggered in the parent subject if the child is refreshed manually. This way, the user can force the parent to refresh when the application is in auto-save mode.The auto-save mode can be set in the menu User interface > Subjects > tab Settings > tab General. Minor fixes and tasksIn a process flow, when zooming into a detail was followed by the actions Activate detail or Add/Change row, the last action always started in the first zoomed-in document when the flow was executed repeatedly. This has been fixed. It now selects the correct instance. When a detail tile was open, it wasn't possible to open the menu item from the sidebar. This has been fixed. The result is two open documents, one with the screen type Main and the other with the screen type Zoom. We've fixed that an error appeared after adding a record that fell outside the filtered GUI set. The error was: "Notify record nog found failed. Error: bad_request". The DateTime controls are now visually comparable to the other controls.  What we'll be working on next sprintThe next sprint we'll be working on:Auto-refresh a subject using the specified interval. Process flow actions: Activate form - Follow-up action to activate the form component. Activate grid - Follow-up action to activate the grid component. Set prefilters - Follow-up action to set prefilters. Close document - Follow-up action to close a previously opened document. Work in progress: Offline data. Quick Filter. Pagination. Pivot grid enhancements.

Hello everyone,in this sprint, we have added support for the OAuth 2.0 login connector, and we solved some issues.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.12 here. Download Web GUI 2021.2.12 here. New Support for OAuth 2.0 login connector (Windows GUI)We've added support for the process action OAuth login connector. This process action will be available as of the 2021.2 Thinkwise Platform release.While the process flow is running, a popup will show the site of the configured OAuth 2.0 provider where the user should log in. After the token is received or the popup is aborted, the process flow will continue to run. Minor fixes and tasks(Windows GUI/Web GUI) We've fixed the problem that the icons/logos set in IAM's global settings were no longer shown in the GUI when Indicium Basic is used. (Windows GUI/Web GUI) An error occurred when sign characters (+ # &) were used in a lookup or import, and the GUI was connected to Indicium Basic. This has been fixed.

Hello everyone,In this sprint, we added some new features, like standard computations and the possibility to preload models at startup, to reduce the response times. We also solved some issues.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.11 here. Download Indicium Basic release 2021.2.10 here (no new release). Indicium Universal New location 'Debug' for messagesIn the upcoming Thinkwise Platform release (version 2021.2) we have introduced a new Location value for messages, called 'Debug'. Messages using this location will not appear to the user, but Indicium will log them in the database event log.The message location indicates how messages are displayed. It is set in the menu User interface > Messages.The database event log can be accessed from the Universal GUI, the root page of Indicium, or by navigating directly to /account/ui/dbEventLog. It requires you to log in with a user that is a Development Mode administrator in IAM. Error message for a failed login with an external identity providerPreviously, when a user logged in through an external identity provider (e.g., Azure AD), there was no visible feedback that something went wrong if the credentials were correct, but the corresponding user in IAM was configured wrong. For example, a user was able to log into the authorized app through an Azure AD tenant, but:IAM does not contain a user entry corresponding to the email of the user that logged in. Or: IAM found a corresponding user, but this user is not configured with the External authentication type.The following generic login failed message is now shown to the user that tries to log in:Login failedSince these errors usually occur due to misconfigurations in IAM, Indicium logs more details about what went wrong for the user inside the error log. The error log can be downloaded by IAM administrators from Indicium's root page. Configuration settings to preload models at startupFor platform versions 2021.1 and higher, a configuration setting is added that allows you to specify application models that Indicium must try to preload from IAM during startup. This can help to reduce the response times for the users who are the first to access these applications after a cold start or restart.The feature can be configured under the Applications:Preload configuration key by specifying either the ID or alias of the applications that need to be preloaded.Notes:For applications containing system flows, this feature has little to no effect. The reason is that Indicium already implicitly loads applications containing system flows during startup, as it needs to know the model before it can execute the scheduled flows. Due to the way that Indicium handles loading models from Software Factory sources, this feature only works for models synced to IAM. If a new version of a preloaded model/application is synced to IAM, Indicium will not automatically preload the new version.Example:By adding the following section to the appsettings.json configuration file, Indicium will try to load the models for the specified applications during startup:{ "Applications": { "Preload": [ "itst", 23, "does-not-exist" ] }}This process is also logged to the default Indicium log:Preload log  Changes for Indicium Universal New system flow scheduler for 2021.2For the upcoming Thinkwise Platform release (version 2021.2), we have revised how the system flow schedules are communicated from IAM to Indicium, and how Indicium schedules them. These changes have improved the reliability of Indicium's scheduling to the point where it will never skip a single instance of a schedule. At the same time, the load on the database server caused by Indicium's polling is reduced to nearly zero. Minor fixes and tasks for Indicium Universal Process flows starting with the process action Execute Tab Task would not start when executed from an empty table or view. Instead, it would be interpreted as an Execute Task process action. This has been fixed. We fixed an issue where Indicium returned a 500 internal server error when using a DateTime output parameter in a task. The task was executed successfully, but the output parameter was not correctly converted to a corresponding OData type before writing the value to the response body. There was an issue with ‘grouping by’ two columns of the same navigation property. A request similar to the one below would result in an error, even though it's a correct request. This has been fixed. Now the groupby is performed correctly. /project_sub_project?$apply=groupby((transl_project_id/project_id, transl_project_id/project_name)) In very rare cases, Indicium's internal application model cache could become corrupt, causing requests to applications to throw errors until Indicium was recycled. The most notable example was when the application model was loaded or refreshed while synchronizing. As of this version, Indicium's application model cache is fully robust against these types of issues by automatically invalidating and refreshing incorrect application models.