Creating Connections is a legacy function that is only necessary for using Deployment Center. As of January 2022 Deployment Center is officially deprecated and will be removed from service on January 15, 2023. Prodly strongly recommends transitioning to Guided Deployment before the deadline.
For the Prodly AppOps service to retrieve data from and deploy data to your Salesforce orgs, you must establish connections between the Prodly AppOps service and the orgs responsible for deployment control, schema, data sources, and data destinations. Depending on your use case, an org can serve multiple purposes.
An org connection consists of:
- An optional connection name.
- An org ID.
- Access and refresh tokens (for authorized access) or certificate details (for preauthorized access).
- A flag indicating whether or not the connected org is your control org.
Prodly recommends that admins with a full system administrator profile create your connections to avoid permission and access issues. AppOps Release initially sets the owner of new connections to the owner of your control org connection. You will want to ensure that the Contol Org Connection Owner has proper access to the objects you are trying to deploy as well as Prodly Admin permission set. For destination orgs they will need to have write access for all of the objects and have read access for all of the objects for data source orgs.
To establish a connection between the Prodly AppOps service and your control org:
- Click the Connections tab.
- Click New. If you have not previously established a connection to your control org, you’ll be automatically prompted to do so.
- Optionally, in the connection name box, enter a connection name. Prodly recommends entering Control Org.
- Optionally, select a Folder Name to better organize your Prodly object data in folders.
- Click Create.
- Notice the checkmark for Control Org, indicating that this connection connects the Prodly AppOps service to the control org.
To establish a connection between the Prodly AppOps service and a Salesforce org you are authorized to access:
- Click the Connections tab.
- Click New.
- Enter a unique Connection Name.
- Optionally, select a Folder Name to assign the connection to a folder to better organize your Prodly object data.
- Select a Connection Type. Your options are:
- Authorized Access – Instructs the Prodly AppOps service to authenticate connections using the refresh token OAuth flow.
- Preauthorized Access – Instructs the Prodly AppOps service to authenticate using the JSON web token (JWT) OAuth flow. Using preauthorized access requires first installing and configuring the Prodly AppOps Deployment connected app.
- Continue with these next steps for your selected connection type:Steps for Authorized AccessSteps for Preauthorized Access
- Select Allow
- Any error you might encounter during connection creation is likely due to a conflict with an existing Salesforce.com session open in your browser. Log out of all existing Salesforce.com sessions, clear your browser cache or use a private/incognito mode window, log back into your control org, and try establishing the connection again.
- Click the Connections tab to see your newly-added connection in the list of connections.
AppOps Release sets the owner of your new connection to the owner of your control org connection. If you need to change it, use the standard Salesforce edit to adjust the field value.
Using the JWT OAuth flow solves the issue of having to recreate source org and destination org connections after a sandbox refresh and/or when using Salesforce DX, but you cannot use them for schema org connections.