6. Advanced Settings

Advanced settings

Reminder content customization

1 Introduction

1.1 Function introduction

By customizing reminder content, important information can be made more obvious, easier to read, and save time and effort.

1.2 Usage scenarios

It can be used in scenarios such as equipment repair reporting and application result push to facilitate recipients to see important information in a timely manner.

1.3 Effect display

As shown in the figure below, after configuring the reminder content in the "Equipment Warranty", the message reminder received will display the configured content.

2 Setup steps

2.1 Function entrance

Enter the target process node, click "Advanced Settings," and turn on "Reminder Content Customization."

Only the application, approval, filling, and carbon copy nodes support the "reminder content customization" function.

2.2 Reminder method

2.2.1 Customized Platform Reminders

receive reminders through the WeChat service account, and the platform version receives reminders through third-party platforms.

2.2.2 Email reminder

After turning it on, the bound mailbox will receive information such as to-do items, application results, carbon copy, etc., and can enter the corresponding workspace through email to handle tasks.

2.2.3 Process nodes can configure email reminder templates

Prerequisite: Private cloud, in the process node editing drawer, this email reminder is not turned on in "Extended Settings". After
Checking the custom email reminder, the reminder events of this node type will be displayed, and emails can be created for different events. Templates can make different reminders received by different persons in charge of the process.

If you do not create an email template, the Anffy default template will be used.

Read the template priority: "Node - Reminder Content Customization - Email Reminder Selected" > "Extended Settings - Reminder Settings - Email Reminder Selected" > Anffy's default reminder template is in "Extended Settings" - "Email Template."

2.2.4 Email templates can be customized

Customize the name, reminder title, reminder content, and attachment content of the email template in "Extended Settings" - "Email Template". You can insert fields in the reminder title and content.

2.3 Turn on/off reminders

You can configure whether to enable reminders in the "Reminder Settings" in the "Extended Settings" of the target application. If you turn off the reminder at this time, you will not receive the message even if you configure custom reminder content.

3. Precautions

• Only private cloud can configure custom email templates
• WeChat Service Account Enhancement" is configured , the to-do items will not display the content configured in "Reminder Content Customization", but will be displayed according to the original system default reminder content.
• the DingTalk version of Anffy in DingTalk and the official version of Anffy in WeChat notifications, the timeout warning reminder and the timeout reminder will not display the content configured in the "Reminder content customization". Still, it will follow the original system default reminder content. exhibit

Data Sources

Introduction

Data sources can also be understood as the method of collecting data. After adding data in a third-party system, the data can be added directly in the current application.

Data sources can be created in two ways - Q-source or DingTalk M2 Smart Front Desk. Therefore, as long as you open the Q-source or DingTalk M2 smart front desk in the "Plug-in Center-Data Collection Tool," you can use it.

Use Cases

1. DingTalk M2 smart front desk

PS DingTalk M2 Smart Front Desk is currently an additional purchase item for the basic version. When the workspace is upgraded, you can go to the plug-in center to purchase it.

1. After opening the "Plug-in Center - Data Collection Tool", "click Sync Device" in the configuration pop-up window;

2. In the application's "Process Design - Applicant Node - Advanced Settings - Data Source", click "Add Source" and select "DingTalk M2 Smart Front Desk."

3. To configure DingTalk M2 smart front desk, the following must be set:

• Device: You can add multiple M2 devices that have been synchronized with Anffy
• Assignment rules: The data transmitted from M2 is the person who clocked in and the time they clocked in. The corresponding information needs to be matched with the fields.

setting up the release , when there is new personnel check-in information on M2, a piece of data will be automatically added to the form.

Process timeout

1 Introduction

1.1 Function introduction

Process timeout can realize timeout warning, timeout reminder, or automatic submission of timeout of the process node by setting the time and notification object when the process reaches the node.

1.2 Application scenarios

It can be used for leave approval, reimbursement approval, feedback evaluation, etc. For example, in the leave approval process, a timeout warning is provided before the start date of the leave, and the approval node is automatically passed when it expires so that the subsequent process can proceed smoothly.

1.3 Effect display

2. Setup steps

