onSubmit Field Validation in Configurable Workspace (UI Builder)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 07:18 PM - edited 12-04-2024 07:21 PM
I have a requirement.
I have a task extended custom table. And I have to validate the change in state when user submits the form.
For example, if there are 5 state choice values - A, B, C, D, E for the Custom Table.
And the state should ideally be changed from A to B, C or E.
If the user opens a record with state as A and changes it to D, when the user saves the form it should show a confirm box with appropriate message and if user hits ok button - it should allow the submit, else return back on the form and revert the state value on the form to A.
I can easily achieve this in native UI using a Display BR and an onSubmit Client Script. However, I am lost in case of Workspace. Any guidance will be helpful.
I have gone through Confirm modals, but unable to implement it for my case. Also unable to validate in the condition to show modal that the state changed from A to D. Any guidance will be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 09:36 PM
Usually client scripts, business rules that you create on platform side. it works on workspace as well and you don't need to separately configure any thing. Can you check that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 01:09 AM
I have already implemented an onSubmit Client Script with UI type as ALL. It is working as expected in native UI however not working in Workspace.
@Brad Tilton could you please assist on this issue. I've gone through your videos on Workspace in youtube. However, i am unable implement this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2024 02:02 AM
put some alerts, check the logs whats coming in workspace side while using the client script.where is it breaking