Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
I'd like to be able to export data to Excel-file, where different data is written into different worksheets within a single Excel-file. This has to be done without the user continuously selecting a different grid and pressing export to excel.I'm thinking about using a trigger-task to start the proces. Then use other tasks to create content for worksheets. I'd like to use Write file to export this content to a specific worksheet in the mentioned Excel file. So would need an additional option to indicate the name of the worksheet in the Write file action.
I would like to suggest the idea when copying a task to add a parameter whether to copy the control procedures and the program objects. Most of the time when you copy a task you don't want the control procedure of the copied task to be bound to the new task, so most of the time you need to de-assign the control procedure.So when unchecking this parameter the copy task does only copy the task, the task parameters, the task references and the table task and table task fields. (in that case you need to create a new control procedure just like when adding a new task)
I'd like to use the kanban board in the Software Factory, but one of the drawbacks for me is the lack of nested work items. I'd like to be able to group them. For example: a work item to create a table, and this parent work item has child work items like datamodelling, UI/UX, setup of the combined filter, screentypes etc.
Currently you can select any font and color that is a available within Thinkwise.For styling purposes I'd like to preselect a number of colors and fonts that can be used in the application and only select one of these colors and fonts. In this way I can't make a mistake and selecting something alike, but not exactly the same. Furthermore it will then be easier to change these selected colors and fonts as part of a theme.Multiple themes can have the same names for these selected items, but have different colors and fonts associated to them. In this way you define these items at a, for instance, project level and give them actual content within a theme. Usage can then refer to the defined items, which might even be a combination of color and font.Think about a single way to define a validation error or warning, or a single way to present too_many, too_few, etc.
We use prefilters a lot as “switches”. When the prefilter is switch on we would like to change not only it's background but the icon to another one and when it's “inactive” change the icon back to its default. Let say like styling with CSS “:active:focus” I think it would be a great feature for all customers. We all use “On/Off” pre-filters and let us create 2 icons “Button ON / Button OFF” icons or “Green / Red”, “Switch ON / Off” etc.
Jump Links to go further down on the Grid View and Form View to all information on 1 View and avoid using multiple tabs.
If possible to auto-hide / auto-appear the Form Detailed View.For example to have a collapsible/expandable Form Detailed View, if the user double-clicks on record or clicks on a specific button/icon to expand/collapse that View.We could have records on Grid View and use a collapsible/expandable Form Detailed View to show details of the record.Similarly how the Main menu works as seen on the attached image.
While configuring roles in my project, I noticed that the roles look similar to activities in the process analysis. For example 'new quotation' and 'send quotation'. I think it would be a nice addition to the Software Factory if it would be possible to convert certain process activities (user requirements) into roles.
It has happened too often that we create a single role in order to deploy a package for testing to Thinkwise, that we have missed to check the All rights option.Setting this field default to True will help alleviate this error.Further on when setting specific rights, this toggle can be removed automatically.Compare this to the toggles for subject performance of default, context, layout and badge. In which case the stored procedures are initially not called, but only after a template has been linked to a program object.
When you need the available space to show the pivot table or chart, but you want the user to be able to drag&drop cube fields, it would be nice if you could hide the pivot table fields by default and only show them when requested. Just like you hide the menu (unpin).
This idea focuses on a new setting for tasks. This settings would allow you to indicate whether you want to receive confirmation that the task has run successfully after its execution.For some tasks you just want to be sure that they have been run completely and successfully. It would also be ideal for situations where you work on some other things while the task is running. You will then be notified when it is completed.Currently, this can be achieved by writing additional code or including the task in a process flow. I would prefer to have a formal setting in the model to do this.
I would like to have the option to colour items in a dropdown. something like a conditional layout in a table column.e.g. to express a preference in wich items to choose from the dropdown first (green items are the prevalent values, yellow are next, red are last)
Expectation is that if it is a single page is under a group that we have the page elevated, to eliminate too many actions on the menu itself. User does not need to go from group dropdown to click on single page of the group. It needs to elevate the page in place of the group and no dropdown.
With menu list and menu treeview you always have to have at least a group. Usually this is fine. Unfortunately there are situations in which a specific menu item is requested to be directly clickable, without first having to open the group.This seems currently impossible, but would be a nice addition.
When adding data conversion it would be great to have other options than only adding a constant default value.For the develop environment this may be sufficient, but when setting it through to other environments you lose the option to look into the database and see which constant value is appropriate.Being able to have expressions you can at least determine an appropriate value. Being able to add a script, you even have the option to add a dummy record and reference that one. This particularly when a foreign key field changes to mandatory.
9 out of 10 times when creating a new project we create a work project. when people are new to the SF it can be very confusion to have the option 'work or base' project. Would it be an idea to remove this option when creating a new project? Every project you create will be a work project. When you like to create a base project you can go to the variant in the advanced menu.
An idea to make a domain control type that is a button.At this moment i'm using a check box instead of a button.
Can 'Theme', 'Default Menu' and Language be added as optional fields in Runtime configurations in SF, to test various themes and menu's during development more efficient?
I wish to have an option to skip all read-only fields, after entering a value in a field.In some scenario's the tab key must be pressed multiple times to reach next fiels.
We need to have a Home button in the top ribbon of the Universal GUI to be able to return to the initial login splash page or to a predefined default page.The problem is when having the option to Hide Documents as enabled, means you cannot see the opened pages and you cannot close them. If those are not visible to close them, you can’t really see the initial login splash page at any time after login in.The requested solution:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.