Gemini.Workflow Gemini workflow Advanced Tutorial: Foreign Control Engine API: Overview

Preface:

Gemini workflow provides a set of external API, used to control the overall operation of the system, here's a look at the introduction, in fact, very simple.

External API Control Engine General Information:

Gemini.Workflow Gemini workflow, provide both API, both in Gemini.Workflow the WF under static class.

 

Screenshot is not enough, there are two drop-down: WF.Table and WF.User.

Under ah, a total of nine control directions herein, this brief first, and then for each of the subsequent detailed description.

1, WF.Actor: personnel information flow control node and the next operation.

Mainly used for further processing to control people, to see a screenshot below:

 

Next above, a node to be provided, the flow goes to what, who submitted to the background of the control API are in WF.Actor.

2, WF.Context: context parameter collection in various states.

The context of the process, the core parameters, will be used in the process operation, the context (that is, a collection of a bunch of parameters) is then passed from the beginning to the end.

So context parameter expansion, it should be up, WF.Context this class can help get the context parameter in various states.

3, WF.DBInfo: database metadata.

By this class, can obtain all the workflow database tables, fields, instructions, data structures, and the like.

4, WF.Deploy: deployment process, i.e., updated and stored flowchart.

Save and update the corresponding picture map interface, as shown below:

 

 5, WF.Designer: associated flow control converter designer

WF.Deploy the end result is a control flowchart of archiving and updating.

WF.Designer i.e., control and convert the intermediate process of the flowchart of the initial template, data format conversion.

6, WF.History: track circulation history

This will turn less, and for the history of the node to the end of the track came after or before obtaining section nodes recursively.

When allowed to return step process, by acquiring historical trajectory, optional fallback.

7, WF.Run: core process engine running

Start the process of circulation Next, turn read, the end of the various commands are all here.

8, WF.Table: workflow operation of each table ORM

To add or delete operation to check each modified data table, there can be manipulated.

9, WF.User: external docking users, organizational units, roles

如果要操作工作流接入的用户、组织部门、角色,那么用这个控制即可。

总结:

双子工作流提供的API,分类清晰,使用简单,每个方向提供的方法,只有核心的几个,花不了几十分钟就能清楚了。

在下载Aries项目中,在文档目录中,可以看到有相应的API文档:

 

Gemini.Workflow 是后端API文档。

Gemini.Workflow.js 是前端js的API文档。

刚新上传了:Gemini.Controllers 源码,上面有API最详尽的应用。

 

Guess you like

Origin www.cnblogs.com/cyq1162/p/11959499.html