Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Creating mock data sets is the single most time consuming task when creating unit tests. Often data already exists in the project database which, after some careful adjusting, is suitable for unit tests. I would like to easily import this data into a mock data set to speed up creating unit tests.
In addition to the following topic:It would be nice to be able to weave code before the begin try so we are able to create custom scenarios in the software.(For example for logging purposes)For the same reason it would be nice to be able to weave code after the end catch.
Can we please get a more user friendly version of cubes? Setting up a simple graph is more complicated than it should be. I feel like we could greatly benefit from having the UI/UX team having a look at cubes and think of a more refined way of creating cubes and graphs. Maybe adding a wizard to guide you through the creation process would be very helpful.
Per request of @Vincent Doppenberg & Rene JochemWe’ve build more than a few systemflows to act like if it is a asynchronous processflow. These systemflows will do some stuff when it finds a record in a certain table, for example the recalculation of prices within an (larger) offer, which can take a while to complete due to fetching stuff like current prices from the outside world. The systemflow will scan every 5 seconds to see if there is something it can do and for a very large percentage of its lifespan it will find nothing to do. With enough applications on a server this will cause harsh spikes on them.What we were and still are looking for are asynchronous process flows, that for example are triggered by the end users push on a button (within the Windows GUI) in which the process flow will act like a systemflow does and needs no more user interaction so that the user can either log out or do something completely different with the application.rgds Ricky
Goal is to have a separate icon defined for a filter when Active and a different one for Inactive. We came to a situation where we need to have a filter icon more visible towards when active or inactive. Currently the only separation between the 2 states is the underscore under the icon itself.The idea is to be able to define the icon for Active like and when Inactive likeWe can use icons of opposite state for defining the Active and Inactive state.
The FTP-connector currently supports regular FTP and FTPS. The sftp or SSH protocol is not yet supported. I would like to see this additional protocol supported.
Currently, grouped columns open by default with all groups closed and only the top row expanded, like this:I would like to have an option in the subject to open all grouped columns by default. Then it will look like this when I open the document: This option is already available for the tree settings, but not yet for grouped columns.
Hi,A suggestion for the improvement to the current deployment process for table changes in our Software Factory. At present, when a table undergoes a change, the deployment package generates a CREATE script for the entire table. This approach often results in significant data migration, which can be time-consuming during deployment.To improve efficiency, I propose that if a table change involves adding a column at the end, the deployment package should generate an ALTER statement instead. This modification would significantly expedite the deployment process.Implementing this change would be highly beneficial for us, as the order of columns in a table is generally not critical. The GUI is configured in the Subject, and for views, handlers, triggers, etc., the code should specify the correct columns explicitly.Could this be considered as an optional feature in the deployment package?Thank you for considering this suggestion.Blommetje
One of the greatest features in Office 365 nowadays is the Microsoft Search box on top of every Office 365 screen. It searches through all O365 tools, records and document content I have access to. This does away with the traditional need to navigate to the right menu/folder and then filter/search for the right record or document, as well as with the concept of adding a very long and descriptive title or tags for a document.Other tools also offer this feature and display the returned records order per Entity (see attachment for how Salesforce does this). Could this functionality be added to Thinkwise, having the Search box in the top bar of the Universal GUI?
Who hasn’t seen a user entering an order number or a product number in the menu search bar only to get disappointed that it does not work this way? So why not make it possible to search for (the main) objects of our applications this way? Of course performance is key, so I am thinking it should be configured by a developer on what exactly will be searched and with what condition (different from what is configured as global search for each object). There are countless ways to implement this and how the result could be presented. But by taking Microsoft office as an example, it would be cool if the user could select one of the configured subjects or search in all. When clicking on something in the result list, I am expecting that it will open the subject page jumped to/filter on the selected object.
In universal you can only add/remove custom prefilters. What’s missing is the customization of predefined model prefilters like in the windows gui. Because of this if you deactivate a prefilter it will stay deactivated. This makes the universal very confusing to use. If you deactivate a prefilter to find a inactive company that prefilter will stay off. The next time you open the screen all inactive company’s will be visible again. The show active company’s only prefilter is there for a reason. I think the windows gui logic makes more sense. The on/off settings in the model should be respected, and there should be the option to change this in the prefilter settings (like in the windows gui). so i propose: 1. add the model prefilters to the prefilter customization settings for UP.2. don’t save prefilter settings by default but always revert unless changes were made to the UP.
I would like to maintain views in the SF which should be part of a different database schema, so not dbo.Use case is a set of views which will be authorized for a group of users (via Excel link) of reporting system (e.g. PowerBI) to query on.Assigning the rights is much easier if a specific schema can be assigned to create the views.Also it will be clear what the purpose is of a certain set of views.
I would like to have the option to hide a detail tab if no data for it is present.This obviously only useful for data that the user does not have to add, only for display, update or delete.In some applications it can prevent inexperienced user for clicking on loads of empty tabs to find the information she/he is looking for.
Currently the context procedure is not being called when adding a record. I wonder why and what the drawback of this could be. When the context procedure is called when adding a record each time a default procedure (if any) would be called, the following could be achieved in the application: When creating a new order for (in this case) a vehicle, it could be the case that a vehicle is not known in the database. So while adding and no vehicle is yet selected, a task is available to the user to create a vehicle with the minimum of known information entered as parameters. A vehicle is created with a “request” status, someone else can enter all viable information at a later point in time…. The new vehicle_id is an output parameter en will be entered in the new order's field…. But with a context procedure not being called at this stage, I can't hide or show the task and someone can keep clicking on it, creating one after the other partially entered vehicle… I could circumvent this with a default and layout procedure in the task, but I'd rather see the task hidden completely when a vehicle_id is entered while adding a new order…. Long story short: why not call the context procedure always the same time when calling a default procedure (at least when adding a new row)….
I would be useful if users could deselect search columns in their user preferences. Developers can then set up desired columns for all users, after which users can make them specific to themselves
Change the behavior of the open/zoom function of the preview component to responsive, instead of opening images scaled to 100%.See the example below. End users experience this as annoying.
It would be nice to have a variant_id for layout , context and default
Hello,It would be nice if there is a possibility for the handler logic to be variant dependent. Just like badge functionality, I would suggest adding a parameter @variant_id.An example usecase is where we have 2 screens in our application. The first screen disables the default edit button when the row has a specific status. The second screen is a screen available for some type of admins, where they can make changes to the row. However, because of the handler logic, the edit button will always be disabled when it reaches the specific status in all variants of the subject.As a workaround, we changed the handler logic to check if the user is an admin or not and disable the button based on that logic. However, I think it would be nice if we had access to a @variant_id parameter in the handler logic.
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