The Approval Request / Response messages facilitate a two-way, real-time integration. That allows Unimarket to retrieve approver information directly from an external ERP or Finance system, as a requisition progresses.
How it Works
When a requisition is created and routed for approval, Unimarket triggers an integration request to the external system to identify the next required approver. This process repeats at each step of the workflow, until all necessary approvals are secured.
Use Cases
This integration is an ideal alternative to the standard Approval Configuration Request (loading master data) in the following scenarios:
Dynamic Rules: The organization has highly complex approval logic in their ERP that would be difficult or inefficient to replicate within Unimarket.
Single Source of Truth: The customer prefers to keep all approval data and hierarchy maintenance exclusively, within their external Finance system.
Reduced Maintenance: It removes the need to perform regular bulk uploads of approval groups, chains, and rulesets into Unimarket.
Comparison of Approval Methods
| Feature | Master Data Upload (File Automation) | Approval Request Integration |
|---|---|---|
| Data Location | Loaded into Unimarket | Stays in ERP/Finance system |
| Processing | Rules evaluated by Unimarket | Rules evaluated by external system |
| Speed | Instant evaluation within the app | Dependent on external system response time |
| Complexity | Best for standard hierarchies | Best for complex, dynamic logic |
Technical Requirements
Communication: This is an active, real-time integration point requiring a stable connection via the Workato On-Premise Agent or Unimarket Connector.
Response: The external system must respond with a valid approver identity, that exists within the Unimarket community.