Working with Application Workflow Manager (AWM) requires an understanding of the data model it is based on.
This topic provides you with a short description and understanding of the key AWM concepts which are later developed in the Data Model Details chapter.
Function packages are a central feature of AWM and provide tool sets for specific application functional areas. Adding a function package to an AWM model can enable you to manipulate properties, objects, and tools for a specific functional area. For example, a function package is provided that enables you to work specifically with Eclipse resources. Another function package provides tools that enable you to work with RESTful Web applications.
Every tool used in a model must be taken from one of the function packages.
A function package can provide the following AWM modeled objects:
A property is a fundamental concept in AWM, it represents any relevant attribute within the application system that is to be integrated into an AWM model.
At run time, a property will be set with property values. For example:
| Property | Property Value |
|---|---|
| File name | MyDocument.txt |
| Change date | 2014/05/25 |
| Write protected | True |
A property can be used in various contexts within an AWM model. For example, a property can be used as an attribute of an element type, as a criterion of a filter type, or as an input or output parameter of a tool descriptor. That is to say, the meaning of a property is defined by the context in which it is used.
A property is referred to as a linked property type if it is introduced by a function package.
Values of linked properties are not internally maintained by AWM during run time. When a property value of a linked property is needed during run time, AWM forwards the request to the corresponding function package. The function package can then provide or set the property value.
A class of elements with common properties is called an element type.
The element types are derived through analysis of the application systems to be integrated into an AWM model. Every resource type of the application system to be integrated is a candidate for an element type.
An element type is called a linked element type if it is introduced by a function package. AWM does not cache property values of linked element types. Property values of linked element types are requested by AWM from the corresponding function package provider at run time.
Linked element type functions include, but are not limited to:
An example of a linked element type is the Eclipse resource provided by the Eclipse function package. The Eclipse function package provides the following features for an Eclipse resource:
A tool represents an executable program that can communicate with the client application via input/output parameters. Tools are provided to AWM by a function package. The Function package provider defines the tool's attributes and parameters to be used in the AWM model. The function package provider also provides the tool implementation.
A tool is defined in the AWM model by a tool descriptor. A tool descriptor describes a tool in such a way that the model interpreter can execute it and can react to its outputs.
The following are standard attributes defined in a tool descriptor:
These standard attributes can be extended by additional attributes defined by the AWM model extension for this tool.
An action is a closed function that is triggered in the user interface. An action consists of one or more statements or tools.
An action is defined in the AWM model by an action descriptor. The processing sequence of the statements/tools of an action are determined by the sequence of the Action Has If/Else, Action Has Loop, Action Has Continue/Break Loop, Action Has Exit, or Action Has Tool relationships. AWM enables the conditional execution of statements belonging to an action depending on property values at the point of run time.
The execution of an action is usually triggered actively by a user. In some cases, an action can also execute automatically, such as to determine an element's properties.
At run time, actions can occur:
The actions that will be carried out for the listed AWM object types are specified in the AWM model through the relationships of the object types (element type, filter type, and so forth) to action descriptors. Actions which do not belong to a certain object type must be modeled as a global action. See Global Action for more information.
Filters with the same types of filter criteria are referred to as filter types. Filter types are used in AWM to create a list of elements based on common values in the filter criteria properties for further processing.
AWM supports the usage of wild cards in filter criteria properties.
Element list structures are the concept in AWM to define the structure of tables in the Table Results view. The relationship of an element list structure to its column properties defines the structure of the corresponding table at run time.
An element list is created by a "Create Element List" relationship from an action descriptor. The element list structure has to be referenced in the "Table Structure" attribute of the relationship so that an element list is displayed in the Table Results view.