Flow Shapes
The available shapes are
1) Start task 2)Assignment 3)Assignment service 4)Comment 5)Connector 6)Decision
7) Subflow 8)Flow end 9)Fork 10)Integrator 11)Notification 12)Router 13)Spin-off
14)Split-join 15)Split-for each 16)Pool with swin lanes 17)Ticket 18)Utility
Related Links:
1. Explain about Assignment shape?
An assignment is an instance of a class derived from the Assign- class.
Assignments record a temporary condition of an open work object within an executing flow.
For every Assignment , add at least one flow action .
The assignment normally appears on the work list of the user who executes the flow.
2. Explain about Connectors?
To connect a shape element in the flow with the next shape element. To indicate a possible path for the flow execution.
3. Explain about Notify shape?
A Notify can send an e-mail message to a work party.Connect the notify shape to the bottom edge of an assignment shape.
4. Explain about Router shape?
Sends an assignment to a user, workbasket, or agent other than the current user.
Associate a Router task with an assignment task. This activity determines which worklist or workbasket is to contain the assignment.
5. Explain about Spin-Off shape?
When a work object advancing through a flow reaches the Spin-Off shape, process commander starts execution of a different flow, using the current work object or different work object.
Processing in the current flow rule continues in parallel, without waiting for the other flow to complete.
Use the Spin-Off shape to start a Synchronous flow execution.
6. Explain about Split-Join shape?
Split-Join shape is used to multiple subflows of our flow be completed before the current flow continues execution.
This allows subflows to execute asynchronously, in parallel.
The Split-Join shape must contain at least two called flows.
7. Explain about Split-ForEach shape?
Split-ForEach shape is used to iterate over the pages of a
Page List
or Page Group
property. For each page, we can conditionally start a flow execution for the work object.
Processing in the orginal flow pauses while sub flow execute.
We can’t use Split-foreach shape to create work objects.
The embedded page must exist before the Split-foreach shape is reached.
8. Explain about Fork shape?
The fork shape is used to choose one of a few different paths (connectors) based on tests on the work object.
At runtime, the system evaluates the conditions on each outgoing connector, starting with the connector assigned the highest likelihood. The flow execution continues along the first connector that evaluates to
True
.
9. Explain about Decision shape?
Decision shape is used to reference a map value rule, decision table rule, decision tree rule or a Boolean expression.
At runtime, the system evaluates the decision rule based on inputs from the flow and the work object, and chooses one of the outgoing connectors based on the result.
10. Explain about Ticket shape?
We can start the execution point in the flow at any point in the flow by using Ticket shape.
The ticket is same as GOTO in programming language.
Ticket creation:
1. Create the Ticket
2. Drag a ticket shape to where we want to jump in the flow and Complete the Ticket Properties panel
3. To configure the ticket in activity, Call the SetTicket activity and pass Ticket name
4. Create separate flow action and mention above activity as post activity in flow action.
5. Mention this FLOWACTION as LOCAL ACTION in assignment from where we want to jump.
6. At the time of running the flow By default Connector Action is Displayed.
At the time of run the flow we need to select the local action at that particular assignment where we mention the ticket activity.
11. Explain about Utility shape?
Each utility task references an activity with an Activity Type of
Utility
.
Utility activity is defined in a class derived from the Work- or Data- base class and activity of type Utility.
12. Explain about Integrator shape?
Integrator activity identifies an activity that connects our process commander system to an external system to send or receive data.
For example integration task can connect to a customer data base to retrieve account balances or verify account numbers and status.
Integrator task use activities that call connector rules.
13. Explain about SubFlow shape?
Sub Flow shape may represent any of the following:
§ A branch to another flow without returning (one or more incoming connectors, no outgoing connectors)
§ A call to another flow with return (one or more incoming connectors, one or more outgoing connectors)
§ Part of a Split/Join or Split-forEach shape (at least one incoming and one outgoing connector)
A flow rule that is branched to or called by another is sometimes informally called a subflow.
In subflow we can define flow on current work item or another work item.
14. Explain with an example, the difference between a Decision shape and a Fork?
A decision task is a shape on a flow rule that references a rule of one of three types:
1)A map value rule (Rule-Obj-MapValue rule type) 2) A decision tree rule (Rule-Declare-DecisionTree rule type)
3) A decision table rule (Rule-Declare-DecisionTable rule type)
At runtime, the system evaluates the decision rule to determine how a work object progresses through the flow. The work object progresses along one of the connectors leading from this shape, depending on the outcome of the decision rule.
On the other hand fork checks the conditions directly on the object and unlike decision shape it never asks for a Decision tree, table or map value and two or more connectors can emanate from a fork shape.
Related Links:
15. Consider this scenario: After a work object had reached a particular stage in a flow, I need to run two flows in parallel to each other. How this can be achieved?
This can be achieved by using Spin-Off shape. Just drag the spin off smart shape and fill in the appropriate values depending upon what you choose among “On Current Work item”, “On Another Work Item” or “On Embedded Page”.
So the flow started by this shape will be called a subflow and the original flow as parent flow
No comments:
Post a Comment