238 results found
-
Update User Step when returning from Subtask
We would like to have the feature for reloading sub-tasks within a User Step. The subtask should be updated with data from a Machine Step, provided that the a machine Step is connected to the User Step using a Data Arrow. If so, the User Step will be updated when a sub task in the User Step is done and the User returns back to the User Step. The reload of data can also be triggered manually by swiping down. Works in Android app but not in Web client.
3 votes -
Enhanced Workflow Menu Filtering
Currently, when clicking "Add Workflow to Menu" in a workflow, the list of server objects displayed is filtered to show only menus, which is beneficial. However, the list still includes "folders" that do not contain any menus, leading to unnecessary clutter. We kindly request an improvement to this feature that removes folders without menus from the view.
3 votes -
Ability To Insert Variable Into Priority For Buttons
The proposed feature centers on enabling developers to incorporate variables into the priority settings for buttons. This means developers can assign dynamic priority values to buttons based on contextual factors, such as user interactions, screen content, or application states. The platform will use these variable priorities to determine the order in which buttons appear on the user interface.
3 votes -
Enhance Portal 2 Record Selection Listeners to Include Deselect Events for Real-Time Data Refresh
In Portal 2, the current record selection listeners provide a powerful feature to update portlets when new records are selected. However, we have noticed that the listeners do not trigger when records are deselected, resulting in stale data being displayed in other portlets. To improve the user experience and maintain data accuracy, we propose enhancing the record selection listeners to include deselect events or introduce a new listener specifically for deselecting records. This enhancement would enable portlets to refresh in real-time when records are deselected, ensuring that users always have up-to-date information displayed across all relevant portlets.
3 votes -
Visual Indication for Editable Columns in Datagrid
As a user, when working with a datagrid, I often find it difficult to determine whether the data is editable and which specific columns allow editing. This lack of clarity can lead to confusion and potential errors when interacting with the grid. To enhance user experience and improve usability, I would like to request the implementation of a visual indication for editable columns in the datagrid.
3 votes -
OData Connector Attribute List Ordered Alphabetically
We would like “Order of attributes“ is an example where attributes have no order to be ordered alphabetically. In Read operation keys (indicated bold already at the moment) could be first in the list and the remainder of the list should be ordered alphabetically.
3 votesThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
Find Usages of a Flow Property
The usage of propertied enhances the productivity and maintainability of software development by enabling developers to gain insights into the usage of specific properties in their codebase quickly and efficiently. This should show in which Flows the property is used and be able to quickly navigate to that Flow.
3 votes -
Save Data in Table Portlet on Enter Keyboard Command
A user should be able to save data when pressing the "Enter" key in a Table Portlet.
3 votes -
Option to to take the local server address into account in on prem self hosted environments
we would like to have the same link on all our installation, not need to change it per installation, then we have taken #DB_SID# in the hostname, and we can have the same link on all installations, but with the current setup, we still need unique link as the server address is embedded.It would be great if an option existed in the on-prem image to take the local server address into account.
2 votes -
One Spinning Circle Instead of Two Loading Report/Document Viewer
The customer would appreciate if there were one spinning circle when loading report/document viewer items instead of two. it was not how it behaved in prior versions of Portal. One spinning circle would better appealing.
2 votes -
Allow Date Inputs to Interact Within Same User Step
Component: Workflow → User Step → Date Input
Customer Feedback:
We often use date ranges (from–to). Both default to today, but if the 'From' date is set far ahead, the 'To' date should adjust automatically. Users find it frustrating to manually scroll through the calendar to correct the 'To' date.Current Limitation:
You cannot reference or update the value of one input field based on another within the same User Step. Referencing works across steps, but not within the same step.Request:
As a user, I want a date input to be able to update another date input within the…2 votes -
Add support of editable date and time columns
We require a change in the data grid component to support editable datetime columns. This is need for our users to be able to select dates and times in the brewing process that is very sensitive.
2 votes -
Select taborder
Be able to select taborder or press enter for different grids and list selections not just the last one on the grid.
2 votes -
Move Data Grids Horizontally In User Step Elements
The customer would like the option to move data grids horizontally within user steps. Currently they can only be stacked vertically.
It is similar to how the text used with the labelled static text element can be moved when using the medium/large setting. This would allow the customer to see more data on large screens without having to scroll in excess.2 votesThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
Remove unnecessary words in assertion step
Assertion steps in Portal2 currently include server log information, which is unnecessary for users. It would be better to omit this and display only the assertion messages.
2 votesThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
Disable update prompt
Kohberg, like many organizations, manages software installations and updates through a centralized deployment service. However, the current Windows client lacks the option to disable update prompts, which can interfere with managed deployment strategies and lead to inconsistencies in software versions across the organization.
2 votesThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
Transaction names for offline data
Allow users to provide transaction names or a similar process that allows users traceability for what transaction are queued.
2 votes -
Mathematical Constants in Flow Script
Introduce additional functions or constants in Flow Script that provide users with direct access to key mathematical constants such as "e" and "Pi".
2 votes -
Allow Scheduler Portlet to listen to "onRefresh" of other portlets, particularly the record viewer
In some instances the drag-and-drop functionality of the Scheduler is not ideal, but you still want to display the data in a Scheduler and edit it in a separate portlet like the Record Viewer. This works, however the changes are not reflected in the Scheduler portlet until it is refreshed, and you cannot set a Scheduler portlet to listen to OnRefresh from a Record Viewer Portlet.
2 votes -
Update Web Service connector with new WSDL file once connector has already been setup on Cloud
Currently a WSDL contract is necessary when creating the connector. However, once the connector is set up, it doesn't need ongoing access to the contract. On an on-premises server setup, the contract could simply be placed in the file system and accessed from there. However, on a cloud setup, direct file system hosting isn't possible.
One suggestion is using a file system connector, which would allow users to upload the file onto the cloud server and then point to it. However, this approach is somewhat unconventional and a bit of a “rouge style”. An additional layer of complexity exists if…
2 votes
- Don't see your idea?