English

App Management

Application Management

Notes:

  1. Required: Form field attributes, this field needs to be filled in to save or proceed to the next step.

  2. Unique value: form field attribute. This field value must not be repeated in the same field when compared with other form data.

  3. Value: Used to store the database when filling in specific fields. It is mostly used for system or process operations and is not affected by the language version.

  4. Word: used for display when filling in specific fields.

  5. Process variables: The process can provide the variable types used by each component when the process is running.

  6. Component variable: Variable type used only by the component itself.

Application design

here is the core function of OMFLOW. Custom processes can be established here and put on the shelves for use by general users or external systems.

※ This article mainly introduces the functions of each page. How to create an application from scratch, please refer to the [Building Applications and Processes] Chapter

Application List

Location: [Main Menu] > Application Management > Application Design

Every application can be regarded as a container with multiple processes. The functions of the application list page are introduced as follows:

  1. Add: Create a new custom application

  2. Delete: Delete the checked application

  3. Launch: Put a completed application on the shelf

  4. Filter: Search by keyword, filter attributes, and display the number of data items at one time

  5. Restore: Restore the filter to the default Setting value

  6. Import: Import old applications

  7. Export: Export the selected applications

  8. Cloud download: Download official cloud applications, which belong to the following It can be used when:

• When the version is updated, the corresponding built-in process needs to be downloaded simultaneously • After the official release of a new suite application, you can see the Settings button on the far right of the application list after adding an application. Click to modify the following information:

  1. Application Name: Modify the application name

  2. Application Design Permissions: Enable this role to perform ** without granting application management permissions Design**, launch and design related service requests.

  3. Application Parameters: The set parameters are provided for process access and can be exported with the application.

※ "Application Design Permissions" gives "designers" the authority from design to release adjustment for a specific application.

Process list

Location: [Main Menu] > Application Management > Application Design > [Any Application]

Click any application in the application list to enter the process list page. The functions are introduced as follows:

  1. **New Added **: Create a new form and select "Form Process, Static Form". Form Process will execute the designed process when opening an order.

  2. Copy: Copy the selected process to another application

  3. Delete: Delete a process

  4. Filter: Search by keyword, display the number of data items at one time

    • Restore*: Restore the filter to the default value

  6. Package: List the packages required for all processes of the application

  7. Language: Import and export the translated language pack

※ In The processes seen in this list are henceforth collectively referred to as main processes to distinguish them from sub-processes.

Design form process > Parameter setting

Location: [Main Menu] > Application Management > Application Design > [Any Application] > [Any Process] > Parameter Setting

Click *Add * button or [any process] to enter the process editing page. First you will see the Parameter Settings tab. The following describes the settings:

  1. Process Name: Enter the text and put it on the shelf. Unable to change, required

  2. API path: Enter alphanumeric characters as the table name of the database, unique value, required

  3. Description: Explain the function of this process.

  4. Execution Process Record (LOG): Record the input and output at each point of the process.

  5. Application Programming Interface (API): Allows the process to be called by other functions and systems through API.

  6. Internal Interface Edit: Allow other processes to invoice and push orders through the "Internal Process, External Process, Program Code" components. Please refer to the "Program Code Components" chapter.

  7. Internal interface deletion: Allow other processes to delete orders through the "code" component. Please refer to the "Code Component" chapter.

  8. Internal Interface Query: Allow other processes to query it through the "Code" component, please refer to the "Code Component" chapter.

  9. Whether to create a task: Allow this process to generate tasks in My Tasks.

  10. View current process and progress: Enable the Process View function on the form page, refer to the [Apps>Process View] chapter.

  11. View form data operation history: Enable the Process function on the form page, refer to the [Apps>Process] chapter.

  12. Attach file function: Enable the Attach file function on the form page, refer to the [Apps>Attach file] chapter.

  13. Display data association: Enable the Association operation function on the form page, refer to the [Apps>Association operation] chapter.

  14. Fill in and display work log: Enable the work log function on the form page, refer to the [Apps>Work Log] chapter.

  15. View Service Level Status: Enable the Service Level function on the form page, refer to the [Apps>Service Level] chapter.

  16. Show Print Button: Enable the Print function on the form page, refer to the [Apps>Service Level] chapter.

  17. Quick operation confirmation window in the form: When the user uses a quick operation in the form, whether to pop up a confirmation window.

Notes: (1) After the application is launched, Process Name will be bound to API Path. If you need to modify it, you can only change the translation (2) API Path is the identification name of the process. Once changed, It is regarded as a new process

In the advanced parameter setting

, you can check Form Number to customize the code rules, which are introduced as follows:

  1. Text: Enter text, generally used for the English abbreviation of the beginning of the order number. .

  2. Date: Invoicing time will be displayed after text. Example: Fill in ymdHMS and it will display 20240227135959. Please see the table below for details.

  3. Serial number length: Date will be displayed next. Serial number and set its length, example: fill in 5, the end of the first order number will display 00001

  4. Serial number reset time: Set whether to set a reset period for the serial number.

Date SymbolDescriptionDisplay Example

y

Year

2024

m

month

02

d

day

29

H

hour

23

M

minute

59

[Main Menu]>Application Management>Application Design>[Any Application]>[Any Process]>Permission Settings Here you set which roles can have permissions for the process, and

it

