

Designing the Procedure Logic › Design Designer-Added Procedures › When Not to Use a Design-Added Procedure
When Not to Use a Design-Added Procedure
In general, a designer-added procedure should not perform CREATE, UPDATE or DELETE actions on entity types identified during analysis.
The following list details the exceptions to this guideline:
- Maintaining business or designer-added entities in support of user tasks; for instance, contained in personal work-in-progress, or in a work queue.
- Maintaining replicated data by procedure logic instead of by the DBMS.
- This is the recommended method, but may not be possible where more than one DBMS must be used, or data is related to data in a current data store not maintained by the application.
- Transfer or deletion by archive procedures of entities that are no longer of interest or that can legally and safely be discarded.
More information:
Build Designer-Added Procedures
Copyright © 2013 CA.
All rights reserved.
 
|
|