First, give conclusions that can be used for decision-making
The focus of judgement is not product names, but business responsibility for processes. Common synergies such as leave, reimbursement, printing, etc. are appropriate for the OA; processes such as orders, contracts, letters, procurement or customer services, which cut across multiple systems, have complex rules and continuous changes in their versions, require BPM or professional business systems. OA can serve as a single entry point, BPM is responsible for process organization, and ERP, CRM and others continue to maintain official business data.
What conditions need to be identified before judgement is made?
The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.
Suggested order of advance
First, we'll be clear about the target and the border.
Three high frequency processes were selected, drawing roles, data and system actions.
Validation Key Dependence
Distinction between coordinated approval, professional operations and cross-system presentation.
Development of assessable outcomes
Compare OA configuration and BPM program with real normal and abnormal samples.
Make sure you decide the next step with the real results.
A closed link to the line before deciding whether to expand the unified process platform.
How do you understand it in the actual business?
The contract approval process is completed in OA, but the customer, offer, refund and electronic signature are from CRM, finance and signature platforms, respectively. At this point, OA is suitable for the delivery of the portal, BPM or integrated services are organized in a responsible state, and the main contract data are still managed by the contract or business system.
The easiest pit to step on.
Make all operations OA forms, create new data islands.
Just to see if the flow chart can be pulled, not verified and back
OA and BPM maintain the same process state separately without primary responsibility
How should we end up receiving and confirming?
Real processes should be used to validate initiation, branching, signing, return, withdrawal, agent, timeout, interface failure and change of authority, and to identify each type of data master, version, log and operator.
When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.