Skip offering selection if there is only one
Custom form configuration
Per service definition dynamically configurable form (Simple Form)
Would configuration-in-code be alright for hardcoded fields? In that case, I'd put a constant somewhere like this:
MANDATORY_FIELDS = {
"metadata.name": {
…
Restrict user input to more sensible ranges
rixx
pushed to 243-service-provider-improvements at servala/servala-portal
2025-10-24 10:24:42 +00:00
Sanitize Input fields for Allowed Characters
Are you sure we don't need umlauts/accented characters in organization names?
Inline user info in service offering page