will take effect when the application is launched.

  1. Add: Add an existing role and give this role the permissions for this process.

  2. Delete: Remove the permissions for this process from the checked role. The newly added role can be set with four permissions, which are introduced below:

  3. View: This process can be displayed in [Main Menu]>Apps and the form list of the process can be viewed.

  4. New: Orders can be issued on the Form List page of this process.

  5. Update: When the form enters manual input, you can push the form to the next step.

  6. Delete: You can delete the form of this process.

※ When the application is re-listed, all role-related process permissions will be deleted first, and then the permissions will be re-granted.

Advanced settings

here allow users with viewing permissions to only see specific forms under certain circumstances. After checking, you can see the following fields:

  1. *View all forms *: Select the specified department, role, and user to view all data of the process regardless of conditions.

  2. When the specified form fields match the user's personal information, the user can view the form: When the specified fields of the form match the user's personal information, the form can be viewed.

  3. When the specified form field meets a specific value, selected departments, roles, and users can view the form: When the specified form field meets a specific value, specific departments, roles, and users can view the form.

※ Each of the above three viewing rules is established independently. When the user meets any of the rules, he or she can see the order.

Form design

Location : [Main Menu]>Application Management>Application Design>[Any Application]>[Any Process]>Form Design

Design fields for users to fill in and bring them into the process Calculation and application will be introduced below:

Form Design>Block & Half-Block

Click the +Block and +Half-Block buttons to add blocks to the form. Blocks are mainly responsible for dividing positions for forms. The following is an introduction to block functions:

  1. Add new fields [+]: Add various fields to the block. For details, please refer to [Form Field Introduction] chapter.

  2. Delete〔X〕: Delete the block and the included fields together.

  3. Settings [Gear]: Set the block attributes, as introduced below: • Title text: The title text of the block • Mark color: The color of the straight line above the block • * Hide*: Hide this block and the fields within it

※ You must create a block before adding fields.

Form field introduction

The following introduces the basic fields that most fields will have:

  1. Field name: Enter text as the name for the field display

  2. Annotation: The field's Description, displayed as placeholder

  3. Default value: Default value brought into the field

  4. Type: Divided into text, number, password, unique value, URL, and email

  5. Required: Required fields will be checked when data is created or pushed, and the operation will be rejected if the value is empty.

  6. Read Only: If checked, the user can only view this field but cannot modify it.

  7. Hide: Hide this field

Form design>Input box

is a field for inputting text, and can be adjusted according to the following attributes:

  1. Format check: After entering the regex syntax, the system The content will be checked according to the syntax to see if it matches. If it does not match, the user's operation will be rejected.

  2. Enable camera scanning of barcodes on mobile devices: A mobile-specific function that can automatically input barcode data.

  3. Mask: Mask the field data. The following are the masking rules:

  4. Number of digits to display at the beginning: Fill in the numbers, and the first character to the specified character will not be masked.

  5. Number of display digits at the end: Fill in the number and count backwards from the last character to the specified character without blocking.

  6. Minimum number of characters to mask: Fill in the number to ensure the number of characters to be masked.

Form design > Multi-line input

Number of lines: This adjustment is usually for the sake of beautiful form layout and does not limit the length of content input by users. If the user types more content than the setting, a drop-down scroll will appear next to the field.

Form Design > Drop-down Menu

The drop-down menu has an additional tab for options, and you can add delete options. Hold down **↕︎** to drag options. Check: Allows the selection of multiple items Option sort: After checked, the user's selection order will be recorded, example: 3,1,2 Check limit: When checked, it can The upper limit of the selected quantity Lower check limit: The lower limit of the quantity that can be selected when checked Default value: The default value of the check should be separated by semi-rectangular commas, example: 1,2,3,4

"Options" tab

  1. Value: Fill in the "value", which is provided for system calculation and will not be affected by the language version.

  2. Display text: Fill in the "text" and display it for users to identify.

※ Drop-down menu fields are stored in the database format as [＜value＞,＜value＞,...]

Form design＞Single-select/multi-select menu

this column All options can be customized and checked. Most of the options are the same as the "drop-down menu". The following introduces other options: Other: When the user does not have a suitable option to check, he can use this "Other" column Fill in the bits by yourself, and the filled-in will be stored as "word, value" at the same time.

※ Single/Multiple Select Menu field regardless of single or multiple selection, the storage format in the database is [＜value＞,＜value＞,...]

Form design＞

Fixing of title form Field, similar to the input box field:

※ Many functions of OMFLOW will use the title field to represent the name of this form, such as "My tasks, related operations" and so on.

Form design >

Fixed fields of status forms, similar to drop-down menu:

※ Many functions of OMFLOW will use status fields to represent the current stage of this form, such as "I tasks, associated operations" and so on.

Form Design >

The fixed field of the light signal form is similar to drop-down menu, but there are only three fixed options of red, yellow, and green lights.

※ Many functions of OMFLOW will use light fields to represent the severity or urgency of this form, such as "My Tasks, Service Levels", etc.

Form Design>The fixed fields of the assignee and department

forms are composed of two fields: "department and user". After selecting a department, the User field will dynamically generate users under the department for selection. The settings are introduced below:

Include assignee field: The default is checked. If If this check box is cleared, only the Department field will be displayed in this field.

Default value: You can fill in ＜Department ID＞,＜User ID＞ as the default assignment object when billing, ID query to Personnel Management>User Management and* *Personnel Management>Department Management**View the number "number" field.

This field determines the creation and assignment of Task. If only Department is selected but User is not selected, all users in the department will be able to create and assign tasks in "My Tasks" ” Saw this order.

