Enterprise Enabler’s Process Designer is the graphical interface that allows users to create processes in the form of flow-sheets by simple dragging-and-dropping components, and then adding some configuration to those components.

A Process comprises all the necessary steps that have to happen for a particular job to be completed.

Traditionally, one was required to possess and learn several software tools, each one working differently. A tremendous amount of work was required to make sure that all of these tools worked together in some useful way. And maintaining them was challenging. Enterprise Enabler’s Process Designer enables design of processes around these disparate systems and allows a well coordinated choreography between them. Each process within Enterprise Enabler is represented by a flowchart. Each process is composed of several different pieces denoted as “Nodes”, as well as variables. Each process needs to have a Trigger Node, a Start Node, a Stop Node, and other nodes in between that can be Action Nodes, Send/Receive Nodes, Decision Making and Branching Nodes, Transition Nodes, Merge Nodes, or Parallel Split nodes. The symbols used to represent the above objects in the Process Definition are given below.

Process Designer Nodes Remastered.jpg

When deployed, the executable process can be triggered by an event or a by ad-hoc request.

One of the most common nodes is the Strongly Named Transformation Node which uses an Aii to perform data transformation. Upon execution of this node, the chosen Aii will execute the Aii’s designated source and destination templates. Below is an example of a Process with a Strongly Named Transformation node.

 

Example on how to create a Process using a Strongly Named Transformation Node.

a)  Go to the File menu —> New –> Process. By default, a Run Once trigger node, a Start and a Stop nodes are already in the work area when a new process is created. Leave all the nodes untouched.

b)  To the left of your screen will be a pane named Action Nodes inside the Toolbox pane. Click on the Strongly Named Transformation node and drag it over into the Process pane.

c)  Notice that the Start node and the Strongly Named node each have an arrow at the bottom whereas the RunOnce and Stop nodes do not. This is because the run once node only triggers the process and the Stop node ends it. The Start node needs a connection (the arrow it carries at the bottom) to indicate which node is next in the process. In a similar fashion, many nodes will have a node connected to them and they themselves will be connected to the next node. That being said, connect all the process nodes by using the connectors they carry. Just click on the end of the Start node’s arrow and drag it over to the Strongly Named node. Then click on the end of the Strongly Named node’s arrow and drag it over to the Stop node.

Strongly Names Trans Node

d)  Click on the Strongly Named Transformation node in the Process area, then in the Properties tab to the right click on the AiiName field and click on the ellipsis button ().

Ellipsis

e)  In the “Object Browser” section select the Category where your aii is located and select your desired aii. In this example, our category is TEST DOCUMENTS, and our map is named aiiNorthwind. Click on your aii and click on the Select button at the bottom of that screen (sample screenshot below).

Select Aii for Strongly Named node

f)  In the “Properties” tab to the right of the screen click on the CategoryName field and choose the category you want your process to be under, or create a new category by just typing in a new Category, then click on the Name field and type a name for your process. In this example, our category is TEST DOCUMENTS, and the name of our process is pNorthwind.

g)  Go to the File menu, then click on Save to save the process definition.