Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Could a page with an overview of all hotfixes be added to the documentation portal or TCP? Now the only way to determine if hotfixes are all installed is to download the complete set from TCP and compare it with the records of the table hotfix.
A new Thinkwise developer was creating his first project, using the e-learning. After deploying his datamodel and making a few changes in the User interface he wanted to create a new project version. Sadly here it went wrong. He used the Task ‘Create project version’ instead of ‘Copy project version’, expecting it to create a new version of his project. After a while he found out that all his work was gone and didn't knew what caused it. Maybe we should rename the task or make it a bit more clear that it is used for creating a new empty project version. This is not something you are not going to do many times, during development. Any suggestions?
I use a confirmation message on a delete task in my application to inform the user that the delete will delete every underlying record of the record that the user tries to delete. When validation my application I see the validation 'Task confirmation message without parameters’ and tell me the following: ‘The user does not get any indication what the task will do when he is asked to confirm or decline the task. Add a message (with parameters in the translation).’ The only problem is that I can't select any value for the parameter if I would use one, so I'm left with approving this validation to make it go away. If I could select a column in the Task screen in the Software Factory that would be given to the message as parameter, that would make me able to make the message more specific and more informative to the user. Then I could change 'Do you want to delete this record and all underlying records’ to 'Do you want to delete and all underlying records’ with being the value of the column selected in the Software Factory.
Either with use of the process flow or standard functionality I would like to be see my subject refreshed after a background task (task with Await result = No) has been finished. Currently I have no other option than to refresh the screen myself or put in an automatic refresh; both not ideal. The task is updating statuses and I would like to be able to see the progress in real-time without user interaction. Maybe introduce even a tsf_send_refresh function?
When you request something from indicium (ie a table or subroutine) and a column is empty, then indicium will not send the column with the respond. It would be nice if there is a setting per request if you want the empty columns to be sent or to be hidden.
I would like to be able to change the color of the progressbar. Currently it's always Thinkwise-blue, but when designing a custom splash screen for a customer this blue isn't always the best option. Being able to adjust this color from within the IAM would be a nice improvement!
Currently when user uses a filter within our tree component, the GUI will only display rows matching the filter value. I would like to tree component to display all the parents of the row matching the filter value and the rows matching the filter value, instead of only displaying the rows matching the filter value.
Currently I use conditional layout on a Status column and if for some reason I change my domain element database values, I have to change the conditional layout conditions too. So I got the thought, why can’t we connect it straight to a domain element? My column import_message_status has a same-called domain with elements for each status. If I could select an element of this column's domain, that would mean any changes in the domain will also affect the conditional layout condition. Example: Let say if I change the Done status from value 5 to 6, I only need to change it at the domain elements and the conditional layout condition will read that value over there instead of I need to change it at all places where I name the status column in conditional layouts. Implementation suggestion: Column determines which domain. Type of value: (Domain) Element Value: Lookup to select which element of the column's domain In code, a join/a subquery is used to get the right db value of the chosen element
We can use functionality to influence decisions in a proces flow, but from the designer it is not visible that a code template is assigned to a process step. I'd like it if a symbol was there to indicate an assigned code template. Generated symbol in a process step (quick and dirty mock-up)
I would like to be able to indicate which tables should be kept in memory in order to improve the performance.
For example, for insurance companies it is important to look at photos to make an accurate judgement whether or not the company should pay out insurance money. Or for a webshop that sells printers it is important to show the customer what the product looks like. Currently we can kind of make something like what I will suggest here (in combination with a list and the document viewer) but it's not exactly like it.What I picture is something like this:Picture slideshowHow I picture this in the Thinkwise software (pun intended), is that this would be a Screen type component.A table “Product” with a detail table named "Product photos” should be created. The screen type should be attached to the “Product Photos” table and will show all photos from a single product. The way it should determine which column to use for the image slideshow is to find a column in the table that has an Image control. Uploading photos can be done by either making a Task or maybe even through the screen type component.What do you think about this idea? Let me know
I would like to have the ability to tell the model to hide or disable a task when you do not have a row selected. Now when you create a task that needs variables/values from a table you need to write a context to hide/disable the task when you do not have a row selected. This happens when you start with a empty table for example. It will save time to just have to tell the model to disable/hide the task when you do not have a row selected. In some instances you do want to be able to open the task (for example to create a record), but most tasks are related to the tab task parameters you enter.
For those of you who don't know, there is a feature in the SF that automatically highlights columns that might contain privacy sensitive data. This works based on lists of words that it checks for in the column name. For every field in the database there is the option to decide whether it contains sensitive data or not, but especially for these suspicious fields it is recommended to make the decision to automatically anonimize the data or not.However, the validation that brings this to the attention of the user, is called “Suggested columns with undecided sensitivity”. I would like to change the wording of this to “Columns with potentially privacy sensitive data have not been reviewed”. Although I am not a native speaker I think this makes more sense to the user, but more importantly it increases awareness for AVG/GDPR compliancy.Thanks for voting if you do.Mark
Currently the Software Factory offers no setting to enable or disable “Excel Style” filtering. Whether this option is enabled, is determined based on the Filter and Sort settings. I would like to enable or disable “Excel Style” filtering regardless of the Filter and Sort settings.For example: I have a row which display an amount or margin. I would like to sort on this column. I cannot allow “Excel Style” filtering for this column, because the amount of unique values exceeds the amount the “Excel Style” filtering can handle, the result is an application freeze. Therefor I would like to be able to disable “Excel Style” filtering.
Deleting a record is not possible when the record is linked in other tables (unless ‘cascade delete’ is set). The GUI will show the following error message when this situation occurs.The error message doesn’t clearly mention which records are causing this problem. A user would like to see the specific records that are linked to the row. This error could occur in a lot of screens when ‘cascade delete’ is OFF.A solution would be to create specific errors per table. But this would result in a lot of INSTEAD OF DELETE triggers and a lot of (TSF) messages.I’d rather see the GUI solving this issue with the knowledge of the metamodel behind it and showing every entity with the look-up value of conflicting records.
Within the Software Factory you can create variants for lots of things, but not for themes. I often have separate themes for windows, web, mobile and universal, to tweak the little things that just look better on a certain platform. Or use different themes for the DTAP environments, to make it extra clear that you are in development or test. Now I have to copy my 'base' theme, which works just fine. But when I want to make a change to something that is identical in all of my themes, I have to manually go through them all. I would like the ability to create theme variants, that work just like the other variants in the SF: always look at the base, only adjust the differences in the variant.
Currently when downloading a TW Suite upgrade, the downloaded folder contains 2 TW deployer executables: twdeployer twdeployerGUI I find it confusing that the executable, that starts the deployment tool, is currently the twdeployerGUI. Based on the names, I would expect that the executable, which I have to use, is the twdeployer. However this executable is used to start the deployer while using command prompt. Therefor I would suggest, change the name of this executable. So for example twdeployerCONSOLE or twdeployerCMD. If any of you has a better suggestion, feel free to post it as a reply to this post.
I'd like to use a slider as an user interface control. In this way, I could configure the column/domain to have a certain range and increment.
To get a good visual structure in the requirements and to increase maintainability it is necessary to be able to nest FR's. When describing a functional requirement about for example a new attribute in the logical datamodel, it is often the case that there are other requirements that are directly linked. For example: when creating a relation input in attribute X is mandatory. By nesting these requirements the maintainability increases, because if the attribute is not needed, by deleting the main functional requirement the nested requirements are deleted also. The same in copying requirements, nested requirements are copied also.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.