Workflow Server Forms

General information

Workflow Server provides an end-user interface to manage processes. By default, it is off. To enable, you should click the Start button in the Forms tab. By default, the service starts at port 8078. The default port is specified in the DefaultFrontendPort parameter of the config.json file.

WFS Forms uses Vue.js and Element UI. WFS Forms provides for two types of forms: user and system forms. By default, only user forms are shown in the admin panel. To display the system forms, you should switch the slider.

Form building

Workflow Server Forms uses the concept of master page and placeholders to inherit and build forms. Master page is specified in the form settings.

To declare a placeholder on the master page, use:

<div wfs-placeholder="customContent"></div>

Where 'customContent' is the placeholder's name.

Then, the object content with the attribute wfs-content="customContent" will be inserted into this placeholder.

<div wfs-content="customContent">
    <!-- Your content -->
</div>

To insert the content of another form, use the tag: wfs-forms

<div wfs-form="header"></div>

Form settings

Each form has the following settings:

1. Name - the form name.
2. MasterPage - the master page.
3. Type (All processes, My processes, Inbox, Outbox) - the page type to determine the data loaded into the form; used to display the list of processes. The default Type is Form, this type means that only one process will be displayed on the form
4. Schemes - the list of schemes available in the form. This option works only for multiple processes form.
5. Draft, InProgress, Final - additional options for filtering.
6. Security Access - CRUD access setting in accordance with the role (available after the authorization is done).
7. Fields - columns / controls block to be displayed on the form or in the list of processes.
8. CustomUrl - the page url; when opening the url, the corresponding form is opened.
9. Click Set Placeholders for pasting the list of placeholders from the master page into the form source code. The format to add a placeholder:

<div wfs-content="placeholdername">
    <!-- Insert your content here -->
</div>

Where 'placeholdername' is the placeholder name from the master page.

System forms

The systemforms.json file contains the default settings for the system forms. This file is stored in the frontend folder. The code of all system forms and the static resources for the user interface are stored in this folder.

You can change the settings and body of the system forms in the admin panel; on changing, the Overridden flag gets enabled. The Reset To Original button returns the form to its original state.

The basic forms are:

• master - the master page for all forms.
• index - the first page, displays the list of all schemes.
• all - the page with the list of processes.
• my - processes of the current user (available after the authorization is done).
• inbox - processes of the current user (available after the authorization is done).
• outbox - processes approved by the current user (available after the authorization is done).
• processes - the base page for the list of all processes.
• header - the page header.
• sidebar - the left panel.
• process - the base page for process, contains commands, process fields and timeline.
• processtimeline - the control with the process timeline (approval history).
• processform - the form fields bound with the process.

Process startup options

The process scheme has the Auto Start flag that defines the principles of the process creation. If the flag is not set, then you will see the process form with the inscription "The process is not started. Click on a button for starting the workflow." To start the process, you should click the button in this window. If the AutoStart flag is set, the process will be automatically created.

The index page displays the list of processes. Each process has one or more commands:

• If Auto Start is unchecked, Open is displayed. After clicking this button you will see the process form with inscription "The process is not started. Click on a button for starting the workflow.". You need to click any initial process commands button to start the process.
• If the scheme is without initial commands but with Auto Start checked, then Launch is displayed, the process automatically starts after clicking this button.
• If the scheme is with both initial commands and Auto Start checked, then initial commands is displayed, the process automatically starts after clicking any command button.

Timeline a Process History

Process timeline displays simplified data about transitions between the process states.

If you use WriteProcessHistory and UpdateProcessHistory predefined actions, then the history of approvals with future steps is displayed.

If not used, a simple transition history is displayed.

How to work with fields

The list of fields is used for the list of columns in the tables and the inputs of the process forms. You can specify the list of fields in the form editing interface.

1. Name - the process parameter name.
2. Title - to be displayed in a form or table.
3. Control - a display control. The following controls are available: text, checkbox, select, select-multiple, textarea, custom. Used in the process forms (when Type = Form) only.
4. Options - the options of the controls. Basically they specify the validation of values. The following options are available:
   • required - to make the field required.
   • email - the field must be a valid email.
   • number - the field must be a valid integer value.
   • float - the field must be a valid float value.
   • url - the field must be a valid url.
     Several options can be specified.

If no Type set, i.e. it is one process form, the synchronization control appears in the upper left corner of the Fields section. After clicking on it, the list of controls is added to the page source.

For example, the following set:

Name	Title	Control	Options
title	Title	text	required
email	Email	text	required email
amount	Amount	text	required number
flag	Flag	checkbox

Turns into the following code:

