Product Updates

We start off the year with the release of 2020.1 for the Thinkwise Platform!   Process flows can automate many tasks that would require a lot of manual work. However, they still require a person to be present to “push the button”. In this release we’re introducing system flow scheduling to help with that. A system flow can be defined as any process flow that can run autonomously without user input. Users can now create a schedule to automatically run system flows at any time. Which means, no more waking up in the middle of the night to generate those sales invoices! Besides this cool new feature, we’ve worked on many other features and fixes, such as: Requirements and Design: Improved Kanban board Work linking and history Unit tests for triggers Temporarily approve validations Temporal tables OpenID configuration Application preferences in IAM Sort domain elements by translation More features and fixes can be found in the release notes. The 2020.1 release can be downloaded from TCP here. Upgrade notes With the introduction of temporal tables in the 2020.1 version of the Software Factory, the required minimum version of SQL Server will be 2016. For more information, see https://community.thinkwisesoftware.com/blogs-21/end-of-sql-server-2012-2014-support-820.

  When a table, task, report or process flow contained unit tests and the object was renamed, the existing unit tests wouldn't be linked correctly to the new object name. This has been resolved with this hotfix. To make this possible however, the results of the unit tests won't be included in the process.

A hotfix has been made for the SF 2019.2. It was not possible to rename or delete a table using the corresponding task, when the table was used in a data set. This has been resolved with this hotfix.

Hello everyone! We've got some exciting updates for you. We've been working hard on improving the cube charts and tab pages and kept working on the stability of the Universal GUI. As always, we've made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. We'll keep you updated regularly about Universal's progress. Beta build Like with every blog, we've released a beta build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: Universal is currently actively tested on the internet browser Edge. Edge has been updated to use Chromium, which greatly changes the way it works under the hood. Once our testing is done, we can recommend Universal to be used on this browser as well. 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 your beta build here Cube charts We're continuing to improve the cube, this sprint we've added support for all chart types and constant lines. Here are some examples of the new charts: Stacked bar graphColumn graphDoughnut graphChart with a constant lineLine chartMultiseries line chartComplex graph with cumulated axesThe message when cube rows or columns are missing is now translatable. Signature control We have added a signature control, it looks like this: The signature control in actionTab page improvements We now only show the assigned details in each detail tab page container or detail tile rather than all visible detail in all detail tab pages. This makes the screen much more clean and quiet. When a detail goes into edit mode, its parent is now also locked. The unsaved changes indicator now also appears when a detail has unsaved changes. Details are now also updated if the parent becomes empty, for example by filtering. This is what tab pages look like now: Tab pagesUnit tests In the past three weeks we've added another 88 unit test cases to the components and inner workings of Universal. This brings us up to 1296 test cases in total. Lots of minor fixes/tasks Miscellaneous Added support for the 2020.2 platform Universal now loads applications in the order IAM prescribes Tree images now also work when the image is from a domain We now support the default expanded level for hierarchy and attribute trees UI/UX The text in the about dialog is now translatable. Fixed a bug where the chart didn't fill out the height nicely. Technical We fixed several fatal Unknown errors by changing how errors were generated and handled. When logging in or switching application, we now send a warmup request for the end product to Indicium. By doing this, data from the end product can be loaded faster when opening a subject. Added the unit tests for the charts. We did the groundwork for the tree menu Performance We no longer load tasks and reports on every tab page change What we'll be working on next sprint We're working towards a version with all essential features. For next sprint this means: Improve charts more Lookup popups Hierarchical menu Fix a few bugs Research and ground work for the pivot grid Research for process flows

Good day everyone. We're excited to start the new year off with some awesome additions to Universal. And to give you a small look under the hood, every few months we have a wildcard day. This means that we can work on anything we want for the day. These days often lead to very interesting projects, a few of which you'll find in this blog. As always, we've made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. We'll keep you updated regularly about Universal's progress. Beta build Like with every blog, we've released a beta build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. 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 your beta build here Keyboard shortcuts (wildcard) We've added keyboard shortcuts to Universal. You can use them when you are working in the form. The following shortcuts have been implemented: Add: Ctrl + + Cancel: Esc Copy: Ctrl + alt + + Delete: Ctrl + - Edit: Ctrl + e Save: Ctrl + enter The shortcuts have been added to the tooltips in case you want a reminder: The shortcut is in the tooltip  Confirmation messages (wildcard) Since it's even easier to accidentally delete a record with shortcuts, we've also added confirmation messages. Translations for these confirmations will be added to the SF shortly. We have confirmation messages for deleting and cancelling. It looks like this:   A confirmation when deleting a record  A confirmation when cancelling a record that has been edited  Movable splitters (wildcard) At times you want a little more space for a component like the grid than the developer intended. In Universal you could make the screen smaller to activate a different breakpoint, but this doesn't always have the desired result. We now made the splitters movable so you can adjust the screen to your needs. Be aware that the adjustments you make to the screen are not saved for now. It looks like this: Movable splitters in action  Hierarchical tree We already had an attribute tree, and now we've also implemented the hierarchical tree. Here's a reminder about the difference between two: An attribute tree creates a level in the tree per column. So if you have table with employees, and sort on the column department. You'd get a node for each department, with all the employees in that department below it. A hierarchical tree creates a level for each relation. If you have the same table with employee, you'd group the data on manager_id. You'd get a node for each manager, with all the employees they manage below it. This is what the hierarchical tree looks like: The hierarchical tree  We also implemented images for and improved styling to both the hierarchical and the attribute trees.   Progress bar We've added a progress bar control to Universal. It's available in the grid, cardlist and form. It looks like this: The progress bar in the grid and form  Tabpages and details We now support all tabpages and details are now loaded directly into the tab, rather than just showing a button that allows you to open the detail in a new document. It looks like this: Tabpages with details loaded right into the screen  Note that we for now show all details in all tab, rather than just the detail assigned to the detail group. This will be implemented next.   Build onto Universal We added the option for developers to add functionality to Universal. You can add a website to the same subdomain as where Universal is running and load that via the preview component. This allows you to communicate with Indicium via a custom page that is loaded into Universal, it looks like this: Universal has been loaded into Universal, which in turn has been loaded into Universal again  Cube charts The first step for implementing cubes is showing simple graphs. We now support the following types of cube views: 1 or more data fields, no categories (rows) and no series (columns) 1 or more data fields, 1 category and no series 1 data field, 1 category and 1 series We do not support computations yet (e.g. year of a datetime field) Now to the awesome part, here's what charts look like: Charts in UniversalSync indicator We now indicate in the topbar when the GUI is processing updates to the form. This helps the user see that things might still change in the form (default and layouts for example): The sync indicator in the blue top bar  Unit tests In the past three weeks we've added another 43 unit test cases to the components and inner workings of Universal. This brings us up to 1208 test cases in total.   Lots of minor fixes/tasks   Miscellaneous Fixed several bugs that occurred when Universal tried to perform an action for a document that was already closed. GUID's no longer get sent with quotes around them   UI/UX Universal no longer briefly shows a message that The screen type cannot be found when first opening a screen. Fixed a bug where the sidebar would be open on small screen when loading Universal and would close when you tapped anywhere on the screen.   Technical Fix console bug that impeded development speed Added easy way to enable proxy, making it easier for us to debug any application Removed a lot of unused legacy code   What we'll be working on next sprint We're working towards a version with all essential features. For next sprint this means: Improve the charts Multi-language about dialog Ground work for the tree menu Tree component default expand level Performance improvements Stability improvements Signature control

Hello everyone. This sprint we've focused on laying a lot of ground work. While this is not immediately visible, it enables to do start working on a lot of features. As always, we've made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. We'll keep you updated regularly about Universal's progress.   Beta build Like with every blog, we've released a beta build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. 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 your beta build here   Tree (Attribute-based) We've implemented the tree component. This version works for attribute-based trees, hierarchical trees (parent-child relations) will be implemented later. So what's the difference between the two? An attribute tree creates a level in the tree per column. So if you have table with employees, and sort on the column department. You'd get a node for each department, with all the employees in that department below it. A hierarchical tree creates a level for each relation. If you have the same table with employee, you'd group the data on manager_id. You'd get a node for each manager, with all the employees they manage below it. It looks like this: The tree component in action  The styling of the tree will be looked at next. Think icons, margins, conditional layouts etc.   Ground work This sprint we've been working on a lot of ground work. Ground work is perhaps the most important part of implementing new features, but it unfortunately isn't very visible. We still didn't want to keep this from you so you'll know what to expect soon.   Cube chart We're preparing to add cube charts. This sprint we've researched what information we'll need from the Thinkwise Platform and in what form to create charts. We also researched what components we might be able to use. We eventually came up with a shortlist and made Proof of Concepts for each.   Tiles menu We've created the underlying architecture to be able to create tiles menu. We now have the definition of tiles menu's available and prepared the current menu for the upcoming change.   Tab navigation in the screen We already have tab navigation on the root level of the screen, now we have the architecture to support any type of tab navigation. We have the structure of each tab available and store what each tab looks like. With this change we can start building any tab component, anywhere on the screen.   Details When we encounter a detail in a tab page, we now show a button to open it in a new document. We created the underlying architecture and state to show the actual detail itself.   Unit tests In the past three weeks we've added another 34 unit test cases to the components and inner workings of Universal. This brings us up to 1165 test cases in total.   Lots of minor fixes/tasks   Miscellaneous Added support for Thinkwise Platform 2020.1 The correct hour is now shown when DateTime values have high millisecond precision   UI/UX Fixed radio buttons misalignment Changed the label for the dark mode toggle in the User Preferences menu   Technical Refactored all actions to be type-safe   What we'll be working on next sprint We're working towards a version with all essential features. For next sprint this means building on the ground work we've laid in this sprint: Hierarchical tree component and styling the trees Figuring out how to fetch the data for cube views and loading the cube view definitions Showing details in the screen, rather than a button to open a new document Implementing all tabpages Creating a component that loads other web applications into Universal Testing and completing the work done on the wildcard day. More on this in the next blog

The task in IAM to copy an application contains several options to determine what you want to copy. This also applies to user preferences. After choosing this option the user preferences for "Default prefilters" were not copied. A new hotfix for IAM 2019.2 is available to correct this.

Unit tests were incorrectly hidden when the corresponding project version was inactive. A new hotfix is available to correct this, by changing a technical prefilter from "On" to "Off and hidden".

In the installation of IAM 2019.2 the script 999_Apply_roles_on_database.sql was missing. This hotfix provides this missing script.

Hello everyone, these past three weeks we've put the finishing touches on tasks, started with reports, added canvas navigation, and more! As always, we've made a demo for you: try it here. We'll keep you updated regularly about Universal's progress.   Beta build Like with every blog, we've released a beta build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. 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 your beta build here Video control We've added a readonly video control so now you can watch video's in Universal. It looks like this: A video control in Universal  Canvas navigation Canvas navigation is about tab pages on the highest level of your screen (we call those canvasses). Now you can switch between canvasses. You can have component and detail canvasses, just like you're used to with tab pages. It looks like this: Canvas navigation in action  When you go into edit mode, the first canvas that has an editable component (i.e. a form) will automatically be activated. All other canvasses will be disabled when in edit mode. The first tab with a form gets activated when going into edit mode (all other tabs get disabled)You can control the visibility (regular, read only, hidden) of detail canvasses using context procedures. Detail canvasses for now contain a button that allows you to open the detail in a new document. The next step for canvasses would be to actually load the detail in the current screen. Tasks We've put the finishing touches on tasks. Now you can execute tasks from the menu, and you can get a confirmation popup when executing a task. A confirmation for a task that has been executed from the menu  Reports You can now execute and view reports. They work quite similarly to the way tasks work. This is what it looks like: A report being executed from the menu and viewed  User preferences We've created a user preferences screen. This is where all user preferences will be managed. For now we've moved the theme mode (dark/light) to this screen. You can find it here: User preferences in the topbar  And it looks like this: The user preference screen  We also made the topbar more responsive, on small screens the name of the logged in user moves to the overflow menu and the dropdown array disappears:   The topbar on small screens  Unit tests In the past three weeks we've added another 65 unit test cases to the components and inner workings of Universal. This brings us up to 1131 test cases in total. Lots of minor fixes/tasks   Miscellaneous Universal uses only the login options from config.json when the login options on the login screen are disabled. Technical Refactored where we store the current application and how it is used. This helps us implement tasks and reports executed from the menu. Upgraded our user interface toolkit, Material UI, from version 3 to version 4. Use context path for executing badges We no longer use the current application id when working in form fields What we'll be working on next sprint We're working towards a version with all essential features. For next sprint this means a lot of ground work: Creating the tree component (grouped on columns) Making the breadcrumb responsive Starting the ground work for charts Starting the ground work for non-canvas tabs Starting the ground work for showing the content of details in their tab, rather than a button to open the detail

Thinkwise Platform version 2020.1 will no longer officially support SQL Server 2012 and SQL Server 2014.The official minimum supported version of SQL Server will be 2016.Impact on development environmentsVersion 2020.1 of the Software Factory will leverage temporal tables. This immediately brings the minimum required version of SQL Server to 2016 upon release.The Deployment Center will prevent installation or upgrade of the Software Factory to version 2020.1 when the SQL Server version is below 2016 or the database compatibility of the Software Factory database is below SQL Server 2016.Impact on production environmentsThe Intelligent Application Manager, Indicium service tier and the GUI's will not immediately leverage SQL Server 2016 features with the upcoming 2020.1 release.Existing products will continue to work on SQL Server 2012 and SQL Server 2014 for now. New database versions of products built using the Software Factory 2020.1 will not require SQL Server version 2016, unless temporal tables are leveraged or version-specific language features are used in business logic.Future impact on production environmentsFuture versions of the Thinkwise Platform will eventually require SQL Server 2016 as minimum version for the Intelligent Application Manager and product databases. Future releases of the Indicium service tier and the GUI's will eventually cease to support SQL Server 2012 and SQL Server 2014 as well.Please plan the upgrades of SQL Server environments accordingly.TimingThinkwise Platform version 2020.1 is currently in the final stages of development and is planned to be released in January 2020.The changes in SQL Server version support will be reflected in the lifecycle policy.

A new hotfix has been made for the SF 2019.1 and 2019.2 to fix the delete task for messages. When a message was used as a confirmation message for tasks, deleting the message would also lead to the task being deleted. Deleting a message will now no longer delete the associated task, but instead empty the confirmation message column.

In SF versions 2019.1 and 2019.2 you may get an error like this: XML parsing: line 1, character 2967663, illegal xml character.When you get this error, it is very hard to determine where the illegal character can be found.  To solve this, we introduced a stored procedure called task_search_illegal_xml_characters. This stored procedure searches in all character fields in your project version for illegal characters. Because this procedure can be time consuming, we made it is also possible to search in a specific table.The parameters of this procedure are:@project_id @project_vrs_id @tab_id@project_id and @project_vrs_id are mandatory. When you fill in NULL for @tab_id, the procedure will search in all tables with a project version.In the upcoming SF version 2020.1 this procedure will be available as a formal task on project version.

This hotfix for 2019.2 fixes an issue where dragging and dropping Business processes, Features or Iterations would not recalculate the specification, work and acceptance progress. The hotfix will also recalculate the progress for every Business process, Feature and Iteration and correct them where needed.

This hotfix for the SF 2019.1 makes it possible again to set the layout type output for expression columns. This way an expression column, which is read-only by default, can be hidden in the layout procedure.

In the 2019.2 release we have added the invalid character check/replacement to screentypes. This also led to breakpoints (<) being incorrectly replaced. In this hotfix an exception to this character has been made, so that breakpoints can be used again. Other invalid characters will still be replaced with an underscore.

Hello everyone. Rather than a trick let us give you a treat! The past few weeks we've been working on tasks, an image upload control (and a progress indicator in all upload controls), we've added an about popup to give you more information about which meta version and Universal version you're using. Of course, we also squashed a couple bugs and did some minor tasks. As always, we've made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. We'll keep you updated regularly about Universal's progress.   Beta build Like with every blog, we've released a beta build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. 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 your beta build here   Tasks with parameters You already could execute tasks from Universal, as long as that task had no visible parameters. That restriction is gone, so you can execute tasks with parameters now. When you click a task with parameters, you get a popup that holds a form so you can fill those parameters in. It looks like this: A task with parametersWhen a task gets executed we might need to wait for it to finish. This is visualized like so: A task is executingImage upload control After the file upload control we now also have an image upload control. It's similar to the file upload control, but shows a preview of the image and by default only allows you to upload images. It looks like this:   Image upload controlFile upload control with progress When we implemented the file upload control, we thought it would be awesome to show the upload progress in the control itself. This became a side project which now has been implemented in Universal. The image upload control also shows progress. It looks like this: File upload control with progress  About popup It can be useful to know exactly what SF version you're running. It's even more useful to know which version of the Universal GUI you're running (since it changes more often). We've implemented an about popup to show you exactly that. It looks like this: The about popup  You can find the about popup in the profile menu (we know it has no translation yet): Where to find the about popupUnit tests In the past three weeks we've added another 55 unit test cases to the components and inner workings of Universal. This brings us up to 1066 test cases in total. This is less than what we started with because we removed 70 test cases by removing the old non-responsive implementation of the action bar which wasn't in use anymore. That implementation had its own tests, which were removed too. Lots of minor fixes/tasks   Miscellaneous We now show the user's first name in the top bar rather than the user id (if the first name is filled in) The login button now gets disabled after submitting the form to prevent double logins Performance Fixed duplicate requests for prefilters Set page size to 100 rather than 1000 Technical Removed the old action bar code Save context path into state Use context path for adding and copying records Execute layouts and context using a navigation path What we'll be working on next sprint We're working towards a version with all essential features. For next sprint this means: Upgrading material UI Single-level canvas navigation (top-level tab pages) Finishing up tasks (starting tasks from menu, confirmation message) Start on reports A lot of behind-the-scenes technical work to prepare for coming features

Context About two years ago, Service Pack 21 of Crystal Reports was released. This new service pack required applications such as the Windows GUI to update to a new version of Crystal Reports. Furthermore, the required .NET Framework version for this Service Pack was updated to to 4.7.1. Updating to the new version would mean that the previous service pack would no longer be supported and older .NET Framework versions would no longer be supported. To keep supporting the status quo, we set the maximum supported version of Crystal Reports to Service Pack 20. Since only one version of Crystal Reports can be installed on a client machine, this meant all other applications using Crystal Reports were also limited to Service Pack 20 or earlier. Breaking change We will be upgrading the following Thinkwise Platform components to only support Service Pack 21+ of Crystal Reports: Windows GUI Web GUI Indicium Indicium Universal Reporting Service The required .NET Framework version for these components has already been updated to match the Crystal Reports Service Pack 21+ requirements, with releases dating back to december 2018. Timing The new versions of these applications which become available around November 18th, 2019. The changelog will clearly indicate this breaking change. Impact Web servers and desktop environments using Crystal Reports Service Pack 20 or earlier will have to be upgraded to Service Pack 21 or higher. This will have to be done in concert with the upgrade of the Thinkwise Platform component(s) running in this environment. Continued usage of the Thinkwise Platform component(s) supporting Service Pack 20 and earlier after the Crystal Reports upgrade to Service Pack 21+ may result in failure to execute reports using Crystal Reports. Environments using Crystal Reports Service Pack 20 or earlier that will not be upgraded can no longer receive updates of Thinkwise Platform components. Doing so may result in failure to execute reports using Crystal Reports. The Intelligent Application Manager uses Crystal Reports. Environments used to run this report will need to be upgraded. Update: As mentioned in the comments - Crystal Reports Service Pack 26+ introduced a new incompatible change. This means that the Thinkwise Platform does not support service pack 26+ until further notice.

