Improved customizations of user inputs validations
exploring
Dor Meiri
Port self-service actions already support a rich set of input controls: required fields, type enforcement, regex patterns, and JQ-powered dynamic forms. We want to take that further by letting portal builders define validation rules that run directly in the form, before execution.
This means conditional logic like "replica count must be at least 3 when deploying to production", cross-field rules like email confirmation, and meaningful error messages that actually tell users what to fix. All without touching backend scripts or waiting for a failed action run.
Dor Meiri
marked this post as
exploring
Dor Meiri
Merged in a post:
Conditionally required action inputs
M
Matan Heled
In case of very dynamic action forms (where the form changes as result of certain inputs) it would be ideal to be able to make certain inputs required dynamically, as result of a certain field change.
An input can be hidden until a certain point, and then when it is visible it might be required. You cannot set it as required, since it if remains invisible it will cause triggering issues.
Dor Meiri
Merged in a post:
Dynamic "required" per field rather than per form
P
Pavel Pikat
The current design where "required" is defined once in the form's JSON, makes it very difficult to add multiple complex conditions for different fields. E.g with 5 different conditions, the jqQuery becomes quite messy.
The proposal is to make "Required" configurable for each individual field, similar to how "visible" works at the moment.
Dor Meiri
Merged in a post:
Ability to provide custom self service action regex validation error message
J
James Daniels
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".
Dor Meiri
Merged in a post:
Conditional Form Submission & Step Control
D
Daniel Holcik
I’d like to propose a feature that would prevent users from progressing to the next stage or submitting a form based on specific conditions.
Right now, we’re relying on hidden required fields to enforce this, which is bug-prone and limited. Implementing it similar to “Step-level visibility”[https://docs.port.io/actions-and-automations/create-self-service-experiences/setup-ui-for-action/advanced-form-configurations?additional-inputs=visible] would provide more robust, flexible validation, improve user experience, and eliminate the current workaround.
Also implementing it as a new feature would make sure nothing breaks for existing users of Port who are using the workaround so negative impact to existing customers would be hopefully non-existent.
Dor Meiri
Merged in a post:
Cross-field/dynamic validation in SSA form inputs
N
Niran Amos
We want to dynamically validate action form string inputs so that the second field must exactly match the first. Currently you can apply a regex to each input, but they don't work to validate between fields.
Example Use Case: An SSA where the user inputs an email address, and then they're required to confirm it by entering the identical value in a second field.