Author Archive

Prior to Studio Release 12, database interface exceptions were commonly handled by:

1. Including a result code field for each database interface.
2. Confirming the results for each return call of a database interface to decide the action to take (i.e. throw exception).
3. Executing a special exception workflow with appropriate notifications.

For example, for one RiverStar client we created custom action to execute on every database interface that called an API to check the result code field. If it was set to “1”, the API would ...