E1: ORCH: FORMEXTNS: Is There a Way to Validate Data Entered on Form so That When Orchestration/Logic Extension Throws an Error, the Action of Saving is Stopped
(Doc ID 3036734.1)
Last updated on JULY 23, 2024
Applies to:
JD Edwards EnterpriseOne Orchestrator - Version 9.2 and laterJD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.
Goal
There is a requirement to validate data on a screen so that when the user selects the OK button, a form error is displayed and the action of saving on the form is to be stopped.
EXAMPLE SCENARIO
Form Extension and Orchestration Design:
- Create a Logic Extension that accepts the phone type value and if the value entered is equals to "HOM" phone type, throws a Form Error (018A).
- Create an Orchestration to call this Logic Extension and implements the Messages option to display a message once execution is completed.
- Add a Form Extension on the Phone Numbers form (P0115|W0115A) and associate the Orchestration to the OK Button (Button Clicked event).
- Map the Phone Type value.
- Set the Execution option to "Execute After Event"
- Set to Run Synchronously and Show Message.
Testing Steps:
- Run Address Book application (P01012).
- For a Address Book record, select Row Exit "Phones"
- On Phone Numbers form, enter phone number record with HOM as the phone type.
- Click OK button.
Result:
- Message is displayed as form error stating an invalid value error.
- Cancel out of the screen.
- Go back to the Phone Numbers form, the record is still saved.
Expectation:
The user's expectation is to stop executing the existing event rules on the form when the Orchestration throws an error so that the form data is not saved.
Is there a way to prevent form data to be saved when Orchestration that is associated in a Form Extension throws an error?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |