Analyzing Interactions › Defining Entity Views › Defining Attribute Views

Defining Attribute Views

Each entity view contains one or more of the attributes of the entity type of the view based on the needs of the process. For example, the Entity Relationship Diagram fragment for the process Take Order shows that the entity type CUSTOMER contains three attributes:

• Name
• Address
• Phone Number

Based on the illustration of the manual Take Order process, the entity view of customer in the import views of Take Order includes only the Name attribute. So, the only information required for a customer is the value of its Name.

The only property available for an attribute view is its optionality within the import views.

If an import attribute view is specified as mandatory, it must have a value when process execution begins. You must therefore be sure that a value for every mandatory attribute is available to the enterprise when an entity is first recognized (that is, needs to be created) by a process.