Product Updates

Hello everyone, In this sprint, we added, among other things, a Cancel button to the login pages. In addition, we built support for password changes from RDBMS users. We also fixed a rare issue that might possibly be breaking. You can read the Indicium user manual to read about Indicium's features. We will keep you updated regularly about Indicium's progress. Download Indicium Universal release 2021.3.15 here. Download Indicium Basic release 2021.3.15 here. Contents of this release Breaking Indicium Universal: fixed dependent lookups being cleared erroneously in rare situations Indicium Universal Change password from RDBMS users SQL print statements available in log Login pages have an extra button for cancel Minor fixes and tasks Indicium Basic Minor fixes and tasks Breaking Indicium Universal: fixed dependent lookups being cleared erroneously in rare situations In this release, we have addressed an issue that caused lookups filtered by expression columns to become empty in certain situations when they should not have. In particular, this issue would occur if the expression value changed and the dependent lookup got a new, valid value in the default procedure. Indicium Universal would not respect the value set in the default procedure and clear the dependent lookup. This scenario is quite rare, and the changes that we have made to address it are fairly subtle, but they are technically breaking changes, so please be aware of this. Below you will find a description of the old behavior versus the new situation. Old behavior: Apply default logic. Validate all editable lookups that were set in the default procedure. Validate all editable lookups that are dependent on properties that were set in the default procedure. Reevaluate the expression properties with the current state of the resource. Validate all non-expression lookups that depend on an expression property whose value has changed. New behavior: Apply default logic. Reevaluate the expression properties with the current state of the resource. Validate all editable lookups that were set in the default procedure or are expressions whose value changed. Validate all editable lookups that are dependent on properties that were set in the default procedure or expressions whose value changed. Indicium Universal Change password from RDBMS users Indicium Universal now supports password changes from RDBMS users. This was already available for Windows and Web. SQL print statements available in log If a stored procedure contains a print statement, it will now show up in the dbeventlog in Indicium's root page. We made a new column that contains all the print statement messages. Login pages have an extra button for cancel We improved the behavior of the different login pages and now allow canceling the login flow.For instance, when you try to log in and are presented with the two-factor validation page, you can now cancel the login and return to the original page. This also applies to the change password page and the two-factor setup page. Minor fixes and tasks We fixed the issue that parameters were not replaced in messages thrown from triggers. We fixed that the id_token_hint parameter was not sent along with the OpenID Connect remote logout requests. This did not cause issues with Microsoft Azure AD integration, but it did cause issues while logging out with other OpenID Connect implementations. These issues have now been resolved. We fixed an issue that caused that dependent lookups were not imported correctly. When translating the display values of a lookup from the Excel or CSV file back to their data values for the inserts/updates into the database, it would not take the context of the lookup into account. For example, the display value 'Subproject 1' would be resolved to the same data value regardless of the corresponding project. Indicium Basic Minor fixes and tasks We fixed a bug when a record was updated in a table with a prefilter on an expression field. Indicium would throw an exception in that case. We fixed an issue with default value expressions that returned DateTime types. For example, having a column with a default value expression of 'GETDATE()' would cause an error.

Hello everyone! We’ve released the following hotfixes over the last few weeks: SF 2021.2 20211111 - Sort order index columns When generating projects, sort order indexes are created for tables based on its sorting. The order of the index columns was alphabetically instead of based on the order no. This has been fixed. IAM 2021.3 20211103 - Execute source code regex update It was possible that code files would be split into multiple statements at wrong places causing errors during the Execute source code process. This has been adjusted.

