Most processes worth an app touch several systems: the order in the ERP, the account in the CRM, the history in the lake, the ticket in the service desk.
Every screen reads through a data handler bound to the system that owns the object, so the buyer sees the SAP order as it is at that moment and the seller sees the Salesforce account as it is. The access rules of each system apply when the handler reads: a seller sees their own accounts, a buyer their own purchasing groups. The app adds the process on top: who acts, in which order, with what criteria, within which clocks.
When the flow ends, the write goes to the system that owns the object, through its released interface, and the acknowledgement is stored. The decision is also recorded in the lake beside the history it was made on, so an analyst can ask next quarter how many price changes were approved and against what margin.
Building it takes the same steps as any app: five handlers registered from the catalog, four lanes, four screens drafted from the handlers, five criteria, two clocks. The catalogue estimates 4 to 6 working days for a production-grade version.
Quotes, credit limits, complaints and returns: the customer and the opportunity in Salesforce, the order, the invoice and the credit exposure in the ERP. Customer credit limit change and Quote discount approval are built this way.
Reviews on history: excess stock, supplier scores, budget variance. The decision needs a year of data, read from the lake, and the action goes to the ERP. Excess and obsolete inventory review and Supplier scorecard and corrective action.
Changes and incidents: the equipment in the ERP, the change or the incident in ServiceNow, the maintenance order back in the ERP. Health, safety and environment incident and Change advisory board.
Two divisions, two ERPs, one process: a shortage room or a material creation across SAP and Oracle, with a handler per object per system and one screen showing both. Critical component shortage room.
The screen shows both values with their sources, and a rule can decide which one the process uses, or route the case to a person. The Master Data capabilities of the platform resolve the disagreement at the record level when it is a master-data problem.
Each connector holds its credentials in the vault; each write runs under the acting person's identity where the system supports it, and under the integration user otherwise, with the person's name in the log.
Yes: a Change Data Capture message from Salesforce, a business event from Fusion, a goods receipt in SAP or a row landing in the lake can be the start criterion.
A screen is a filtered query on indexed columns, the same load as a person opening a transaction. History at scale is read from the lake, where it belongs.
Bring one process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.