Page Comparison

...

• Sign up for Free Trial

• Build Salesforce Pipelines
  - Choosing a Salesforce Template 
  - Registering GIT RepoGit Repository
  - Creating a Salesforce Pipeline
  - Creating a Salesforce Task
  -Launching a Salesforce Workflow
  - Supported Actions

• View Unified Insights 

• FAQs

...

1. Go to https://portal.freetrial.opsera.io

2. Click Get Started.
   

   Image RemovedImage Added

3. Click Email Address, and enter your contact information to create a new account.

4. You will receive a confirmation email upon successful registration. 

5. Go to your email and access the attached link to set up okta activation.
   

   Image RemovedImage Added

Upon successful registration, your account will be ready to use. You can login using your credentials.

...

• Choosing a Salesforce Template 

• Registering GIT Git Repository
  - Registering new Git Accounts
  - Using Existing Git Accounts

• Creating a Salesforce Pipeline
  (i) Salesforce Metadata Deploy Basic

(ii) Salesforce Metadata Deploy Unit Testing

(iii) Salesforce Metadata Deploy Advanced

• Creating a Salesforce Task

...

• Task

(ii) Salesforce to Git Merge Sync

Choosing a Salesforce Template

...

Once you have chosen the Salesforce template, the Git repo from which the data needs to be retrieved needs to be registered. You can choose to do one of the Git repo between GitHub and GitLab. Once the repository details are added, they will be stored so you can reuse it for your next pipeline creations. 

...

To register a git repository: 

...

Choose an option between Github and Gitlab.

...

Enter the user credentials to register your account.

...

To use an existing repository, choose the repository from the Account dropdown.

...

following:

• Register a new Git account

• Use an already existing Git account

...

Registering New GitHub and GitLab Accounts

When you are first time user, or want to use a new account for the workflow, then you need to register your existing Git accounts with Opsera. This requires entering the Git Credentials such as Username, Personal Access Token, or SSH Keys. The entered credentials will be stored in Opsera, securely within the vault.

Registering a New GitHub Account

1. In the Create Salesforce Workflow popup, choose Github.

2. Enter your GitHub account Username and Personal Access Token. Personal access tokens are alternatives for using passwords in GitHub authentication. Learn more on how to generate personal access tokens.

3. Alternatively you can login using your SSH Keys. Toggle SSH Keys, and enter the Private Key and Access Key. Learn more on how to generate SSH Keys.

4. Click Next.
   A test connection to verify the account will be auto established.

Registering a New GitLab Account

1. In the Create Salesforce Workflow popup, choose Gitlab.

2. Enter your GitLab account Username and Personal Access Token. Personal access tokens are alternatives for using OAuth2 in Gitlab authentication. Learn more on how to generate Personal Access token.

3. Alternatively you can login using your SSH Keys. Toggle SSH Keys, and enter the Private Key and Access Key. Learn more on Gitlab SSH keys.

4. Click Next.
   A test connection to verify the account will be auto established.

Using Existing GitHub and GitLab Accounts

The Gitlab and GitHub accounts when registered in Opsera using credentials, will be stored under the Accounts dropdown. You can reuse them by choosing the account name.

Selecting an existing GitHub/Gitlab account

1. After choosing the Salesforce template, choose the type of Git account as GitLab or GitHub.

2. Click the Accounts dropdown and choose an existing account.

3. The account credentials will be auto populated in the respective fields.

4. Click Next.
   A test connection to verify the account will be auto established.
   
   The created git accounts will be available for reuse as you create more pipelines. You can view the entire list of accounts by navigating to Workspace tab > Registry.

...

1. In the Source Salesforce Account form, you can either choose to select an existing account or create a new one.

2. To choose an existing account as a source, choose an account from the Account dropdown. To create a new account, enter its details such as Domain URL, Salesforce Login Username, Salesforce Client ID, Salesforce Client Secret, Salesforce User Token and the Password. 
   

   Image RemovedImage Added

3. Click Next. A test connection will be automatically established.

4. Click Launch Task.
   
   Your pipeline is ready to be launched. Refer to the Launch Salesforce Workflows section to view the  step-by-step instructions.

...

1. Choose the pipeline run method as Add New Run Configuration.

2. Click Start New.

3. Under Component Types, select the required components for which the permissions need to be migrated.
   

   Image RemovedImage Added

4. Click Proceed with Selected Components.

5. Select the components you want to migrate. All the metadata components for the selected component type available in the Destination Org will be displayed. Proceed by clicking Proceed with (number) Files.
   

   

6.  Package XML will be generated to start the execution. You can view the count of the components under the Component Counts tab.

7. Click Proceed.

...

1. Choose the pipeline run method as XML/File Upload Process.

2. Click Drop Files here or click to Select file and upload the XML/CSV file from your local machine.
   

   Image RemovedImage Added

3. The Salesforce Pipeline Run: Validation File Viewer Page will be displayed. Here it will validate the components for its availability against the configured Salesforce Orgs and show the available components under Validated Files table and the components which are not available against the Org under the Invalid Files table.

4. Click Proceed with files.

5. Package XML will be generated to start the execution. You can view the count of the components under the Component Counts tab.

6. Click Proceed. The pipeline will begin its execution.

...

• Recent Pipeline Status: Lists details of recently executed pipelines
  

  

  
  The KPI displays a list of every execution that has taken place up to this point, ordered by the most recent pipeline run. Each row/execution displays the pipeline's status, including whether it succeeded or failed. For simple sorting, click on each column's row in the table. Viewing historical results from more than 5 executions is possible with pagination.

• Deployment Frequency: Displays how often code is displayed along with success/failure rates
  

  

  An important metric based on DORA, Deployment Frequency measures the number of times deployment/change has happened for a given period of time. The graph shows the trend in both success and failure deployments.

• Salesforce Components: Displays a comprehensive report on your deployed components
  

  Image RemovedImage Added

The dashboard displays a basic view/statistics on components that have been handled over a given period of time. This also provides total validations and unit tests count, which highlights the anomalies against the number of deployments that have happened.

...