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，审核通过后 看是否有下一节点，没有就审核完成
完善中......
标签：node,name,next,审核,采购,prev,id,crm From： https://www.cnblogs.com/sunlong88/p/17431057.html