Form design > Note 1, Note 2, Note 3 - 1.2.1

Fixed fields of the New form, similar to the Title field, can be used when some special information needs to be displayed in "My Tasks" Store in this field.

※ This field is displayed by default in My Tasks. If you do not need to display this field, you can refer to the chapter [My Tasks > Hide Remarks] to hide it.

"Options" tab

This tab can limit which departments can be selected.

Form Design > Date

Clicking this field will pop up the Date interface for selection.

Form Design > Date/Time

Clicking this field will pop up the Date and Time interface for selection.

Form Design > Subquery

This field will display a list of form data from other processes in OMFLOW. The user can check any piece of data and backfill specific fields into this form: Users are not allowed to enter by themselves : Only query is allowed and the fields are backfilled by the system. Manual input is not allowed.

The following introduces the setting steps of subquery:

  1. Form tab: Select the application and process to be queried (referred to as: Queryed process)

  2. Conditions tab: Set conditions Carry out preliminary screening to narrow down the range of data displayed in the checked process

  3. Dynamic Conditions tab: Use the data of user and this form as conditions to filter and narrow down** The range of data displayed in the checked process **

  4. Backfill tab: When the user selects the data in the checked process, the field value of the data will be backfilled into the specified column of this form. Location

Setting ** conditions and dynamic conditions ** Notes: Use "value" as the query target in the "drop-down menu, radio/check menu, status, light signal" field. Use "ID" as the query target in the "Assigned Department, Department, User" field.

Form Design > External Query

This field can return a data list through python code. The user can check any piece of data and backfill specific fields into this form: Users cannot enter by themselves: Only the query method is open and the fields are backfilled by the system. Manual input is not allowed. Distributed computing: Specify the Collector to execute the code of the "Python" tab.

The following introduces the steps to set up subqueries:

  1. Filter tab: Before executing the Python code, the variables are sorted here (referred to as: component variables). For details, please refer to [Application Management > Filtering] chapter.

  2. Input tab: Set those "process variables and component variables" to be brought into Python code, and provide Python code calls with new variable names.

  3. Package tab: Fill in the name of the package that needs to be installed first when executing Python code. Please ensure that OMFLOW can be connected to PIPServer.

  4. Python tab: Write code here and point the result to the result variable. The data must be a two-dimensional array with the following format:


#Point the result to the result variable 

result = [ 
    ["Title1", "Title2"], 
    ["row1" , "row1" ], 
    ["row2" , "row2" ] 
]

  1. Backfill page Sign: When the user selects the data, the corresponding value of the data will be backfilled into the specified field of this form according to the set field name [Title]

Form Design > Department

drop-down menu selection has been created Departments can be set to check. Default Value tab: Please separate the selected default values ​​with commas. Example: , , Option tab: Which departments are restricted? Can be selected or linked to the "User" field through field calculation rules. 1.2.1 New

Form design>User

drop-down menu to select the user that has been created, and you can set the check box. Default Value tab: Please separate the selected default values ​​with commas, for example: , , Option tab: Limit which departments can be selected, or link it with the "Department" field through field calculation rules. 1.2.1 New

Form design > Subtable

provides fields in Table format to store multiple pieces of data (referred to as: subtable data):

  1. Number of rows: The number of rows displayed by Table by default Height

  2. Required: When checked, this field requires at least one subform data

  3. Hide Toolbar: Hide the "Add, Data Move, Delete" function

4 . Customized form: And design a subform according to the Table field. The following points must be noted; • Required: When a piece of subform data is filled in, the relevant Required fields must also be completed. • Field Calculation Rules: Set the linkage mechanism for the same subtable data. For details, please refer to the chapter [Application Management > Field Calculation Rules]. • Subtable Field Width: The subtable fields are adaptive to the page width by default, and the minimum field width is 150. You can also enable the custom function to fill in a fixed width. 1.2.1 New

※ The "Subquery, Field Calculation Rules" field of the subtable can refer to the fields of this form as query conditions.

Form design>

Fields for reminders and warnings, support HTML format

※ The content of this field is only for display and cannot be edited by the user or used by the process.

Form Design > File Upload

provides fields for uploading files, which can further control functions such as "file type, quantity, read-only".

Form Design＞※The work log

provides the function of viewing the "work log" directly on the form. For details, please refer to the [Apps>Work Log] chapter.

Form Design＞※Signature

provides the function of viewing the "Signature Record" directly on the form. For details, please refer to the [Application Management>Signature Design] and [Signature Mechanism] chapters.

※ If the process is designed with an approval function, the Approval Record field will be automatically displayed at the top of the form

Form Design > Field Calculation Rules

Set calculation rules for the form. When the field value changes, at the same time Change the settings or values ​​of other fields.

※ This rule will only operate when the user fills in the form. These calculation conditions will not be triggered when the field value is modified or the field is backfilled during the process.

Click the Add button to add new rules (referred to as: calculation rules). On the far right of each calculation rule is the "Copy, Set, Delete" button. Click Settings [Gear] to Jump out of the setting interface, as follows:

  1. Settings tab: After entering the setting screen, you can modify the name and add comments for this rule.

  2. Trigger Field tab: Click Add to add a trigger field. When the user fills in the form and the value of the trigger field is changed, the trigger condition will be checked.

  3. Trigger Condition tab: When the trigger condition is met, the calculation will start. If the trigger condition is empty, the operation will be performed directly.

  4. Operation tab: Start calculation and backfill the results into the specified fields, classified as follows: Number: Select the form field as variable and add it to the Operation content block , and perform operations using mathematical symbols. String: Select form fields as variables to add strings. Date: Select the "Date" field of the form and add or subtract the specified length of time. Date/Time: Select the "Date/Time" field of the form and add or subtract the specified length of time. Date/Specified Time: Select the "Date/Time" field of the form, add or subtract the specified date length, and then re-specify the time. Data Query: Similar to subquery settings, the corresponding field values ​​of the queried form data are backfilled into the fields of this form. Field linkage: Modify the field settings of this form, such as read-only, required, options, etc.

Process Design

Location: [Main Menu] > Application Management > Application Design > [Any Application] > [Any Process] > Process Design

When the new form is "Form Process", you can Click the Process Design tab to enter the process design interface. After entering, you will see a preset process. Most of the components are connected by arrowed lines to form a flow chart. The process will be displayed after the order is placed. Execute the design here in order. The following is a brief introduction to the basic operation of the component:

clicking on the "Manual Input" component will display function buttons around the component. The following introduction:

  1. Drag: hold down the component with the left mouse button and move it. Drag the position on the flow chart

  2. Setting: Click to pop up the relevant setting interface. For details, please refer to the [Introduction to each component of the process] Chapter

  3. Copy: Copy this component (including the set parameters)

  4. Delete: Delete this Components (including the lines connected to the components)

  5. Connection points: Connect to other components. For the connection method, please refer to the chapter [Create Applications and Processes > Create Connections]

For an introduction to each component of the process,

click *+Add in the upper left corner of the main screen * button can be used to add specified components to the flow chart. Each component is introduced below:

Component -

the source of starting a process. It is recommended to create process variables here for use by subsequent components. The following describes the purpose of each tab:

  1. Settings tab: Set the general properties of this component, among which "Display Name" can modify the display name of the component to facilitate users to identify the current location when viewing the process. Checking Data Verification will turn on the verification function.

  2. Input tab: Write the field value or fixed string into the variable. The variables created here are process variables, and all subsequent components can use these variables. Here you will see that there is a default input, result=success, whose variables have many functions in OMFLOW, and are generally used to declare whether the order has been executed normally.

※ The variables designed here can be used as input variables for the data verification code operation, and the data can also be taken over by this variable when the data verification is output for subsequent process use. 1.2.1 New

  1. Data Verification tab: This tab will appear when Data Verification is checked on the Settings tab. You can write Python code to check the form content, and use The status variable determines whether the form is allowed to be opened. For details, please refer to the chapter [Application Management > Program Code Components].

Component -

The end of a process. Only when the process reaches this component, the Close Order action (closing the task, ending SLA monitoring...etc.) will be performed. When the process is controlled by other processes When calling, the execution result will be returned only when the "end" component is reached.

※ Under normal circumstances, the process should be allowed to execute smoothly until the "End" component.

Please be sure to connect to the "End" element when the process falls into the following situations, otherwise the process will not be completed smoothly: • When the process is a sub-process • When the process will be called by other processes • When the process is a data collection process

** Filter** tab: Here you can organize the "process variables, form fields, system parameters, application parameters" parameters that are to be output, to facilitate subsequent process interfaces or data return to the main process or OMFLOW Server, among which the ** system For parameters**, please refer to the chapter [Application Management > Parameter Management].

※ The variables created by filtering can only be used by the current component, not process variables.

Component - Once the manual input

process reaches this point, it will stop to allow the user to review, fill in the data and advance (can be advanced through the front-end interface or API).

※ When entering manual input, only manual order push or API order push can make the process move forward.

"Settings" tab

  1. Log: It has the same function as the Execution Process Record (LOG) introduced before. The difference is that this function will only affect the current component.

  2. Show Send Button: This option determines whether the send button needs to be displayed in addition to the quick action button after the user enters the form when quick operations are enabled.

  3. Enable the sign-off function: After the sign-off function is enabled, there will be an additional sign-off tab, and the submit button that users see in the form will be changed to a sign-off button. After the signature is completed, the subsequent process will proceed regardless of whether it is agreed or not.

  4. Designate signature sender: This function must be enabled for signature first. If the signature sender is not specified after activation, the person who pushed the order will be the signature sender.

  5. Send signature directly: This function must be enabled for signature first. After this function is enabled, when entering the manual processing, it will not stop and will directly enter the sign-off. At this time, if the designated sign-sender above is not specified, the sign-sender will be the assignee. If there is no assignee, the sign-sender will be the assignee. System.

The "Filter" tab

can organize the "process variables, form fields, system parameters, and application parameters" parameters to provide subsequent tab access to this component.

※ The variables created by filtering can only be used by the current component, not process variables.

The "Field Settings" tab

modifies the field values ​​in the database when the process is stopped. When the user opens the form, the modified content will be displayed.

The "Customized Form" tab

allows you to choose whether to load the form designed by the form design. After selecting to load, you can modify the currently presented form - delete or add some fields to meet the current content that needs to be presented to the user. If you do not choose to load, the form designed by the form will be applied directly.

The "Data Verification" tab

will appear when Data Verification is checked on the Settings tab. You can write Python code to check the form content, and use the status variable to determine whether It is allowed to push orders. For details, please refer to the chapter [Application Management > Program Code Components].

※ During data verification, if the status is error, the message will be displayed on the interface as an error message.

On the "Approval" tab,

