Product Updates

Hello everyone,in this sprint we've solved some issues and, most importantly, we've added support for default initial default expressions when updating or importing data.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 the Thinkwise Windows GUI. Download the Thinkwise Web GUI. New Initial default expressions in update and import (Windows GUI)Windows GUI 2021.1.15 (hotfix) and .16 (this release) in combination with Indicium Basic 2021.1.16 now supports initial default expressions in the Update and Import functionality. This means that the default expressions are executed when the import/update column mapping screen is opened. This also works for tasks and reports. Please note that this does NOT work for process variables.Update or ImportDefault values (type: expression) are set in the menu Data > Domains > tab Tables > tab Columns.Example: Default value type “Expression”, and QueryThe result when importing data:Example: initial default expression in import screen Changed No more extra download pop-up for reports and exportsDownloading reports or Excel exports now runs directly in the Web GUI, without the extra download popup dialog. This popup was deemed unnecessary. Fixes and tasks(Web GUI) Using arrow navigation in a context that shows, hides, or disables a part of the GUI resulted in an error and an incorrect selection. This has been fixed. The error won't occur any longer (Web GUI) Navigating with the arrow key rapidly through the grid in the Web GUI resulted in an incorrect row selection. This has been fixed, now the correct row is selected. (Web GUI) Refreshing a page no longer restores a cube to its default view. (Web GUI) We've fixed a problem with conditional formatting in background detail tabs in Web GUI forms. Now the conditional formatting is displayed as it should, refreshing manually is no longer necessary. In multiple selection mode, it wasn't possible to deselect nodes in a tree list. This has been fixed, now it is possible to change your selection. 

Hello everyone,this sprint, we've added more awesome features to Indicium Universal, the most important of which is the migration to .NET 5. Below you can read about the benefits of this migration. We also worked hard, among other things, on authentication and further improved security.We'll keep you updated regularly about Indicium's progress. You can read the Indicium user manual to read about Indicium's features. Download Indicium 2021.1.17 here. Indicium Universal BREAKING: Migration to .NET 5As of this version, Indicium Universal will be running on .NET 5. This means that in order to run Indicium Universal on IIS, you need to install the ASP.NET Core 5.0.4 Windows Hosting Bundle.The update to .NET 5 offers the following advantages compared to Indicium Universal version 2021.1.16:Platform independence: all releases of Indicium Universal from this point onward can run on Linux and macOS as well. Performance: this version of Indicium Universal has multiple big and small performance improvements compared to 2021.1.16. The two request types which benefit most are those that return a lot of data in the response and smaller requests which were already quite fast. Overall, you can expect an improvement of around 10-40% in response times, depending on the request and various variables. Maximum load: though hard to quantify, this version of Indicium Universal will be able to handle more load than version 2021.1.16, meaning that a single instance of Indicium can handle more concurrent users. Data usage: the response sizes are roughly 30-40% smaller in this version of Indicium Universal. This is part of the performance improvement described above, but it also means that clients will use less data and that the performance improvement will scale higher on poor network connections.The update to .NET 5 allows us to improve the performance even more in the future!The following components of Indicium Universal still require .NET Framework version 4.7.2 or higher (NOTE: not .NET 5). Without .NET Framework 4.7.2 or higher installed, Indicium Universal will start, but these components will not work.:CrystalReports. DevExpress reports (will be .NET 5 compatible in the near future). SQL Server Reporting Services.Using this version of Indicium for DB2 databases requires some additional installation steps which have been outlined in our Installation manual. BREAKING: Chromium browsers no longer support http://Some of Indicium's authentication features, such as Single Sign On (SSO) and Single Logout (SLO), require Indicium's authentication cookie to have the samesite=none attribute. Chrome has recently made a change that causes cookies with this attribute to only work when the cookie is secure, meaning that the cookie was requested and received over a secure channel (i.e. https://). Consequently, you can no longer log in over http:// when using Chromium-based browsers such as Chrome and Edge, and this behavior will likely extend to more browsers in the future.We already require usage of https:// in production environments, but if you must do testing over http:// then a different, non-Chromium browser needs to be used, such as Firefox. We will look into minimizing the inconvenience of this in our next release, by looking into not using the samesite=none attribute when it is not required. However, since we can no longer guarantee that all of Indicium's features will work over http://, we recommend using https:// for both development and testing environments. Authentication through OAuth 2.0 Bearer TokensBeing an Identity Provider, Indicium already served access tokens, but these tokens could only be used to fetch user claims and not to access Indicium's API itself. As of this version, we’ve added support for the JWT Bearer authentication scheme that allows access tokens to be used as a means to authenticate users for API access.Note that this feature is specifically meant for third-party clients and won't be used by our own clients such as the Universal GUI.A third-party client will receive an access token after a user has authenticated and given consent that the client may access the API on their behalf. The client can then make a request to Indicium’s API, using that token in the Authorization header. An access token will give access to all APIs that are available to that user, no more and no less.For this feature to work, an OpenID client needs to be configured in IAM (menu OpenID > OpenID clients). Be sure to check the API checkbox for the OpenID client and add a redirect URL and client secret. Furthermore, the location of the Authority, which is the URL to Indicium, needs to be provided by means of the BearerTokenAuthority setting in Indicium's appsettings.json. This Authority URL must use 'https', e.g.:{ "BearerTokenAuthority" : "https://localhost:5001" } Once the OpenID client and Authority URL are configured, an access token can be requested like this (in the example below, the API tool Insomnia is used):Example: access token requestGrant type: Indicium uses OAuth 2.0’s Authorization Code Flow which exchanges an Authorization Code for a token. For more information, see https://auth0.com/docs/flows/authorization-code-flow. Optionally, PKCE can be used as well if the client is deemed insecure. Authorization URL: This endpoint is used to retrieve an authorization code via the browser and involves authentication via the login prompt and (when required) consent. The Authorization URL can be retrieved by calling the following endpoint on the Authority URL: <Authority URL>/.well-known/openid-configuration. Typically, the authorization URL looks like this: /connect/authorize. Access token URL: This endpoint is used to retrieve the access token. Just like the authorization URL, the Access Token URL can be retrieved by calling the following endpoint on the Authority URL: /.well-known/openid-configuration. Typically, the Access token URL looks like this: /connect/token. Client ID, Client secret and Redirect URL: Client information from IAM. Scope: This should include full_api_access in order to obtain an Access Token that gives API access. Other scopes such as openid, profile, email, etc. can be requested simultaneously if necessary.When in IAM is configured that consent is required, the following consent page will appear. Only after allowing, Indicium will give out the access token.Please be aware that at this moment, Indicium only gives out access tokens, the exchange of a refresh token is not supported. Access tokens are valid for one hour.Consent page PKCE support for OpenIDWe've added PKCE support for OpenID to reduce security risks for native apps.PKCE is short for Proof Key for Code Exchange. It is an OAuth 2.0 security extension for public clients on mobile devices, to avoid a malicious program creeping into the same computer from intercepting the authorization code. Single Logout (SLO) for external OpenID Identity ProvidersIn this version of Indicium Universal, we have augmented our support for authentication through external Identity Providers with Single Logout (SLO). This means that it is now also possible to log out of the external Identity Provider in an integrated way from Indicium's log out page if you were logged in with an external Identity Provider (see OpenID connect).In order to use Single Logout on top of this, we have added two new properties to the configuration in the appsettings.json: SignOutButtonIcon and SignOutButtonText. These properties allow you to configure the sign-out button that will appear on Indicium's logout page:"OpenIDConnect": { "IdentityProviders": { "Microsoft": { "MetadataEndpoint": "", "ClientId": "", "ClientSecret": "", "ButtonIcon": "microsoft.png", "ButtonText": "Sign in with Microsoft", "SignOutButtonIcon": "microsoft.png", "SignOutButtonText": "Sign out of Microsoft" }}The type of SLO that Indicium supports is called front-channel logout. The way it works is that Indicium will redirect the user to the logout page of the external Identity Provider where the user can log out. Upon doing so, the external Identity Provider will send a logout call back to Indicium before redirecting the user back. This logout call will need to be configured at the external Identity Provider. Taking Microsoft's Azure Active Directory as an example, the screenshot below shows how you can configure the front-channel logout URL. Just like how the post-sign in redirect URL is /signin-{name} — where {name} is the name of the Identity Provider in the appsettings.json — the front-channel logout URL is /signout-{name}.If the Identity Provider is configured as the DefaultIdentityProvider, then the Indicium logout page will not be shown, but it will be as if the Sign out of X button is clicked automatically, immediately redirecting the user to the external Identity Provider's logout page.Redirect URI and Front-channel logout URL Partial support for the report parameter property "Export Path"Indicium now partially supports the Export path report parameter Property. This property can be selected in the menu Processes > Reports > tab Report parameters > tab Form > tab Report parameter > field Property.Indicium still won't export report results to disk, but it will respect the file name provided in the download that it offers to the client. Indicium will determine the download file name as follows: If there is a Report parameter with the Export Path property: If the value of the parameter is a file path that ends in a file name, Indicium will use this file name. If the extension is incorrect, Indicium will correct it to, for instance, .pdf. If the value is not a file path or it does not end in a file name, Indicium will use the translation of the report as the file name. If there is no report parameter with the Export Path property: Indicium will use the translation of the report as the file name. If the report does not have a translation, the report ID will be used instead.  Minor fixes and tasks We've fixed an issue with the $export request parameter when the selected data set contained a column with data type 'TIME'. We've fixed an issue that caused the OpenID Authorization Code flow to fail sometimes in load-balanced environments when using Indicium as the Identity Provider. To fix this issue, Indicium will augment the IAM database with three new tables upon starting: dbo.__EFMigrationsHistory indicium.DeviceCodes indicium.PersistedGrants. Multiple load-balanced instances of Indicium need these tables to communicate intermediate tokens with each other in order to have the Authorization Code flow succeed when not every request goes to the same instance of Indicium. We've fixed an issue for message protocol independent process flows that caused responses with content types likes application/json or application/xml to be returned as if they were string literals. For example the response{ "some_property": "some_value" } would erroneously be returned as"{ \"some_property\": \"some_value\" }"

2021 March 26:Changed version to 2021.1.14.1. Added hotfix:  If a report had spaces in its name, it would wrongfully get underscores surrounding the file name, which changed it into a pdf-file that could not be accessed. This has been fixed.Hello everyone,During this sprint, we've worked on the support for badges and five more process actions. Moreover, we've enabled the cursor focus and improved the Resource Scheduler further.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 Universal.We'll keep you updated regularly about Universal's progress. Universal GUI version 2021.1.14.1Don'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. Universal 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.1 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 on the latest version of Indicium Universal.Download Universal version 2021.1.14.1 here New Badges on detail tiles and detail tabsBadges can now also be shown in detail tiles and detail tabs. Badges are numbers that can attract the attention of the user.Badges in detail tilesBadges in detail tabs Process action supportUniversal GUI now supports the following process actions:Show Message - To show a popup to the user, containing defined actions as buttons. Each button can continue to a different path in the process flow. Change filters - To change the filter values for each column and disable the active prefilters. The parameters Allow wildcards, Ignore diacritics, and Case sensitive are not yet supported by Indicium. Clear filter - To clear the filters set by the process action Change filters. Go to first/last/previous/next row - To jump to the first/last/previous/next row in the grid. Go to row - To jump to a specific row in the grid. Support for Start objectsUniversal GUI now opens the tables, tasks, and reports that are configured as start objects in either IAM or the User Preferences ribbon in your end application using the Windows GUI or Web GUI. Configuring start objects in the Universal GUI (using the User Preferences menu under the user profile) will be implemented in a future release. New and changed in the Resource SchedulerIn the last release, we added a basic version of the Resource Scheduler. In this release, we've changed the header location to improve working with the Resource Scheduler further. Now it's placed on the right, and it includes both the navigation buttons and the date range of the current view.Moreover, it's now possible to show a tooltip in the Resource scheduler component. Just add a multiline control, and you'll see the tooltip appear when hovering over the activity.Changed header location Focus for specific form control while editingWe've added support for focusing on a specific form control while activating edit mode and after updating a control value. On Add/Edit/Copy, the Universal GUI will place the cursor in the first editable control.For replacing the cursor after updating a control value, parameter cursor_to_col can be set in the default stored procedure on the database, see Default. Minor fixes and tasksThe setting for a light or dark theme is now kept when a user logs out and back in instead of using the application's default theme. When clearing the browser cache, however, the application will return to its default theme. We've removed the unnecessary 'empty' option in a mandatory lookup. When a layout procedure made a lookup field first read-only and then regular, the Clear icon stopped working. This has been fixed. In Software Factory versions 2020.1 and older, a screen with a lot of details (e.g., 87 details) could fail because the request length was too large. This has been fixed. After logging in, the loader was displayed at the top left of the screen. Now it is in the middle, as it should be. The screen component property HIDE_TOOLBAR now also works for tab panels at the root level. Checkbox controls now work properly with NoOfPositionFurther = 0. This means that two checkbox fields next to each other will both be displayed correctly. If a report had spaces in its name, it would wrongfully get underscores surrounding the file name, which changed it into a pdf-file that could not be accessed. This has been fixed. What we'll be working on next sprintThe next sprint we'll be working on:Process flow actions: Delete row (follow-up action to delete a row). Work in progress: import, filter form, form conditional layouts, auto-refresh, offline data. And we'll solve some issues.

Hello everyone!We’ve released the following hotfix this week:IAM 2019.2 and up20210222 - Exclude users in API view where end on is exceeded It will not be possible for users to log in to an application anymore when: The user has a date set in 'Start on' which has not passed yet The user has a date set in 'End on' which has passed

