AB#128603 - ABC - Custom label for form buttons

[Joselgc1]

Description

Forms were always using the same save and draft labels, including when the same form was opened inline or in a modal. Admins can now configure normal text or SurveyJS-style expressions for both actions in the Form Builder, with separate modal overrides available under Navigation > Advanced so labels like “Save and Send” or “Update draft” can change based on answers such as status, while still falling back to the existing translated defaults when no custom value is set.

Type of change

• New feature (non-breaking change which adds functionality)
• Improvement (refactor or addition to existing functionality)

Screenshots

To change a form's labels

To change a form's modal Labels

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[AntoineRelief]

@Joselgc1
Requested change
The save button label should not be the same between the form modal & the form
By default, the text isn't the same, so we must have 2 distinct options

[Joselgc1]

Implemented in new commit.

[AntoineRelief]

@Joselgc1
If you can give me example with working expression in details of PR please

[Joselgc1]

Working Expression Examples:

The new button-label settings accept either:

• Plain text, for example Save changes
• A SurveyJS expression, when the value contains {...} and resolves to a string

Examples below assume the form has a status question.

saveButtonLabel: iif({status} = 'draft', 'Continue editing', 'Save form')
Result:

• In the regular form, if status = 'draft', the button shows Continue editing
• Otherwise it shows Save form

modalSaveButtonLabel: iif({status} = 'draft', 'Update draft', 'Update record')
Result:

• In the form modal, if status = 'draft', the button shows Update draft
• Otherwise it shows Update record

saveAsDraftButtonLabel: iif({status} = 'draft', 'Update saved draft', 'Save as draft')
Result:

• If status = 'draft', the draft button shows Update saved draft
• Otherwise it shows Save as draft

Additional info:

• If the value does not contain {}, it is treated as a plain static label
• If the value contains {}, it is evaluated through survey.runExpression(...)
• The expression must resolve to a string, otherwise the raw configured value is used as fallback

One important note:

• With the current code, modalSaveButtonLabel falls back to saveButtonLabel when modalSaveButtonLabel is empty. Same for modalSaveAsDraftButtonLabel and saveAsDraftButtonLabel.