click the New button to add a new approval template. The following settings can be made for the approval template:

  1. Approval Name: Select an existing one Sign-off template.

  2. Allow users to adjust themselves: When set to allow, the stage setting of the approval template will pop up after the user clicks to submit the sign. The user can add additional stages, but cannot delete the original stage. .

  3. Conditions: When there are multiple approval templates, after setting the conditions, the user presses Submit Signature, and which approval template will be executed according to the conditions. If more than two conditions are met, use The corresponding approval template will pop up on the user's screen, and the user can decide which approval template to execute.

  4. Sign-off settings:

Input: Input variables from the process into the sign-off.

Phase: The stage tab here is only for designers to know which stages the sign-off template has gone through. If the design exceeds two stages, the following conditions can be set.

Conditions: Set conditions to determine whether the approval will proceed to subsequent stages. Assume that there are three stages. If the conditions of the second stage are not met, neither the second nor the third stage will be executed. That is, the result of the first stage is the final result of this approval.

The "Output" tab

is similar to the input of the "Start" component, and outputs the field content updated by the user into process variables for use by subsequent components.

The "Action 1, Action 2" tab

is also called quick operation. After the design is completed, it can be used on My Tasks>Task List, allowing users to push directly without viewing the form content. When used, the field value will be modified according to the design there and the process will be advanced. Many fixed replies and advances can be completed through this function.

Component - Field settings

fill variables or fixed strings into the database. This component can be selected when the database needs to be modified without manual processing.

Component - Field/Variable Filter

Simply replace variables or fields or obtain system parameters and default fields, and then output them to other process components for use.

Component - The call process

calls another process under the same application. When the process comes to an end, this process will continue to advance.

  1. Pass on Exception: When an error occurs in the component during process execution, whether to ignore the error and allow the process to continue.

  2. Process: Select the main process to be billed.

  3. Process Input: After selecting the main process, the form fields of the process and the input of the "Start" component will be brought into this tab. **If no value is entered, the system defaults to entering an empty string. . **

  4. Process Output: After selecting the process, the "End" component output of the process will be brought to this tab. Select the required output and put it into the process variable of the current process for use by subsequent components.

Component - The sub-process

calls the sub-process of the current main process. When the process enters the "End" component, the process will continue to advance. The rest of the [Application Management > Call Process] is basically the same.

  1. Subprocess: Select the subprocess to be executed.

  2. Sub-process input: After selecting a sub-process, the form fields of the process and the input of the "Start" component will be brought into this tab. **If no value is entered, the system defaults to entering a blank word string. **

  3. Sub-process Output: After selecting a sub-process, the "End" component output of the process will be brought to this tab. Select the required output and put it into the process variable of the current process for use by subsequent components.

Component - Code

to write a piece of Python code for the data center/collector to execute. The following will be introduced for each tab:

"Settings" tab

  1. Display name: given to the A name for the component to help users identify the current location when viewing the process.

  2. Pass on Exception: When an error occurs in the component during process execution, whether to ignore the error and allow the process to continue.

  3. Distributed Computing: When this option is checked, the server will assign the program code to the "Distributed Computing" group and randomly assign a Collector for execution. For details, please refer to the chapter [Data Collection > Collector Management] .

  4. Record Log: It has the same function as the Execution Process Record (LOG) introduced before. The difference is that this function will only affect the current component.

"Filtering" tab

Filtering tab: Here you can organize the "process variables, form fields, system parameters, application parameters" parameters to be output, to facilitate subsequent Python code access, among which System parameters can refer to the chapter [Application Management > Parameter Management].

※ The variables created by filtering can only be used by the current component, not process variables.

On the "Input" tab,

enter "variables, strings, field values" into the Python code. The following example shows how to use it:

Assume that the code typed in the python tab is as follows:

d = a + b + c

At this time, four variables a, b, c, and d need to be brought in. The settings are as follows:

| Input variables | Variable name | Description | | ---------- | - - ------- | -------------------------- | | 1 | a | Point the fixed string to column a | | Bit B | b | Point the specific field value to b | | Variable C | c | Point the component variable or process variable to c | | | d | Create an empty variable |

Points to note: • Enter "d" into Yes To be able to bring it back into the process. • All parameters entered are strings, so they need to be converted into the required data type in the program code.

"Package" tab

When there is an additional package needed in python, enter the package name here. During the system launch process, it will be judged whether the package already exists. If there is no package, it will be downloaded and installed from the Internet.

※ If there is no external network, you can set up the pypi repository server yourself and modify the system settings.

"Python" tab

to write the required python code. The return of the final result of the program does not rely on return, but needs to write a variable in the outermost layer of the input tab to receive the result. The code is as follows:

d = a + b + c

※ From * Input tab* The variables set can be called without declaring them in the code.

The "Output" tab

obtains the python execution result (d) and writes back the process variables.

| Input data | Variable name | Description | | ---------- | ----------- | ------------------ --------- | | d | calculation | Add new process variable calculation |

※ Only variables that have passed the input tab can be output here!

Component - The external process

calls the process of the application that has been launched. When the process enters the "end" component, the process will continue to advance.

  1. External Process: Select the external process to be issued and executed.

  2. Process Input: After selecting the process, the form fields of the process and the input of the "Start" component will be brought into this tab. **If no value is entered, the system defaults to entering an empty string. **

  3. Process Output: After selecting the process, the "End" component output of the process will be brought to this tab. Select the required output and put it into the process variable of the current process for use by subsequent components.

Component - Conditional Judgment

