Product Updates

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

November 26, 2021: Full release from version 2021.3.13 BETA. Hotfixes: We fixed two bugs that caused the Universal GUI to crash when the session had expired or the user had logged out. We fixed errors that occurred when a task deleted the current record. Hello everyone, In this sprint, we added support for showing messages thrown from the Badge logic and we now support the lookup control type 'Combo (sorted)'. We also improved some features, like the form's HTML editor, and fixed some issues. 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. Contents of this release Universal GUI version 2021.3.13 Changed Tasks marked as "double click" hidden in the toolbar Process flow continues in the last document when the follow-up action says so New Messages from the Badge logic Support for 'Combo (sorted)' HTML edit / non-edit popup Minor fixes and tasks What we will be working on next sprint Universal GUI version 2021.3.13 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 the 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.13 here Changed Tasks marked as "double click" hidden in the toolbar Tasks marked as ‘double click’ are hidden in the toolbar now. This setting is available in the menu Processes > Tasks > tab Table tasks > tab Form. Process flow continues in the last document when the follow-up action says so We made process flows a little smarter when running outside the context of a document, e.g., when running a task from the menu. When the follow-up action points to a subject, it tries to find it in the last involved open document of the flow. This is helpful when running a task that should not be accessible from the document's toolbar. The task can be executed globally filled by process variables, and afterward, the flow can continue in the active document. We strongly advise you to thoroughly test your process flows if they contain one of the following actions: add / copy / edit / delete task / report execution open / activate / close document zoom detail. New Messages from the Badge logic Like the other GUIs, the Universal GUI now shows messages thrown from the Badge logic. Notice that the badge may be displayed multiple times and run again after a certain interval. As a Software Factory developer, you are responsible for preventing messages from popping up multiple times. Support for 'Combo (sorted)' Universal GUI now supports the lookup control type 'Combo (sorted)', so you can configure a combo in another way than just alphabetically. This setting is available in menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > field Def. control. Note that: Some more complicated combinations of sort fields, like a domain element with values followed by another sort on a lookup field, are not yet available. This lookup control type is not yet available for lookup controls in the filter form. HTML edit / non-edit popup We have improved the form's HTML editor. It is now possible to show and edit the formatted document in a larger popup. You can click on the new icon to open the popup for editing HTML in edit mode. The formatting toolbar (to make text, for example, bold) has also been moved to the popup. In the form editor, you can still edit the text in the currently applied format. In both the popup and form editor, you can use the shortkeys for formatting. In non-edit mode, you can use the popup to inspect the contents in a larger display. This was the previous HTML editor, with the formatting toolbar: Previous HTML editor with formatting toolbar Now, the formatting toolbar has been removed, and a popup icon has been added: New editor without the formatting toolbar, but with a popup icon The new popup in edit mode now contains the formatting toolbar: The new popup editor in edit mode, with formatting toolbar This is the new popup in non-edit mode (read-only): The new popup editor in non-edit mode (read-only, no formatting toolbar) This is only the first release of this feature. For future releases, we have planned: To replace the Close button with Save/Cancel buttons. Now, after opening the popup while editing, changes made to the HTML text are always synchronized. Later on, the Cancel button should provide the option to ignore them. To improve the styling of the formatting toolbar. We wish to apply equal padding at the top and bottom and add a border between the buttons and content. To solve a known issue, which has been in the Universal GUI for a couple of releases. At the moment, scrolling in the HTML control of the form in edit mode is not possible with the scroll wheel. Manually grabbing the scrollbar still works. We will plan this as a separate issue. Minor fixes and tasks Messages from a process flow now show parameter values. In some cases, a type error 'Cannot read properties of undefined (reading 'applications')' occurred when the login token had expired. This has been fixed. When adding a record in a task was followed by a Go to row process action, the new record was not selected. This has been fixed. The controls for the Cortex and regular barcode scanners used to lose focus when the scan button was still loading. This has been fixed. The input now retains the focus. We fixed two bugs that caused the Universal GUI to crash when the session had expired or the user had logged out. These bugs made the GUI unusable with a `reading properties of undefined` error that kept recurring. We are working on a final fix to prevent these types of errors when logging out. That final fix will be available next release. For now, the Universal GUI will no longer become unusable when such an error occurs. We fixed errors that occurred when a task deleted the current record. What we will be working on next sprint The next sprint we will be working on: Record not found on lookup open - When a look-up popup is opened and the selected record is not in the current filtered set, it should try to fetch the record by removing all the pre-filters. Lookup from grid Ctrl+Alt+P shortcut - Open the look-up for the currently selected field in the grid with the Ctrl+Alt+P shortcut. Form list design Automated testing General maintenance.

