Feature ideas

Currently, only admins can view action runs histories (via the audit log), but it would be helpful for non-admin users to be able to view runs other than their own in order to be able to debug issues and use other runs as examples.

In certain scenarios in bigger organizations it is not unusual to have an approval flow that will involve more than one team. The review for a request can be done in * parallel - request denied by any of the teams would stop the workflow * sequentially - request review progress to the next step only after the previous team has approved Even a basic implementation on top of the existing could provide a lot of value and further anchor the use of the portal as a coordination tool for processes and teams.

Allow sending a validation requests with user inputs to the backend prior submitting the form. For example, validate the user input for corectness against custom business logic, and display an error returned from the backend under the text field, without actually submitting the form. This way, the user has a chance to adjust the input, without having to re-submit the entire form with all the values again

We propose adding support for configuring a query to look up created entities. This enhancement will allow SSA (Self Service Action) runs to be populated with details of the created entity based on the lookup query after the SSA finishes successfully. The process will include the following steps: Configuration of Lookup Query: Introduce a configuration option to define a query that will be used to search for the created entities in the system. Entity Association Post SSA Completion: Once an SSA run completes successfully, the system will execute the configured lookup query to find the associated created entity. Retry Mechanism: If the entity is not found immediately, the system will perform several retries at defined intervals to locate the entity. The number of retries and the interval between retries should be configurable to accommodate different system requirements and latency considerations. Explicit Marking of Not Found Entities: If the entity is not found after all retries, the SSA run will be explicitly marked as "Entity Not Found." This status will help in identifying and troubleshooting issues related to entity creation and association. Benefits: Immediate Feedback for Users: People running the SSA will see the entity created via the SSA in port almost instantly. This provides users with immediate feedback on the action, eliminating the need to assume the entity was created or manually look it up in the port. The created entity will be presented in the context of the SSA, enhancing user experience and satisfaction.

In some cases, we may want to create a certain default value for a field based on previous selection made by the user. This can include literals and even multiple fields references. The default value should be adjusted automatically until the field becomes visible.

Currently defining an input as a secret does not work in cases where there is an approver on the action. https://docs.getport.io/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/secret Port should support using input secrets and approvers in the same action.

In some cases an operation failed and a retry will solve it. Adding a retry action for a run can be nice addition :)

Now that a deep link to a specific self-service action is available, we have taken advantage to link directly to a self-service action. Specifically, we have made a similar portal feedback mechanism to the one offered in the demo site, and then added a hyperlink within the description of a given page like "Have feedback about this page?" which is hyperlinked to the "Leave feedback about the portal" Day 2 action. Unfortunately, this link takes the user to the Self-service page (albeit with the correct action modal opened to the form). Completing the form then leaves then on the Self-service page. Similar to how related self service actions are handled within an entity table or from an action card, it would be nice to have a way to trigger the display of the appropriate self-service action form as a modal over the page that the user is currently (perhaps with some opinionated/specially handled markdown syntax to designate creating a link to trigger the display of a specific self-service action?).

Today if a user enters text to a string based input field for a Self Service Action that happens to be invalid determined by a Regex match pattern. The user is presented with a red font colour error message in the format "must match pattern {regex-pattern-here}". Even though we have a human readable validation hint message on the field description. We've had numerous users not find that and instead become blocked and distracted by the red error which they don't understand. To avoid them reaching out to a admin/action owner for support. I would like to be able to set a custom match pattern error message text. If set the user see's my error message and not the default one. So in my guess here I would say something like "Name use lower case characters a-z or numbers 0-9 but can't start with a number. Name must be at least 3 characters long".

As self service action URL do now exists: https://app.getport.io/self-serve?action=my-action . It will be great if we can add also pre-filled form parameter to the URL, something that could looks like this: https://app.getport.io/self-serve?action=my-action&key1=value1&key2=value2