SHARK workflow implementation and comparison of WMFC & OMG specifications

SHARK workflow implementation and comparison of WMFC & OMG specifications

----- Section 7: How to establish a connection information and business information

Keywords: Shark workflow WMFC OMG specification

After work flow installment, you need to connect specific activities and business processes. If it is user interaction activity, you also need to specify interfaces related to this activity.

The work of this part is the specific implementation, and the WMFC specification has not been mentioned.

Let's take a look at JBPM practices: JBPM-1.0-SRC / JBPM-1.0 / Examples / Process / Holiday / ProcessDefinition.xml

JBPM does not use standard XPDL workflow description language, as follows:

Holiday

REQUEST

This Process Manages A Planned Absence of An Employee.

AE

Start a Request for a Holiday

Requester

connectionFactory

a holiday Was Requested from $ {start date} to $ {end Date} with comment $ {comment}

previousactor You Requested a Holiday

You Requested a Holiday from $ {start date} to $ {end Date} with comment $ {comment}

In this activity, you have to evataate the holiday-request of your employee.

previousactor-> group (hierarchy) -> role (boss)

boss

evult

this is a notification of the refusal of your holiday request. by Submitting this form you declare to have taken notice of the refusal.

Requester

in this Activity, You Have to register That An Employee Is Taking Holiday.

role (boss) -> Group (hierarchy) -> role (hr-responsible)

hr-responsible

You Get Notified That your holiday request has been approved.

role (Requester)

If you are familiar with Struts readers see the above description, it will find that This is very similar to the page jump in the Struts configuration file.

The above writing is very intuitive, but the XPDL implementation of Shark is compared. Recommended or using XPDL process description.

XPDL puts a scattered jump in JBPM together:

转载请注明原文地址:https://www.9cbs.com/read-30271.html