Hello everyone,in this sprint, we've added more awesome features and 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 2021.1.16. Download Indicium Basic 2021.1.16. Indicium UniversalMulti-row task support using MultiselectParameterIDWe've added support for executing multi-row tasks using a runtime XML parameter that is provided through the MultiselectParameterID extended property. For more details, see the blog on Multi-row task execution in our Community. Message protocol-independent web services in process flowsIn version 2021.1 of the Software Factory, 'Message protocol independent' web services in a process flows were introduced. As of this version, they are supported by Indicium Universal.This feature allows you to create entirely custom APIs, receive and process the HTTP requests on the database, and set the HTTP response as well. Please note that this feature is not meant to simply create an API for a process flow because you want to start it with an API call. Every process flow already has an API  that allows you to start it with an API call. This feature is specifically meant for situations where you have limited control over the contents of an HTTP request, but you want to process it in your Thinkwise application. For instance, if you want to implement a webhook and a third-party service will send data in XML form to a certain endpoint and you want to process it, then this would be a good solution.Message protocol-independent webserviceWhen the API checkbox is checked, Indicium Universal will create a special API endpoint for you:/open/iam/<appl>/<process_flow_id>If the API alias field is filled out, the endpoint will be:/open/iam/<appl>/<process_flow_api_alias>The first segment of the endpoint is /open because this is a special endpoint that is entirely separate from Indicium's regular OData endpoints. This endpoint will accept any type of request that you send to it, as long as the path of the URL is as shown above. No matter what the HTTP method is, whether you add a query string to the URL, which headers you include or what the request body is, all requests are valid.Once the API checkbox is checked, you can choose to link properties to your process variables, similar to how this works for report parameters. These properties represent properties of HTTP requests and responses. When an HTTP request property (Method, Path, Query string, Request body, or Request headers) is mapped to a process variable, that process variable will be initialized with the corresponding value in the HTTP request that triggered the process flow. When an HTTP response property (Response body, Response code, Response headers) is linked to a process variable, the values of those process variables will determine the response that Indicium will give.Please note the following restrictions that apply to these process variable properties:Method - The domain must be a string type, such as (n)varchar or an equivalent type. Path - The domain must be a string type, such as (n)varchar or an equivalent type. Query string - The domain must be a string type, such as (n)varchar or an equivalent type. Request body - The domain must be a string or binary type, such as (n)varchar, varbinary, or an equivalent type. Request headers - The domain must be a string type, such as (n)varchar or an equivalent type. The value will be formatted in JSON like this: { "Header1": [ "value1", "value2" ], "Header2": [ "value"] } Response body - The domain must be a string or binary type, such as (n)varchar, varbinary, or an equivalent type. Response code - The domain must be an integer type, such as int or an equivalent type. The value must be a valid HTTP response status code (e.g. 200, 204, 404, etc.) Response headers - The domain must be a string type, such as (n)varchar or an equivalent type. The value must be formatted in JSON like this: { "Header1": [ "value1", "value2" ], "Header2": [ "value"] }For more information, see Message protocol-independent webservice.Process variablesChangedThe title property in IAM's Global settings will now be used as the issuer for TOTP secrets (Time-based One-Time Password). This means that whatever is entered as the title in IAM will be shown in Authenticator apps as the application for which the TOTP codes are meant. This also makes it possible to register a TOTP secret for the same user in multiple IAM databases in one Authenticator app. Previously, 'Thinkwise' was always shown as the issuer. Now, only if no title property is entered, 'Thinkwise' is shown. Ensure that the latest hotfixes are applied, at least 20210203 - Add title to i_core_global_settings.sql. Minor fixes and tasksDatabase storage did not work if the storage column containing a binary large object (BLOB) was an expression column. This has been fixed. We've fixed that informative messages were wrongly shown as errors on Indicium's pages. The title property in IAM's Global settings will now be used as the page title on Indicium's authentication pages. Previously, 'Thinkwise Identity Provider' was displayed as the page title. If no title property is entered, 'Thinkwise Identity Provider' will still be used. Ensure that the latest hotfixes are applied, at least 20210203 - Add title to i_core_global_settings.sql.To improve the stability of the new export feature we've fixed two issues and made one change:Columns with GUID data types, like UNIQUEIDENTIFIER, will no longer cause the export to fail. Having multiple columns with the same translation will no longer cause the export to fail. File columns, including data storage columns (BLOBs), will now be skipped when exporting to avoid the export of sensitive information and instability of Indicium due to memory usage. Indicium BasicMinor fixes and tasksDatabase storage did not work if the storage column containing a binary large object (BLOB) was an expression column. This has been fixed.

Hello everyone,in this sprint, we improved the loading time for DevExpress reports, 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. NewReduced loading time for DevExpress reports (Web)To reduce the loading time when opening a DevExpress report for the first time, the assembly needed for the DevExpress is preloaded during application warm-up in the bootstrap.ashx.To activate the application warm-up, please check the documentation. ChangedTask dialog height is now adjusted by the layout (Web)When a field in a task dialog is hidden outside the form using the layout, the dialog will now adjust the height based on the visible fields on the form.Dialog height Fixes and tasksActivate document from a process flow on a variant subject (Web)We investigated an issue in the Web GUI where a document, opened earlier in the process flow, was not activated again by using the Activate Document process flow action. Two causes have been found and solved:In the Software Factory, the Activate Document process action is not subject variant-specific (yet). We've fixed the Web GUI, so it won't take the variant into account while looking up the document to be activated when the process variable document_id is not given or faulty. Process variable document_id was ignored because of its datatype in the Software Factory. Our Windows GUI uses an incremental number for this, so datatype 'INT' is fine. The Web GUI uses a number too, but also attaches the tab ID to it, which makes the expected datatype a 'VARCHAR'.Process variable document_id Capital letter behavior support in Grid (Windows)Capital letter behavior is now supported in the grid.Capital letter support User session logging for reports (Web)In some cases, an executed report action was not registered in the user logging of IAM when working with the Web GUI. We've tested several cases and fixed the logging where needed.

