105 results found
-
Persistent Rendering of Results in Scheduler
Currently, when users render a result in the scheduler, then navigate to a different page, and later return to the scheduler page, the previously rendered result is not retained. This behavior contrasts with the functionality found in the filter portlets and the Gantt portlet, where results persist through page navigation.
We propose that the scheduler should retain the rendered results even after navigating to a different page and then returning. This persistent rendering will provide a more consistent user experience and align the scheduler's functionality with other parts of the system.
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.
-
Enhanced and Customizable Highlighting for Scheduler
Currently, the visual emphasis when an object is selected in the Scheduler is quite subtle. This could potentially cause users to struggle in identifying their selected object, especially in a dense schedule.
We suggest enhancing the object highlighting functionality in the Scheduler. This could involve introducing a more pronounced visual cue, like a more prominent shadow or highlight. It would be beneficial to make the intensity of this visual cue customizable. Additionally, users should be allowed to choose the color of the highlight, providing another layer of customization and personalization.
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.
-
Improved List of Values Display in Portal2 with Filtered Inputs
In Portal2, when using a List of Values (LoV) tied to a table column, there seems to be an issue displaying the data if the LoV's data source is a Flow with an input filter. The data is displayed if no input filter is considered, but it does not show up when inputs are taken from Portal.
Proposed solution is to address the inconsistency by ensuring that the List of Values in Portal2 displays data correctly even when the LoV uses a Flow with input filters from Portal. It's crucial to provide consistent visibility and accessibility of data irrespective of…
1 vote -
Custom "Edit Operation" button labels
Currently, to have editable columns in a table, 'Edit Operations' must be enabled. This approach allows only the usage of pre-set buttons named "Update/Delete/Create". However, in some contexts, these pre-set names are not suitable or meaningful to the end-users.
We suggest allowing customization of the button names in 'Edit Operations'. This feature will allow users to rename the "Update/Delete/Create" buttons to terms that better fit their specific use cases.
1 vote -
Both date & time set with "Today" button in Filter Portlet
Currently Portal 2 datepicker has separate date and time pickers. This feature request would allow users to set both date and time by pressing the "Today" button.
1 vote
- Don't see your idea?