Previous Topic: Develop Standards for Subsetting UsageNext Topic: Example: RI Trigger Names


Shared Objects

Among the most important standards to develop for subsetting involve the creation and treatment of common objects. In particular, define the following common objects early in the Design phase:

Test shared Design objects thoroughly for correctness and ease of implementation by the developers. To ensure the readability and usability, implement and test a small set of screens and review them with the business user.

If you wait too long to define common objects, developers create different objects for the same purpose. For example, they create multiple exit state messages for the same condition.

Carefully coordinate changes to common action blocks. Instead of checking in changes as they are made, consider keeping the action blocks on the workstation until the changes have been tested.

Consider protecting common objects by checking them out before checking out subsets for further development.

If you are using workstation Construction, work out a plan for sharing generated executables, RI triggers, and databases. Decide who generate each, how to share, what is available and when.

See the Protection Subsets section in this guide and Construction subsetting task recommendations.