Hello everyone,In this sprint, we've added more awesome features we think you'll like, and we've 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 Universal. We'll keep you updated regularly about Universal's progress. Universal GUI version 2021.1.13.1As always, we've released a version so you can test Universal 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. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and SF that you plan to use for Universal. Make sure you are on the latest version of Indicium Universal.Download Universal version 2021.1.13.1 here  NewBasic resource schedulerA first basic implementation of a resource scheduler is available now! It has a lot of neat features like drag & drop, active row navigation by clicking on resources, and conditional layout.Contrary to the other user interfaces, the resource scheduler does not require an extender to initialize. Instead, a heuristic approach is used. Simply place the Scheduler screen component in the screen type and the component will initialize via the following rules:A subject needs to have at least 2 date/time columns. The order of these columns will determine the start and end of an activity. The title of the activity is determined by the Display column. The resources of the scheduler will be determined by the first field in the subject that has a sort with a Group Until. This needs to be a readable text identifier, lookups will not yet be translated. You can add resources that do not yet have an activity by including a row in the subject with an empty start- and end date. Drag & drop is allowed. The start- and/or end date of a row can be changed manually and by dragging the resource horizontally. If the subject is a view, this could require an instead-of update trigger. Dragging an activity to another resource will update the Group Until column to the target value. Note that, since the translation of lookups isn't yet supported, you might have to translate this back to a correct foreign key value using an instead-of update trigger. The activity color can be set with a conditional layout. The conditional layout has to be set to the Display column.Basic resource scheduler Process action: zoom in on detailWe've added the process action Zoom in on detail. This opens a detail in a new document. This is what it looks like:Zoom in on detail Hide toolbar for a screen typeSometimes the toolbar (search, refresh, etc.) doesn't make sense for a screen type. Now it's possible to hide the toolbar per screen type, by adding the screen component property HIDE_TOOLBAR with any value (for example, "yes") to the root screen component:Hide toolbar Support for "Refresh after execute" option "All" for tasksIt is now possible to use All for refreshing data after a task has been executed in the Universal GUI. When configured for a task of a child subject, it will make sure the parent subject is refreshed as well. This option may affect performance, so do not use it unnecessarily.In the example below, All is configured as refresh after the execution of the Generate invoices task in the child subject Sales invoices. After the task has been executed successfully, the parent subject Customers is refreshed, too.Refresh all Debug mode for breakpointsWe've added a debug mode to help developers add breakpoints. It is enabled by the setting debugMode: true in the config.json. You will see the current width and active screen type for each screen. If that screen type is a breakpoint, you will also see the screen type that it is a breakpoint of. It looks like this:Debug mode for breakpoints Hide login optionsWe've added the option to hide the login options by the setting "loginOptionsHidden": true in the config.json. The login screen then looks like this:Hide login options Tasks for multiple records allowedWith multiple records selected in the grid, tasks can now be executed for all these records simultaneously, unless the popup for each row setting is turned on. Message location supportUniversal GUI now listens to the message location configured in the Software Factory. Messages with a location "panel" are shown in a snack bar at the bottom of the screen because Universal GUI doesn't have a panel.More information about the message location.  Paste links into an HTML fieldWhen pasting a URL into the HTML control, it now will become a clickable link. ChangedReport filenameThe name of a downloaded report (as a pdf) is now the filename, as configured in the Software Factory. It used to be a random string. Note: This does not yet work for iOS. Improved confirmation popupsThe meaning of the answers OK and Cancel wasn't clear in the questions "Are you sure you want to cancel?" or "Are you sure you want to execute this task?".Now the button text has been changed to "Yes" and "No". A hotfix on the translations provided by the Software Factory/IAM will update the question to the user to "Do you want to discard your changes?".Improved popupsMinor fixes and tasksAn empty chart is no longer white in dark mode. The update notification would slide under the sidebar menu when there was not enough space. This has been fixed. We've fixed an issue with the "record not found" notification showing up unnecessarily after deleting a record. The data set was refreshed twice after deleting a record. This has been solved, which means performance has increased when deleting a record. We've fixed an untranslated lookup suggestion that displayed "[Object object]" after a value was chosen. When a user had a lookup popup open and tried to open another one, all lookup popups would close. This has been fixed, the second lookup popup now opens as it should. We've fixed a bug where Universal GUI gave an error when trying to translate hidden or untranslated lookups. When using a barcode scanner control in a task popup, it showed an empty space where the barcode control should have been. This has been fixed. We've fixed the time showing milliseconds in a form in non-edit mode. Now the milliseconds won't show, just as in the grid. The Activate document process action now also triggers when opening the document from the menu rather than from open documents. Setting installNotificationDisabled in the config file to 'false' will now actually enable the install notification. What we'll be working on next sprintThe next sprint we'll be working on:Badges on tiles and tabs. Follow-up actions in process flow actions: show a message dialog to the user, set filters, clear filters, go to a specific row, go to first/previous/next/last row. Work in progress: import, filter form, and form conditional layouts. And we'll solve some issues. 

Hello everyone,In this sprint we've added some extended properties, a small change has been made in the scheduler, and we've fixed some issues for you.You can read the GUI user manual to read about the WinWeb GUI's features.We'll keep you updated regularly about the WinWeb GUI's progress. New extended propertiesWindows & Web: Now it is possible to hide the popup when an async task is started, by setting the global extended property HideAsnycTaskPopup in IAM to 'true' or 'yes'. Web: The global extended property NoClaimableApplicationMessageENG allows IAM users to set a customized message to let their users know that all of their applications are already in use. If not set, the default error message will be "All applications for this user are currently in use.".See Extended properties. Changes and fixes in the scheduler (Windows)In the scheduler, the background of the time cells used to be white by default, they now change according to the settings in the extender. If they were white before and have rainbow colors now, please set the time cell background color in the extender to 'White'. An error has been fixed that would occur when you had a scheduler component in a splitter tab, with a detail tab in the other splitter tab. The date picker in the scheduler will now update accordingly when scrolling through time. When performing the double-click task on a time cell in the scheduler, now only the date and resource_id parameters in the task popup will be filled. Minor fixes and tasksWindows & Web: Grid group headers will now not be drawn when there is no visible column with a group header. Also, invisible columns now no longer prematurely stop a group header. Windows: Radio buttons were incorrectly shown as read-only controls when opened in a form with default edit-mode. This has been fixed. Now the radio buttons are editable, as they should be. Web: Reactivating an already active document using the process flow caused the interface to be built incorrectly. This problem has been fixed. Web: We've fixed a null reference in the method setComponentSizeUP. This error was only shown in the logs, not to a user. It occurred when a user moved a splitter.

Hello everyone!This week we’ve released the following hotfix:IAM 2021.120210202 - Show open documents With this hotfix the field 'show open documents' will be visible in the menu modeler. This is a Universal feature, for more information see: https://docs.thinkwisesoftware.com/docs/sf/menus.html#hiding-open-documents-on-top-of-a-menu.