There is a new E-learning course is available in the Thinkwise Learn environment. In this course we will guide you through all the basics of SQL and data modelling, in order to help you prepare for the Software Factory Associate training. The topics that will be covered are all of the most essential parts a developer needs when working with the Thinkwise Platform. Although the target audience for the course is the starting Thinkwise Developer, it is open for everyone to enroll. Perhaps you would like a recap on certain topics, or want to test your own SQL and data modelling knowledge. Why do we have this course? You will find many courses about SQL and data modelling on the internet. None of them, however, are specifically designed to be used in combination with the Thinkwise Platform. We use SQL in a different way than it is used in most applications. If you follow our SQL course, we can assure you that you will pick up on all the guidelines and best practises for the Thinkwise platform. You will also learn more on how SQL and data modelling are related to working with the Software Factory. In this way, the course help you focus on the parts that matter the most for a Thinkwise Developer. The course consists of two modules: Data Modelling and SQL - General Theory In this module, we will cover the most important aspects of data modelling, like the relational model, strong and weak entities, database normalisation, data types and the language SQL. Additionally, we will also have a look at how a relational model and SQL relate to the Software Factory. This module will be mostly theoretical, but you will perform quick knowledge checks during the process. SQL Basics In this module, we will focus on writing queries in SQL. We will go through all the basic elements that you will need to create your application with the Software Factory. We will follow the Thinkwise coding guidelines and cover best practises from our in-house developers when writing SQL. For every subject, we have created exercises to directly bring the theory that you have learned into practise. You can complete the exercises in a training database, which you can download from the course. You will also find an example solution to check your own work at the end of every subject. We also offer the possibility to receive coaching from our own trainers/developers during this course. Your code will be reviewed and you will receive more tips and tricks adapted to your own learning path. If you are interested in this, please contact your sales contact person. Coming soon: Update Thinkwise Associate - The Software Factory Currently, we are working on a new version of the Thinkwise Associate learning path. The new course will cover the relevant content about the recent Platform releases. As well as an educational, instructive and graphical update. In 2022, you will be hearing a lot more about the online learning content for the Thinkwise Platform. Keep an eye on our posts to stay informed!

November 5, 2021: Changed beta release to full version: 2021.3.12. Added fix: We fixed that the grid did not update summary values. Hello everyone, In this sprint, we added, among other things, support for opening lookup pop-ups from the grid and improved the marker in Maps. We also fixed some issues in default editable grids, lookups, and messages. As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI. We will keep you updated regularly about Universal's progress. Universal GUI version 2021.3.12 Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation and be sure to keep the following in mind: A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform. Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI. Make sure you are using the latest version of Indicium Universal. Download the Universal GUI version 2021.3.12 here New Improved marker in Maps When clicking the marker in a map, the grid will now navigate to the row that the user clicked on. Additionally, Maps now supports custom markers. As of the Thinkwise Platform release 2021.3, the Maps model extender has been replaced by a Maps component. Using a custom marker in the Maps component requires a Data mapping column with an 'Image combo' control. The image from the grid is used as a marker. For platform versions older than 2021.3, using the Maps model extender, the Type column binding needs an 'Image combo' control to use a custom marker. Custom marker in Maps Support for opening lookup pop-ups from the grid It is now possible to open lookup pop-ups from the grid, using the menu on the right. This option is only available for look-up columns with Lookup has pop-up enabled in the menu Subjects > Links > Lookups. Opening a lookup pop-up from the menu in the grid Minor fixes and tasks We upgraded our core grid component to a newer version that can better compute changes when the columns change. A user can now scroll from an HTML control to the next available field. In some screens, it could take seconds for the task and report buttons to become clickable. This delay was caused by an or query on i_ui_task_parmtr, i_ui_task, i_ui_report_parmtr, or i_ui_report. The Universal GUI now asks for this information in multiple requests. We fixed a bug that blocked users from logging in with 2-factor authentication. We fixed that the grid did not update summary values. If users lost their internet connection without going into the offline mode or restoring it, problems arose. For example, task pop-ups could not be canceled or reopened. These problems have been fixed. We also added a visual offline indicator to the task pop-up, so users cannot accidentally use it without an internet connection. Before: Problems after a lost internet connection After: Clarity on the disconnection Fixes in default editable grids When opening a default editable grid, an error could be displayed: method not allowed. The cause of this error was that the record was set to 'read-only' by the layout. The Universal GUI did not wait for the layout correctly. When clicking a checkbox in a default editable/autosave grid, the value would change to 'checked' and then return to its previous value. This has been fixed. We partly reduced the flickering grid content while modifying data in the edit mode. Fixes in lookups In the pop-up of a read-only lookup, the Select button has now been disabled. A lookup can be set to read-only in the Layout stored procedure. We also fixed that a read-only grid lookup field (as set in the Layout stored procedure) appeared as editable in grid edit mode. In the example below, the Country lookup column is read-only due to the layout. Before the fix, it seemed editable, but as you can see at the bottom of the screen, changing the value failed because the column is read-only: Read-only lookup with error message Now, the column is displayed correctly as read-only: Read-only lookup without error message Fixes in messages Confirmation messages now show the value of hidden task parameters. Error messages are no longer shown with [ ][] blocks around it. General messages, like [application_model_expired], are now translated correctly. Messages did not include a subject's translation if the subject had never been opened in the GUI at least once. This has been fixed. Messages thrown by a process flow now use the process variable values in the message translation. What we will be working on next sprint In the next sprint, we will be working on: Support for the lookup control type 'Combo (sorted)'. Editing HTML in a full-screen pop-up.