Hello everyone, In this sprint we have updated the DevExpress Report Designer, and we have 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.16 here. Download Web GUI 2021.3.16 here. New DevExpress Report Designer updated to Devexpress version 21.1.6 (Windows GUI & Web GUI) The DevExpress Report Designer has been updated to DevExpress version 21.1.6. Version 1.50 from the Devexpress Report Designer can now be downloaded. Double-click task support (Windows GUI & Web GUI) We have added formal double-click task support to the Windows and Web GUIs. This concerns task execution by clicking twice on a row. The formal setting is available in the menu Processes > Tasks > tab Table tasks > tab Form > checkbox Grid double click. It has been part of the Software Factory since the 2021.2 release, and that release has already upgraded all double-click extenders to the formal model. Therefore, we no longer support the double-click extenders set in the menu Projects > Full model > Extender. If you have made changes to the double-click extenders since the 2021.2 release, please update the formal model so that all functionality remains the same. Minor fixes and tasks (Windows GUI) We fixed an issue regarding auto-refresh. Previously, when you had auto-refreshes in child subjects and switched to a new subject, the old auto-refresh would persist. This resulted in unnecessary refreshes that negatively impacted the user experience. (Windows GUI & Web GUI) We have fixed a DevExpress report export bug caused by a missing required DevExpress DLL. Released as hotfix (Windows GUI) When entering values in the zoom editor of a text field with the Multiline control, the changes were lost when the zoom editor was closed. This has been fixed, and the changes are now also updated in the form field once the zoom editor popup has been closed.

