Deploying Using Connected App / External Client App Authentication

Deployment helps to migrate objects (kanban, forms, actions) with their dependencies between organizations.

This method of deployment uses a Salesforce Connected App authentication mechanism. Connected App authentication is a secure connection and authentication mechanism between Salesforce and external applications. In this case, it will be used to connect one Salesforce org with another. Using a Connected App doesn’t require you to store target Salesforce org passwords in a Salesforce Source Org, which improves security.

Here is how it works:

  1. The Flexi Kanban Deployment tool provides a way to configure a list of target organizations via Connected Apps configurations. You can add a configuration for a Connected App in the first screen of the deployment wizard tool.

  2. When users configure a list of target organizations, the following info must be provided: Organization Name, Domain URL, Client Key, and Client Secret.

  3. Client Key and Client Secret should be obtained once from the target organization via Flexi Kanban Connect application (ask the target Salesforce org admin for assistance).

  4. Once added, the desired organization may be selected from the appropriate picklist as the target for deployment.

Deployment Procedure:

  • Select the desired Kanbans, Forms, Actions, or Action Groups from their respective pages and click "Deploy" button.

Drawing

  • The Deployment Wizard will be shown. Select the Target Organization and click the "Next" button.

Note: The Target Organization configuration must already have been configured according to the instructions provided later in this article.

Drawing

  • Check the items to be deployed. Select the desired necessary Action and click the "Deploy" button.

Drawing

  • The progress of the deployment will be indicated:

Drawing

  • After the deployment procedure has completed, a confirmation message will be displayed:

Deployment is now complete. Target organization will now contain all of the deployed objects according to their folder structure.

Deployment Actions

Object Does Not Exist in Target Organization

If the object (kanban, form, action, action group) does not exist in the target organization, only the "Create" action will be available.

After deployment is complete, the new object is added to the target organization along with other referenced objects.

Object Exists in Target Organization

If an object already exists in the target organization, the Deployment Wizard will allow the user to choose between the "Create" and "Overwrite" actions. Overwrite is suggested by default.

If select "Create" instead of "Overwrite", a new object will be created, even if some object with the same name already exists.

Last updated