B端业务crm 采购 销售审核流配置

B端业务crm 采购 销售审核流配置 方案一：

[
  {
    "id": 10,
    "name": "CRM系统-发票审核一",
    "remark": "CRM系统发票审核流程一: 含不同销售部门仅CEO审核即可",
    "type": 1,
    "create_uid": 1,
    "create_time": "张三",
    "flow_list": [
      {
        "prev_node_id": 29,
        "prev_node_name": "CEO审核",
        "next_node_id": 0,
        "next_node_name": ""
      }
    ]
  },
  {
    "id": 11,
    "name": "CRM系统-发票审核二",
    "remark": "CRM系统发票审核流程二: 同一销售部门仅销售总监审核即可",
    "type": 1,
    "create_uid": 1,
    "create_time": "张三",
    "flow_list": [
      {
        "prev_node_id": 30,
        "prev_node_name": "销售总监审核",
        "next_node_id": 0,
        "next_node_name": ""
      }
    ]
  },
  {
    "id": 12,
    "name": "CRM系统-发票审核三",
    "remark": "CRM系统发票审核流程三: 天眼查验证失败，需销售总监审核后再由总经办审核",
    "type": 1,
    "create_uid": 1,
    "create_time": "张三",
    "flow_list": [
      {
        "prev_node_id": 31,
        "prev_node_name": "销售总监审核",
        "next_node_id": 32,
        "next_node_name": "总经办审核"
      },
      {
        "prev_node_id": 32,
        "prev_node_name": "总经办审核",
        "next_node_id": 33,
        "next_node_name": "CEO审核"
      }
    ]
  }
]

crm审核表，当前审核节点id   curr_audit_uid 存储该业务对应的审核流的 prev_node_id，审核通过后 看是否有下一节点，没有就审核完成

 

方案2：

[
  {
    "flow_node_id": "1",
    "flow_node_name": "销售主管审核"
  },
  {
    "flow_node_id": "2",
    "flow_node_name": "销售经理审核"
  },
  {
    "flow_node_id": "3",
    "flow_node_name": "销售总监审核"
  },
  {
    "flow_node_id": "4",
    "flow_node_name": "采购员审核"
  },
  {
    "flow_node_id": "5",
    "flow_node_name": "采购经理审核"
  },
  {
    "flow_node_id": "6",
    "flow_node_name": "采购总监审核"
  },
  {
    "flow_node_id": "7",
    "flow_node_name": "总经办审核"
  },
  {
    "flow_node_id": "8",
    "flow_node_name": "COO审核"
  },
  {
    "flow_node_id": "9",
    "flow_node_name": "CEO审核"
  }
]


[
  {
    "id": 10,
    "name": "CRM系统-发票审核一",
    "remark": "CRM系统发票审核流程一: 含不同销售部门仅CEO审核即可",
    "type": 1,
    "create_uid": 1,
    "create_time": "张三",
    "flow_list_tags": "2"
  },
  {
    "id": 11,
    "name": "CRM系统-发票审核二",
    "remark": "CRM系统发票审核流程二: 同一销售部门仅销售总监审核即可",
    "type": 1,
    "create_uid": 1,
    "create_time": "张三",
    "flow_list_tags": "3"
  },
  {
    "id": 12,
    "name": "CRM系统-发票审核三",
    "remark": "CRM系统发票审核流程三: 天眼查验证失败，需销售总监审核后再由总经办审核",
    "type": 1,
    "create_uid": 1,
    "create_time": "张三",
    "flow_list_tags": "2_3_7"
  }
]

flow_list_tags 标识审核的节点数  2_3_7表示需要经过审核节点2，3,7三个审核，分别是销售经理审核，销售总监审核，总经办审核

数据库审核业务中current_node可以存储2表示 待销售经理审核，存储3表示 待销售总监审核，存储7表示 待总经办审核。

至于每个业务是经过具体哪个审核流可以手动配置，比如发票审核配置审核流固定为12 三级审核