Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
If you have a text area field (memo field) and you have a lot of text so you need to scroll, there is a popup on mouseover. This is such an annoying popup, because it makes it impossible to read the information in the field, because in the popup everything is plain text and it covers completely the text in the text area: It would be awesome if we could use the textfields.
I would be great if the combo-elements can have a default API call to fetch translations for element ID's.
One of the validations that I am currently missing, in regard to configuring roles, is a validation that informs you as developer of task/report parameters and table columns that are marked as granted but are not available. This scenario often is a result of changing the lookup table or lookup value. In that case the rights will be reset to not available, while the parameter or column is still granted.It would be of great help if the Software Factory could detect this issue during the validation run. Because often you are unaware of the fact that your change has broken this lookup and therefor these rights.The result is often that this issue is only detected in the final phase of acceptance testing or even worse, after pushing the new release to production.In summary I would like to have 3 additional validations:Column is set to granted but lookup is not available Task parameter is set to granted but lookup is not available Report parameter is set to granted but lookup is not available
To ensure data is stored in the database correctly and consistently we have to use code to fix user input. It would be great if we could put input masks on field so the user has a visual clue what to put in and how to put it in. Also this could lead to more consistent data insertion. See:
My users complain that when a multiline field contains more text than can be displayed, they don't have the magnifying glass in Universal to open a pop-up of the field. The field can't grow either, so they have to scroll but are never able to see the whole message in a single moment.They do however get a tooltip with the whole text compressed and in a smaller font size, which is also not very useful, if the field had a magnifying glass or a more useful tooltip, the app would work a lot better.Maybe when a magnifying glass has been enabled on the domain disable the tooltip?
Control procedures can be assigned to multiple tables. Usually these are more generic procedures e.g. a default to set a date field to today (default_set_today), or a layout procedure to make a field mandatory (layout_mand).Finding these control procedures can be difficult as they don’t include a table name in their name. When copying a table name from the application and then pasting that name in the Functionality search bar then does not provide the right result.Alternatively we have the Code Overview screen, but this can be slow to load and displays (only generated) full program objects instead of control procedures.Can't we include a column in the Functionality screen, that displays all tables that the control procedure is assigned to?This can then be assigned as a filterable column by the combined filter, and decrease the time required to look up what control procedures are connected to the table/screen you are working on.This new column would be updated every time an (un)assignment is done so that it would always be available, also when the project version is not yet generated fully.Using this approach would also encourage developers to create smaller chunks of code, which could be an extra incentive to create unit tests for these smaller chunks of code, providing a higher unit test coverage.
To be able to easily share things you’ve made or explain what is going wrong on the community it is handy to be able to upload screengrabs.This is currently done by uploading still screenshots or gifs. Gif files are very limited in length due to the file size and low picture quality.It would be great if we could get support for webm files.
We are currently using the resource scheduler to plan work orders for employees and the resource part of this scheduler shows many employees.If we switch to a month, week or day view, a combobox appears above the scheduler in which you can select one or more resources (employees), but in the timeline view this combobox disappears. The only way to filter the employees in the timeline view is by using the filter in the menu of the right mouse click and there you can use a contains or something similar. What I would like is the ability to select multiple different employees just like in the combobox that appears above the other views.More user friendly woudl be to have the resource part of the scheduler work exactly like a grid view. Where you have the filters and sort options above the column in the header. That way I can also filter on additional columns that I have visible in this part of the scheduler.Would that be possible?
Since TWP 2023.1 it is possible to store different Pool user credentials, provided that data protection settings are configured in Indicium's appsettings.json. The Encrypt/Decrypt process actions provide great potential to secure our own data too. However, the current behavior is rather tricky: Indicium will generate a new Key every 90 days, but in order to decrypt data that is encrypted with an older Key we need to keep all old Keys.As a result the Docs contain below warnings, but these Docs are not necessarily top of mind of IT Operators. Also, 10 years from now we would have 40+ of such Keys, some of which more than 10 years old. That might trigger IT Operators to clean up the Key vaults. As such, I believe the current setup poses a serious and hard to manage risk that old Keys will be lost at some point. IDEA: every time Indicium triggers creation of a new Key, all Encrypted data must be updated with the new Key and the old Key should automatically be deleted afterwards. This will ensure we only need to safeguard the most recent Key and will significantly reduce the risk of lost data.
In the Software Factory (2023.1), when I switch branches I get the following message and when executed all documents are closed: Most of the time I don't want this to happen, because I also have my Requirements, Taskboard etc. documents opened, prefiltered, sorted. Closing these documents will result in me opening the same documents again and doing the prefiltering and sorting again. I suggest that only model-specific documents will be closed or I have options to choose whether I want to:close all documents, close all model-specific documents, or do not close documents
I don't have a clue how many of us are still using the Windows and Web GUI's instead of the Universal GUI, but I have noticed that the tooltip timeout (mouse hover / mouse over) of a field in the grid is absent in Universal, whereas in the Windows Gui a build-in timeout of some 4 or 5 seconds seems to be used…In the Web gui the tooltip isn't even shown at all for the field in this example. But that could be to the fact that it's not the most recent Gui we're using.It would be nice if a timeout could be set Application wide in for example the Extended Properties of an Application. In the example below we have a field that has aggregated various user messages in one field in the grid en when the mouse hovers over the field, the aggregated message is shown. Perhaps it isn;t the most elegant solution, but it covers what the user needs.In Universal the popup stays indefinitely In the Windows GUI a user has to be very quick in reading, as the popup dissapears in a few seconds. And I'm not even mentioning the fact that the tooltip isn't limited in width… It is extended over the current windows’ dimensions.. I would like to see this fixed in the Windows GUI (configurable in Extended Properties would be sufficient when it's up to me).
Currently the GUI does not distinguish between Zoom screens versus Main screens in the Open Documents part of the Menu. It would be very helpful to have a subtle indication (a small icon f.e.) of an Open Document being a Zoom screen, as it would help users to quickly know where to go (usually to Main) and/or which screens to close (usually Zoom).Which one is Main and which are Zoom screens?
When I hit F5 my browser (Edge chromium) closes all active “open documents” etc.Is it possible to keep these open after refreshing?
Sometimes it is useful to enter multiple values in the combined filter that are searched in an OR condition
I think it would be good to automatically disable program objects when removing/deleting a handler control procedure. Or at least automatically disable them when no (0) templates are assigned.My situationI thought using a handler was a good option, but during the process I decided this was not the best option. So I deleted the Control Procedure (which includes the template). I thought this was all I had to do to undo the handler that I created.Unfortunately this resulted in errors:[ERR] An unhandled exception occurred while processing the request. (ffba027a)System.Exception: The identity value should be set by the api_call_settings handler.I also noticed that the SF kept creating the a Stored Procedure on the database.Only when I re-created a handler and disabled the Program Object, the error was gone.
Can .dwg (AutoCAD) be added to the supported file formats for the previewer component?
Similar to the Creation screen, we would like to be able to use the ‘Set source for data migration and upgrade’ task in the Deployment package screen and then decide to Continue creation or Review mapping: Currently there is no way to see and/or determine which Source branch and model version are going to be used in the Deployment package. One has to navigate to Model overview > Branches > Form to figure out the setting, and if incorrect, navigate to Data migration and execute the ‘Set source for data migration and upgrade’ task. Following up on the conversation with @Mark Jongeling in this topic as well as the conversation with @Ester and @Anne Buit at the Thinkwise office, I believe it adds value toAt least be able to see which Source branch and model version will be used in the Deployment package Be able to set which Source branch and model version will be used in the Deployment packageWe often perform incremental upgrades on our DEV/TEST environment using the Creation tasks/APIs, but for our Production deployments always use the Deployment package. As such the Source branch / model version always needs to be set before creating a Deployment package.Note: one might argue that this situation does not apply if the practices for the MAIN branch as explained in this Thinkwise blog are followed. But currently such a setup is not feasible for us, among others due to the lack of proper Data migration support in the merging process.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.