Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When we need to provide API access to our data we want to ensure that the connection is secure. We utilize session_id’s to achieve this.Currently, we lack the ability prevent session hijacking or session ID guessing because we can't bind session_id with other client properties, like the IP address or User-Agent.https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html#binding-the-session-id-to-other-user-properties
The default Zoom/Sizing of the Universal GUI is too large in Chrome/Edge browser on Windows 10. We now have to recommend our End users to use the browser zoom option and set it to 80% to have much better overview... Could this by default please be reduced? If not by default, we then at least need an option to set another default sizing in our environment.
When developing I sometimes want to open the same screen multiple times and finding the menu entry can be a bit tedious. I rather have the option in the context menu to duplicate the selected window. It does not have to keep the filtering but if it does, it's okay too.
I am trying to achieve integration between Thinkwise applications and Office 365. The problem I encounter is that the Authorization protocol OAuto 2.0 does not seem to be supported by the HTTP connector in process flows. The ultimate goal is to come to a solution where end users can independently set up PushNotifications in Office 365, for example if files are added in Sharepoint, incoming E-Mail messages, integration with MS Teams, etc. I guess that once the authentication OAuto 2.0 type is available, connections with others platforms like Google and Dropbox, will be possible too.
It's great to have different view types for the resource scheduler (see below).Unfortunately the Full Week view (https://docs.devexpress.com/WindowsForms/17623/controls-and-libraries/scheduler/views/full-week-view), is not supported in the GUI. Because our production works in shifts, 7 days a week, it would be more readable to have 7 days besides each other (like the Work week view).This would make it more usable for us. It could even replace the Week view. Don't forget the startday of the week.
For context: I'm a support engineer, so I look a lot in the Indicium log files for error analysis, I download them for others to analyse, etc. These are mainly Production and Demo environments.Problem: We have a lot of TW applications, that share a server. Logging can be found in the folders belonging to these applications, this is Indicium and Indicium_universal logging. The issue here is with the filenames of these logfiles, these are the same for all applications.Example: Note that these are two different applications and two different Indicium types, but the filenames are identical. This can lead to looking at the wrong loggin by accident, or to mistakes after downloading these, as the files replace each other and are nog easily recognized outside this context. Idea: It'd be much more convenient and reduce risks plus time spent by support, if the application names and indicium-type could be added to the logfile names. So my two examples would then be something like this:1 : GRP05-Indicium-20210422.txt2 : GRP08-IndiciumUniversal-20210422.txtIs is possible to change this?
It is great that Indicium and Universal GUI now support SSO based on the Open ID protocol. In our case we'll use Azure AD as Identity Provider and wish to enable SSO with Universal. Since Universal GUI 2021.1.15 we can enjoy the beauty of SSO, PWA ánd Seamless SSO. The Seamless SSO is how we want to have it working for our end users, as there is no added value in having to click through multiple screens in 99% of the cases. This means that we have to set loginOptionsHidden or loginOptionsDisabled to true in the config.json of Universal GUI and set a DefaultIdentityProvider in Indicium appsettings.json.However, the current solution is a bit too rigid, as there is no way to circumvent the said Seamless SSO, except for changing the Indicium setting and redeploying Indicium. There are multiple scenario's for which this rigidness is unwanted: If we wish to enable multiple Open ID providers, but still wish to make it as Seamless as possible for each individual user If 1 of our foreign offices does not have Azure AD or if a user is not added as a Guest User in our tenant, we might want to give those users an IAM account If we plan to create customer portals: same as with first bullet If Azure AD is down for some unexpected reason, then we want to be able to get into our application using an IAM admin account as backup If (like we do on TEST now) we want to test with dummy users who reference a User Group, we want to create those users in IAM and not in Azure AD. For all regular users (especially with admin rights) in TEST we would like to enforce Azure AD SSO + MFA though. Now what we like best as a solution would be something client-side, which could be removed when clearing cache (ideally it would not be removed for every Universal GUI upgrade we get though). Given the above examples I don’t think it is ever going to be very useful to have the DefaultIdentityProvider setting in appsettings.json. How about adding a ‘Remember my choice’ checkbox on the Indicium login screen which value is stored in the cache?This provides all the benefits we’re looking for: In case of enabling multiple Open ID providers, a default can be selected by the user, enabling Seamless login the next time they login For non-Open ID users they can simply use the IAM login and perhaps also use Stay signed in + Remember my choice checkboxes to reduce the login steps It provides a way to get into Thinkwise in case the Open ID provider is not available (either through Clear cache or through Incognito browser) It will always and easily allow us to circumvent SSO default when testing in an Incognito browser tab An alternative would be to have a second login screen on Indicium with its own URL that is not impacted by the SSO settings, but it’s less convenient than above solution. There could be other alternatives, and we’ll leave the choice up to you. But something is needed here.
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.
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].
At the moment when you open the dropdown menu the first option is a white space, but we do not want to see the white space in a combo/dropdown menu.From a user(s) perspective: A user would click on a dropdown menu and see only the data field which are selectable. The white data field won’t be presented.BeforeAfter
This is for Universal GUI.As a user I would like to update/change my password while already logged in the application.It would be useful for users to have that ability provided to them in the Account menu.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.