Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
The Software Factory offers a solution in which you can configure unit tests for various functionalities/procedures. You are capable of comparing an expected output of your procedure with an actual output. This is a great way to verify whether changes within your current version might have broken this procedure/functionality.However several procedures use the GETDATE() option. This will lead to the fact that the actual output will never by equal to the expected output, since this was using a different date (and or time) stamp. I would like to be able to overrule the GETDATE() statement within my code into a preset date/time. When this is possible I will be able to compare the expected an actual output properly for these kind of procedures/functionalities.
The idea is to skip an editable field with Enter (or Tab) without it jumping to the next selectable piece like a field, icon or button (without making the next selectable piece read only. shown as below)
Currently all Process actions are available to the user and there's no indication during development that the created Process Flow is a valid System Flow. There's a validation that tells if there are Process actions used that are not available to be used in System Flows but it lacks helping the developer successfully set up a System Flow.With a checkbox in the main Process Flow screen, not only will it be easy to find System Flows in the long list of Process Flows, it can also be the indication for the SF to limit the amount of Process actions available for use. Also the Process schedule tab can then be hidden for Process Flows whilst available for System Flows.When changing an existing Process Flow to be a System Flow, there could be a check upon switching the checkbox if there are Process actions used that are not supported. When true, show a message.
Ability to have the Lookup icon on the other side, also (in Edit/Add mode) the dropdown icon to be on the other side with the Lookup icon
We need a way to highlight or change color of the 3 dots in the attached screenshot, so users will know that there are filters available but because of the screen size they are hidden.
A view is by default not editable so it would be nice if the SF automatically disables the add/delete/edit/mass update and import buttons when you create a view. Now it is often forgotten to disable the buttons what results in errors if the user uses them.
From version 2019.1, making a little adjustment in Roles requires a full sync between SF and IAM. An option to only Sync Roles/Authorisation Settings will help to make this routine less heavy.
Currently it's possible to add/alter/delete model objects of a project version that is being synced at that moment. This can cause that there are loose objects in IAM.For example there was a sync going on in the project I work on. At the time of the sync, another developer deleted a table (with columns). But during the syncing process, the columns are synced first and the tables later. During the syncing of columns and syncing of tables, the table has been deleted, causing the table to not end up in IAM. But the columns were already there.This inconsistency caused Indicium (Universal) to not run any System Flows for that application because the model was incorrect.I would like a protection for this as upon opening the IAM application there's no visible error or anything about the model being incomplete or incorrect. The only way to find out things are not working properly is by looking in the Log of Indicium.
When you copy a project version, the Software Factory automatically gets the current project version +0.10. I always change that to +0.01. For example: If I'm copying project version 1.34 to a new version, the SF suggests 1.44, but I want it to be 1.35. Maybe make the project version number increment a variable that you can set per project?
All supported databases support the concept of sequences. To clarify what a sequence is, I'll quote Microsoft: A sequence is a user-defined schema bound object that generates a sequence of numeric values according to the specification with which the sequence was created. The sequence of numeric values is generated in an ascending or descending order at a defined interval and can be configured to restart (cycle) when exhausted. Sequences, unlike identity columns, are not associated with specific tables. Applications refer to a sequence object to retrieve its next value. The relationship between sequences and tables is controlled by the application. User applications can reference a sequence object and coordinate the values across multiple rows and tables. Sequences are quite useful in various scenario's, for example to assign (unique) batch-numbers the products that have been produced and are being stored in a stock table. I think it would be useful if we could make use of these sequences and be able to define them within the Software Factory. I think the best place to define them would be at the datamodel-level. It should have options like: Name Datatype Start with value Increment value Min value (optional) Max value (optional) Cycle (no/yes)
Hi!When unit-testing, for instance default control procedures, I would like to to be able to compare the expected output with something else than a static value. It would be nice to compare the test result with the result of a query or even something like NOT NULL.I need to check if the result of the test matches the current date + 1 month. Since this changes every milisecond I can’t compare this to a static value. It would be great to compare it to:dateadd(month , 1 , getdate()) But comparing it to NOT NULL would help too, since this at least gives some convidence that the code is behaving as expected.As it is, I see no way to create a functional unit test for this default code procedure.
It would be a very nice feature if we can set a default password expiration, as in 2 month for example. So after 2 months the user will be forced into changing it's password.
Since the update to v2020.02 the time fields with control time shows HH:mm:ss including the seconds. In the previous version 2018.2 this control was shown as HH:mm.How can we change this so, that our time fields only show HH:mm??We work a lot with time fields and the seconds are not relevant for us. So I don’t want to frustrate the users with seconds in all the time fields. However, for the trace fields we want to show the seconds, so a solution where all time fields are changed to not showing the seconds is not acceptable.Hope someone can help me out..(Maybe someone can change this issue to question!!! The portal keeps telling me that the kind of topic is not selected, but the quesion bullet is marked.
We've got a table with years of historic data. Numerous fields are dropdowns with a fixed set of of domain elements. A customer now has the desire to come up with a complete different set of possible values and keep the historic data working (with the old values). There is no way to get this done with how domains and elements work currently. A great addition (i.m.h.o) would be the addition of a new field in a domain element "active" or "available_to_gui" or something like that. This would then reslult in the GUI not showing elements that are not active when the drop is pulled (or grayed out if that's a better way), but in that matter the translation would still work for historic data. When adding new records to the table, the inactive elements should not show up.
Using the Windows GUI it's possible to perform a check on the entered value and (re-)place the cursor in the desired field using cursor_to_col_id in a Default procedure. This only works when the user uses [Enter].A same kind of validating is needed in Universal GUI, but then should also “be aware” of the user leaving the field using [Tab].
Tab button order to be customizable. For example when a user wants to change the default Tab order to be able to customize it as he likes.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.