Notes during process setting

Recently, during the definition of taskspace, it is found that the process is actually changing infinitely. The configuration interface of general manager Lin is full of traps. The current problems are as follows:

1) After the Process Template is defined, an error occurs during the saving process, prompting that the initiate and end processes are faulty.

If you are using process builder to create a process, note the following:

A. The INIT process in process can only have one output, and the first action can only have one input. Therefore, if your first user processes tasks with multiple inputs, we recommend that you insert a process data mapping template before the first task. In fact, this template basically only serves as a data transfer template, which has no major impact on the system and is easy to use.

B. The End Node of the process can only have one input. If multiple tasks can reach the end of the task complete, we recommend that you insert a process data mapping node, all the task nodes are aggregated here and then end.

2) After the process is started, the corresponding task cannot be obtained at the summary node.

A summary node named worker is a node that can be reached by multiple tasks. The startup of such nodes is conditional: all front nodes are started after execution, any front node is started after execution, and the specified front node is started after execution. If you need any front node, you can drive the node, modify the settings in the trigger;

3) role permission Configuration

In Documentum, the relationship between roles and user groups is very messy. You can specify a user in the role, assign the role to the group, or define the group and add users first, we recommend that you define the user, role, and group, and establish the relationship in sequence: User-> role-> group, I personally think it is clear (because when I define the executors of a workflow, I usually divide the workflow by group). Of course, I can also define the workflow based on actual needs.

4) Define and use the adaptor in the specified form

In form builder, you can customize the adaptor and call it in the template. The main function of this compiler is to bind some custom operations to the controls on the form template, complete data initialization, assignment, adjustment, judgment, and calculation. It should be noted that the controls mentioned here are generally some text input or selection controls, such as textfield, dropdownlist, text, radio button, and so on, which correspond to buttons, this type of control form provides some common basic operations: suspend, finish, submit, etc.

5) The button processed by the form corresponding to the task

Because you can customize the user processing interface in taskspace for your convenience, you can use form builder to create a corresponding form template. In the process of creating a template, the system automatically creates an interface for the user based on the selected Process Template and the corresponding docview. At this time, there are several default buttons on the Interface: Finish, accept, Delegate, repeat, close, and so on. Based on your actual needs, you may only need to have the function of processing and submitting tasks. At this time, there are two buttons that must be saved. Finish (submit the task ), accept (get task) and close (close interface ). The default process of a Documentum task is view task-> Accept task-> Process Task-> finish task. Therefore, the accept process must be retained.