General Discussion

Tech Talks: Support – Important Update on App-to-App Calls and TrueContext Rebranding

  • 1.  Tech Talks: Support – Important Update on App-to-App Calls and TrueContext Rebranding

    Posted 30 days ago
    Edited by Pat Cooney 30 days ago

    In November 2023, TrueContext completed its rebranding from ProntoForms. One common question our Support team receives concerns App-to-App calls and whether the URL for configuring these external applications, such as Salesforce, ServiceNow, and ServiceMax, has changed with this rebrand.

    Impact of Rebranding on App-to-App Integrations

    Our Engineering Team has added the URL schemes truecontext:// and tcxt:// for App-to-App integrations. Previously, the URL parameters required prontoforms:// or the alternative https://prontofor.ms, which are still supported for existing integrations.

    Going forward, all new App-to-App integrations should use truecontext:// or tcxt://. This update aligns with the rebranding from ProntoForms to TrueContext while continuing to support existing integrations with all supported external systems.

    Note: To maintain existing integrations, TrueContext will continue to support prontoforms:// and the alternative https://prontofor.ms/.

    What are App-to-App Calls?

    App-to-App calls, or "deep links", allow seamless communication between the TrueContext app and another app on the device. App-to-App communication includes incoming requests ("calls") to the TrueContext app and, for those on the Advanced or Enterprise tiers, outbound "callbacks" to an allowed domain or app.

    The TrueContext app can receive data and instructions from another app on the same device. An inbound App-to-App request can direct the TrueContext Mobile App to launch in the foreground and complete an action or even populate and send data in a form without that form ever opening. You can learn how the inbound App-to-App calls work here: https://docs.truecontext.com/1374411/Content/Features/h3AppToAppForCentral/Introduction/HowAppToAppWorks.htm

    The TrueContext app can also send information to another app or URL (if you are on the Advanced or Enterprise tiers) through x-callback parameters. You can find a complete guide on App-to-App x-callback parameters here: https://docs.truecontext.com/1374411/Content/Features/h3AppToAppForCentral/AppToAppTechnicalDetails/AppToAppXCallbackParams.htm.

    These callback parameters have not been affected by the rebranding.

    How to Configure App-to-App Communications?

    You can find all the information needed to configure App-to-App Communication in our documentation: https://docs.truecontext.com/1374411/Content/Features/h3AppToAppForCentral/LandingPages/AppToAppLandingPageH1.htm.

    Remember that while existing integrations using prontoforms:// and https://prontofor.ms/ are still supported, new connections should use truecontext:// or tcxt://

    You can also set up custom App-to-App callbacks, based on your specific business requirements, using our proprietary Data Reference Expression Language (DREL). For more details on custom App-to-App callback setup, visit: https://docs.truecontext.com/1374411/Content/Features/h3AppToAppForCentral/CustomCallbackParameters/AppToAppCustom_Configure.htm.

    If you encounter any error codes when setting up new App-to-App integrations, you can look them up here: https://docs.truecontext.com/1374411/Content/Features/h3AppToAppForCentral/AppToAppTechnicalDetails/AppToAppErrorCodes.htm.

    If you experience any technical difficulties while using the App-to-App actions, please submit a support ticket using the process outlined here: https://support.truecontext.com/hc/en-us/articles/4406631384340-How-To-Contact-Technical-Support. Our team will be happy to assist you.



    ------------------------------
    Aditya Trivedi
    Technical Analyst
    TrueContext
    Ottawa
    ------------------------------



Reminder: Content posted to our Community is public content.  Please be careful not to post Intellectual Property that you do not have permission to share.  For more information please refer to our Terms Of Use