2.1 Function entrance

On the form editing page, click "Add Process" in "Application Editing," enter "Advanced Settings" in the process node, and turn on "Process Timeout."

2.2 Function setting steps

2.2.1 Timeout trigger time

You can customize the trigger time of process timeout by selecting the trigger time type.

Custom time: Set when to issue a timeout reminder after the process reaches the node

Trigger immediately: Trigger immediately after the process reaches the node for a specified number of days.

Trigger at specified time: After the process reaches the node for a specified number of days, it will be triggered at the specified time of the day.

According to the field in the form: set to the corresponding date type field in the form, and when to issue a timeout reminder based on the date of the field

Date calculation method: You can choose to specify the day calculation method as "natural day", "working day (Monday to Friday)" or "statutory working day"

Natural days: refers to Monday to Sunday.

Working days (Monday to Friday) : refers to Monday to Friday, Saturday and Sunday are not included when calculating the specified number of days.

Statutory working days : working days determined based on the "Annual Statutory Holiday Arrangement" announced by the State Council. Statutory holidays are not included in the calculation of overtime days. (The State Council generally publishes holidays for the coming year in November or December each year. When the specified number of days exceeds the known "annual statutory holiday schedule", the excess will be calculated as "working days (Monday to Friday)". When the system When the latest holiday schedule is obtained, the set specified days will be updated according to "statutory working days")

As shown in the figure, when the process reaches the node on May 17, 2023 (Thursday), and the timeout trigger time is set to 12:00 after 3 days (working days (Monday to Friday)), the trigger time is 2023 12:00 on May 23 (Tuesday), that is, Saturdays and Sundays are not included in the calculation.

2.2.2 Who to notify after timeout

When the set timeout reminder time is reached, the corresponding member will receive a process timeout reminder. The type of notification object can be selected as member, department, role or dynamic.

2.2.3 Timeout processing

Automatic submission: When the node process times out, any submission restrictions will be ignored and the current node will be automatically passed.

Submission restrictions: formula calculation, submission verification, required, association with existing data, etc.

2.2.4 Timeout Warning

Timeout warning: before triggering process timeout, when to remind the corresponding members of the impending timeout

Who to remind: When the set timeout warning reminder time is reached, the corresponding member will receive a reminder that the process is about to timeout.

2.2.5 Email and WeChat reminders

You can send reminders about process imminent timeout or process timeout reminder to designated members through WeChat service account or email.

• Go to "Extended Settings" on the form editing page and select "Reminder Settings" to turn on "Timeout Reminder" or "Timeout Alert Reminder"
• The reminder method can be "Send Email" or " WeChat Reminder ". After selecting, reminders can be sent to designated members through WeChat service accounts or emails.

The process is about to time out: " WeChat Reminder " and "Email Reminder"

Process timeout: " WeChat reminder " and "Email reminder"

2.3 View timeout data

2.3.1 Process timeout data

When the process node times out, the corresponding member will be notified with a red "timed out" reminder.

Method 1: Check the timeout data from "My To-Do".

Method 2: Check the timeout data from "Timeout".

Method 3: View timeout data from "View"

2.3.2 Warning data about process imminent timeout

When the data reaches the process node, and no timeout is triggered, but a timeout warning is triggered, the corresponding member will be notified with a yellow "Timeout is imminent".

Method 1: Check the upcoming timeout data from the "To-Do List."

Method 2: Check the upcoming timeout data from "Due soon."

Method 3: Check the upcoming timeout data from "View"

3. Precautions

• Only the approval node and filling node can set process timeout
• When the time when the data arrives at the node is later than the "timeout trigger time", there will no longer be a "timeout warning reminder"
• When data reaches a node without a responsible person, "timeout reminder" and "automatic submission after timeout" will not be triggered.

Related reports

1 Introduction

When viewing data in the current application, you can also view related data in other applications or lightly analyze the data in the data set through associated reports to achieve quick viewing of data.

2. Setup steps

2.1 Configuration example

In the "Store Management" application, if we want to see the product information of the store in addition to sales orders, we can click " Start Creating " in the extended settings of the "Store Management" application - Association Report to add an association, optional Data source Anffy application or light analysis of the data set

