Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Hello dear Community readers, In the upcoming release of 2023.1 we expect to technically change the way screens are opened for every screen that used the ribbon to select a project and version (so almost all SF screens).A side-effect is that is it now possible to automatically (read: with process flows) open other SF screens without losing the connection to your selected project and version. I could think of a few places where this is very helpful, for instance to switch from data model to subject with respect for the table that you were working on.My question to you is; where would you like to use this the most in the Software Factory? I would love to hear your ideas! Greetings,Ester Product Owner SF & IAM
In the project I work on it happens that both my colleague and I happen to be working in the same Code template. Most of time we communicate about what we work on at what time, but sometimes it happens that we work on the same long piece of coding.It would be nice if I could get a notification or visible indication if someone else opened the code (externally). An alert icon next to the 'Open externally’ buttonExample of Alert icon next to ‘Open externally’ button
With the release of the 2023.1 version of the Thinkwise Suite a new feature was introduced, the Smoke Test. I would like to utilize this feature and allow it to do a quick performance scan.Since it's actions will require the opening of screens, it could help identify possible performance issues within an application. In order to so, it needs to store the duration of the steps which are executed.Could this be implemented in the Smoke Test?
At the moment you can assign a role to one or more modules. An IAM administrator can manage roles per module.In the roles (management, Software Factory) screen it is not possible to see to which module(s) a role is linked nor can you use a module to filter the roles which you would like to edit in the role screen.I would really like to have an extra column in the role screen (first column) which contains the modules to which the role is assigned. If a role is assigned to multiple modules, just put all the modules in this column and use a “,” as separator. Also include this field in the combined filter.Having this in place will allow me to remove the module name from the role name.
After Tuesday's session around CSS, it became clear to me that there are quite a lot of items in the Universal UI that can be styled. Currently any set up CSS could break after a new release of the Universal UI. For most of the style able items this is to be expected. However, it would be great of Thinkwise could (temporary) support a default set of custom CSS items. For example, the form group header font and coloring. This support can be dropped when these setting become available in the Software Factory.This support could even be as simple as just mentioning in the release notes that previous set up custom CSS for this item will break in the release.
Currently, we can use a filter form to filter for values that occur in the dataset. If filtered for a specific value, the set of values in the filter form will be filtered in addition to the dataset. As a result, you must first remove the value in the filter form, which in turn causes all the data to be displayed unfiltered (and thus the values in the filter form as well). Only then you can enter the new filter value. We would like to be able to configure that the values in the filter form are not filtered based on the selected value in the filter form. The values presented should then depend on the original dataset, and not on the dataset currently being looked at. The set of values then becomes a "unique" set of data that is refreshed again with each filter action, based on the original dataset.Without any active filtering all available dates are shown in the dropdown box.After selecting a date and submitting the selection other options are no longer available because of the previously filtered value.
We are saving interface messages to file storage and when using the Document Previewer in Universal we get a unformatted string without syntax highlighting. Our workaround is copy pasting the content to Notepad++, it works but ain't pretty. Would be very nice to have a JSON formatter and syntax highlighting build into the Document Preview of Universal.
Hi,I was looking for a way to for the Combined filter to have a "Starts with” condition, but we have notice that the condition column was not implemented to the combined filter.Only the Filter and the Search have the condition column. It would be nice to have a Condition field on the Combined Filter just like from the Filter and Search Regards,Jason Philip
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.