User:anonymousLog inRegister
Recents:
Correspondence between Business Process Diagram in Version X and Evolution 1


GeneXus X GeneXus X Evolution  Description
Image:Interactive_activity_wkf   Interactive Activity Image:User_image_wkf User

Task that will be executed by a user.

Image:Batch_activity_wkf   Batch Activity Image:script_wkf Script
Task that will be automatically executed by the Workflow engine.
Image:Subprocess_wkf   Subprocess Image:reusable_wkf Reusable
Sub-process embedded in the current process.
Image:Init_process_wkf   Start
Image:None_start_wkf  None
Start of the process (optional)
Image:Fin_proceso_wkf   End
Image:None_end_wkf  None
End of the process (optional)
Image:Conditional_wkf   Conditional Image:Inclusive_wkf  Inclusive
It indicates the evaluation of conditions to choose the route that will be followed. One or more routes can be taken.
Image:Route_activity_wkf   Route Activity Image:none_route_wkf  None
This task is automatically executed by the Workflow engine and doesn't imply any action by the user. At design time it is considered a task that hasn’t been defined yet.
Image:And-join_wkf   And Join Image:parallel_wkf  Parallel It represents a synchronization point in which, in order to move forward with the flow, all tasks connected to this symbol have to be completed.
Image:Choice_activity_wkf   Choice Activity Not supported (see note)


Note: When migrating a diagram that uses the Choice Activity symbol from one version to another, we have to generate optional routes from the symbol’s preceding task up to the subsequent tasks.

  • Start and End Symbols

It is no longer necessary to use the start and end symbols in all workflow diagrams.
They are strictly required in the case below:

- The initial tasks of the process have input edges, that is to say, at some point of the process it is possible to return to the initial task.

  • Nested Conditionals

It is no longer necessary to include a symbol of route activity type between nested conditionals.

  • Workflow Context

It is no longer necessary to define the variables corresponding to the process instance, definition and work item.
To access the context the following code should be used:

&WorkflowContext.ProcessInstance
&WorkflowContext.ProcessDefinition
&WorkflowContext.Workitem

In addition, this context can be accessed from all the objects involved in the call chain.

  • Deadlines

Now to represent a deadline you must use an intermediate event, the timer.

Example

Image:Example_BPD_X_version                                                                      Image:Example_BPD_ev_version



Created: 05/16/09 10:33 AM by marcedupo Last update: 02/01/12 04:29 PM by dmarquez
 
Page
Share
Categories
Group
Powered by GXwiki 4.0 Beta1 (generated with GeneXus X Evolution 2)