Howdy everyone! The past three weeks we've been working on the upload file control, compatibility with the 2019.2 Universal themes and conditional layouts and a config file to make deploying Universal much easier. As always, we've made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. We'll keep you updated regularly about Universal's progress. Beta build Like with every blog, we've released a beta build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. 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 your beta build here Upload file control We now added the ability to upload files in Universal. It looks like this: File upload controlConfig file We created a config file so the config settings can be changed by customers without requiring a new GUI or editing obfuscated JavaScript files. Note that  .json files need to be set as static content on the server. It looks like this: Sample config file  We provide the following options: defaultApplication: The id of the application that should be loaded, e.g. insights or 173 defaultPlatform: Whether to start Universal as Windows (0), Web (1), Mobile (2) or Universal (3) loginOptionsDisabled: Disables editing the login options serviceUrl: The URL where indicium can be found   SF 2019.2 themes and conditional layouts Universal now supports the new SF 2019.2 Universal theme color settings and conditional layout settings. This enables you to set the theme colors and backplate, and the conditional layout settings separate for dark and light mode. It looks like this: Differing theme colors in dark and light mode  Differing conditional layout appearance in dark and light mode  Unit tests In the past three weeks we've added another 34 unit test cases to the components and inner workings of Universal. This brings us up to 1088 test cases in total. Lots of minor fixes/tasks Miscellaneous You can now select grid cells to copy its value. Clear cache button on login screen now properly resets the login options. Edit mode is no longer lost when you switch between documents. Styling Made suggestion control's clear and chevron icons consistent with the other controls. Removed sidebar mini mode on touch devices. The dropdown menu's (e.g. application switcher) are now dark in dark mode. Technical Show an error message when the item is no longer available for the action that the users want to perform. Implemented infrastructure to support tasks with parameters including lookups. Errors about missing reference columns are now handled more gracefully. The blurring of input fields on the login screen has been refactored. What we'll be working on next sprint We're working towards a version with all essential features. This includes: Reports Details Charts Navigation within screens Look up popups A blog post with the planning for all essential features will follow shortly. The next sprint we'll be working on the following things: Execute tasks with parameters from a subject: you'll get a popup with a form to input the parameters and be able to execute the task Improving working in details - we'll autofill the fields when adding or copying a record. For example: if you go from Projects to Subprojects and press add, we'll fill in the original project for you. Implementing an editable image upload control. We'll also squash some bugs and improve the performance even more.

Thinkwise Platform version 2019.2 is now available!Information about this release can be found here in the Updates and Releases section.To receive e-mails about new releases and hotfixes, be sure to subscribe to the Updates and Releases section.Subscribe! 

The second release of 2019 for the Thinkwise Platform is now available!This time around, requirements and design has undergone a complete overhaul. Specifications are now placed outside of projects and project versions. Requirements and work items can now also be organized under features and iterations. Features can help categorize the work more efficiently while Iterations facilitate the planning process.But that is only scratching the surface. For everything on the requirements and design rework, please refer to the release notes and our documentation.But wait, there's more...The 2019.2 release comes with much more. Keep an eye out for:Module authorization Concurrent Access Limitation Unit testing with mock data New icons Universal Theme And many more features and fixes...Every detail of this release can be found in the release notes. Download the 2019.2 release, available in TCP right now! 

The past three weeks we've been working on applying context logic, applying translations, showing error messages and a redesign of the breadcrumb.As always, we've made a demo for you: try it here.We'll keep you updated regularly about Universal's progress. Alpha buildLike with every blog, we've released an alpha build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind:Universal isn't actively tested on the internet browser Edge at the moment. Edge will be updated to use Chromium, which greatly changes the way it works under the hood. Once this is done, we will be testing on Edge too. 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. This is an Alpha version, there is no compatibility plan in place for Universal just yet. Indicium updates and IAM hotfixes will eventually break this Alpha release. Download your alpha build here Context logicTo disable or hide details and tasks we fetched the context for the active record. Now you can see if a task or detail is disabled or it's hidden completely. It looks like this:Disabling tasks that cannot be executed for the active record TranslationsSome displayed words in Universal were hardcoded in English, even if the application was in another language like German or Dutch. We now fetch translations for the users' language and show the correct translation translations.For now, the following words have been translated:Actions Details Filters Logout No Result Open Documents Search Error messagesError messages from Indicium are now shown when a resource cannot be found (e.g. when trying to edit a record that someone else just deleted) or when the user has no permission to perform an action (e.g. trying to delete an invoice that someone just sent to the customer). For now these messages only show as an ID since we do not have the translations available yet.Trying to delete a record that already has been deleted  Trying to modify a sales invoice that has already been sent to the customer  BreadcrumbThe breadcrumb has gotten some UI / UX improvements. The whole breadcrumb is now always placed under the open document title. This way the user always knows where to look when wanting insight of his navigation path. Also is the data displayed less scattered because the selected row used to be on top, but now it is the last part in the breadcrumb underneath the open document title.The below figures show the changes. The breadcrumb shown in the blue area.Before:Previous version of the breadcrumb in the Project Activities documentAfter:Updated version of the breadcrumb in the Project Activities document  Unsaved changesWhen trying to close a document with unsaved changes, we now show a Material styled popup instead of the native popup that was shown before. The title still shows up as an ID because the translation hasn't been added yet.Before:Trying to close the Customers document with unsaved changes - beforeAfter:Trying to close the Customers document with unsaved changes - after  Unit testsIn the past three weeks we've added another 30 unit test cases to the components and inner workings of Universal. This brings us up to 1054 test cases in total. Lots of minor fixes/tasksStylingFixed large space between a HTML editor and its label in some cases. Fixed inconsistent padding between words in HTML cells in the grid. Fixed a bug where the whole page would scroll on iOS. Fixed a bug causing tooltips not to work.PerformanceReduced the number of times the toolbars (filters, task, reports, CRUD, details) need to render.TechnicalWe now store the SF version so we can support any changes made in future versions The form was refactored to make it suitable to handle task parameters. We implemented loading the tasks and task parameter model information for listbar items.

Hello everyone! The past weeks we've been working on making Universal much more responsive with a responsive toolbar and a responsive form. We also implemented showing messages. As always we made a demo for you: try it here. We'll keep you updated regularly about Universal's progress. Alpha buildLike with every blog, we've released an alpha build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: 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. This is an Alpha version, there is no compatibility plan in place for Universal just yet. Indicium updates and IAM hotfixes will eventually break this Alpha release. Download your alpha build here. Responsive toolbarThe responsiveness of Universal continues! So next up; responsive toolbar with an Action and Filter components. For now the Action component will contain: CRUD Tasks Details (details of a screen will be later removed from the Action component, for now it's in the Action component) The Filter component will contain: Search (formerly: Filter) Prefilters The toolbar is divided with a 50% / 50% ratio for the Action and Filter component. This later on will be a setting for the developer to make sure each screen is suitable for the content of the Action and Filter component. Overflow menuWhen the content from an Action and / or Filter component doesn't fit in its available space it gets pushed to the overflow: Tasks and details in the overflow menu The prefilter overflow menu will always shows all prefilters. This helps the user get an oversight of all prefilters, their names and a to get an overview of all active / inactive prefilters: Prefilters and their state in the overflow menu Before content gets pushed to the overflow menu, the Action and Filter component tries to fit a much content as possible. This results in the following states for a tasks or details (CRUD actions and prefilters are always icons) ordered in maximum to minimum available space: 1. Button with icon and text: 2. Button with text: 3.Icon: 4. Overflow (moved to the overflow menu): Collapsing into the overflow will happen from right to left. This collapsing will be done per group so tasks, details or prefilters will never be separated from their group. First prefilter group collapsing The order of collapsing to the overflow is from right to left (in the future we want to use priority numbers to determine which items should stay the longest in the component). Tasks collapsing to the overflow menu Here, both sides are partially collapsed "But I see white space?" Yes, this is because the task group would never fit with text and thus collapses to icons. Overlay search fieldIf the screen gets really small and all the items are collapsed the search field will also collapse to an icon. To perform a search the user has to click the icon that will show the search field in an overlay. If the overlay is closed but there is still a search active the search icon will be in the active state so the user can see that the results are filtered. Searching on a mobile device Future improvementsThe work we've done is a huge improvement over what we had, but there still are some things we can do to further improve how toolbars behave. Enable the developer to define priorities, maybe on some screens, tasks are way more important than CRUD actions. Interpret groups for tasks. We'll add another step where tasks or reports will collapse into a dropdown, before getting pushed into the overflow menu. Use toolbar as a component anywhere in the document. Group related actions regardless of their type. The last item needs some more explanation. Right now you have all the prefilters, then all the tasks, etc. But this might not be the optimal solution. Imagine an invoice screen. You can generate invoices, approve invoices and send invoices to your customers. It might behoove us to have a bar that contains a prefilter that shows us all the invoices that have not been approved, and a task to approve them. The next bar would have a task that shows all approved invoices that have not been sent to the customer, and the task to send them to the customer. This approach would enable the developer to create and position their own toolbars. Grouping tasks, prefilters, reports, etc. by what they mean, not just by the fact that they are a task or prefilter. This is however not an easy feat, it is just an idea so it will take a while to accomplish. Responsive formHaving multiple columns in your form is a great way to make the most use of the screen real estate. But having two or three columns in your form on a small phone will get very crowded very fast. So on small screens, forms will now always have one column. Form with one column on a small screen Snackbar componentTo show messages to the user we've implemented a snackbar component. Since you might not be familiar with the term, here's what it looks like: An Indicium error message being shown in a Snackbar With this we can show any kind of notification, be it from Universal itself, Indicium, messages the developer made, or anything else. We don't load all GUI message translations yet, but we do show some messages. More messages will be added later. Unit testsIn the past three weeks we've added another 103 unit test cases to the components and inner workings of Universal. This brings us up to 1024 test cases in total. Minor fixes/tasks Styling Fixed a bug on iOS where part of the cardlist would be hidden when scrolling. Performance Universal no longer tries to load detail subjects to get the icons when there are no details. We now use objects to style components rather than calculating the style each time where possible.

Hello everyone, a new Universal Development Update is here! The past three weeks we've been working on an HTML control editor, applying visibility to form fields and action buttons while navigating, usability on Mobile devices and a popup component. As always we made a demo for you: try it here. We'll keep you updated regularly about Universal's progress. Alpha buildLike with every blog, we've released an alpha build so you can test Universal out for yourself. Don't forget the documentation and be sure to keep the following in mind: 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. This is an Alpha version, there is no compatibility plan in place for Universal just yet. Indicium updates and IAM hotfixes will eventually break this Alpha release. Download your alpha build here Edit mode HTML Control editorA first basic HTML control editor has been implemented. With this editor you can apply bold, italic and underline text styles and create numbered and bulleted lists: Basic HTML editor Paper animation when going into edit modeTo let the user know where to edit the data when going into edit mode, we've animated the paper behind the form. When you go into edit mode it briefly gets more shadow: Paper of form briefly gets more shadow when going into edit mode Layout logic in non-edit mode ButtonsButtons can now be disabled or hidden due to layout logic. In the example below you cannot edit or delete booked hours that have already been invoiced because the buttons are disabled. Disabled buttons in non-edit mode FieldsAlso field can be disabled or hidden in non-edit mode. In the example below, you can see that 'Employment ended on date' will become visible if 'Employment ended' is checked. Field hidden in non-edit mode Improved login screen for small screensThe login screen now takes up less space on a small screen. In the image below the left image shows the old implementation and the right image is the new implementation. The paper background is removed on small screens and the input fields are more responsive. Login screen comparison on a 320 pixel wide screen Popup componentWe have created a popup component which will be used for example by task popups in the future. It is resizable and you can move it around. Check it out in the video below! Popup component with example content Unit testsIn the past three weeks we've added another 49 unit test cases to the components and inner workings of Universal. This brings us up to 921 test cases in total. Lots of minor fixes/tasks Styling Fixed Suggestion and Combo control not working on empty values. Fixed empty form fields being hard to focus with the cursor in it. The sidebar no longer opens when clicking anywhere on the screen on small devices Reduced margin of content when on small screens Fixed filelinks being shown as "[object Object]" instead of the filename in the Form and Cardlist. When clicking URLs without 'http://' or 'https://', it now opens the URL, instead of reloading Universal. Fixed inconsistent conditional layout background size in some Grid controls. Clicking on a link with the middle mouse button now also closes the Cardlist overflow menu. The clear cache button is now a text button so it won't be mistaken with the login button. Technical Fixed data not getting loaded on some screens because lookups failed to load. Fixed error when closing the last opened document while editing it. Performance Only one request for a subject's definition is now sent rather than multiple

A new hotfix has been made to improve the performance in some situations when starting an end product against the Software Factory 2019.1. Technical: adjustments were made in the stored procedure get_gui_tab_variant_col.