<div wfs-content="fields">
    <el-form-item :rules="[WorkflowServer.Rules.required]" label="Title" name="title" prop="title">
        <el-input v-model="FormData.title" :readonly="isreadonly()">
        </el-input>
    </el-form-item>
    <el-form-item :rules="[WorkflowServer.Rules.required, WorkflowServer.Rules.email]" label="Email" name="email"
                  prop="email">
        <el-input v-model="FormData.email" :readonly="isreadonly()">
        </el-input>
    </el-form-item>
    <el-form-item :rules="[WorkflowServer.Rules.required, WorkflowServer.Rules.number]" label="Amount" name="amount"
                  prop="amount">
        <el-input v-model="FormData.amount" :readonly="isreadonly()">
        </el-input>
    </el-form-item>
    <el-form-item label="Flag" name="flag" prop="flag">
        <el-checkbox v-model="FormData.flag" :disabled="isreadonly()">
        </el-checkbox>
    </el-form-item>
</div>

The following types of controls are available:

• text
• checkbox
• select
• select-multiple
• textarea
• custom

For the "custom" type, an element with the div tag is added; for an unknown type, the span tag is used. If you plan to use a control of yours, set custom, and then replace it with any tag you need. By default, the controls available for use at Element UI.

Fields are saved in the process parameters and are accessible by SetParameter and GetParameter operations of WorkflowAPI.

The following parameter names are reserved, you can set these parameters in the Actions as usual process parameters. This way you can manipulate displaying forms from your processes code.

• For the process editing form:
  • readonly - set the form to the read-only mode.
• For the process lists:
  • title - the process name, formed by calling the WorkflowServer.getTitle function. This function is located in /frontend/scripts/workflowserver.js so you can customize it. By default, the first non-empty parameter value is taken: title, name, Id, ProcessId.
  • commands - the lists of available commands. Filled automatically.
  • actions - available additional process actions (e.g. deletion).
  • localizedstate - the localized state name.

How to bind the form and the process?

If the Default Form parameter is set in the list of process schemes, this form is displayed when viewing the process.

In Activity, you can call ShowForm predefined action and specify the form to be displayed at the current and subsequent stages of the process. To reset the form call ShowForm with an empty form name.

How to create a static form?

You can create a form and specify Custom Url. When opening this url, the Workflow Server displays your form.

Global WorkflowServer javascript object

The WorkflowServer object is globally accessible on the page and contains the page data. This object is located in /frontend/scripts/workflowserver.js file. The basic properties and functions are the following:

• VueConfig - the parameters to initialize a Vue object.
• Data - the form/object data.
• Rules - the validation rules.
• loadInstances - load the instances for the current page (works if Type is set for the form, i.e. it is multi process form).
• executeCommand - execute a command.
• deleteInstance - delete an instance.
• loadSchemes - load the schemes.
• loadFlows - load BusinessFlow.
• fetchJson - JSON server request.
• fetch - server request.
• DataExtend - extension for WorkflowServer.Data.
• saveForm - save the form data in the process.
• getTitle - returns the title of the process. The first non-empty field value is taken: title, name, Id, ProcessId.
• formatDate - format the Date value.
• reload - reload the page.
• showError - show an error.
• showConfirm - ask for confirmation.

Instances filtering

WorkflowServer.loadInstances can use additional filters in the format:

var param = {};
...
params.filter = [
    { column: "title", value: "Test", term: "=" }
];

WorkflowServer.loadInstances(params).then(function (response) {
    WorkflowServer.Data.items = response.items;
    WorkflowServer.Data.itemsCount = response.count;
});

Custom validation

To add custom validation, use the following script:

WorkflowServer.Rules.customRule = {
    validator: function (rule, value, callback) {
        var regex = /^\d+$/;
        if (!value || (value.match(regex) && !isNaN(value))) {
            callback();
            return;
        }
        callback(new Error(rule.message));
    },
    message: 'Error'
}

More details on how to write validators can be found here.

Process parameters loading

When loading the form, the Workflow Server finds the script tag for workflowserver.js.

<script src="/scripts/workflowserver.js" type="text/javascript"></script>

And inserts the form data. For example:

<script>
    WorkflowServer.DataExtend({ ... });
</script>

Thus, on loading the page, you immediately get full access to the form data through WorkflowServer.Data.

The system process parameters are loaded into WorkflowServer.Data, the user-defined process parameters are loaded into WorkflowServer.Data.Form. Only user-defined process parameters are available for change.

For the processes list pages, the data are loaded using the WorkflowServer.loadInstances method.

Vue Initialization

It is a part of the master form:

<script>
    WorkflowServer.VueConfig.el = '#app';
    WorkflowServer.VueConfig.data = WorkflowServer.Data;
    WorkflowServer.App = new Vue(WorkflowServer.VueConfig);
</script>