Hello everyone,this sprint we've added more awesome features, like a barcode scanner control, the first version of a pivot grid, an immediate export possibility to MS Excel, and a configurable column order in your search tooltip. Another important change is, that you can now try Universal GUI in a beta version. The first beta version was released last week, this is the full version. Changed release flowWe want to make sure that the Universal GUI has the highest quality possible. That is why we will first release a beta version before releasing the full version. We used to release Universal GUI every three weeks on Tuesdays. We will now release the beta version the Friday before that. You will be able to download and test this version yourself. We will use the following week to perform our regression tests and release the full version the next Friday.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 Universal. We'll keep you updated regularly about Universal's progress. Universal version 2021.1.12Don't forget the deployment 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. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal GUI only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and the Software Factory that you plan to use for Universal. Make sure you are using the latest version of Indicium Universal.Download Universal version 2021.1.12 here. Barcode scanner controlIt is now possible to use the barcode scanner control for a domain in Universal. This control can be configured in the menu Data > Domains > tab Form > tab Domain. In the Control field, select 'Barcode scanner (mobile)'.The barcode scanner control is a regular text input with a barcode icon next to it, as can be seen below:When a user clicks the barcode icon, Universal will ask permission to use the camera. If the camera permission has been given, Universal will start scanning in a popup like this:The barcode scanner supports the following barcode symbologies:Aztec DataBarExpanded PDF417 Codabar DataMatrix  QRCode  Code39   EAN-8  UPC-A  Code93  EAN-13  UPC-E  Code128  ITF  1D-Codes DataBar MaxiCode    2D-Codes  By default, the barcode scanner will try to find barcodes with all of the symbologies above. If only a few symbologies need to be supported, the scan performance can be improved by letting the barcode scanner search for only specific symbologies. This can be configured in the config.json file in the Universal GUI folder. For example, when only UPC-E and QRCode are necessary, config.json can be configured like this:{  "barcodeScannerSymbologies": ["UPC-E", "QRCode"],  "defaultApplication": "",  "defaultPlatform": 3,  "loginOptionsDisabled": false,  "installNotificationDisabled": true,  "installNotificationExpirationInDays": 30,  "serviceUrl": "https://web10.thinkwise.app/ng_indicium/iam/iam"} Basic pivot grid availableWe've created a first basic version of a pivot grid. A pivot grid is a textual representation of a graph. It can be used to perform a first analysis of a variety of information available in your application. Interactivity is not available yet. The supported aggregation types are: Sum, Average, Min, Max, or Count.In this first setup, the pivot grid is determined by a cube view in the Software Factory. You can sort the row items on a different cube field, but only if it is present in the cube view. Multiple row items are supported, but only when the data field aggregation is of the type 'Sum'. In your end-application, a user cannot change the dimensions of the cube view. We've planned to add grand totals and subtotals later on.For more information:To put the component on the screen: Screen types. The pivot grid listens to the same configuration as the charts: Cubes.This example calculates the sum of all booked hours per project per status. Immediate export to ExcelWe've added the option to export the data immediately to an Excel file. This file contains translated headers and values. It will take your prefilters into account and will export all the data that falls inside those filters.It looks like this: Column order in the tooltip of a search field is configurableThe tooltip of the Search field in your application shows a list of columns. This list is now determined by the column order for filtering in the Software Factory, in the menu User interface > Subjects > tab Subjects > tab Default > tab Data > tab Filter.In the example below the subject column is placed in front of the employee_id primary key column, which is expected to be the first in the original list of columns in the data model (menu User interface > Subjects > Columns).Column order Custom message for task confirmationWe have added support for setting a custom message in a task confirmation. This allows the developer to ask a different question to the user, to confirm whether or not the task should be executed. In a task confirmation, only the translations can be customized. For more information, see Task confirmation. Process flow: show a report dialog or execute a task without contextIt is now possible to show a report or to execute a task without context when using a process flow. This means you can show reports and execute tasks without the need to add them to any menu's, etc. Lots of minor fixes/tasksIn the Grid, Chart, and Preview component the message 'Data cannot be visualized' was shown wrongly while initializing the subject. This has been fixed, the message won't show any more. We have fixed an issue where initial values flashed back after saving the changes made in edit mode. Now the last changes are shown. When the edited subject is default editable, we do not refresh the entire data set anymore when navigating to the next record, to improve the grid editing performance. Later on, we expect to improve this even more. Tasks without visible parameters could only be executed once and even caused an error after closing the active document. This has been fixed. In a task popup, multiple columns didn't show as set. This has been fixed. Now the popup will no longer become smaller after opening, so it shows the multiple columns based on noOfColumnsInForm and the actual number of columns in the form. After activating a detail tab by a process flow, it is now possible to continue the flow in a sibling detail tab. Before, it was only possible to dive deeper into the subject that the process flow is running on. You can now also navigate back up or side-ways. A process flow wouldn't continue after an 'activate detail' action. This has been fixed, the next process action after an 'activate detail' action will now execute correctly. The Activate document process action now also triggers when opening the document from the menu rather than from open documents. Setting installNotificationDisabled in the config file to 'false' will now actually enable the install notification. To improve the readability in dark mode, the primary color will now be used for the links in the HTML control if no other color has been set manually. What we'll be working on next sprintThe next sprint we'll be working on:Starting tasks using multi-selection. The first basic version of the resource scheduler. Process flows: zoom in on detail. Support TSFSendMessage options and location. The possibility to completely hide the toolbar for a screen type. Pasted links are recognized as and converted to hyperlinks. Performance improvements. Squashing some bugs.

Hello everyone!We've released the following hotfixes this week:SF 2020.2 and up20210118 - Fix task variant trigger for tile image data This hotfix fixes the trigger on task variant so tile images are saved correctly to the database.     IAM 2021.120210120 - Fixed insufficient rights to default menu in i_ui_platform Default menu in Universal is now listening to the role and user group preference settings of the user.

Hey everyone, welcome to the first WinWeb update of the year! We’ve spent the last two sprints of 2020 working on a lot of fixes as well as spending a chunk of our time checking off work for Windows GUI (3-tier).Despite having fewer (wo)manpower hours during the festive season, we’ve still managed to work on a steady 31 work items, mostly focusing on maintenance issues from TCP and continuing on our plan towards getting Windows GUI (3-tier) up and running, along with a feature here and there. Here are our most notable implementations in a row:  New featuresExtended property SmallDetailTiles is now also available for Web.IAM > Global configurations > Extended properties > SmallDetailTiles = yes/noBugs fixedTimeout error after switching detail tabs in Firefox (Web) After editing a date field, Save button was not working on the first click (Web) Error after executing tasks within a process flow (Web) Refresh was not working together with a ‘Close document’ action from another subject within a process flow (Web) Search form component fixed to jump to the given searched term (Windows). Wrong grid grouping bug fixed (Windows) Hiding of password control value for application logic (Windows)Hidden password value in debugger 

Hello everyone!This week we’ve released the following hotfix:SF 2021.1 20210112 - Fix project folder spec This hotfix fixes the project folder specs for the base project. Trigger mechanisms on the project folder spec will then make sure any other file specs in the base project are updated to the correct path as well.  

Hello everyone. Happy new year from all of us from Universal. This sprint we've added more awesome features we think you'll like.We've had an extra release with support for 2021.1. You can read more about it in this blog. This also mean that our versioning scheme has changed to be consistent with other Thinkwise products. So rather than 1.9, the versions will be something like 2021.1.11.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 Universal.We'll keep you updated regularly about Universal's progress.Universal version 2021.1.11Like with every blog, we've released a version so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind:Edge has been updated to use Chromium, which greatly changes the way it works under the hood. We now also recommend this browser to be used for Universal. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and SF that you plan to use for Universal. Make sure you are on the latest version of Indicium Universal.Download Universal version 2021.1.11 hereProcess flowsThis sprint we've implemented two suggested actions: start report and activate document. This is a nice addition to the suggested actions we already support.The activate document process actionThe show report process actionWe also fixed the activate detail flow when the detail is a sibling tab page.Grid summary rowWe've added a summary row to the grid. The supported aggregation types are:Sum Min Max Average CountThis is what it looks like:A grid with a summary rowIndicium DB logIndicium provides access to a database event log. This is only possible when using the SF or when the user is explicitly configured for developer mode in IAM.The database event log can be a bit hard to find for developers. To solve this, a menu item has been added. This is comparable to the Windows GUI where the database event log is also available in the developer ribbon. The menu item is available in SF version 2021.1+.This is what it looks like in the user menu:The new button in the user menuWhen you press that button you'll see a screen like this:The actual DB event logApple splash imagesWe've removed the additional Apple images so it's easier to customize Universal to your branding. This means you'll no longer see a splash screen by default with the Thinkwise logo on Safari (when added to your Home Screen). If the splash screen on Safari (while added to the Home Screen) is necessary, you can edit the index.html file and add the following line to the HEAD tag. <link rel="apple-touch-startup-image" href="%PUBLIC_URL%/placeholder.png"When added, you can place the splash screen image in the Universal folder. In the example above the filename of the image is placeholder.png, but you can call it what you want. The HEAD tag and the filename should match.Unit testsIn the past three weeks we've added another 25 unit test cases to the components and inner workings of Universal. We also removed many unit test cases that were obsolete due to 2021.1 support. This brings us up to 1783 test cases in total.Lots of minor fixes/tasksBugsThe install notification is now disabled when the config properties are missing Clearing a lookup control will now also focus the lookup controlTechnicalSecurity fixes for 3rd party componentsWhat we'll be working on next sprintThe next sprint we'll be working on:A simple pivot component for the cube view Barcode scanner control Making the grid more performant A few process actions Show task dialog (without context) Show report dialog (without context) Exporting all data to a file Squashing some bugs

