Sapho’s patent-pending Extract, Transform, Notify (ETN) technology integrates with each source system to process the “active” data. “Active” data differs from system to system: the active data in an ERP system is typically open Purchase Orders, while the active data from a CRM system is typically new leads or changed opportunities.
Sapho uses native and web service APIs to connect directly to each source system and offers flexible write backs to match your compliance requirements.
Sapho uses each target system’s API to transform its data into a format that enables Sapho to easily monitor for changes – or events – that occur. Sapho then stores a local copy of only the active data in its SQL 92 Server. The Sapho Administrator can specify exactly what data to monitor and can set a refresh interval for each system. Upon refresh, Sapho detects changes to the underlying data and notifies users on their preferred channel that there is a relevant event for their attention.
Since all active data from a source system is stored in the SQL 92 database of your choice, it can be fully secured like your other internal data stores. This data should be considered a cache that is automatically refreshed as needed and not another version of the “truth” that must be maintained.
Sapho can easily combine data from multiple data sources. The Sapho ETN process transforms data to ensure that data elements, such as customer IDs and employee user names, are easily available. This data can then be used to directly join data across systems, or through a join table that links identifiers across systems.
Once the active data from different systems are in one place, it is easy to include often overlooked but critical data into workflows, such as adding recent incidents from your customer service system about a contract renewal opportunity to a workflow notification for a sales person.
When a user performs a write back action, such as approving a Purchase Order, Sapho uses an admin account to the target system to perform the write back.
Sapho can write directly back to source applications using native APIs. Database write backs are performed with JDBC. Application write backs can be performed in two ways: with delegated authentication or with direct user login. With delegated authentication, Sapho uses the application's API with a master account to perform the write action, along with an audit trail of the user logged into Sapho. With direct user login, Sapho deep links directly to the source application, where the user can be auto-logged on with their SSO and can complete an action.
Sapho maintains an audit table of all write backs in the SQL 92 database.
Explore a demo portal to see the benefits of a digital experience platform for employees (DXPe)!Try now