Sometimes it would come handy to be able to not export rows, records or tables from a database, but rather an entity from an application. The logical set of data that makes sense for the application or business rather than raw database data. And have the ability to import it into another instance of the same application, even with different sequence numbers and IDs, but retaining the data relations.
General Key Features:
- Define your schema using xml into storable configurations (i.e. whole TIA schema, limit to product, make parent entity customer or policy)
-
Export limited data sets by named list of parent entities (i.e. list of customers could export all data related to those customers)
- define column as a function value, rather than actual value
- potential for data anonymisation via function calls
-
Import an exported data set into a target environment
- optionally replaces unique keys and identifiers from target environment sequences
- maintains links between records by correctly re-assigning replaced keys
- Not restricted to TIA, but designed with TIA in mind
Key Benefits:
- Extract as-is policy / customer (or list of them) from production environment and import into a UAT / TEST / DEV environment to test new code or fix defects
- Repeatable named imports (create multiple instances of same data with different IDs)
- Data for the whole parent entity stored in a single readable xml file
- Optional parallel export and import for improved performance when moving large data sets between environments
- Create dynamic processes that, for example, vary on the fly based on customer Net Promoter Score.
- Avoid duplicated logic with centrally-managed process components.
- Integrate with and enhance Salesforce standard email templates.
- Build processes for use in Salesforce and via Communities on any device.
Request Demo