Hello everyone, It has been a while since the Thinkwise Deployment Center (or 'Deployer' for short) has received new features, but over the past year, we have been gradually reworking the code to support some of the most frequently requested ones. There have been a couple of breaking changes compared to the last version, which we will highlight in this post. Download the Thinkwise Deployment Center 2.0.2 here. Deployer GUI and CLI New Support for specifying manifests as YAML Deployer GUI BREAKING CHANGES No more GUI and Indicium deployment during IAM installation and upgrade No more assistance for selecting a target meta source for Indicium and GUIs New Landing page rework Universal GUI deployment Installing a Universal GUI Upgrading a Universal GUI Local IIS support Indicium deployment reworked Windows GUI deployment reworked Web GUI deployment reworked Known issues Indicium application initialization not configured properly when using IIS API Deployer CLI BREAKING CHANGES Changed command-line library New Indicium commands Universal GUI commands Generic IIS commands Next release Deployer GUI and CLI New Support for specifying manifests as YAML In addition to the current JSON manifests: { "schema": 2, "products": [ { "type": "IAM", "version": "2021.3", "projectFolder": "T:\\Product Innovation\\Applications", "dependencies": [ "CompatibilityLevel130" ], "packages": [ { "type": "Install", "path": "IAM/Install", "defaultDatabaseName": "THINKWISE_IAM" }, { "type": "Upgrade", "path": "IAM/Upgrade", "supportedVersions": [ { "version": "2021.1", "upgradesTo": "2021.2", "files": [ "2021.2\\020_Upgrade.sql", "2021.2\\030_Checks.sql", "2021.2\\040_Constraints.sql", "2021.2\\050_Indexes.sql", "2021.2\\060_Functions.sql", "2021.2\\065_Table_valued_functions.sql", "2021.2\\070_Views.sql", "2021.2\\080_Procedures.sql", "2021.2\\090_Instead_of_triggers.sql", "2021.2\\100_Triggers.sql", "2021.2\\110_Tasks.sql", "2021.2\\120_Defaults.sql", "2021.2\\130_Layouts.sql", "2021.2\\140_Contexts.sql", "2021.2\\145_Badges.sql", "2021.2\\150_Processes.sql", "2021.2\\999_Apply_roles_on_database.sql", "2021.2\\999_Manual.sql" ] }, { "version": "2021.2", "upgradesTo": "2021.3", "files": [ "2021.3\\020_Upgrade.sql", "2021.3\\030_Checks.sql", "2021.3\\040_Constraints.sql", "2021.3\\050_Indexes.sql", "2021.3\\060_Functions.sql", "2021.3\\065_Table_valued_functions.sql", "2021.3\\070_Views.sql", "2021.3\\080_Procedures.sql", "2021.3\\090_Instead_of_triggers.sql", "2021.3\\100_Triggers.sql", "2021.3\\110_Tasks.sql", "2021.3\\120_Defaults.sql", "2021.3\\140_Contexts.sql", "2021.3\\150_Processes.sql", "2021.3\\999_Apply_roles_on_database.sql", "2021.3\\999_Manual.sql" ] } ] }, { "type": "Hotfix", "path": "IAM/Hotfixes" } ] } ]}YAML can now also be used: schema: 2products: - type: "IAM" version: "2021.3" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel130" packages: - type: "Install" path: "IAM/Install" defaultDatabaseName: "THINKWISE_IAM" - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.1" upgradesTo: "2021.2" files: - "2021.2\\020_Upgrade.sql" - "2021.2\\030_Checks.sql" - "2021.2\\040_Constraints.sql" - "2021.2\\050_Indexes.sql" - "2021.2\\060_Functions.sql", - "2021.2\\065_Table_valued_functions.sql" - "2021.2\\070_Views.sql" - "2021.2\\080_Procedures.sql" - "2021.2\\090_Instead_of_triggers.sql" - "2021.2\\100_Triggers.sql" - "2021.2\\110_Tasks.sql" - "2021.2\\120_Defaults.sql" - "2021.2\\130_Layouts.sql" - "2021.2\\140_Contexts.sql" - "2021.2\\145_Badges.sql" - "2021.2\\150_Processes.sql" - "2021.2\\999_Apply_roles_on_database.sql" - "2021.2\\999_Manual.sql" - version: "2021.2" upgradesTo: "2021.3" files: - "2021.3\\020_Upgrade.sql" - "2021.3\\030_Checks.sql" - "2021.3\\040_Constraints.sql" - "2021.3\\050_Indexes.sql" - "2021.3\\060_Functions.sql", - "2021.3\\065_Table_valued_functions.sql" - "2021.3\\070_Views.sql" - "2021.3\\080_Procedures.sql" - "2021.3\\090_Instead_of_triggers.sql" - "2021.3\\100_Triggers.sql" - "2021.3\\110_Tasks.sql" - "2021.3\\120_Defaults.sql" - "2021.3\\130_Layouts.sql" - "2021.3\\140_Contexts.sql" - "2021.3\\145_Badges.sql" - "2021.3\\150_Processes.sql" - "2021.3\\999_Apply_roles_on_database.sql" - "2021.3\\999_Manual.sql" - type: "Hotfix" path: "IAM/Hotfixes" Deployer GUI BREAKING CHANGES No more GUI and Indicium deployment during IAM installation and upgrade In the old Deployer, when installing or upgrading IAM, you would be asked if you liked to install an Indicium or any of the GUIs. However, since new deployment options for those products have been introduced, configuring them during the IAM flow has become quite complicated. For this reason, we have decided to remove the ability to deploy other products during the IAM flow. The Deployer was always meant as a helper tool for deploying our products, and thus we expect someone using it to at least know the basic cohesion between our products. So, as a user, you should know which products you need to deploy and in which order to make your environment work. For more information, we recommend reading the Thinkwise Platform Overview section on our documentation site. No more assistance for selecting a target meta source for Indicium and GUIs Previously, the deployment flows of Indicium and the Windows/Web GUI had steps for selecting a target IAM to use as the meta source. Due to the new way we configure these products in this release, we had to cut these steps from the flow. We are looking into the possibility of adding additional buttons to the configuration steps that have a Simple mode to once again select a meta source with the assistance of UI dialogs. New Landing page rework Due to adding more options and splitting existing ones to accommodate the deployment process better, the number of items on the landing page got rather long. To solve this problem, we have reworked the landing page to group the deployment options per product. You can find them in a drop-down menu on the left side of the landing page. Product menu on the landing page Universal GUI deployment We added the ability to install or upgrade the Universal GUI on an IIS server. The landing page of the Universal GUI Installing a Universal GUI The process to install a Universal GUI has been broken down into: Select the site on IIS where to deploy the Universal GUI. Select an empty path relative to the selected site. Specify the contents for the Universal GUI's config.json configuration file. The configuration step supports two modes: Simple and Advanced. In the Simple mode, you can only change the basic options for running a Universal GUI: Universal GUI Simple configuration To configure an option not listed in the Simple mode, you can use the Advanced mode instead. In the Advanced mode, the Universal GUI will only check if the serviceUrl property has been specified correctly. Other options are used as-is. Universal GUI Advanced configuration Upgrading a Universal GUI The process to upgrade a Universal GUI has been broken down into: Select the IIS site containing the Universal GUI to upgrade. Select the path relative to the site that contains the Universal GUI installation. Optionally change contents for the Universal GUI's config.json configuration file. Just as with the installation process, you can select either the Simple or the Advanced mode to upload a new config.json file. You can choose to skip this step altogether and keep the current config.json in the installation directory. Optionally, mark any additional files that contain settings for changing how the Universal GUI works. Universal GUI: files/folders of the current installation to preserve Local IIS support An important feature request we received was the ability to deploy products to an IIS instance running on the current server without the need for the Microsoft IIS Administration API. After a considerable effort in re-implementing the entire IIS deployment code, this has been made possible. Products that deploy to IIS now have both a Local and an IIS API option on the landing page: IIS API deployment options on the landing page This is available for the following products: Indicium Indicium for Mobile GUI Universal GUI Web GUI. Indicium deployment reworked The deployment process for Indicium and Indicium (Mobile) has been reworked. Previously, there was a single deployment option for both installation and upgrading. This made the logic for the deployment more convoluted than necessary, and it made it harder to add new features to the process. For this release, we have split the single deployment process into separate install and upgrade flows. Just like with the Universal GUI process, there is now a dedicated step to configure Indicium's appsettings.json. Both the Simple and Advanced modes are included, and the step can be skipped during the upgrade process. Indicium: Simple mode for configuring the appsettings.json Additionally, there is an option to help configure the application initialization feature for Indicium. When running Indicium as an agent of an IAM, e.g., to generate projects in the Software Factory 2021.3 or run scheduled system flows, we recommended turning on this feature. Additional Indicium settings Lastly, just like with the Universal GUI process, it is now possible to retain certain files as-is inside the installation that is being upgraded. Indicium: files/folders of the current installation to preserve Windows GUI deployment reworked The deployment process for the Windows GUI has been reworked. Just like with Indicium, there was previously only one deployment process for the Windows GUI. This process has also been split into separate installation and upgrade flows. Additionally, we have added an option to only create a new startup configuration file (.ini) by selecting an existing installation. Windows GUI deployment options on the landing page When creating a startup configuration for the installation, there are three options to choose from: Create new Link existing Skip. By choosing Create new, you can load a preset template based on the meta source connection you are going to use and then modify it with the required values. When using the Indicium template, make sure that the Windows GUI you are using supports it. Create a new configuration file for the Windows GUI If you choose Link existing, e.g., to create a shortcut later in the deployment process, simply enter the path to the desired ini file. Windows GUI: link an existing startup config to this installation If you select the Use ClickStart option, any shortcuts made during this deployment will target TSF_CS.exe instead of TSF_dotNET.exe. It is possible to modify the clickstart.ini to configure the behavior of TSF_CS.exe. Windows GUI: configuring the ClickStart ini Lastly, you can either Skip creating or create a new shortcut that links the selected startup configuration to the Windows GUI installation. Remember that selecting Use ClickStart in the Startup configuration step will make this shortcut to TS_CS.exe instead of TSF_dotNET.exe. Windows GUI: create a shortcut for the startup configuration Web GUI deployment reworked Just like in the Indicium and Windows GUI deployment, the Web GUI deployment has been split into separate installation and upgrade flows. This rework is not as broad as the other two, but we have enabled the options to enter your own settings.ini and to preserve files/folders when upgrading. Configure the settings.ini of the Web GUI Known issues Indicium application initialization not configured properly when using IIS API Currently, the Microsoft IIS Administration API does not expose the properties we need for configuring the application initialization feature properly for Indicium. We have made pull requests to the official repository on GitHub to try and fix this, but there will seemingly only be one more update by Microsoft to this repository to upgrade the software to .NET 6. We are currently discussing whether it is worth it to continue support for this way of deploying our products. Deployer CLI The command-line version of the Deployer has also received some updates. Some of these updates are breaking changes compared to the previous version. BREAKING CHANGES Changed command-line library The previous version of the Deployer used a command-line argument parser that did not support sub-commands. Due to this, several command names were appended together instead, e.g., iam-install/iam-upgrade/iam-hotfix. This made adding more commands to the CLI difficult since the help would soon be a lot more cluttered, as was the case for the landing page in the Deployer's GUI. Because of this, we have changed the underlying command-line library to a different one that does support sub-commands. This is a breaking change. Not only because, for example, iam-install must now be called as iam install but also because some subjects, like argument parsing, might be handled differently than before. We recommend using this version to thoroughly test the scripts that use the Deployer CLI program before updating any previous executables currently used in production. As part of adding sub-commands, the commands to auto-install, upgrade, or hotfix an IAM, Software Factory, or application have been moved from twdeployer.exe iam (OPTIONS) twdeployer.exe sf (OPTIONS) twdeployer.exe app (OPTIONS) to the following commands: twdeployer.exe iam auto (OPTIONS) twdeployer.exe sf auto (OPTIONS) twdeployer.exe app auto (OPTIONS) New Indicium commands We added commands to install, upgrade or reconfigure Indicium on a local IIS instance. We also added a command to create an application pool with recommended settings for Indicium. These commands can be called using twdeployer.exe indicium iis. The commands must be run from an elevated prompt because modifying IIS requires admin privileges. Indicium CLI commands Universal GUI commands We added commands to install, upgrade or reconfigure the Universal GUI on a local IIS instance. These commands can be called using twdeployer.exe universal iis. The commands must be run from an elevated prompt because modifying IIS requires admin privileges. Universal GUI CLI commands Generic IIS commands Some commands were added to the Deployer CLI to control application pools on the local IIS instance. You can now: List information about every or specific pools Create new pools Edit the properties of one or more pools Start one or more pools Stop one or more pools Delete one or more pools. These commands can be called using twdeployer.exe iis pools. These commands must be run from an elevated prompt because modifying IIS requires admin privileges. IIS application pool commands Next release Even though Thinkwise has no dedicated Deployer team (like there are dedicated teams for the GUIs and Indicium), we would still like to ship the following changes before the 2022.1 Thinkwise Platform release: Dedicated support for deploying the Thinkwise Upcycler. Move Deployer CLI to .NET 6 While the commands that target IIS might not work on anything other than Windows, users would still be able to deploy IAM, the Software Factory, or application products on other operating systems. Depending on the amount of work, we might have the Deployer GUI run on .NET 6 (Windows only) as well. Add options to install an application without syncing the model to an IAM. Add a separate flow that only syncs the application model to IAM. Check access rights on the target directory when installing Indicium to a local IIS. One of the most common causes we encounter where users cannot start their Indicium installations is that the user the application pool is running on does not have write access to Indicium's installation directory. We plan to add a deployment action that checks if this is configured correctly. Would like to have: A simple configuration mode for Windows GUI flows to make it easier to get a basic installation up and running. A UI-assisted meta source selection for simple configuration modes during Indicium and Windows GUI flows.

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.