

Building the Action Diagram › How to Define Logic for Elementary Processes and Procedures › Add Entity Actions › Expand Expected Effects in the Action Diagram
Expand Expected Effects in the Action Diagram
Expanding expected effects consists of the following activities:
- Select an elementary process in the Activity Hierarchy Diagram or Activity Dependency Diagram.
- Specify the expected effects of a process on one or more entities.
- Access a Process Action Diagram that contains no existing actions.
- Expand expected effects.
When you expand expected effects, CA Gen generates the following information in the Process Action Diagram:
- Defined import and export views are added. This is not a specific result of expanding expected effects; it occurs as a result of defining import and export views for a process.
- Entity action views reflecting the entities you specified for expected effects are added to the Action Diagram. These views are unnamed; you must detail the entity action views to name them.
- Attribute views reflecting the attributes of the entities you specified for expected effects are added to the entity action views.
- Any combination of the entity actions (CREATE, READ, UPDATE, or DELETE) on associated entity action views are added. These actions reflect the expected effects you specified for the selected process in Matrices, the Activity Hierarchy Diagram, or the Activity Dependency Diagram. The actions also represent the actual effects of processes on entities.
For example, if you specify the expected effects of READ and DELETE on the entity CUSTOMER in the Activity Hierarchy Diagram, CA Gen populates the entity action view subset with an unnamed view of CUSTOMER. CA Gen also automatically generates a READ customer action and DELETE customer action with appropriate subordinate actions based on other menu selections you make while expanding expected effects. This is an efficient way to populate entity action views in the Action Diagram.
Expanding expected effects applies only to the Process Action Diagram. It is not applicable in Analysis action blocks, Design action blocks, or the Procedure Action Diagram.
Copyright © 2014 CA.
All rights reserved.
 
|
|