Hello everyone!This week we’ve released the following hotfixes:SF and IAM 2019.1 and up 20201222 - Look-up table variant for variants When using table, report or task look-ups, it is possible to choose a look-up table variant. This means that the look-up for the table/report/task will show the selected variant instead of the main table/report/task. It is also possible to use this same setting on variant level. However, in this scenario the Universal GUI would also use the look-up of the main table instead of the look-up as provided on variant level. This is now fixed. 20201224 - Universal look-up refactor This hotfix has been released to allow Software Factories and Intelligent Application Managers of version 2020.2 and earlier to allow them to be compatible with version 2021.1 of Universal. In doing so, the Software Factories and Intelligent Application Managers affected by this hotfix will no longer be compatible with Universal 1.8 and earlier. Update your Universal and Indicium accordingly. More info in this blog post. SF 2021.1 20201222 - Decision and appl connector system flows Using a decision node or application connector in a scheduled process flow will now allow the schedule to be synced to IAM properly. The validation warning about an user action when this was the case has been updated as well. In addition, the validation warning about an action requiring user input will now properly warn the developer when delete row, add row, update row, execute task or report is used in a scheduled system flow.         SF 2020.1 and up 20201224 - Unit test trigger parameter Computed columns are now excluded when running a trigger type unit test. These columns are read only and cannot be inserted or updated.

Hello everyone,The first version of Universal with support for Thinkwise Platform 2021.1 has just been released.The version number is 2021.1.10. Subsequent versions of Universal will also adhere to this version numbering structure to indicate the Thinkwise Platform version compatibility. This matches our other runtime components such as Indicium and other GUIs.RequirementsUniversal 2021.1 requires an Indicium Universal with at least version 2021.1 to be installed.Hotfix for earlier platform versionsUniversal 2021.1 is backwards compatible with earlier versions of the Thinkwise Platform as per our lifecycle policy.However, to be able to use Universal 2021.1 with Thinkwise Platform version 2020.2 or earlier, a hotfix that has been released today must be executed in those environments. This hotfix affects both the Software Factory and the Intelligent Application Manager.The hotfix can be recognised as 20201224 - Universal look-up refactor.Note that this hotfix for Thinkwise Platform version 2020.2 and earlier to support Universal 2021.1 does not allow for compatibility with older versions of Universal.Once the hotfix is in place to support Universal 2021.1, Universal version 1.8 and earlier cannot be used anymore.Indicium version 2021.1 is also required to run on earlier versions of the Thinkwise Platform. This version is also backwards compatible as per our lifecycle policy.More infoFeature-wise, this version is identical in features to the earlier released 1.8 version. More info here.Download Universal 2021.1.10 here. The most recent version of Indicium and the hotfixes for the Software Factory and IAM can also be found in TCP.Happy holidays!

Hello everyone.This sprint we've added a few more process flow continued actions like activate detail, add row and edit row. We've also made installing Universal on your device as an app (this is what PWA is all about) much easier and we've made quite a few other improvements to Universal.This release does not yet have 2021.1 support. We have mostly finished development and at the moment we are testing and reviewing column authorization. We will do an extra release with 2021.1 support no later than Tuesday. The first version of Universal that supports 2021.1 will be 2021.1.10.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 Universal.We'll keep you updated regularly about Universal's progress.Universal version 1.8Like with every blog, we've released a version so you can test Universal out for yourself.Don't forget the documentation and be sure to keep the following in mind:Edge has been updated to use Chromium, which greatly changes the way it works under the hood. We now also recommend this browser to be used for Universal. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and SF that you plan to use for Universal. Make sure you are on the latest version of Indicium Universal.Download Universal version 1.8 hereProcess flowsThis sprint we've implemented three suggested actions: activate detail, add row and edit row. This is a nice addition to the suggested actions we already support (you can find those in this blog).A process flow that activates a detail and then performs add row A process flow that activates a detail and then performs edit rowPWA install optionsIt's possible to install Universal as an app. This sprint we've improved how this works. We've added a button in the user menu. On platforms that support direct installation, you will get the option to install Universal as an app directly. On platforms that do no support this, you will get instructions on how to install it yourself.We've also added a config option to get the notification automatically, so the user doesn't even need to go to their user menu. We will be testing and reviewing this a bit more, so for now we've set this to disabled. When this is done we'll enable getting the notification automatically by default.This is what it looks like:Install on Chrome on androidLive video Install on iOsLive videoConfiguration PWA for installationWhen you want to install Universal as an PWA you want to apply your own branding. This can easily be done by opening the configuration file manifest.json (inside the Universal folder). The name and short_name options are used to indicate the name of the app. You can also adjust the images like logo.png, logo-512.png and favicon.ico.Configure install notificationIf you want to let your users know they can install Universal on their Home Screen, we have support to show an notfiication. This notification will be shown when the user has logged in, but this can be disabled in the config.json (inside the Universal folder). In the config.json you'll find a option called installNotificationDisabled , which can be set to true to ignore the install notification or false to show the install notificationThe install notification will not be frequently shown to the user, after they either installed or canceled the notification will be suspended for 30 days. The 30 days are based upon the config.json option installNotificationExpirationInDays , which can be configured to be more or less. After the 30 days are passed the user will one again receive an install notification.Unit testsIn the past three weeks we've added another 26 unit test cases to the components and inner workings of Universal. This brings us up to 1782 test cases in total.Lots of minor fixes/tasksBugsDetail tabpages will now load data even if the parent has no components that need lookupsUI/UXThe error messages on the login screen no login disappear after a short amount of time Scrolling in the sidebar on mobile no longer opens menu groups When there is no row selected, the preview component will say that there is no preview available rather than no matching record found. The back button of your mobile device no longer exits the app The form in task and report popups now listens to the SF setting for Number of cols in form The form in task and report popups now listens to the SF setting for Field width and Label width It's now possible to not show image upload in the cardlist menu by setting the extended property HideMenuImageUpload to trueTechnicalTable parameters in messages are now translated, rather than getting something like `dbo.hour`, you will get `Hour`. Fixed vulnerability in 3rd party dependencyWhat we'll be working on next sprintThe next sprint we'll be working on:Implementing the summary row for the grid Implementing a simple pivot component Research for the resource scheduler Continued process flow actions: Activate document Show report dialog

Hello everyone,This week we have released the following hotfixes:SF & IAM 2019.1 and up 20201215 - i_ui_tab_detail directional translations View i_ui_tab_detail will now supply the correct directional translation when one is used for a link table. Please see https://docs.thinkwisesoftware.com/docs/sf/translations.html#link-tables for more information on directional translations for link tables. SF 2021.1 20201216 - Fix code file paths This hotfix resets the base project code file paths to the base value. The file paths will then be properly replaced again with the project version file paths when generating. IAM 2021.1 20201216 - Scheduling sync Fixed an issue where synchronizing to IAM was not possible because a field was wrongly designated as mandatory.

Hey everyone, we’ve kept ourselves busy during the last couple of sprints with a lot of general maintenance and support for Windows GUI (3-tier) as well as feature support for our latest release, one of the earliest of 2021’s versions.In this time we’ve put away 34 work items, mostly general maintenance with more than a quarter of which were features, along with quite a few work items specifically for one of our customers. Here are some of our notable improvements to the Windows and Web interfaces you might already have noticed:New featuresApplication icon now shows as favicon (Web) Cache is written to the AppData by default (Web) Scheduler features 2.0 in Windows (Acto) Support for AWS File storage and support subfolders is now complete (Win/Web) Screentype designer in SF now allows the tab page icon to be uploaded using a file dialog, as seen below in the Windows interface. Starting tasks from a grid row (Win/Web) Bugs fixedFiles were being re-uploaded when any other data within the same record was being edited. (Windows GUI + Indicium) Default input parameters were affecting the output field values after editing. (Windows GUI + Indicium) Could not save row when copy was being used during an ongoing process flow. (Windows) Mandatory prefilter groups were not being applied correctly. (Win/Web) Incorrect data was showing in the detail tabs of grouped grids. (Web) Menu disappeared after switching applications (Web)

Hello everyone!Here are the hotfixes we’ve released this week:SF 2019.1 and up 20201202 - Flag modified process actions This hotfix ensures that when you change a domain, the process action procedures that use this domain are also recreated during an upgrade. 20201204 - Process action variable mapping Fixed a possible inconsistency between model objects and process action variable mapping that could occur when the model object was copied. IAM 2019.1 and up 20201124 - Fix for XML escaped characters When converting to XML raw, columns containing an "_x" in it"s name are escaped to "_x005F_x". This occured when synchronizing to IAM, which resulted in the top statement for cube view fields not being honored in IAM. This has now been solved by adjusting the synchronization procedure in IAM for cube view fields.

Hello everyone. This sprint we've spent a lot of time on unexpected fixes for auto-edit and auto-save. This means that the process actions for activate detail, add row and edit row have been pushed back a release.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 Universal.We'll keep you updated regularly about Universal's progress.Universal version 1.7Like with every blog, we've released a version so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind:Edge has been updated to use Chromium, which greatly changes the way it works under the hood. We now also recommend this browser to be used for Universal. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and SF that you plan to use for Universal. Make sure you are on the latest version of Indicium Universal.Download Universal version 1.7 hereAuto-edit and auto-saveIn case you missed it, we did an extra release since the last blog, this included:Immediately change checkbox value in grid when clicking on any row when auto-edit is on Only save changes when leaving the grid row when auto-save is on Changing rows in the grid is no longer possible when in edit mode Prevent heavy flickering in the grid when editingThis is what it looks like:Setting checkboxes with auto-edit and auto-saveProcess flowsThis sprint we've improved the actions we've already implemented. Actions like open document and execute task now work much better. More specifically we did the following improvements:Universal now informs Indicium of the current context after a continued action. This fixes that some process actions didn't execute. Fix process flows sometimes having a bad url Fix error with process flows when logging out while in a flowUnit testsIn the past three weeks we've added another 4 unit test cases to the components and inner workings of Universal. This brings us up to 1756 test cases in total.Lots of minor fixes/tasksBugsFixed error when executing a task or report from the menu when it had validation errors Fixed fields errors being cut off in the form Fixed group headers overflowing in form fields when there were validation errors The tiles menu now has the correct background color in dark mode when the background image cannot be loaded Fixed a bug where details sometimes wouldn't load if the parent had no other visible screen componentsUI/UXThe card list now listens to field height in positions correctlyTechnicalImproved the way we perform a search. This also makes it possible to search for domain element translations. (For the technically minded, we implemented $search)What we'll be working on next sprintAs the year is coming to a close, we'll be working on support for the 2021.1 release. The effective application of column authorization doesn't work in Universal yet, so we'll be implementing that next. Besides that we'll be fixing issues that were reported by our customers. We already started development on the process actions for activate detail, add row and edit row, so we'll complete those. We will not pick up other new features this year. We also started work on implementing a button to install your application, we'll complete that as well.The next sprint we'll be working on:2021.1 support Continued actions: Activate detail Add row Edit row Install as application Squashing several bugs

With December fast approaching and the days getting shorter and shorter, 2020 is coming to a close. And what a year it has been. With all the changes to our daily lives we’ve faced over the year, one thing that hasn’t changed is our commitment to developing quality software. And with the 2021.1 release of the Thinkwise Platform we’ve added a feature that will help everyone achieve the same.The quality dashboard is a new feature that shows an overview of the quality of your projects. It does this by looking at a number of quality metrics and scoring them. The quality dashboard is an excellent tool for locating any areas in your project that might need a little boost in quality.The quality dashboard measures the quality of your projectsOf course that’s not all. This release comes with loads of new features, such as:Unauthorized columns AWS S3 file storage support Message protocol independent web services for process flows Expressions in default values Creating personal ERD diagrams from existing diagrams Estimations for requirements and design Copy tasks for work, requirements and business processes And many more features and changes which can be found in the release notesThe Thinkwise Platform 2021.1 is now available for download in TCP. Important Universal GUI note:Indicium Universal (as API) and the Universal GUI and are currently not yet compatible with the 2021.1 release of the Thinkwise Platform. If you use Indicium Universal (as API) or the Universal GUI, we strongly advice to wait with upgrading your Thinkwise environment. We expect a fully compatible Indicium Universal and Universal GUI to be released in a couple of weeks.

