1. Examples of business usage scenarios

Second, the detailed introduction of the batch

2.1 Batch preset scenarios

• All: The person in charge is the current user, or his subordinates or related team members include the current user, or his subordinates, or the person in charge of the record in the batch "Data Sharing" rule configured in "Data Rights Management", or the department to which the person in charge belongs The data of the current employee is shared with the current employee, or the department the current employee belongs to, or the user group the current employee belongs to, or the data of "I am in charge of the department".
• The person in charge is the current user or his subordinates.
• Or related team members include the current user or his subordinates.
• Or configure the "Data Sharing" rule of the batch in "Data Rights Management" to share the data of the person in charge or the department to which the person in charge belongs to the current employee or the department to which the current employee belongs or the user group to which the current employee belongs.
• Or "for my department" data.
• I'm responsible: The responsible is the current user.
• I'm In: The current user is included in the related team members.
• My subordinates are in charge of: the person in charge is the subordinate of the current user.
• Participated by my subordinates: The relevant team members include the user's subordinates.
• Shared to me: Configure the "Data Sharing" rule of the batch in "Data Rights Management" to share the data of the person in charge or the department to which the person in charge belongs to the current employee or the department the current employee belongs to or the user group the current employee belongs to .
• I am in charge of the department: the current user is the department head of the main department, and the main department of the relevant team members in the record is this department. Remarks: Whether the responsible department includes all subordinate data is determined by "CRM Management-Rule Settings-Basic Settings-Superior Visible Data Scope".
• The current user is the department head of the main department.
• At the same time, the main department of the relevant team members in the record is this department.
• Remarks: Whether the responsible department includes all subordinate data is determined by "CRM Management-Rule Settings-Basic Settings-Superior Visible Data Scope".

• "CRM Admin" can view all data.
• All records whose status is "Obsolete" can only be seen by the "CRM administrator", and no other personnel can see it.

2.2 Batch business operations

2.2.1 Create a new batch

• Manual creation entry: [batch] list page
• Import, see Import for details
• Batch number: The main attribute of the batch is the batch number, which cannot be repeated.
• Associated product: When creating a new batch, it must be associated with a specific product, and the associated product must be a "on-shelf" product, and batch management is enabled;
• Fixed approval process: You can create an approval process in the approval process management. When a new batch is created, the approval process can be automatically triggered and executed. See 【Approval Flow Management】 for details
• Note: No matter whether the approval status of the batch is confirmed or not, it can be referenced by related objects. After batch approval, it can no longer be modified or withdrawn, and printing is supported.

2.2.2 Batch Inventory

• For products with batch management turned on, the corresponding batch must be selected when warehousing. After the warehousing is successful, if the batch is the first warehousing, the system will automatically generate the corresponding batch inventory and add the corresponding batch. Secondary inventory quantity. the
• You can see the total batch inventory of a batch under all warehouses in the batch list, or click on the batch to query each batch inventory record under the batch.

2.2.3 Replacement Confirmer

• Business description: In the process of process flow, the confirmer can be replaced due to reasons such as the resignation or job transfer of the current pending person.
• Business operation condition: In the approval process, the batch status is "confirming"
• The employees or roles that can perform this operation are: Approval node confirmer
• Business operation entry: "Batch" details page.

2.2.4 Withdrawal

• Business description: When a batch is submitted and confirmed by the next node processor, the previous node processor can withdraw the process, and the pending batch of the next node processor will be withdrawn.
• Business operation conditions: In the approval process, the batch status is "confirming".
• The employees or roles who can perform this operation are: the person in charge, the superior of the person in charge, the relevant team members with "read and write" permissions, and the superiors of the relevant team members, the party whose data is shared and with "read and write" permissions.
• Business operation entry: "Batch" details page.

2.3 Batch general business operations

• See Common List Operations for common operations on the list page
• Add sales records, see sales records for details
• Common business operations, including changing the person in charge, adding relevant team members, printing, importing, exporting, editing, voiding, deleting, etc., see Common business operations
• Business operations combined with collaborative office, including forwarding, scheduling, reminders, making phone calls, sending emails, etc., see Common business for details Action