Let the Gallop workflow engine ccbpm use a custom form to implement its own business logic.

1.1.1.1:SDK form

Summary: We refer to the process engine and the form engine collectively as CCBPM, but some users do not want to use the form engine, but rather use their own forms, using only the process engine, such a way to adopt the CCBPM SDK Form development mode.

about CCBPM SDK: ccbpm's SDK is ccbpm all the operations of the process into a class of static methods, which involve all aspects of the process operation.

The name of this class is: BP. Wf. Dev2interface.* such as:

For menu-related methods: Get launch list, to-do, in transit, CC ...

Actions for the process are: send, return, transfer, revoke .....

There are ways to organize your operations: login, log out ....

In fact, the functional interface inside CCBPM's WF, such as initiating, waiting, in transit, and CC, is generated by invoking the relevant API of CCBPM.

These APIs are invoked behind the CCBPM work processor and the various parts on the working processor, such as sending, returning, handing over, revoking ...

It is not difficult to understand the overall architecture of CCBPM, and we will explain how to use the SDK form to handle your business logic.

Process Demo Case:

Node Property configuration:

Note: In the Configure Form URL text box, you can use the @sdkformurl variable.

Open the form:

Open the SDK under the Send button Invocation of:

The table above shows how to invoke the Send API, complete the send, and return an obj, which can get the variable information in the sending process, and then output the result.

Send Demo:

Send prompt:

An important way to send:

Case Path:

D:\ccflow\trunk\CCFlow\SDKFlows\QingJia

Please refer to the CCBPM SDK Development section for details.

Let the Gallop workflow engine ccbpm use a custom form to implement its own business logic.