You need to have permission to analyze data to see the data set options here.

After adding, you need to set association rules and select the report to be associated. In this example, the rule is that the product category in the "Store Management" application is not empty. Then select the report to be associated and publish it.

2.2 Functional effects

2.2.1 Open associated display

Just click Table View - Edit View and click Data Permissions on the right to open the associated report. You can also set the permissions and fields for viewing the report.

2.2.2 Effect display

After the above example is set up, when we click on the details of a single piece of data in "Store Management", we will find that there will be an additional column of the inventory report that has just been associated next to the sales order. In this way, we can Check the store's sales orders and product quantities at the same time.

Similarly, in the sales scenario, we can also set up associations for applications such as customer information, order management, contract management, business opportunity records, etc., and realize the query of all other data related to a certain customer at the same entrance.

3. Other settings

3.1 Adjust the order of reports

After the associations are created, you can also adjust the position of each association. The order from top to bottom is consistent with the order finally displayed in the pop-up window.

3.2 Visible range

Each node can independently set the visible range of different associated reports. For example, in a store management application, the sales order report can be set to make all nodes except the approval node invisible.

3.3 Quickly create associated reports]

If you find that there is no report or the report you want when selecting the associated report, you can use the shortcut keys below to quickly jump to the corresponding interface to create the report.

3.4 Data permissions in associated reports

The linked report inherits all permissions of the original report, including the following permissions:

• data range
• Field show\hide
• Operation permission
• Report visibility permissions

4. Precautions

• You need permission to analyze data to have the data set option.
• If the member who opens the data does not have permission to view the report, this column will not be displayed in the pop-up window .
• If the data table is associated, the association settings of the data table will no longer be displayed in the data details opened in the associated data table.
• Pay attention to the settings of report permissions, including application permissions, data permissions, and report permissions.
• the data source of the light analysis report , it is divided into " Anffy application" and "data set", so when selecting different data sources, the mapping relationship is also different. The following lists the fields for selecting the light analysis report and the matching field types supported by the corresponding Anffy report.

Brief analysis of report field types: text fields, numeric fields, date fields, time period fields, member fields, department fields, address fields (under development)
Anffy report field types: single line text, multi-line text, link, phone, email, single item Selection, drop-down option, multiple selection, image selection, positioning, number, numeric field, date field, time period field, member field, department field, address field.

Submit verification

Function introduction

For different nodes, when the business scenario requires certain conditions to be met before data can be submitted, the submission verification conditions can be set to judge the corresponding nodes.

Anffy 's submission verification currently supports two types of settings: field verification conditions and application verification conditions. Click to view the specific functions and setting methods~

Submit verification-field verification

Function introduction

According to the requirements of the business scenario, certain verification conditions are set for the values of several fields at the corresponding nodes. Only data that meets the verification conditions can be submitted.

Setup steps

Set up entrance

Find "Submit Verification" in **Application Editor-Process Design-Advanced Settings**, click "Only data that meets the conditions can be submitted", and select "Field Verification Conditions"

Node types that support [Submit Verification]: REMOVED node, Approval node and Fill-in node

Set field validation conditions

The submission check of the node defaults to " all data can be submitted " . When you select " submit only when conditions are met", all data arriving at the node must meet the conditions before it can be submitted to the next node. If it does not meet the conditions, it is not allowed to be submitted. submit.

For example, in the process of inventory management, we generally do not allow "negative inventory", that is to say, the maximum outgoing quantity is determined based on the existing quantity of inventory.

When setting conditions, the commonly used formulas are as follows, which can be used according to the scenario:

• Greater than>
• less than<
• equal to ==
• Not equal to!=
• Greater than or equal to >=
• Less than or equal to <=

Notice

Supports setting multiple application verification conditions. As long as one verification condition is not met, data cannot be submitted.

Supports setting application verification conditions and field verification conditions at the same time. Similarly, as long as one verification condition is not met, data cannot be submitted.

Add verification prompt

For each verification, add a prompt to remind the person in charge to make modifications when it cannot be submitted.

Effect

