Introduction

The Model & Go! perspective is provided to support building and managing simple Process Definitions in the Infinity Process Platform Portal. It is intended to enable users with less Process design and implementation experience to quickly build and deploy processes in the Infinity Process Platform Portal.

Note that users with Administrator rights can access the Model & Go! perspective.

The following browsers are supported for the Model & Go! perspective:

Refer to the Infinity Release Notes Release Notes in the Infinity Process Platform Documentation for the Firefox and Chrome browser versions currently supported by Infinity.

Infinity provides support for a business object-centric view on Process Data.

Core Model

To work in the Model & Go! perspective, a core model and its elements must be defined in the Modeling perspective. A core model should define:

Model & Go! retrieves elements from all models in the model repository, therefore these elements can be distributed between multiple models.

Business Objects

A Business Object is not mandatory to create Process Definitions in the Model & Go!, but without it your Process Models can contain only the following:

To work with service task, you need to have a business object and business object compatible application or process interface available. For details on Business Objects, please refer to chapter Business Objects Business Objects of the IPP Concepts. Concepts in the Documentation.

Wrapper Processes

Simple Process Definitions can leverage wrapper processes defined in the core model, which the editor would invoke. Wrappers would apply "by name" data mapping logic. For the "by name" mapping we would create a Data Mapping from Data X to Parameter X - assuming that the types are consistent (e.g. BusinessDate or StartDate). The "by type" mapping would just find a parameter of type Fund and try to find the only process data with that type - provided that there is only one.

Process Descriptors

Descriptors for Model & Go! processes are created implicitly on model load for specified Business Object data fields. To setup a descriptor for a process:


Figure: Process Descriptor

  1. Open the data model in the Modeling perspective
  2. Open the Structured Data Type property view for the same business object
  3. Under the Storage field property, select the Descriptor checkbox
  4. Under the UI properties, specify name for the descriptor in the Label field. This field is optional.
  5. Deploy the model in the Modeling perspective

Process Model

Each simple process is in fact a Process Definition and appears in the Modeling perspective. Simple Process models created in Model & Go! should not be modified in the Modeling perspective.

Process Topology

Simple process models are mapped to strictly block-structured process topologies. This specifically implies absence of any loop constructs. Simple Processes have tabular structure. There is a sequence of rows, each of which may contain one to many cells.

How this is mapped to the underlying process definition is explained here:

The process topology, with the use of OR gateways, is quite simplified and a multi-task row looks pretty much the same as a single task row (single cell). A task row primarily consists of:

This mapping ensures that: