Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
Goal: customizing the Universal GUI for different platformsIt could be helpful to tweak the Universal GUI based on the platform. We would like to make a difference in look & feel between mobile and universal logins.Currently there is no selector in the custom css, so selectors for ‘mobile’, ‘universal’, ‘windows’ and ‘web’ could do the trick
In the Themes used by Windows & Web it is possible to disable the display of icons on tabs. I was wondering where this could be set for Universal themes. I need to disable the icons on tab level. We only want to display icons on the tiles and not on tab level. This setting is not available in the Universal theme page of the SF.
To give the user a language choice as a user preference in the Universal UI.We also need this for ourselves to get rid of the different logins (demo_en, demo_eng, etc.) in the Insights application.
The current dbEventlog has potential but not very friendly to work with, can it be upgraded a bit to have the abilitty to filter, sort the list on long running queries. Also showing the type of query (app, sf, iam) the main subject would help.. now you have to decipher the query to actually know what it's doing. And lastly, can you show the query and not the prepared statement..
It would be a nice feature if we could make certain filter form values mandatory and set a default value. Especially with big datasets you would require the user to for example fill in minimal 3 filter criteria before actually executing the filter.. (in this case we would start empty with filter).
The option to enable system versioning is great for creating log options. As I see it the SF could do it automatically already by creating a copy of the system versioned table, make it a meta custom view, copy all the column names into the view column_names and add the valid_from valid_to fields at the beginning as PK's. I do it manually now, but it would be great to have it as a default option in the SF.
Currently, the "code" of a role (role_id) can contain a maximum of 100 characters.To clearly define roles, we would like to have more space available, so that we do not have to work with all kinds of obscure abbreviations to be able to make sufficient distinction within those 100 characters.The description of a role is longer (1000 characters), but in many places in the SF and IAM the role_id is shown and not the description.Can the length of the role_id field be increased, for example to 250 characters?
Dear thinkwise We are using the Odata api to retrieve data from the thinkwise application but when we retrieve the openapi document from:https://server/indicium/sf/insights/openapiwe find it contains too much information too.Is it possible to only retrieve the information of certain endpoints/tables so we can automate the updating of the openapi definition in other application.
Our application is very large. This also leads to a very large OpenAPI spec (~50MB) and metadata file (~3MB).This is disproportionate for any external application that may wish to integrate with a Thinkwise application, which generally only need access to a small portion of the application.However, the OpenAPI spec is considered the industry standard for consuming an outward-facing API.In our Thinkwise application, we have several defined menu’s for different apps, which can be switched to in the Windows GUI through the context menu.See below screenshot for an example:The context menu within the Thinkwise Windows GUIThe “DMS app” and “Klantportaal” are menu’s containing a subset of views, tables and tasks which the respective applications use.Currently, these applications each required a lot of effort to implement each endpoint, because there is no tangible way of getting the specs for this menu.I understand, from this answer on a forum post, these specs and metadata files are filtered based on the authorized user's roles defined within the Thinkwise application.This is sufficient in the context of a user account defined in the platform, but falls short in the context of an external application which doesn't interact with Thinkwise in the context of a user.Currently, in Indicium Basic, the OpenAPI spec and metadata are available at http(s)://{{server_url}}/indicium/[iam/sf]/{{app_id}}/openapiandhttp(s)://{{server_url}}/indicium/[iam/sf]/{{app_id}}/$metadatarespectively.It would be a great addition for Indicium if these endpoints could become available per menu. For example, the OpenAPI spec for above “dms_new_mobile_app” menu could be accessible through http(s)://{{server_url}}/indicium/[iam/sf]/{{app_id}}/dms_new_mobile_app/openapior something similar.I think this would be a good step in making applications developed in Thinkwise more accessible to external applications.Currently, as a developer working on external systems, Thinkwise seems a very isolated environment, with little to no flexibility for integration.This seems like a design flaw for a low-code platform suitable for “large and complex business applications”, of which the data is almost always required by other applications that exist in an organizational landscape.I would love to discuss what possibilities there are, or even discuss other potential solutions for improved integrations.Should you have any questions, do please ask them in the comments.Thanks in advance!
I'm missing this button in the GUI when I’m using a password field:Show password button I only see this: Can this 'Show password’ button be added? Else there is a possibility that I put in a wrong value.
In IAM you can see your system flows and also add an extra schedule as a application owner. But the thing I am missing is that an application owner can manually start a system flow from IAM.Epically handy when in D/T/A environments but also useful in production when you don't want to wait 59 minutes for a system flow to become active when it just ran 1 minute ago.
In the Software Factory, we have the Icons screen where we can find every icon used in our project. However, if I reuse the icon for a label, this icon gets duplicated in my overview. As a result my overview gets crowded with identical icons: I would prefer to see the used labels as a detail list per icon. This would motivate the reuse of icons, because I would have a much more streamlined overview of all icons. This would also make the list of icons more manageable: instead of altering an icon per label, I can change a group of labels in one alteration of an icon.
Currently there is no way, in for instance Themes, to differentiate between tables, tasks or reports in a listbar menu. Or I have missed something. See the example below; the last two items are tasks and the rest are tables. I've switched of “Show icons” in the Theme, to keep it slick… Whether a table or view is opened or a task is started (possible on the background) is a surprise for a (new) user…. It would be nice if there were a way to seperate tasks from tables in a Listbar menu. This might be done by the GUI or give the developer the tools to achieve this…Perhaps the addition of a dummy divider line with possibly a translatable label...
When a user currently encounters a deadlock and she is chosen as the deadlock-victim, the user gets a message asking to rerun the transaction.Solving (frequent) deadlocks is something a developer should do, but they still can happen. Often, when a user retries to run the transaction, the problem has gone away.I’d like to propose a client side (GUI/Indicium) solution that will re-try the transaction without the user intervening. This way, the user is not seeing a technical message regarding the deadlock and the action the user wanted to make still pulls trough.I would implement this as follows (my suggestion)Store a setting in SF specifying the amount of deadlock retries (default = 5) GUI/Indicium: Retry the transaction as many times as specified in SF (with an appropriate wait-time) When a deadlock occurs, store the deadlock graph XML in a deadlock-log table in IAM Write to logfile a deadlock has occured (warning) The advantage to this solution is two-fold:The user can (mostly) continue their work and is not bothered by ‘scary’ deadlock messages The developer/administrator has insight in how many deadlocks happen and has got a log of deadlock graphs to look at.
When setting up a unit test for a trigger the input you set up is not passed on as parameter. Instead, it is only available in the insert statement values list (hardcoded). This makes is super difficult to set up an assertion using the input parameters. Therefor the only way to check your inserted data is setting up a hardcoded assertion query, which is not what you want. Because if you change an input parameters you also need to change the assertion query.A unit test for triggers should pass the input as parameters. These parameters can be using in the insert statement and then also be used in your assertion query.Currently example below is not possible. This should be possible.
Hi, when performing an upgrade on a system versioned table, the current data of the table is always completely written to the history table. In most cases this is unnecessary because the data does not change. I would like to see that only records which are mutated by the upgrade go to the history table.Especially for the development environment I can imagine being able to completely disable writing to history during upgrade.
We have been playing around with the Universal GUI and we find it more and more limiting that the action bar doesn't play by the rules of the screen containers. The action bar always covers the whole width of the screen and if you want a list on the left and details on the right it becomes very confusing for the user, because you end up with 2 actions bars one under the other. It shouldn't be to hard to make it follow the screen containers you define. The first screenshot only has a container for the detail and the action bar is contained by it. The second should follow the same principle, the action bar(s) should be contained by the containers they've been put in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.