This component can design branch routes and decide the forward route according to conditions. The following points should be noted:

Important points to note: (1) The rules will be displayed after pulling the line (2) The "FITEM-?" displayed by the rules will appear in the upper left corner of each component screen (3) When two rules are established, the following route will be taken ( 4) When rebuilding the strikethrough, you need to redefine the rules

Component - Approval Judgment.

This component determines the two routes of "agree or reject" based on the final result of the approval, and has the following notes:

Points to note: ( 1) The options of the rule will be displayed after pulling the line. (2) The "FITEM-?" displayed by the rules will appear in the upper left corner of each component screen. (3) This rule component can only determine whether the final approval result is agreed or not, so there is no point in pulling the third line.

Component - Parallel

is different from the "conditional judgment" component. The parallel component will perform each branch route at the same time.

※ **The process variables generated after parallelization cannot be shared by other branches. **

Component - Parallel collection

can collect parallel branches into this component, and select one of the branches as the main line. If the main line is not checked, the last completed branch line will be used as the main line. At the same time, the process variables of all branches will be included. If there are variables with the same name, the main line will be used.

※ **If a collection component is designed, all branches connected to the collection component must be completed before continuing with the subsequent process. **

Component - Dynamic parallelism

allows the process to perform multiple operations on the same route at the same time without affecting each other.

※ **The process variables generated after dynamic parallelism cannot be shared by other branches. **

  1. Number of parallels: Give a field, variable or fixed value to determine the number of parallels: • Array: You can choose the "variable, field" format of the array or directly enter the value (example : A,B,C,D), and calculate the number of parallels based on the length of the array (example: 4 times) • Value: Directly fill in the "variable, field" in the format of a number or directly enter the value (example :3) Determine the number of parallelism (example: 3 times)

2 Array input: Create new process variables and assign different values ​​to different branches • Input data: You can select "variables in the format of array" , field" or enter the value directly, for example: A, B, C, D, then the first branch will get "A" • Variable name: Enter text as the process variable name for input data.

Component - Dynamic collection

can collect dynamically parallel branches. The last completed branch is the main line. If there are variables that need to be merged, they must be set in the output tab. Otherwise, the main line is the main line. .

※ **When all branches are completed, the following processes will continue. **

  1. Output json format: Change the output tab data to string type json format.

  2. Replace "," characters: Replace the "," (semi-shaped comma) in the variable value or field value of the output page with other characters.

  3. Output tab: Select the common fields or variables of all branches to merge and output them into another variable.

The output example is as follows:\ 

Line 1: "A"\ 
Line 2: "B,D"\ 
Line 3: "X,Y" 

The combined variable output is: "A,B,D,X,Y"\ 
If If you check Convert to json on the Settings tab, the output will be: "\['A', 'B,D', 'X, Y']"\ 
If you check Replace "," into" on the Settings tab ooo", the output is: "A,BoooD,X,Y"

Component - Pause

causes the process to pause for specified milliseconds before continuing. The relevant settings are as follows: • Input: Bring in a Numeric variables. • Default value: If the input is empty, take the default value.

Component - Similar positions/responsibilities

This component is linked to "Department, Organizational Chart, Job Management" and can be searched from the default department of a specific user on ** Specify the person in charge of the position and return the relevant information of the person in charge:

The settings of the "Input" tab

are as follows:

  1. Position code: Select to use the position code (position_no) Or query the responsibility name (responsibilitie_name) and enter the corresponding value.

  2. User Number: Fill in the user number, usually the applicant’s user ID.

  3. Query method: Choose to query through organization chart or department structure. For details, please refer to the chapters [Personnel Management > Department Management] and [Personnel Management > Organization Chart] and [Approval Mechanism].

  4. Organization Chart Name: If you select organization chart for query, fill in an organization chart name. For details, please refer to the chapter [Personnel Management > Organization Chart].

  5. Organization chart coordinates: If you select an organization chart for query, you do not need to fill in the organization chart coordinates for the first query. If you want to continue the first query result for the second query, go to the next level. If you continue to search, you can fill in the coordinates of the organization chart output after the first query for positioning, to prevent users from checking the wrong object due to two departments in the same chart.

The "Output" tab

settings are as follows:

  1. Department Number (ID): If a user matching the Position/Responsibility is found, the user's default will be returned Department ID

  2. User ID: If a user matching the position/responsibility is found, the user ID 3 will be returned .Organization chart coordinates: If a user matching the position/authority and responsibility is found, the department code of the position will be returned. When you need to "use this coordinate as the starting point for the next query", you can Use

### component - Department Position/Rights and Responsibilities.

This component is linked with "Department, Organization Chart, Position Management", and you can search for the specified position responsibility from specific department to down person, and return the relevant information of the person in charge:

The settings of the "Input" tab

are as follows:

  1. Department Code: Fill in the department number (dept_no) or department code (dept_code) as the required The starting point for the search.

  2. Position code: Choose whether to use position code (position_no) or responsibility name (responsibilitie_name) for query, and enter the corresponding value.

  3. Query method: Choose to query through organization chart or department structure. For details, please refer to the chapters [Personnel Management > Department Management] and [Personnel Management > Organization Chart] and [Approval Mechanism].

  4. Organization Chart Name: If you select organization chart for query, fill in an organization chart name. For details, please refer to the chapter [Personnel Management > Organization Chart].

The "Output" tab

