Propose your fantastic ideas regarding the Thinkwise Platform to our Product Team.
When a look-up control is set to suggestion, the dropdown of the lookup only shows the first 8 results. But in fact there could be a lot more results. This is not clear to the user. Please add a visual indication for the user when there are more results. Preferably when clicking on the indication, it opens the lookup popup.
Can the configuration under User Preferences to set Start Objects also be made available in the Universal GUI, as it is in the Windows GUI?
Currently task “Code difference” has been disabled for Control Procedures with same name, same baseline, updated in both branches.As we have a lot of these situations it would be very helpful if we easily could compare both code-files and make decision.So please always enable the task in case the object-type and object-name is equal.
We have deployed an application for use on a ZEBRA scanner device.The application functions smoothly and intuitively, with one exception.It is designed around barcode scanning, and in over 95% of cases, the process can be completed simply by scanning barcodes. To support this workflow, the SuppressBarcodeKeyboard setting is enabled (Yes), which hides the on-screen keyboard.However, this has a side effect: users are unable to manually enter codes using the keyboard. This becomes problematic when barcodes are either inaccessible to the scanner or damaged.To address this, we would like to add an action button within the barcode control that allows users to activate the keyboard when needed.Something like this:We hope this is possible.Alternatively, is there another workaround you would recommend?
The new debug center looks great, but we would like to see some adjustments to the layout of the process flow monitor so that it can better assist us in resolving errors. Resolving issues in Process Flows is often very time-consuming. The process flow monitor we had in the Windows GUI wasn’t ideal either, but it still often allowed us to locate issues more effectively.We hope it is not to much effort to come to a layout more like this...Key focus points: Make the most efficient use of screen space wherever possible, assuming that nearly all developers have at least an HD display Indicators showing which actions were not successful Duration of actions in milliseconds, highlight slow ones Type of action with symbol Display associated database event(s) per action as well
A check in development mode versions of the Universal GUI and universal Backend to compare both versions or showing all version information on the information screen in Universal GUI.
I think it would be nice if you could change whether a task is placed in the overflow or a primary action based on data of the row.There are a lot of tables with a large number of tasks. Being able to hide tasks in the context is good, but sometimes I don’t want to fully disable a task, just guide the user with tasks they are most likely to use and tasks that are seldomly used in certain states.
In a current customer project, the customer indicated an issue with how numeric and integer fields handle input length restrictions.At the moment, when a numeric or integer field is configured with a maximum of, for example, 6 digits, users are still able to enter more than 6 digits. This results in a validation error message such as: “Artikel nr heeft teveel cijfers”However, the customer expects the behavior to be consistent with varchar fields. For varchar fields (for example varchar(6)) users are prevented from entering more than 6 characters in the first place.Requested improvement:Align the behavior of numeric and integer fields with varchar fields, users are prevented from entering more digits than the configured maximum length, instead of receiving an error message afterward.
When you make an existing column in a table mandatory (and no default value is set), you get a very helpful validation warning you to setup the data migration for this column.When you create a unique index on an existing column (or set of columns), no validation will be shown.It would be nice to have a warning in the validations list to show the developer that this could lead to issues.
When a domain with datatype BIT and control checkbox is not mandatory, there are 3 options:empty (null) selected/active (0) deselected/inactive (1)When it is mandatory there are 2 options (0 & 1) but an asterisk is shown behind the options. For the user this looks like you have to select the active option. F.e. when you have to agree to an user policy it is obligated to check the checkbox. → We would like to have a mandatory checkbox without the asterisk so the user does not feel obligated to check the checkbox.
Idea to add conditional layout on a card list. Below I have a card list and a normal list with conditional layout. But the conditional layout is not visible on the card list.It would be great if this is possible! 😁
Would it be possible to have an extra Height Unit available called something like “Form Units” which is equal to the raster height in forms? This is the unwanted result when a fixed height in pixels is set, is shows extra whitespace then the height is to much or a vertical scrollbar when the height is set to low and it also depends on the client screen screen size and resolution. Especially on small handheld devices this is annoying.Ideally it should look like this
The backlog of the Universal GUI is really missing drag and drop from a cardlist. In a web-environment a card-list is quite often used (at least we do) and it is really a pity that apparently the drag-drop functionality will not be implemented for this component. I would really like to see drag-drop also from cardlist aside the grid and tree.
Hi,It would be greate to bring the arrange functionality back to the process flow designer screen!Currently, I'm really struggling to get a clear format, that's partly due to how the lines originate from the output side, especially when using a loop or multiple lines. As a result, it starts making strange turns on its own in the design screen.Maybe you are already working on that, in which case I haven't said anything haha.
SummaryAllow Thinkwise customers to share AI-enrichments they've created in their own Software Factory to a central, curated repository managed by Thinkwise — so that the entire customer community can discover, import, and benefit from enrichments written by others.The Problem TodayEach Thinkwise development-team develops AI-enrichments independently in their own Software Factory. There is no mechanism to share these enrichments with the broader Thinkwise community, which means:Customers reinvent the wheel building similar or identical enrichments. Valuable knowledge and innovation stays locked inside individual tenants. Smaller teams with fewer resources benefit less from AI capabilities compared to larger customers who invest more in development.The Proposed SolutionIntroduce a Shared AI-Enrichment Hub within the Software Factory, with the following flow:Create locally — A customer builds an AI-enrichment in their own Software Factory as they do today. Opt-in to share — The customer can choose to submit their enrichment to Thinkwise for inclusion in the central repository. Review & curate — Thinkwise reviews the submission for quality, safety, and relevance before publishing it. Distribute — Approved enrichments become available to all Thinkwise customers, who can browse, preview, and import them into their own Software Factory with one click.BenefitsFor customers sharing their enrichments:Recognition within the community as a contributor. Potential for Thinkwise to provide feedback and quality improvement. Contribution to an ecosystem they also benefit from.For customers consuming enrichments:Faster time-to-value — no need to build common enrichments from scratch. Access to high-quality, real-world enrichments built by experienced peers. Inspiration for building their own enrichments.For the Thinkwise ecosystem overall:Accelerates AI adoption across the entire customer base. Builds a vibrant, collaborative community around the platform. Thinkwise gains insight into how customers are using AI in practice, informing product direction.Possible Limitations & ConsiderationsGovernance & quality control Thinkwise would need a review process to ensure submitted enrichments meet quality, security, and privacy standards. Versioning and maintenance Enrichments may break or become outdated as Thinkwise evolves. A lifecycle policy is needed — who is responsible for maintaining a shared enrichment over time?Context dependency Many enrichments are highly tailored to a specific domain or data model. Generic enrichments will transfer well; niche ones may be less reusable and cause confusion if imported out of context.Discoverability As the repository grows, good tagging, categorization, and search functionality become critical. Without them, the repository risks becoming cluttered.Security & data privacy Customers must be sure that submitting an enrichment doesn't inadvertently expose proprietary data or business logic embedded in the enrichment's prompts or configuration.Suggested Scope for MVPA simple submission flow from the Software Factory to Thinkwise. A basic browsable gallery of approved enrichments, filterable by category or use case. One-click import into the customer's own Software Factory. Clear contributor attribution and a basic rating/feedback mechanism.
In Universal is is no longer possible for a user to create custom aggregations (column totals in the grid for instance), this was possible in the Windows GUI.
In Universal it is no longer possible to drag cube fields to change their order, this was possible in the Windows GUIThe workaround of adding a panel with cube fields is not user friendly, and take up valuable screen real estate
We are currently tightening user permissions within our IAM applications. Each company has its own IAM application with at least one key user. A key user supports IAM activities and is responsible for maintaining the role/permission structure for other users.We have reviewed the key-user responsibilities and adjusted permissions so they only have what they need. As part of this, we removed access that allowed changes to application-level settings. We no longer want to assign Main Administrator or Application Administrator roles to key users.Since these changes, key users can no longer access the “Effective user rights” table. This table is very useful for them because it provides a clear overview of what permissions users effectively have.Is there a way to grant access to the “Effective user rights” table by adding the required permissions to one of the following groups, without giving admin roles? Our key users currently have these roles:Application owners Group administrators User administrators Simulators
Auto-refresh is done based on the last refresh timestamp generated by the client, as the client and server can be out of sync for many reasons this leads so situations where the auto-refresh works incorrectly. This can lead to extra or missing refreshes.My suggestion is to include current server timestamp in the reply of the entity or auto-refresh procedure and use this as the input parameter to send with the next auto-refresh check.This way we are never in situation where we can have any desync of clocks.I am aware there are ways to avoid this issue but all are a workaround to essentially a solvable issue.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.