Hello everyone, In this sprint we made logging easier, and we solved some issues. You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress. Download Windows GUI 2021.3.13 here. Download Web GUI 2021.3.13 here. Breaking Developer mode no longer necessary for logging (Web GUI) Previously, when you wanted to enable logging for the Web GUI, you needed both the extended property WriteLogToFile and the option ExecutionMode (developer) in the settings.ini file. Now, we have removed the developer mode as one of the conditions. So, you can enable or disable logging solely by changing the extended property in IAM. This facilitates limited logging but prevents that users need to log in as a developer. Limited logging (e.g., only exceptions) can be set by combining the extended properties WriteLogToFile and LogSeverity. Minor fixes and tasks (Windows GUI) The scheduler yielded a divide by zero exception when the default row height for the grid was 0. This has been fixed. (Windows GUI) We have fixed an issue with failing file uploads in the Windows GUI in combination with Indicium. This issue only occurred in tables without a default procedure.

Hello everyone, In this sprint, we reduced the amount of double messages, and we fixed a problem with a false positive check. We also worked on some technical issues that do not affect functionality. You can read the Indicium user manual to read about Indicium's features. We will keep you updated regularly about Indicium's progress. Download Indicium Universal release 2021.3.13 here. Download Indicium Basic release 2021.3.13 here. Indicium Universal Reduced amount of double messages in the Universal GUI To eliminate the number of double messages, Indicium will no longer send messages from layout and context procedures if the procedures determine that the action is allowed. If necessary, the messages will be sent by the Universal GUI. Minor fixes and tasks Several of the file system I/O connectors in process flows, for instance, the Write File connector, would first validate if the root location of the file path was accessible (e.g., C:\ or \myFileServer) and then if the direct parent directory was accessible (e.g., C:\files\myProject or \myFileServer\files\myProject). In practice, only the second check is necessary. Moreover, the first check can fail where the second would have succeeded. Users may have access to a specific folder but not to the root of that folder. Therefore, we have removed the first check to solve the false positive 'access denied' scenarios.

