Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When changing the application in IAM the existing tabs, which were opened by the user, will stay open. It would be nice if this could be changed and that when someone changes from one application to another application, the existing tabs were closed. Not as a default but as an option using extended properties.
Dear all,As per current documentation the In-memory OLTP functionality in SF supports regular on Premise SQL server. Since many of us are going to cloud hosted SQL server we need to have this option enabled for cloud as well.Personally my projects are on Azure SQL and have researched only for the specific one. Other might use AWS, Google etc. Requesting that this option is enabled and during Creation process to recognize if In-Memory is Supported by the DB and accordinlgy set the correct options on the tables script creation or upgrade script.Example:On my Dev I have a lower Pricing Tier with no OLTP support. I should be able to run create and my In-Memory configured tables should be created as normal.On my Acceptance (UAT) which is production like my Pricing Tier is higher with the support of OLTP so when connecting during creation to build my code for a deployment it should detect that this is supported and my tables should be created with related option for in-memory use.ThanksMike
If you want to build an application in traditional layers, there are things you don’t want to show as a form, some things only as lookup, for filters, etc.It would be great to be able to define that something is not for user input, and hide it from the subject list.
For the listbar- and tile menu in the Universal GUI, data-testid's are added on the html-elements for the buttons. These data-testid's are missing on the html-elements for the buttons in the treeview menu. Only the html-elements for the icon and the label contain a data-testidA data-testid on the html-element of the button would really help for styling and testing purposes
We increasingly encourage to register the test scenarios they have in the SF under Manual Test Scenarios. Key users should also be able to do this. Both the registration of these scenarios and the execution of a test run. This also includes creating findings. There is actually no role for this yet. A test role. A role that only makes these test functionalities available. The situation is such that we have indicated that we will register the test scenarios in the SF. These are currently in an Excel file.Later, if Key-users are going to perform regression tests, for example, it would be appropriate if they could do this via the SF. Then all these test runs are registered. The wish is therefore to create a test role that can at least be used for the following components:Specification -> Manual Test Scenarios Quality -> Manual Tests
When creating a table column that has a calculation type, it is necessary to write some code. Based on the type, the structure of the code will be different from one and other. Such like Expression columns, you can make use of the “T1.” alias, which is the table itself, whilst Calculated columns cannot use this.Just like the code example in Control procedure for SQL-typed CP's, I would like a short example that shows me as a developer what I can (and cannot) use as code. Example: Expression: concat_ws(' ', t1.first_name, t1.last_name) --Thanks @Robbert :) Calculated: (100.0 + tax_percentage) / 100.0 Calculated (function): select sum(order_total) from sales_order where sales_order_id = @sales_order_id
Currently the Subname object is placed within the Quality → Validation section. This is not preferred. There should a direct menu item for the subnames in the Software Factory. Probably under the menu group Data.
Reason behind the below request is that currently, our soon to be published application will need to server approximately 6k users. Managing mass notifications through scripts and other non-automated actions is not efficient and can easily make mistakes.We are in need of an email functionality within the IAM to communicate with the users.What this functionality needs to do is being able to store specified email templates by the IAM administrator. Be able to set automated emails based on specified template to be send out related to Actions done within the IAM from a user as alerts. User Activation & de-activation. User management related emails ( registration, unregister, account deletion, etc... ) Sending informative and Notification emails (System Maintenance, Downtime, Planned upgrades) Have it linked to the Universal GUI under the Account Menu, for user System notifications within the published apps. The IAM sits on top of Indicium and the SMTP configuration can be used to send out the emails. Please let me know what you think and if there is already the same idea posted share it to be voted.
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?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.