Feature ideas

Today we can add an "affected entity" to an action by using the run_id as a parameter. This approach has 2 challenges: Cannot add affected entities if the action is chaining a few actions that would ultimately create an entity (for example the action triggers a PR, then on merge the entity is created) In the "Run" tab of the entity page, we don't see the action that triggered it if there was an indirect chain of events (for example PR)

Add support for scheduling for actions. For example - allow an action to run every hour/day/week/etc. In addition, provide the option to schedule an action for future execution. For example, an action will trigger once, in an hour (and won't trigger again afterwards)

Be able to have an option to decide which self-service will appear in self-service hub and which will not be there

Currently as it stands, an action can only be associated with one blueprint. It would be great to have an action be associated with multiple blueprints, for example if we want to restart a service, all catalogs will have service overview and likely this action will be associated with service overview entity. In all scenarios there will also be services from respective container orchestration (ECS/EKS) - right now as it stands an action if associated with service overview entity cant be associated with the service blueprint entity - which means a new actions should be created which can be associated with the service (orchestration layer service). The goal here is to be able to use the lightning button and trigger actions instead of going to the action section and triggering it.

Ability to configure timeout values for actions within Port so that certain operations, like deploying a service, do not exceed a certain duration.

Currently, using the dynamic permissions feature, self-service actions will still appear in the UI. In case the user is not permitted, the run will be rejected only after sending the self-service action form. As part of this item, we would like to support hiding/displaying self-service actions using the dynamic permissions policies.

Allow categorizing self service actions for ease of finding appropriate actions for your needs.

When a user executes an action and isn't supposed to (for example entity is created already), the message they get is "contact your admin". It would be good for admins to have the option to predefine a set of message when each rule fails

We would like to have an ability for ordering self-service action items coming from the blueprint.

Port has the ability to configure a variety of advanced inputs when creating an action. Some of these inputs are dependent on other things and take a tiny bit of time to load. Users can execute the action by accident while these inputs are loading. If the button is greyed out until the inputs are loaded in, similar to required inputs that are empty, it would help.