Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

1. Nodes

Node

Applicant node

1 Introduction

It is the default first node of the process and can be used to fill in the form and initiate the process.

2. Setup steps

2.1 Function entrance

Enter the application editing interface, click Add Process, select the applicant node, and set the applicant node.

2.2 Function setting steps

2.2.1 Set node name

You can set the name of the applicant node to easily distinguish different nodes. Click the pencil icon to the right of "Applicant" to set the node name

2.2.2 Set the applicant range

  • Applicant scope: All applicants who can fill in the current form and initiate the process.
  • Workspace can be filled in: Only members in the same workspace can fill in the current form.
  • Specified members can fill in: Only designated members can fill in the current form.
  • Everyone can fill in: Anyone who receives the link to the form can fill out the form. You can choose whether you need to log in to your Anffy account to fill in the form. Check "Require to log in first". Applicants can only fill in the current form after logging in to their Anffy account.

2.2.3 Set field permissions

Field permissions: Whether the applicant can edit or see the permissions of different fields in the form at the current node. The permissions that can be selected are "editable," "visible only," and "hidden." Select the target field and click "Editable," "Visible Only," or "Hide" to complete the operation.

2.2.4 Batch settings

You can set the permissions of all fields in the form to be editable, visible only, or hidden in batches. Click the "Batch Settings" button in the upper right corner of the field to batch set the permissions of all fields in the form on the current node.

When using the "Batch Settings" function to set the permissions of all fields in the form to editable, the permissions of the number field, applicant field, application time field, update time field and subsequently added data source nodes will be set to only visible

Approval node

1 Introduction

1.1 Function introduction

The node leader can be allowed to decide whether the process of the current form can continue, which facilitates process management.

1.2 Usage scenarios

Suitable for scenarios where approval of form content is required. For example, in the reimbursement process, you can use the approval node to decide whether to pass the reimbursement application.

2. Setup steps

2.1 Add approval node

Enter the application editing interface, click Add Process, and after adding the approval node, you can set the approval node.

2.2 Function setting steps

2.2.1 Set node name

You can set the name of the approval node to easily distinguish different nodes.

method one

Select the added approval node and click the "pencil icon" on the right side of "Unnamed Node" to set the node name.

Method two

When adding an approval node, you can directly set the node name

2.2.2 Switch node type

You can switch the current approval node to a fill-in node or a carbon copy node. Select the added approval node and click the drop-down triangle next to the node type to switch the node type.

2.2.3 Delete node

Unnecessary approval nodes can be deleted

method one

Select an added approval node, click the "X" in the upper right corner of the node, and select Delete to complete the operation.

Method 2

Select an added approval node, click the "Trash Can" button in the upper right corner, and select Delete to complete the operation.

2.2.4 Set the node leader

Node leader : the person who can approve at the current node. Click the drop-down triangle under "Responsible person" to choose between "regular approval" or "step-by-step approval " .

Routine approval: Approval according to system process

Level-by-level approval: Starting from the direct supervisor of the process initiator, approval is carried out step by step.

method one

Select the added approval node and click " +" under "Responsible Person" to add the node person in charge.

Method 2

When adding an approval node, click "+" under "Responsible Person" to add the node person in charge.

2.2.5 Approval type

When the node has multiple persons in charge, you can choose the approval type of "or sign" or "countersign". Select the added approval node and click the drop-down triangle under "Approval Type" to set the approval type.

“OR” sign : Among multiple responsible persons, the approval can be completed if one person passes or rejects it.

“And” sign : The approval result will only be considered passed when the approval results of all node leaders are unanimous. For example: if any node person in charge chooses to reject and other person in charge chooses to pass, the approval result will be deemed to be rejected.

The approval type can only be set when the approval method is set to regular approval.

2.2.6 The person in charge is empty

When the node manager is empty, the person who approves the form will replace the node manager. Select the added filling node and click the button below "Responsible person is empty" to add the person in charge of processing.

2.2.7 Set field permissions

Whether the node leader can edit or view the permissions of different fields in the form at the current node. The permissions that can be selected are "editable", "visible only" and "hidden". Select the target field and click "Editable", "Visible Only" or "Hide" to complete the operation

Editable : The person in charge can fill in or modify fields with editable permissions at the current node.

Visible only : The person in charge can view fields with visible-only permissions on the current node, but cannot modify the field content.

Hidden : The person in charge cannot view fields with hidden permissions on the current node.

The permissions of the number field, applicant field, application time field, update time field, and subsequently added data source fields can only be set to visible or hidden.

2.2.8 Batch settings

You can set the permissions of all fields in the form to be editable, visible only, or hidden in batches. Click the "Batch Settings" button in the upper right corner of the field to batch set the permissions of all fields in the form on the current node.

When using the "Batch Settings" function to set the permissions of all fields in the form to editable, the permissions of the number field, applicant field, application time field, update time field and subsequently added data source nodes will be set to only visible

2.2.9 Basic settings

Functions such as "Message" and "Process Log" can be turned on in the basic settings to improve node usage efficiency. Click the "Basic Settings" button to enter the setting interface

2.2.10 Advanced settings

You can turn on "submit verification", batch operations and other functions in the advanced settings, yes. Click the "Advanced Settings" button to enter the setting interface


3. Precautions

  • The "Responsible person is empty" function can only add one member.

