52 results found
-
To make the Database connection option optional for HTML portlets in Portal 2
HTML portlets serve as a repository for exhibiting non-dynamic content in portal 1. However, in portal 2, it requires a select query and a database connection.
This limitation results in a less intuitive experience when working with them.
It would be greatly beneficial to restore this functionality in portal 2 for client applications, allowing for a smoother transition and enhanced user experience.2 votes -
Workflow Datasource Ordering in Portal
When listing workflows for data source in e.g. a table Portlet, the ordering is appearing randomly. Ideally, a selected workflow should be on top and the remaining preferably ordered alphabetically by name given in Studio.
2 votes -
Allow developer to connect one flow to multiple buttons in Portal 2
We would like to use the same flow for multiple buttons in Portal 2. We use the input table to drive what the buttons do. Therefore, we would like to have that functionality in Portal 2 to connect one workflow to multiple buttons. Today, I need to duplicate the workflow to connect one button to one workflow. This adds unnecessary maintenance.
2 votesThe feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
-
Personal Saved Searches in Filter Portlet
Users desire a feature that allows them to save personal search parameters within the Filter Portlet, similar to the functionality provided in IFS. This will enable users to quickly reuse complex filters and searches, enhancing their productivity and efficiency.
3 votes -
Component workflow parameters as default template for added components
When I add a component to a workflow I want to have all the component parameters as a default input to the component when I add it to a workflow.
As it is now I have to open the component to figure out what parameters to use, copy them and paste them into the component step in the workflow.
1 voteThank 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.
-
Explicitly set the type of values fetched in SQL machine steps
I want to be able to define the data types for my SQL query so that the Designer knows the types I can work with when designing my apps and components.
1 vote -
When importing an Flow 6 archive (wap files), get the question if you want to auto-commit components without errors
When I'm importing a Flow 6 file with a lot of fragments, I need to open all new components and commit a version before I can use them in my app. This is very time consuming.
1 voteThank 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.
-
Auto-Centering of Portal 2 Scheduler Based on Current Time
In the Portal 2 environment, users must manually adjust the scheduler's view daily to align it with the current time. This manual process becomes inefficient for users, especially in environments where the scheduler is in a read-only state across all departments.
Proposed solution is to implement an auto-centering feature for the Portal 2 scheduler that automatically aligns the view with the current time upon refresh. This ensures that users always have a centered view of their schedule relative to the present time without manual adjustments, enhancing user experience and operational efficiency.
1 vote -
Option to link datepicker as listener for Gantt Portlet
Currently, users must manually select dates in both the filter portlet and the Gantt date picker when they wish to restrict the data source to specific dates. This process is tedious and requires the portlet to load twice.
We propose a feature that allows synchronization between date pickers in the filter portlet and the Gantt. There should be a setting in the listening portlet that enables users to link its date pickers to one or two date pickers in the filter portlet. When the user filters on specific dates, the linked date pickers should automatically update, reducing manual steps and…
2 votes -
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?