settings are as follows:

  1. Department Number (ID): If a user matching the Position/Responsibility is found, the user's default will be returned Department ID

  2. User number: If a user matching the position/responsibility is found, the user ID will be returned.

  3. Organization chart coordinates: If a matching user is found** Users with position/rights and responsibilities** will return the department code of the position. When you need to "use this coordinate as the starting point for the next query", you can use

Sub-process design

to enter the sub-process tab and you will see Sub-process list, the main features of sub-process are as follows: • Simplify and improve the readability of the main process • Can only be called by the main process • The component category of the sub-process is the same as the main process, please refer to the above introduction

※ When the sub-process editing is completed, please Click the "OK" button in the upper right corner of the main screen to confirm the changes, and click the "Save" button to finalize the save.

Listed applications

Location: [Main Menu] > Application Management > Listed Applications

Interface for managing listed applications.

List of Listed Applications

When an application is put on the shelf, each application will be displayed here, and the following functions are introduced:

  1. Removal: Remove a listed application.

  2. Filter: Search by keyword and display the number of data items at one time.

  3. Restore: Restore the filter to the default value.

  4. Export: Export the selected application and import it in application design.

  5. **Modification:**Modify the remarks for this version of the application.

  6. Record: After clicking, all applications that have been listed (including all versions) will be displayed.

Listed process list

Location: [Main Menu] > Application Management > Listed Applications > [Any Application]

After clicking the application list, it will jump to the process list of the application. The process list function Introduction:

  1. Enable: Enable batches after checking the process.

  2. Deactivation: Deactivate batches after checking the process. When a process is deactivated, tasks in progress are interrupted and the process cannot be billed or advanced again.

  3. Filter: Search by keyword and display the number of data items at one time.

  4. Restore: Restore the filter to the default value.

The status, LOG, API fields and final settings on the list are all clickable buttons:

  1. Status: After clicking, it will switch between enable and disable. The effect is the same as the enable and disable in the list above.

  2. LOG: Turn on or off the execution process recording function. This can be modified dynamically without re-listing the application.

  3. API: Turn on or off the Application Programming Interface function. This can be dynamically modified without re-listing the application.

  4. Settings: divided into field settings and API, introduced as follows:

Field Settings: Modify the fields displayed in the list. Order Opening API: The content includes API, Method, postbody examples and postback examples. Query API: The content includes API, Method, postbody examples and postback examples. Order Push API: The content includes API, Method, postbody examples and postback examples.

Key points to note:

※ The query API here does not query which order numbers are included in the process, but queries the data number that stays at the manual point for a specific order number, because the process design may design parallelism, dynamic parallelism, etc. , so the same order may generate multiple pieces of data at the same time and wait for manual processing. At this time, you need to query the data number for advancement.

Process form list

After clicking on the process, you can enter the form list. Each time you place an order, a piece of information will be generated in this list. When the form is executed, it will appear in a gray state. If it is not executed or an error occurs, there will be an edit option at the end of the data that you can click on. After clicking the Edit button, the current input and output of the order will appear. At this time, you can manually modify the parameters. After modification, click OK to advance the process.

※ Here you can re-push the order for the form with error execution.

Scheduling Settings

Location : [Main Menu] > Application Management > Scheduling Settings For

processes that have been put on the shelf, schedules can be created to issue orders regularly.

Create a new schedule.

After entering the schedule list page, click the Add button to create a new schedule. The steps are as follows:

  1. Select an already listed process. If the process has a design form, there will be one more after the process name. Form content button.

  2. Click the Form Content button to display the form designed for this process. After filling it out, click the Schedule button.

  3. Set the scheduling period, click the OK button, and the order will be issued according to the settings.

Edit Schedule The

created schedule will appear in the schedule list. There are also "Enable, Disable" buttons below the status field for quick operation. Click the Edit button at the end of the list to modify the schedule. Procedure.

Parameter management

parameters are used in the process. The process can obtain parameters for use in the filtering tab of certain components. Parameters can also be imported and exported in batches. The relevant settings are as follows:

  1. *Name *: Parameter name

  2. Description: Parameter description

  3. Parameter value: Parameter value

  4. Mask: When Yes is selected, the parameter value will be displayed in the list as ⋯⋯

※ It is recommended to use this function when many processes need to use the same parameter value, such as server IP.

Service Level Management

Location : [Main Menu]>Application Management>Service Level Management

Service level rules are used to monitor the specified process. When an order is issued or pushed, changes in the field content trigger the service level. , at this time, the light signal and opening event of the order will be modified according to the trigger conditions, and a letter will be sent to notify the designated person.

After selecting a listed process for numerical measurement, select a field. When the field meets the reminder rules, a reminder notification will be sent and the light of the order will be changed to yellow. If the field violates the rules, a reminder will be issued. Violation notice and change the order's light signal to red.

When the value of a specific field meets the conditions, the service level signal is changed. The settings are introduced as follows:

  1. Notification Subject: The subject of sending the credit.

  2. Notification content: The content of the credit card.

  3. Notify Role: You can select multiple roles, and users of these roles will be notified.

  4. Notifier: You can select multiple users, and these users will be notified.

  5. Notify the biller: Notify the biller of the order.

  6. Application Name: Select the application to be monitored

  7. Process Name: Select the process to be monitored

  8. Reminder Rule: When the monitoring field meets the set value, a letter will be sent Notify and change the service level light to a yellow light

  9. Rule Violation: When the monitoring field meets the set value, an email notification will be sent and the service level light will be changed to a red light

