Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
For various types of unit tests, the presence of mock data or a preparation query is necessary, as otherwise they are executed on the data currently present in the end product, which may change and lead to unreliable unit test results. This applies at least to all update and delete handlers and triggers.Can a validation be created for this?
One of the great features of the Thinkwise low-code platform in terms of development speed, is also one of the most annoying features from an end user perspective: the concept of Detail Tabs for related tables. It is very challenging to keep the UI clean and understandable when getting more and more related tables. We often have to revert to Views which combine a few tables in order to improve the user experience.Personally, I like the concept of displaying multiple Related Tables in a Single Tab, Grids below each other with each their own Header, only occupying space for the nr of records it contains (Salesforce does this for example). For most related tables the nr of records is usually low, therefore displaying them each on their own tab is a waste of space. Optionally, the individual Grids could include pagination for each related table, displaying for instance 10 rows by default (nr of rows should be a setting somewhere).How about introducing this in Thinkwise, in addition to the current Detail Tabs & Detail Tiles options?
IAM includes a task to clean up unused role sets.I've noticed in several projects that this feature is not well known, and the documentation is also quite limited.However, in some cases, cleaning up unused role sets significantly improves end-user login performance.Is there a specific reason why unused role sets are retained?If not, my suggestion would be to automatically remove a role set once it is no longer applicable.
When working with dynamic code in the SF, the Tags table can grow rapidly for all kind of different settings. After a while it gets harder to select the right tag when adding it to an object, even when using a naming convention for them. Most of the time, tags are used only to link to one object type (for example just to link to tables), however all tags are always selectable for all object types. In order to reduce the amount of tags to choose from, it could be a simple improvement that a tag has an extra optional field where you can select the object type for which the tag is exclusively used (if the field is empty the tag will still show up for all object types). Another thing that could help with better Tag management is adding an extra field with a sub-table (for example ‘tag_group’) in which you can combine tags of the same subject in order to (pre)filter on them quickly.
As a small QOL feature, I would like the ability in the SF to use a default value for Tags so that when linking the tag to an object it defaults on this value.Use case is a tag that needs a value for a dynamic script, but the value is almost always the same.
As discussed in here: https://community.thinkwisesoftware.com/development-13/expand-collapse-all-items-in-resource-tree-view-resource-scheduler-881 I would like to be able to Expand and Collapse all resource tree view items, just like in a regular tree view.
I want to inform my users of my Thinkwise application there will be downtime because of maintenance. We are using the Windows GUI in combination with Indicium. Suggestion made by Erik Brink - We could think of requesting this information before login from Indicium possibly. (See discussion: https://community.thinkwisesoftware.com/deployment-12/announcing-maintenance-downtime-to-users-1096?postid=3184#post3184)
The preview of a document (or url) is determined by the first eligable column in a table. When there are multiple columns in a table that could provide a preview, it is not possible to specify which of those columns to use. A possible work-a-round is to create multiple views were for each view the relevant column is the first one. This however is not an optimal solution because the end-user would have to switch tabs to navigate to the specific view with only a subset of the data.In our situation we work with different renditions of the same document which can have different storage locations and with that different column types. Although every rendition is a separat record, the different storage types are available in the same record and only the first will be used for the preview. The list of documents can contain documents from different storage locations where only the first technical column shows the preview.My proposal is to, in stead of the technical location, use the definition of a subject (or derived variant) as the base to determine which column to use for the preview. This could then be the first visibile column where a variant or layout procedure would determine the visibility of the column to view. This could mean that when there are two eligable columns in a subject, if the first is made hidden, the second column would be used for the preview.
A number of wishes have been submitted in TCP concerning adding rights to an objects.They indicate that when rights are granted to an object, they must also be granted to its childs. Same goes for revoking these rights. I was able to extract the following situations:Rights for a table should pass on to its columns Rights for a task should pass on to its task parameters Rights for a report should pass on to its report parameters Rights for a menu should pass on to its menu items Rights for a process flow should pass on to its process actionsA number of questions about this wish:What if a new column / task parameter / report parameter / menu item is added after setting up the rights? If you give a table rights because you need a column look-up, you now only get the display. Should this change? Am I still missing situations that should also be taken into account for this wish? Personally, I think that when adding a table task, for example, it is going too far to give rights to both the table with its columns and the task with its parameters. @Jeffrey Tolboom, @Roland van Aggele, @Jaap van Beusekom, @Gijs, @Remco, @Arjan Sollie, @JasperSince you have reported a wish concerning this topic, I would certainly like to hear your opinion. Other opinions are also of course appreciated.
Make translation object generation in TSF automatic in the background. When creating and modifying objects. This saves application developers a lot of unnecessary clicking and waiting.
We have discovered the new possibilities of Action bars and are now going to apply them more and more in the screens.It is useful that multiple action bars can be used, but we are finding that it would be useful to give action bars a logical name. For example toolbar_grid_top, toolbar_grid_bottom, toolbar_form, etc.. Could a rename task be added for this?
Dear all, We identified that there is no posibility to execute a task on empty timecell by double clicking. Scenario: A user upon double clicking on an empty timecell to execute a connected Task. Thanks
It would be great if the Maps component supports a Task to add a Marker. We would expect this Task to be triggered by double-clicking on a position on the Maps component, which should then automatically retrieve the longitude/latitude of the clicked location on the Map. This feature could be similar to the Task on the Resource Scheduler with which we can add new Activities on the Resource Scheduler component.
A strike through is a perfect way to show users that something has been deleted, or is discarded for another reason.
Currently it is not possible to change a unit test it’s linked object. I would very much like a feature that allows me to change the object of a unit test. I can image that you are not allowed to change the object type.When do you need such a feature. For example if you split up a table into 2 tables. Or when you create a view of a table and you would like to also include unit tests from this table to be copied to this his new view.Or when you have to copy/split up a task. You would like to copy units or move them to the newly create task(s).It can also be very usefully when you only find out during running the unit test that you have linked to the incorrect object.As to be expected the output and input columns/parameters can only be preserved when they exists in the new object.
Please add an extra setting for tasks in SF to make it possible to select one of the following button sets to make applications more intuitive for end users.1: Execute - Cancel (default)2: OK3: Save - Cancel4: Yes - No5: Yes - No - Cancel
For a businesscase we have to set the color of a chart column to a specific color, based on the total amount. For example, when the column value <= 20 it needs to be shown in red.I recently created a ticket for this on howto activate conditional formatting on charts, but it isn’t possible at the moment. I think this will be very usefull for other customers to.
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