Hi everyone! We’ve released the following hotfixes for 2021.3 platform version: SF 2021.3 20211029 - Corrections in creation process The task to run a complete creation now waits for other jobs to finish, no longer result in the possible failing of a creation. When a project version was upgraded, the question is now asked again if a new project version should be created. The process flow responsible for focusing on the active definition generation step has been made a little bitt less aggressive, leading to a better user experience. 20211027 - Corrections in creation process A possible situation where the upgrade script was not automatically checked does not arise anymore. There no longer is a specific situation where it might appear that executing a new project version to the database succeeds, when it actually doesn't. Some other minor improvements. IAM 2021.3 20211029 - Corrections in creation process We've been getting several questions on how to deal with messages stating that a job will not be started (directly). These messages have been improved to include the sentence "More information can be found in the Advanced Menu > Log > Jobs." 20211028 - Agent check-in reduced abandon rate A scenario was discovered where scheduled system flows that only allowed a single instance to be running, could end up running multiple times due to the earlier instance of the system flow being marked as abandoned when the interval was expired. This has been resolved. 20211027 - Grant rights to end user role for Get gui maps procedures The necessary rights for the new get gui maps procedures were not granted to the IAM-role “End user”. This could cause errors while starting an application for this role, only when rights to the database were applied. The rights are now granted. 20211026 - Set ‘Legacy API’ to on for Get gui maps procedures Get gui procedures for maps were not available for Indicium Basic causing applications run via Indicium Basic to be unable to open successfully. This has been resolved.

Hello everyone, In this sprint, we have improved the logging and the import functionality. We have also solved some issues. You can read the Indicium user manual to read about Indicium's features. We will keep you updated regularly about Indicium's progress. Download Indicium Universal release 2021.3.11 here. Download Indicium Basic release 2021.3.11 here. Breaking Indicium Universal: Process procedure errors now stop the process flow From now on, errors in process procedures will abort your process flow or system flow. Previously, the order from the model was used if something went wrong, but this could cause unintended effects when the process procedure did not work as expected. Indicium Basic: Support for IAM/Software Factory 2019.2 expired The support for reading application models from the Thinkwise Platform version 2019.2 has expired. Please update IAM and the Software Factory to at least version 2020.1 to use this version of Indicium. Indicium Basic: Now requires the IIS module AspNetCoreModuleV2 to be installed Install the latest ASP.NET Core Windows Hosting module that is linked here. Indicium Universal Updating rows when importing When you tell Indicium not to insert rows and only update, it will throw an error for the rows it cannot update. So, you can download the failed records into a new Excel file. To control this behavior, two new query string parameters have been added to the stage_import endpoint: add_new_rows and update_existing_rows. Their values can be set to true and false, but at least one of them must be true. Improved logging In this version of Indicium, we improved the logging, to make it easier to detect where an error occurred. In process flows and system flows, it is now clear which step caused the error. System flows with invalid actions are logged now. More explanation is available for errors that occurred when editing a resource. Changes Indicium will no longer treat an SQL print message as a TSF message. In the near future, SQL print messages will be logged to Indicium Universal's Database Event Log. Minor fixes and tasks We solved an issue that occurred when you used mandatory exclusive prefilter groups, and the table had an expression column. This issue could cause Indicium to crash and require a restart. On some occasions, Indicium would call the subroutine procedures with the wrong parameter order on DB2. This has been fixed. We solved an issue with the query for lookup references that contained an expression column in its target columns. When configuring an API alias for subroutine parameters, the API alias was not used correctly. This has been fixed. We fixed an issue that could cause failed queries for the combination of `select detail` references with `groupby' clauses. In particular, this could cause pivot grid and charts on detail subjects unable to load their data.

We are very excited to announce version 2021.3 of the Thinkwise Platform. Our highlighted feature of this release is the redesigned and improved Creation process. This redesign offers many advantages: All jobs are no longer performed by a client (the GUI) but instead by Indicium. This shift means that generation, validation, etc., will continue even if you close the Software Factory GUI. Since all jobs are performed by Indicium, it is possible to automate the entire process. All developers can track a job's progress. For example, if one developer starts generating the definition of a project version, another developer can see this in their Creation screen. This behavior extends to the validation- and unit test tabs in various modelers. The Validation and Unit test screens that can be opened directly from the menu have also been updated. You can execute the steps in the Creation process separately or all at once. The screens and steps you already know in the Creation process are still available. But to move the responsibility of the creation process to Indicium, some screens have changed, and we have cleaned up some unused features. For more information, see: Redesigned creation process Task to execute a complete creation Automate your creation process A task for executing all creation steps Of course, this release brings more new features and changes. Some other highlights are: Reusable subflows Multiple running instances of system flows Generation optimization Generation strategies for control procedures Manual test administration For a comprehensive overview, please check out the release notes. The Thinkwise Platform 2021.3 is available for download in TCP now!