※ Advanced The trigger condition button can be used to add trigger conditions. The service level indicator will only change if both "reminder rules and violation rules" are met.

Time measurement

Time measurement is different from numerical measurement. There are trigger conditions and termination conditions. When the trigger condition is met, the timing will start, and when the termination condition is met, the timing will end. When the timing exceeds the reminder rules, modify the light signal, create an event ticket, and send a notification letter. If the timing is exceeded and violated, the above actions are also performed.

  1. **If the trigger condition is not designed, it means that the order will be triggered immediately. **

  2. **If no termination conditions are designed, it means the order will be terminated. **

Sign-off management

Location : [Main Menu]>Application Management>Sign-off Management

The sign-off list

displays the signed-off templates that have been created.

  1. New: Added approval template.

  2. Delete: Delete the approval template.

After adding an approval under the new approval

point, the creation screen will pop up. The following will introduce the tabs at the top of the screen in order.

The settings of the "Settings" tab

are as follows:

  1. Name: Approval template name.

  2. Description: The description of this template is provided for the reference of process designers.

  3. Notify the signer: When approval is assigned to the signer, whether the user receives a notification.

  4. Notify the signer: When the signature is assigned to a new signer, whether the signer receives the notification.

  5. Notification method: divided into system notification and email. Emails will be sent according to the mail server settings in Application Design>Parameter Management.

  6. Notification content format: You can choose the notification content format as plain text or html.

The settings of the "Input" tab

are as follows:

  1. Built-in parameters: Built-in parameters provided by the system. This parameter will be changed according to the current approval settings and stages.

  2. Input variables: Enter variables from the process for subsequent approval.

Click Add on the "Phase" tab to add a new phase. The various settings of the phase are introduced below:

  1. Name: The name of the phase, mainly used to display in the approval record.

  2. Description: Stage description.

  3. Allow quick operations: Determine whether this approval allows users to perform quick operations in my tasks.

  4. Allow signature: Determine whether the signature is allowed to be added. After signing, the user's weight will be transferred to the signing object.

  5. Multi-person counter-signing: After enabling multi-person signing, there will be more items related to the signing result judgment, and the signing supervisor below will also have a new button to add multiple supervisors. (1) All Agree: Only when all the signing supervisors agree will the next stage proceed. When one person vetoes, the signing will be left and the result of this signing will be output as "disagree". (2) Weight Threshold: The result of this stage is determined according to the threshold setting.

  • Reaching the threshold is regarded as: here, first distinguish between agreeing or disagreeing. If the conditions are met, it will be the selected result, otherwise it will be another option. Fill in the threshold score in the numerical area below, the default is 100.

  • Customized weight: If checked, you can enter your own number for the weight of the signing supervisor below. If not checked, the number will be evenly distributed according to the number of signing supervisors (100 points will be divided equally).

  • The current phase ends when the approval weight reaches the threshold: After this item is checked, when the weighted scores of some supervisors after approval reach the approval threshold, the approval forms of other supervisors will be closed, and the approval forms will be closed according to the settings. The determined result will advance to the next stage or leave for approval.

(3) Weight Comparison: After all approval supervisors have signed off, they will be totaled according to their respective weighted scores. The party with the higher score will advance the result.

  • When the weights of the approval results are equal: Select which result will be output when the weights of both parties are the same.

  • Customized weight: If checked, you can enter your own number for the weight of the signing supervisor below. If not checked, the number will be evenly distributed according to the number of signing supervisors (100 points will be divided equally).

  1. Signing supervisor: (1) Weight: This option cannot be changed when multi-person counter-signing above is not enabled. After enabling multi-person signature, whether it can be adjusted will be determined according to its settings. (2) Name: The name of the sign-off supervisor, mainly used to be displayed in the sign-off record. (3) Type: The signing supervisor has the following four query methods.

  • Designated person: Directly specify which user will approve the approval.

  • Organization Chart Query: Query through the organization chart.

  • Department query: query through department structure.

  • External query (Python): Call other systems or other processes within the system to query.

(4) Approver:

*Organization Chart Name: This menu will be enabled only when the type selects Organization Chart Query and is used to enter the name of the organization chart.

  • Query method: This menu will be enabled only when the type is selected as organization chart query or department query. Select one of the same department positions/same department responsibilities/department positions/department responsibilities to query.

  • Select department/position name/responsibility name: This menu will change depending on the type. When the type is a designated person, this menu is for selecting a department; when the type is organization chart query or department query, this menu will display the job title or authority name according to the query method.

  • Select User/User ID/Department Code: This menu will change depending on the type. When the type is designated person, this menu is for selecting the user; when the type is organization chart query or department query, this menu will be displayed as user number or department code according to the query method.

"Notification" tab

This tab is used to design the corresponding subject and content when sending a letter notification:

  1. Subject: The subject of the notification. You can use built-in parameters and variables. To use them, move your mouse over the question mark next to the subject and wait for two seconds for it to appear.

  2. Content: Notice content. Built-in parameters and variables can also be used, and the usage methods are the same.

"Python" tab

This tab is only used when querying the sign-off supervisor. When the sign-off supervisor's query method selects external query (Python), this program code will be called for query.

  1. New: This new addition is used to add a python package that will be used in the program code. The package will be checked when the template is saved.

  2. Program code: Enter the program code to be called by yourself. The response and example are written above. Built-in parameters and variables can be used here. The usage method is similar to notification, except that there is no need to use curly brackets {} to enclose the variables.

PreviousData CollectionNextReport

Last updated