We can see that there are currently only 190 pieces of grapes. If 200 pieces are shipped out of the warehouse, it will prompt that the inventory is insufficient.

Scenario example

• Number digit control: The required number digits to enter is 10 digits
• Quantity control: 1-999 items are allowed for each warehousing

Notice

1. When using formulas, if it is a mutual judgment between text fields, you need to use the NUM() function to convert the text into numbers.
2. The difference between "data verification" and "filtering data" of the branch

• Node verification determines whether the data can meet the conditions and continue to flow to the next link. That is to say, node verification is mainly used to reject data that does not meet the conditions.
• "Screen data" to determine the different process directions of the data

3. Submit two pieces of data for verification in a short period of time. While the data submitted first is still being verified, the data submitted later cannot be clicked to submit.

Submit Verification-Apply Verification

Function introduction

According to the requirements of the business scenario, select several applications for verification at the corresponding node.

If the selected application is adding or updating data , it will not pass the verification, that is, the data of the node cannot be submitted. This is to avoid data inaccuracies caused by new data being generated when data is being added or updated.

Data being added or updated includes -

added data

• Add data via Q-Robot
• OpenAPI
• Q-Source passive mode
• Import Data
• Click the "Submit" button to submit the data

updated data

• Update data via Q-Robot

Applicable scene

• Purchase, sale and inventory-sales orders, inventory incoming and outgoing, etc.

Setup steps

1. Configure the entrance

Find "Submit Verification" in [**Application Editing]-[Process Design]-[Advanced Settings] **, click "Only data that meets the conditions can be submitted", and select "Apply Verification Conditions"

Node types that support [Submit Verification]: REMOVED node, Approval node and Fill-in node

2. Set application verification conditions

The node's submission verification defaults to " all data can be submitted " . When you select " submit only when conditions are met", all data arriving at the node must meet the conditions before it can be submitted to the next node. If it does not meet the conditions, it is not allowed to be submitted.

Precautions

Supports setting multiple application verification conditions. As long as one verification condition is not met, data cannot be submitted.

Supports setting application verification conditions and field verification conditions at the same time. Similarly, as long as one verification condition is not met, data cannot be submitted.

3. Add verification prompts

For each verification condition, add a prompt to inform the submitter of the reason why it cannot be submitted.

The default prompt text is: XX application is being added or updated, please try again later; "XX application" is the selected application.

Scenario example

For example, in the scenario of inventory management, we will avoid that after sales colleague A places an order for a product, the inventory data is still being updated. At this time, sales colleague B places an order for the product again, which ultimately leads to confusion in the inventory data. , or even when the inventory is negative.

In order to avoid this situation from happening, we can configure the following:

1. In the "Sales Order" node of the "Sales Order Management" application, set the application verification conditions, select the "Inventory Flow" application, and configure the prompt text when the verification condition is not passed: "The inventory flow is being updated. Please place your order later…”

2. When the salesperson is placing an order, if the above "inventory flow" is being added or updated, when the salesperson clicks "Submit", the submission cannot be made and the prompt is as follows:

This way your inventory will never go wrong again!

Precautions

If the applicant node of application A is set to verify application B, when application B is adding/updating data, application A cannot——

• Submit the data of the applicant node
• Import data into the process
• Add data via OpenAPI
• Add data via Q-Source passive mode

Retrigger data association or formula on submit/pass

Introduction

When submitting/passing in the process, some fields in the form will be re-associated or calculated to ensure that the data stored in the database is the latest background data.

scenes to be used

• In the purchase, sale and inventory scenario, ensure that when submitting the form, the outbound quantity is always within the safety stock range, otherwise the submission cannot be successful.
• When submitting/passing, the associated data between applications is always up to date.
• Imported data and data after Q-robot can be re-associated/calculated according to the form design

How to set up

Currently the node types that can be set are:

• Apply for node
• Approval node
• Fill in the node

1. In the "Advanced Settings" of the node, turn on the function of "Retrigger data association or formula when submitting/passing"

2. Select the fields that need retriggered, adjust the order as needed, and then submit.

Precautions