Fill in the node

1 Introduction

1.1 Function introduction

You can modify and supplement the form content to facilitate the improvement of the form content.

1.2 Usage scenarios

Suitable for scenarios where you need to modify or fill in the form content before continuing the process. For example, when the after-sales service process proceeds to the designated after-sales person in charge, you can use the fill-in node to add the after-sales person in charge's information in the form.

2. Setup steps

2.1 Add filling node

Enter the application editing interface, click Add Process, and after adding the fill-in node, you can set up the fill-in node.

2.2 Function setting steps

2.2.1 Set node name

You can set the name of the node to easily distinguish different nodes.

method 1

Select the added fill-in node and click the pencil icon to the right of "Unnamed Node" to set the node name.

Method 2

When adding a fill-in node, you can directly set the node name

2.2.2 Switch node type

You can switch the current filling node to the approval node or the carbon copy node. Select the added fill-in node and click the drop-down triangle next to the node type to switch the node type.

2.2.3 Delete node

Unnecessary filling nodes can be deleted

method 1

Select an added fill-in node, click the "cross" in the upper right corner of the node, and select Delete to complete the operation.

Method 2

Select an added fill-in node, click the "Trash Can" button in the upper right corner, and select Delete to complete the operation.

2.2.4 Add node leader

Node leader : the person who can fill in or modify the form data in the current filling node

principal

method one

Select the added filling node and click "+" under "Responsible Person" to add the node person in charge.

Method 2

When adding a node, click " +" under "Responsible Person" to add the node person in charge.

2.2.5 Add the person in charge of agent processing

Acting processing person in charge : When the node person in charge is empty, the person who fills in or modifies the form data on behalf of the node person in charge. Select the added filling node and click the button below "Responsible person is empty" to add the person in charge of processing.

2.2.6 Set field permissions

Field permissions : Whether the node leader can edit or see the permissions of different fields in the form at the current node. The permissions that can be selected are "editable", "visible only" and "hidden". Select the target field and click "Editable", "Visible Only" or "Hide" to complete the operation

Editable: The filler can fill in or modify fields with editable permissions at the current node.

Visible only: The filler can see the fields with visible-only permissions on the current node, but cannot modify the field content.

Hidden: The filler cannot see the fields with hidden permissions on the current node.

The permissions of the number field, applicant field, application time field, update time field, and subsequently added data source fields can only be set to visible or hidden.

2.2.7 Batch settings

You can set the permissions of all fields in the form to be editable, visible only, or hidden in batches. Click the "Batch Settings" button in the upper right corner of the field to batch set the permissions of all fields in the form on the current node.

When using the "Batch Settings" function to set the permissions of all fields in the form to editable, the permissions of the number field, applicant field, application time field, update time field and subsequently added data source nodes will be set to only visible

3. Precautions

  • agent can be added to each filling node

Cc node

1 Introduction

1.1 Function introduction

Form content and process logs can be sent to the node leader to facilitate information synchronization.

1.2 Usage scenarios

It is suitable for scenarios where you only need to send form-related information without filling in or modifying the form. For example, when making a weekly report system, you can use the CC node to copy the completed weekly report to all department members.

2. Setup steps

2.1 Add CC node

Enter the application editing interface, click Add Process, and after adding the CC node, you can set the CC node.

2.2 Function setting steps

2.2.1 Set node name

You can set the name of the CC node to easily distinguish different nodes.

method one

Select the added CC node and click the pencil icon to the right of "Unnamed Node" to set the node name.

Method 2

When adding a CC node, you can directly set the node name

2.2.2 Switch node type

You can switch the current carbon copy node to an approval node or a fill-in node. Select the added CC node and click the drop-down triangle next to the node type to switch the node type.

2.2.3 Delete node

Unnecessary CC nodes can be deleted

method one

Select an added CC node, click the "cross" in the upper right corner of the node, and select Delete to complete the operation.

Method 2

Select an added CC node, click the "×" button in the upper right corner, and select Delete to complete the operation.

2.2.4 Add node leader

Node leader : the person who receives the CC data

method one

Select the added CC node and click "+" under "CC To" to add the node leader

Method 2

When adding a CC node, click "+" under "CC To" to add the node leader

2.2.5 Set field permissions

Field permissions : Whether the node leader can see the permissions of different fields in the form at the current node. The permissions that can be selected are "visible only" and "hide". Click on the added CC node, select the target field, and click "Visible Only" or "Hide" to complete the operation.

Visible only: Applicants can see fields with visible-only permissions on the current node, but cannot modify the field content.

Hidden: Applicants cannot see fields with hidden permissions on the current node.

2.2.6 Batch settings

You can set the permissions of all fields in the form to "visible only" or "hide" in batches. Select the added CC node and click the "Batch Settings" button in the upper right corner of the field to batch set the permissions of all fields in the form on the current node.

Set carbon copy person

Multiple carbon copy recipients can be set. You can set carbon copy recipients by directly entering their email addresses or selecting members from your address book. The received carbon copy data will appear in the carbon copy person's participation data list.

Configure field permissions

Move the mouse over a field to configure field permissions. Only visible and hidden permissions can be configured for the CC node . Visible only means that the CC can only see the field but cannot edit it. Hide means that the CC cannot view the field.

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.