App-to-App Communication
SFM Custom Action of type App-to-App enables customers to export (send) and import (receive) work order data and its detail lines, to and from the third-party app. For example, technician needs to process a payment via the customer's credit card for the work being performed. To accomplish this, technician launches the third-party app from within FSA. The third-party app is capable of capturing credit card information, processing the payment, and returning back to FSA.
To authenticate the export and import of work order data, a unique authorization key is generated and is valid for 24 hours. The export and import of data should take place within 24 hours before the authorization key expires. FSA session should be in active state during this period. When import of data is initiated and the authorization key expires, then an error message is displayed. For more information on App-to-App configuration, refer
App-to-App Configuration.Key Points to Remember
• Supported only on FSA for iPad.
• Supported for all objects.
• Supported only for Standalone Edit SFM process.
• Third-party app should be installed on the device.
• FSA always initiates exporting data to third-party app and only then importing data from third-party app to FSA is possible. The reverse is not possible, as the unique authorization key is generated from FSA.
• Entry Criteria, Data Validation Rules, Formulas, Advanced options configured on the SFM Edit process is respected.
• While configuring SFM Custom Action of type App-to-App, ensure mandatory fields Scheme Name and Path are defined accurately. Ensure the Include Object Data check box is selected.
• To download the custom action of type App-to-App, you need to perform a Config Sync.