1. If the aggregation mode is not set for the "data association" field, the system will take the first value.
2. The order of triggering is from top to bottom. Therefore, if the data after retriggering needs to be calculated, the fields with formula calculation set up need to be sorted after the related fields. For example: the total inventory number number 21005120020 The above table is all the data in application A. We associate the data of application A in application B. Number 1 is the value associated when filling in application B, and number 2 is the value associated in application B. When preparing to submit, the latest data submitted by A is applied. If it is necessary to calculate in application B at this time: remaining inventory = total inventory - outbound inventory. Then the impact of the field order during setting on the results is as follows: Field order (from top to bottom) After recalculation, the total inventory and outbound inventory are correctly demonstrated . Warehouse 1005180 Total inventory, remaining inventory, outbound inventory 100580 Outbound inventory, remaining inventory, total inventory 1005195 Therefore, in order to ensure that the calculation of "remaining inventory" is correct, the position of "remaining inventory" must be adjusted to "total inventory" and "outbound inventory" after
3. If the data added by q-robot is involved in recalculation, the recalculation may not be successful.
4. If the trigger field is selected as the entire table, it is equivalent to triggering the association of the entire table. If you want to trigger table subfields at the same time, you need to add additional table subfields.

Handwritten signature

Function introduction

In some business scenarios of approval and contract signing, the signature of the relevant person in charge is required. To enable these business scenarios to be successfully completed online, Anffy has launched a handwritten signature function. Using this function, the node leader can handle to-dos in the form of an online signature on a computer or mobile phone, flexibly and easily meeting various business scenarios.

Applicable scene

• Process approval
• Agreement signing
• service delivery
• Item receipt
• contract signing
• …

Setup steps

1. First, open the "Handwritten Signature" plug-in

Open the "Handwritten Signature" plug-in in [Plug-in Center]

2. Turn on "Handwritten Signature" at the process node

Turn on "Handwritten Signature" in "Advanced Settings" of "Application Node", "Fill Node" or "Approval Node"

3. Use "handwritten signature"

Computer signature

The person in charge of the to-do list can directly perform the signature operation through the computer, or clear the signature and then sign again; after completing the signature approval, the signature will also be recorded in the process log.

Mobile signature

The person in charge of to-dos can also sign on the mobile phone. During the signing process, clearing and re-signing is supported, and the signature can also be switched between horizontal and vertical screens.

Precautions

• After opening the "Handwritten Signature" plug-in in the plug-in center, you can turn on the "Handwritten Signature" in the process node.
• Fill-in nodes and approval nodes support "handwritten signature"
• After turning on "Handwritten Signature" when filling in a node, when processing the node to-do, a handwritten signature must be made before it can be submitted.
• After "Handwritten Signature" is turned on at the approval node, a handwritten signature is required to pass/reject when processing the node's to-do list.
• Handwritten signatures are not required for rollback and transfer operations

Print "handwritten signature"

Default template

"Handwritten signature" supports printing in the default template

choose process log

Printing effect

Custom printing templates

"Handwritten signature" supports printing in custom printing templates

Set template

In the system field, select "Process Log·Handwritten Signature" to insert into the template

Printing effect

Version restrictions

"Handwritten signature" is available for the basic version and above

Batch operation

1. Function introduction

Have you ever experienced that when the q-robot automatic node is followed by the approval node, you watch hundreds of pieces of data being updated, and the data of each hand point is growing faster?

don’t worry! For situations where a certain backlog node needs to be processed quickly and intensively, the newly launched batch processing function can solve this problem.

2. How to use

First, turn on "Batch Processing" in **Application Editing-Process Settings-Advanced Settings** and then publish the application. Applicable nodes:

• Fill in the node
• Approval node

Usage effect: achieve batch pass, batch rejection or batch transfer.

3. Precautions

• After allowing the node leader to batch process related to-dos, the form verification (required, etc.) will be ignored during batch processing, but the node submission verification and recalculation will still be involved.
• Each batch processing can only process the to-dos of the same process node. If the data of multiple nodes are selected at the same time, only the to-do items in the selected nodes will be processed.
• Batch processing is only valid for node to-do data with "batch processing enabled"

4. Other batch-related operations

• Assign to-do data in the process to other members