Hello everyone, in this sprint we have improved the autorefresh functionality for the Windows GUI. You can read the GUI user manual to read about the Windows and Web GUI's features. We will keep you updated regularly about the Windows and Web GUI's progress. Download Windows GUI 2021.3.11 here. Download Web GUI 2021.3.11 here. Changed Support for IAM/Software Factory 2019.2 expired The support for the Thinkwise Platform version 2019.2 has expired. Please update IAM and the Software Factory to at least version 2020.1 to use this version of the Windows and Web GUI. Autorefresh disabled when a grid or tree is in multiselection (Windows GUI) From now on, autorefresh is disabled when a user selects more than one row in a grid or tree. Before this change, when the screen refreshed, the selection would reset to only the active row. That made it almost impossible to execute tasks based on multiple row selection.Now, autorefresh pauses for as long as the user has multiple rows selected, and thus multiple row task execution can be used. New The new Maps feature supported in the Windows and Web GUI The new Maps feature in the Software Factory (version 2021.3), including its settings, is now supported in the Windows and Web GUI. New application setting (Windows GUI) We added a new application setting: oauthredirecturi . You can use this setting to change the standard OAuth connector redirect uri (http://localhost/oauth-callback ). Minor tasks and fixes Windows GUI: a bug with an empty task output in combination with indicium has been fixed.

October 19, 2021: Changed release version to 2021.3.11.1. Added fix: Chart was not visible when a document was opened for the first time. October 15, 2021: Changed beta release to full version: 2021.3.11. Added fix: The process flow Go to next row would return as successful when used on the last record in the dataset. With this fix, it will return as unsuccessful. The same problem has been fixed for Go to previous row/first record. Hello everyone, In this sprint, we added support for changing an expired password, and for editing multiple rows in a grid with autosave enabled. We also made the resource scheduler more compact in the day view. And again, we fixed some issues, mainly for lookup controls. As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI. We will keep you updated regularly about Universal's progress. Universal GUI version 2021.3.11.1 Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation and be sure to keep the following in mind: A modern browser is required to access the Universal GUI, 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.3.11.1 here New Stay in grid edit mode when autosave is turned on When autosave is enabled, and you are working in an editable grid, it is now possible to edit multiple rows without the need to reactivate the edit mode for every row. Edit mode will be turned off when, e.g., deleting a record, adding a record, refreshing, or filtering. It is also turned off by saving manually or canceling. Edit multiple rows in the grid in edit mode Support for changing an expired password A user logging in with an expired password is now redirected to Indicium, where they can change their password. After that, the user is sent back to the Universal GUI. Please note that sending the user back only works when Indicium and the Universal GUI run on the same origin (recommended) or if the Universal GUI is configured as an allowed origin in Indicium. Previously, the Universal GUI displayed "Incorrect username and password." Changed Resource scheduler more compact In the day view, the year and week labels have been merged, which saves vertical space. In compact mode, the height per resource row and padding below each resource row have been reduced. This row height and padding reduction win 13px per resource row, resulting in more resources fitting in the same height. Before: The resource scheduler before the changes The resource scheduler now: more compact Changed and fixed in lookup controls The lookup suggestion control now shows the start of the options list if it is opened while an option is already chosen. Previously, the options got filtered on the selected value, which resulted in only one option to choose. The lookup controls now have their focus state reimplemented to make them feel like the other controls. Also, we did a few alignment fixes to make them look the same. In some cases, the Clear button showed in an empty lookup control. Now it only appears when a value is chosen. On an empty lookup control without focus, but with a large format label in the middle of the input, the label blocked the mouse cursor from focusing on the field or clicking the buttons. Now, the label is placed "behind" the field to only display the column name without blocking anything. Loading the options for untranslated lookup columns in the filter form has been fixed. Screen components that cannot have data pruned from the screen type Screen components that cannot have data are now pruned from the screen type. Previously, a screen showed empty space or an error message if a component could never show data. Removing these components provides more space for the components that can display data. For example: Detail tiles without details Grid without columns Form without columns Card list without columns Cube without cube definition Scheduler without two date(time) columns Previewer without suitable column Tab with only detail tab pages and no details. Minor fixes and tasks Card lists and form components now keep their scroll position after a screen switch, e.g., after a tab change and back. The process flow Go to next row would return as successful when used on the last record in the dataset. With this fix, it will return as unsuccessful. The same problem has been fixed for Go to previous row/first record. Fixed that a chart was not visible when a document was opened for the first time. What we will be working on next sprint The next sprint we will be working on: Maps Navigate to a row from the map. Customize marker icons. Lookup popup from the grid - Allows the user to start the lookup for a field from a non-edit mode grid. And we will solve some issues.

Hello everyone, We have just released a hotfix for Universal that fixes Universal crashing when logging out or clearing the cache while working on HTTP.This has been released as version 2021.3.10.2 and can be downloaded here.Please note that we strongly advise using HTTPS with Universal, without HTTPS Universal can't work offline and can't detect when a new version has been deployed.

Hello everyone! We’ve released the following hotfix this week: SF 2021.2 20210921 - Exclude clustered indexes from drop all Clustered indexes are now created when the tables are created but were still being dropped by the drop all indexes script. The drop all indexes script has been updated to no longer drop clustered indexes.

Hello everyone, in this sprint, we fixed several bugs. You can read the GUI user manual to read about the Windows and Web GUI's features. We will keep you updated regularly about the Windows and Web GUI's progress. Download Windows GUI 2021.3.10 here. Download Web GUI 2021.3.10 here. Minor fixes and tasks (Windows GUI) We have fixed a bug 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. (Windows and Web GUI) Fixed a bug in the OAuth connector which could result in an Object reference error. [2125S] (Web GUI) Fixed a bug in the 2FA email notification flow where HTML was not correctly decoded. [2069S] (Windows GUI) Fixed a bug in the multiline control popup where changes where not saved on close. [2225S]

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 lookups It is now possible to import into a subject that contains untranslated lookups. Multiple results from a single query in the application connector The 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 Indicium As 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 simulation When 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 simulation When 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 page It 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/usersimulation This 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/usersimulation Request 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 5 We 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 tasks On 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 grid September 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.10 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, 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 changed We 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 boxes In 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 box The 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 record Previously, 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 popups The 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 improvements Fixed 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 controls With 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 pagination Deleting 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. Other The 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 sprint The 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.2 20210903 - 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 tasks We'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.16 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 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 here New Compact mode Ample 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 preferences Besides 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 menu Available 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 mode At 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. Reconnect At 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 offline This 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 scheduler In 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 tasks We 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 sprint The 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. Changes Default values (including default expressions) are now applied to imported rows. Minor fixes and tasks 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.

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 here Windows GUI will not send unnecessary requests after a 401 Unauthorized response The 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 feature Over 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 flows In 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 Checks In 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 }} Changes Default values (including default expressions) are now applied to imported rows. Minor fixes and tasks Various 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 beta Hello 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.15 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 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 here New Prevent document showing data before a filter has been set In 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 form When 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 prefilters In 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 menu Universal 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 tasks 1468S - Resource Scheduler group until column sort order descending not working The 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 shown Under 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 sprint The 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.2 20210806 - 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 databases The 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 databases SQL 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.