Hello everyone. This sprint we've done a lot of research for the pivot grid, grid aggregate rows and more. Besides that, we've implemented some awesome features like the editable domain combo for the grid, hiding open documents and much more.In case you missed it, we did an extra release since the last blog, this included:The start task process flow suggested action Fixed a bug where URL hardening would break subsequent requests Popups from HTML control now break sandbox mode Added support for previewing documents that become a pdf (e.g. Word documents)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 Universal.We'll keep you updated regularly about Universal's progress.Universal version 1.6Like with every blog, we've released a version so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind:Edge has been updated to use Chromium, which greatly changes the way it works under the hood. We now also recommend this browser to be used for Universal. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and SF that you plan to use for Universal. Make sure you are on the latest version of Indicium Universal.Download Universal version 1.6 hereHide open documentsWe've gotten the suggestion that you might not want to show the open documents in some instances. Like searching in the menu, this takes up space. For example in a small mobile application with only a few menu items, it might not be desirable to have a section on top of the menu that shows the open documents. We've implemented the option to hide the open documents. This works for the all menu's, so:Listbar Tree TilesRight now this option can be enabled by adding an extended property called HideOpenDocuments. The value of this extended property doesn't matter, the open documents will be hidden as long as it's present.The open documents are truly hidden, they are not gone. This means that it's still possible to open a different document while the first one still has unsaved changes. You still will need to save or discard those changes when logging out for example. We recommend this feature is used only for compact applications.In the future this will be set via a checkbox in the SFThis is what it looks like:Universal with no open documentsEditable domain combo control in the gridThe next editable control that has been added to the grid is the domain combo control. We've implemented both the combo and the image combo.Here it is in action:The editable domain comboMultirow grid selectionIt is now possible to select multiple rows in the grid. For now this works on desktop. The mobile variant is much more involved (you don't have a keyboard on mobile) and will be implemented later.You can use shift to select a range of rows, and you can use control to add or subtract individual rows to the selection.While you can have multiple selected rows, you still only have one active record (that's the one you also see in the form). We've made the distinction between selected and active rows greater by giving the active row a left border in the primary color.For now it's not possible to perform actions on all selected rows; delete or executing a task will be performed on the active row. The next step will be to implement performing actions on multiple rows.This is what it looks like:Multiselection in the gridProcess flows: Open documentAs mentioned in the intro, we had already published a version of Universal with the suggested action to start a task. Besides that action, we have also implemented the suggested action open document.The following demo shows both in action:A process flow that first starts a task and then opens a documentMandatory exclusive prefilter groupsIt's possible to have mandatory prefilters that are exclusive. This is only possible when the prefilter group is exclusive. We've now implemented this for Universal.We prevent the user from turning off the currently active prefilter in a mandatory exclusive group.This means that all prefilters in an exclusive group are hidden and turned off when a hidden prefilter in that group is enabled.All prefilters will get locked and turned off when a locked prefilter in the group is enabled.This is what it looks like:Mandatory exclusive prefiltersUnit testsIn the past three weeks we've added another 41 unit test cases to the components and inner workings of Universal. This brings us up to 1752 test cases in total.Lots of minor fixes/tasksBugsFixed a bug where the layout wouldn't execute properly if the column id contained the string _type Fixed a bug where the form would sometimes not activate when going into edit mode in a breakpointUI/UXThe user now gets redirected to the Universal login screen after resetting their password Badges now also work for variants The update notification no longer mentions a version number (this version was wrong)TechnicalRemoved an erroneous leading / in the location header, causing requests to Indicium to fail in certain instances Added support for untranslated lookupsWhat we'll be working on next sprintThe next sprint we'll be working on:Allow tasks and reports to be started using multi-selection More process flows suggested actions Activate a detail Add row Edit row Add support for v2021.1 column authorization Grid summary row Simple pivot component Squashing some bugs

Hey everyone, this auspicious new version number brings with it some cool new features and many improvements to the Windows and Web interfaces from the last couple of sprints. Since our last update, we’ve put away a sweet 40 more user stories, a quarter of which were performance enhancements and features, the rest being reported bugs. Check out some of our more notable improvements : New FeaturesDouble-click to execute a task in a grid : this is so cool we dedicated a separate blog to elaborate (Windows+Web) Introduced expressions as a default value for columns, task/report parameters, and process variables (Windows+Web)Configuring a field with an expression field as a default value Introduced AWS S3 filestorage support (Windows+Web) PerformanceIntroduced new extended property RunAsyncTasksInSequence to run the execution of multiple asynchronous tasks in sequence (Windows)Bugs fixedConcerning map components in Web: Context menu in combination with maps was not showing Locations on maps were not showing Debug screen remained empty after a clear-all (Windows) Updating a PK value when on an Indicium connection went wrong (Windows) Quicksearch in the grid didn’t always work (Web) Tasks involving Azure uploads would create empty renamed documents (Windows+Web) 

Hello everyone! This sprint we've added some nice features and squashed a lot of bugs.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 Universal.We'll keep you updated regularly about Universal's progress.Extra release (1.5.2)We made an extra release (1.5.2) since the publication of this post. It contains:A fix to allow the previewer to display files that become a pdf (e.g. Word, pdf, PowerPoint) Added support for the suggested action: start task Fixed an error when executing some process flows (Cannot read items of undefined) We now strip query strings from the Location header (so Universal doesn't break when URL hardening is activated) Popups from the HTML control now break the sandboxUniversal version 1.5.2Like with every blog, we've released a version so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind:Edge has been updated to use Chromium, which greatly changes the way it works under the hood. We now also recommend this browser to be used for Universal. Universal must be deployed on the same server as Indicium or it should be an allowed origin in appsettings.json. Universal only works with version 2019.1 and up of the Thinkwise Platform. Furthermore, make sure you run all hotfixes on the IAM and SF that you plan to use for Universal. Make sure you are on the latest version of Indicium Universal.Download Universal version 1.5.2 hereProcess flowsWe've done a lot of work on process flows. We've added a lot of start actions (those are actions the user performs that start a process flow) and one suggested action (those are actions that the process flow wants to perform).We've implemented the following actions that can start a process flow:Opening a document Activating a document Executing a task Executing a report Adding a record Editing a record Deleting recordWe've implemented the following suggested action:Refresh Start taskBesides the refresh action it's also possible to use all connectors since those are handled by Indicium:Database connector FTP connector HTTP connector SMTP connector Run AutoML model File connectors Copy file Copy folder Create folder Delete file Delete folder Move file Move folder Read file Write file Convert Convert JSON to XML Convert XML to JSON Some other things to note:We prevent multiple process flows from starting against the same document. We ignore incoming process flows if there is already one active. Suggested actions always wait until it's completed succesfully or until it's failed. We clear out the process flow if the document gets closed or if the flow succeeded.Next sprint we'll add the suggested actions for opening a document.Preview componentThe preview component now uses a PreviewUrl provided by Indicium. Indicium transforms the documents into a format that Universal can use. This means we now support previewing Excel and msg/email formats.Documents that become a pdf (e.g. Word, pdf, PowerPoint) are also supported.This is what it looks like:Preview of an Excel documentUnit testsIn the past three weeks we've added another 41 unit test cases to the components and inner workings of Universal. This brings us up to 1711 test cases in total.Lots of minor fixes/tasksBugsFixed a bug where you couldn't delete anything anymore when a delete failed (e.g. because the record had children) You can now correctly search for a quote (') Fixed a bug where lookup controls wouldn't load options if the data was filtered by a previous column (e.g. project > subproject > activity, what is shown in subproject depends on the project you've chosen). You no longer get a fatal error when you press multiple times on a scrollbar in iOS Fixed alignment of the bottom border of domain controls in the form A date primary key now gets passed as a date rather than datetime Fixed a bug where Universal could crash if mandatory task parameters weren't filled in Fixed some lookups not loading in tasks or reportsUI/UXThe topbar now has the correct background color The theme type (light or dark mode) now gets applied correctly from the SF settings If a column is a lookup, we now always show a lookup control in the grid, regardless of the chosen control type Implemented disabling tasks when there are no records (enable_tab_task_when_empty in the SF) Technical database messages are translated properly now (e.g. Hour analysis rather than dbo.hour_analysis)TechnicalResolved security issues in 3rd party packages Added support for meta version 2021.1 Did the groundwork for multirow selection Links from the HTML control now break the sandbox Query parameters for the Location header are now stripped awayWhat we'll be working on next sprintThe next sprint we'll be working on:Technical changes for 2021.1 Mandatory exclusive prefilter groups Redirect to Universal after resetting password Untranslated lookup selection Research for the pivot grid component Domain combo control for the grid Process flows: opening a document Hiding the open documents Badges per variants Squashing some bugs