Creating Views › Create Views in the Export View Subset

Create Views in the Export View Subset

You can perform the same types of activities when you create views in the export view subset as when you create views in the import view subset:

• Create export group views
  • Add export group views
  • Detail export group views
  • Describe export group views
  • Specify export group view cardinality
• Create export entity views
  • Add export entity views
  • Detail export entity views
  • Describe export entity views
• Create export work views
  • Add export work views
  • Add export work sets
  • Detail export work sets
  • Detail export work views
  • Describe export work views

These activities require the same steps as those for adding import views, with the following exceptions:

• When you add export views, select the view subset labeled Export Views. Keep this in mind when referring to other sections in this chapter.
• Since the naming conventions for export views and import views are different, use the appropriate naming convention as recommended in this section.
• When you detail a group view, entity view, or work view in the export view subset, you cannot specify optionality. Optionality is available only for import views.

Export entity views are views of entities that are output from a process, Procedure Step, or action block after execution. These views consist of the information displayed on a screen, printed on a report, or passed to another process, Procedure Step, or action block.

The name of an entity view should always modify the entity type name. The combination of entity view name and entity type name must be unique within a process.

If you have one occurrence of an entity in the export view subset in Analysis, you can distinguish export view names by using a name such as OUTPUT. For example, if you add export views for the entities CUSTOMER and ORDER, you can name the export entity views OUTPUT CUSTOMER and OUTPUT ORDER. The name of an export group view might be ORDER_LINE_OUTPUT. This naming convention is useful when you want to know at a glance from a long list of views the information you are exporting from a process, Procedure Step, or an action block.

The view subset can contain more than one occurrence of an entity. For example, consider the case where information from two separate CUSTOMERS in the same execution of a process is exported. In this case, the process requires two export views of the same entity type. The combination of the entity type name (CUSTOMER) and view name (output) is insufficient to distinguish between the two views. Each entity view must have a unique name.

Procedure Synthesis generates new view names when you specify processes to be implemented by a procedure.

The Consistency Check facility checks entity views against the following rule:

An entity view must have at least one predicate view.

More information:

Using Views