For more information, please refer to this announcement explaining best practices for getting answers to questions.
Fast Formula - Exception Handling and Writing standards
Summary:
When creating a custom Fast formula (FF) - is there a method to capture unexpected errors? Also, are there any standards/best practices for structuring FF?
Content (please ensure you mask any confidential information):
In PLSQL you will have something like:
EXCEPTION WHEN OTHERS to handle unexpected exceptions, so is there an equivalent for FF?
I have encountered an unexpected exception as follows: ORA-20001… a number was divided by zero while running the formula. This is probably due to a data migration issue. Ideally I would want the process to complete with status 'WARNING' and exceptions to be recorded in the log, the seeded functionality partially achieves this but is it possible to programmatically capture information - without uneccessarily creating large log files.