Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Our application is running on a database which is in UTC (Azure SQL), this does come with a unique set of challenges as our business operates in CEST.IAM is giving one of these challenges with it's scheduler, there are a few schedules that should be ran every day at a specific time. This time however is in CEST and the scheduler it's time is in UTC, in practise this means we have to change the schedule twice per year. Please add the possibility to select the timezone for which the schedule is set in. This way IAM can handle the time changes due to summer/wintertime and the actual running time is always the same from a user perspective.
Sometimes you would like to abort a system flow. A reason for this could be that by mistake a never ending loop has been created. Or that a system flow is simple stuck, running and ran into an error but did not stop, preventing the next scheduled time to start the flow.Currently the only way to resolve both cases is by restarting indicium (application pool recycle or webserver restart). This is not really what you want. Because if this occurs in the production environment, this will result in every user getting logged out.Therefor it would be great to have an option to abort a system flow. This option should be available in IAM on the scheduled system flow screen. But also in the process flow monitor, allowing a user to abort a flow during a test or manual run.The expected behavior would be that the system flow will execute its current flow action and after doing so, will simply stop. And if it is not executing a flow action at all, stop as well.
I would like to be able to kill abandoned or long running system flows. Sometimes a flow gets abandoned but the signal is not picked up by indicium/universal and it looks like it is still running. It would be very helpful to be able to kill any systemflow from deployed applications that runs for over a certain amount of time. Ideally the amount of time could be configured by the developers, something like we expect this flow to last for 5 minutes and if longer than 30 we want to be able to kill it.
Hi, When using the standard excel import functionality, all dates in the excel file are shown in the same date time format. Even when the excel only contains a date, a time is added to it. This results in harder to read date fields.It would be nice if the date field in the import functionality would reflect the actual data in the excel.
I would like to see import from clipboard for the universal.
The list of process and system flows is coming bigger and bigger. Often these flows (process or system) have some sort of a relation between each other. The only way to make this visible is by either including this in the description field or the name of the flow. Not ideal.It would be great to add a group to flows (process and system). It should be possible to combined both a process flow and a system flow in a group.This group should also be visible in IAM (scheduled system flows) and in the role assigning within the SF.
We've discovered that we can use the radio control in combination with the auto-commit option in wizard/questionnaire scenarios.To make it perfect, it would be great if there were an OPTION_BUTTON control in addition to the RADIO_BUTTON control. To make it work like the image above, we also need a solution to make the Cancel and Confirm buttons invisible when auto-commit is used. Is there already a solution for this?
Deeplinking is only possible in the Web GUI and on the backlog for Universal development.See details in my question and request @Edwin Saan:Please vote if you need or like this feature in Universal to. Universal Forecast:
Currently you can use the Processflow monitor to test system flows. This is a very useful feature. There is however one issue with the current screen. You cannot search/filter within the list of system flows. Often this list will become quite large.Please implement a search/filter for this dropdown list
Can we please add the original object as a field to the translation form? Now it is hidden in the translation object lookup. I believe it would be better to show in the form that variantofbook is variant of object: book.
Compared to windows GUI we still miss some valuable features for the text editor, liketext color control text background color control subscript / superscriptWould be great if these can be added.
Hello everyone,While we were writing code for a task layout it occurred to us that this could be done much simpler via a task variant. But to our surprise the task variant was not able to do this. Like in subjects, you can alter the visibility of columns per variant, but in task variants this is not possible. As a concrete example: I had a task where three values have to be invisible for a certain role. Now I have a preparation task that prepares a value, sends that to the task that needs to be executed, and the layout logic sets those, otherwise editable fields, to hidden or read only based on whether the value in the preparation task is true or false.It would be easier if I could just set those task fields to hidden in the variant directly, this would save a task and a bunch of code in a lot of instances.So in short, I would like the following option in the subject variants: Where I can give the columns a stricter visibility (and not from read only back to editable) per variant. I think it could be a good idea to implement this in the task variants as well, so that this option becomes available (per variant) here as well: This would be ideal in many situation that now require extra (sometimes unnecessary) code.
A simple idea, but we’ve encountered a situation where a model tag for web connections could be useful.In our situation, we’ve defined tags in the description of the web connection endpoint and in the description of its input parameters. I can imagine that having tags available at all detail levels could also be useful in the future.
Currently when you have a branch which is “protected” and want to set this “unprotected” (required for archiving a branch) you need to disable the checkbox “Protected” on form level in the Branches screen. But sometimes this checkbox is disabled. To help a user with disabling this checkbox it would be great to move the functionality of marking a branch to “unprotected” from the form into a task. This task will be shown when a branch is marked as protected and can always be executed. If the branch cannot be set to “unprotected” the reason why will be displayed in an error message thrown by this task.
In addition to the double-click option for table tasks, we would like to have a single-click option in some scenarios.In particular, to make it possible to open a detail tab from a card list on mobile devices. Perhaps there is a better way to do this, without the need of using a hidden task and process flow for each card list / detail view.
Currently when working with multiple models it is quite inconvenient to share icons between these models. I understand that you would not like to store icons in a model which are not used and that this is why they are stored within a model instead of on global level.However often you do want to use a set, or all of these icons, within multiple models. Currently the only way to copy an icon from a mode into a different model, is by opening a second software factory. Selecting the model/branch from which you would like to copy this. Download the icon and then add a new icon in the model/branch you were working in. Select the downloaded icon and store it. Quite a few steps.It would be great if you could “import” icons from other models. That will allow you to select a set of icons used in model X and move them to model Y. Saving a lot of time. You should be able to select a set of icons. Having an import function to only import 1 icon, will not work.
Reachable objects is a helpfull tool, but half the time I have no clue what I am looking at. Can we get an explain button that explains what it is I am looking at? (a detail, a lookup, a menu item etc etc).Simple Example below, this apparently means that book genre is available as a detail for book and genre. How was I supposed to deduct that from this:
The new debug center looks great, but we would like to see some adjustments to the layout of the process flow monitor so that it can better assist us in resolving errors. Resolving issues in Process Flows is often very time-consuming. The process flow monitor we had in the Windows GUI wasn’t ideal either, but it still often allowed us to locate issues more effectively.We hope it is not to much effort to come to a layout more like this...Key focus points: Make the most efficient use of screen space wherever possible, assuming that nearly all developers have at least an HD display Indicators showing which actions were not successful Duration of actions in milliseconds, highlight slow ones Type of action with symbol Display associated database event(s) per action as well
We often get requests from our business to show a popup form when adding a new record instead of going to a form tab (or have an always shown form below a list). This is a behaviour that is present in many other systems. This is currently done by creating a tasks that shows the same fields as the form, a lot of duplicate, extra, work and lots of places for new bugs to be introduced (rights, defaults, layouts etc etc).Would be nice if we can just select the flow that happens when creating a new recordsCurrent behaviour (default) Show popup formMaybe even support this when doing edit etc.
We use a lot of Modal document form in our application, which works great. There are however some situation where a process flow end with the opened document. After a user is done with the required actions we sometimes desire to take care of certain actions after or triggered by a closing of the document.Unfortunately this Action does not count as a starting point.A workaround for now is using a task in the screen that follows with a “Close document”, but the user often misses that. The “CLOSE’ button takes so much focus, that such a task would be missed. Also if the screen already has many tasks, it would not stand out that much anyway even when marked as primary. The idea is to make “Close document” a starting action in a process flow.The idea of course goes with a warning that the “Close” is always available on such a document, that one should be aware it could be pressed without actively having done anything in the screen and uses it as a cancel, but I think this should be the responsibility of the developer using such flows.
I propose introducing the ability to assign a classification to a table.At a basic level, this would help with simple tasks such as identifying, sorting, or filtering related tables within the platform.At a more advanced level, the classification could be used to drive specific behavior that reflects the nature of the table. Initially this behavior can be implemented by yourself through the dynamic model, while in a later phase the configuration could potentially be formalized in the SF.Examples of table classifications could be:Master: Contains base data such as VAT rates, product categories, currencies, countries, languages, ISO codes, and date conversions. Example behaviour: Make editable, with the awareness that adjustments may have significant impact. Configuration: Contains configurable items such as email settings and system parameters. Example behaviour: Make read-only once accessed from a lookup since adjustments often have unintended consequences. Core Entities: Contains strong entities such as customers, suppliers, and employees. Example behaviour: Apply a screen type which lets you easily see, manage and add these core entities. Operational: Contains process data such as appointments, orders, and invoices. Example behaviour: Provide transactional screens to create, edit, and process these records in line with operational workflows. Interface: Tables that act as a bridge between external systems and the application, such as API staging tables, integration views, or import/export buffers. Example behaviour: Do not require translations, exclude from UI-related validations to prevent unnecessary validation messages. Analysis: Contains analytical structures such as dashboards, reporting, and BI aggregates. Example behaviour: Make read-only for analytical purposes. Archive: Contains historical data such as past invoices and legacy records. Example behaviour: Make read-only for long-term storage. Logging: Contains system/user events such as audit trails, login attempts, and error logs. Example behaviour: Make read-only, automatically place in a ‘Logging’ menu group. Staging: Contains temporary storage such as import buffers and preprocessing tables. Example behaviour: Allow only temporary use with minimal validations, and ensure automatic cleanup or further processing.
In the Universal GUI you can press ctrl-r and the filter form cursor will always be on the first field value.In the Windows GUI you can select a field in a list, press ctrl-r and the cursor in the filter form will be on the value of the selected field. Please add this feature to the Universal GUI too.
when adding a process step in a process flow from decision to the next action, this is added as always even if i change it to (un)successful. It adds value if it´s possible to add a qualification like (un)successful or maybe add a separate description.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK