Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
End subsequent processes when a prior process with exception raised

My use case is there are multiple processes for a save action after page submit. When a process raised exception, I would like to skip subsequent processes and show error message and don’t close the form. How the config to do so? Thanks.
Best Answer
-
my use case is I have a modal form to update a record. The form has a save button and if record can be saved success, it closes the form. I create 3 processes and set server side condition when the save button pressed. 1st process is validation for the record.
Then run it as a validation, not a process. APEX separates validations and processes for a reason.
2nd process is updating record. 3rd process is close the form. How can I ensure the subsequent process should be fired only if the prior process can be completed success.
I trialled this yesterday. The default APEX behaviour was to cease processing when an exception occurred. If you are seeing something different then I suggest you share a demonstration on apex.oracle.com.
Answers
-
Please update your community profile with a recognisable username instead of "User_LI6U7".
What are the process execution points?
What type(s) of processes are involved?
What do they do?
What do you mean by "don’t close the form"?
-
Fac586, my use case is I have a modal form to update a record. The form has a save button and if record can be saved success, it closes the form. I create 3 processes and set server side condition when the save button pressed. 1st process is validation for the record. 2nd process is updating record. 3rd process is close the form. How can I ensure the subsequent process should be fired only if the prior process can be completed success. Thanks.
Once after update my display name, it is saved but not effective.
-
my use case is I have a modal form to update a record. The form has a save button and if record can be saved success, it closes the form. I create 3 processes and set server side condition when the save button pressed. 1st process is validation for the record.
Then run it as a validation, not a process. APEX separates validations and processes for a reason.
2nd process is updating record. 3rd process is close the form. How can I ensure the subsequent process should be fired only if the prior process can be completed success.
I trialled this yesterday. The default APEX behaviour was to cease processing when an exception occurred. If you are seeing something different then I suggest you share a demonstration on apex.oracle.com.