Opsera Free Trial
Opsera’s free trial is intended for anyone who is responsible for designing and developing Salesforce deployment for their Organization. The roles can include architects, developers, DevOps engineers, etc.
Objectives:
Understand the gaps and pitfalls in your existing DevOps process
Get a hands-on experience on Salesforce pipelines
Explore benefits of DevOps insights
Explore advantages of DevOps orchestrations
Get an overview of Opsera’s functionality with minimal efforts
The different sections below give you a step-by-step guidance of the features we offer in free trial.
Overview:
Sign up for Free Trial
Build Salesforce Pipelines
- Choosing a Salesforce Template
- Registering Git Repository
- Creating a Salesforce Pipeline
- Creating a Salesforce Task
-Launching a Salesforce Workflow
- Supported ActionsView Unified Insights
FAQs
Sign Up for Free Trial
You can sign up for the free trial by registering with your email address.
To sign up for the free trial:
Click Get Started.
Click Email Address, and enter your contact information to create a new account.
You will receive a confirmation email upon successful registration.
Go to your email and access the attached link to set up okta activation.
Upon successful registration, your account will be ready to use. You can login using your credentials.
Build Salesforce Pipeline
After successfully logging into your account, you will land on your Home page. The home page displays information of pipeline creations, pipeline status, and a few useful links to help you get started with Opsera. In addition, you can easily build your first Salesforce pipeline from here.
The steps involved in creating a Salesforce Workflow are:
Choosing a Salesforce Template
Registering Git Repository
- Registering new Git Accounts
- Using Existing Git AccountsCreating a Salesforce Pipeline
Creating a Salesforce Task
Choosing a Salesforce Template
To choose a Salesforce Template:
Login to Opsera’s free trial.
In the Home tab, click Get started on the Salesforce tab.
In the Select Salesforce Workflow Option, choose Get Started Here to create a salesforce workflow you wish to create.
Choose a template based on your requirement.
We offer a total of 5 templates involving 3 pipelines and two tasks, ranging from basic to advanced. Our out-of-the-box templates enable you to build pipelines with custom unit testing and code coverage for managed and custom objects. You can click Launch an existing workflow, to instantly trigger an existing pipeline that’s created in Opsera.
Points to remember:
You must obtain the Client ID and Client Secret to configure the Salesforce workflow in Opsera. For this, you must have set up a connected app in your Salesforce org. Learn more about how to create a connected app
In a few Salesforce workflow scenarios, providing the Salesforce User Token will be mandatory. For this, you need to retrieve the security token from your Salesforce org. Learn more about retrieving security token
Registering Git Repository
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 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
In the Create Salesforce Workflow popup, choose Github.
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.
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.
Click Next.
A test connection to verify the account will be auto established.
Registering a New GitLab Account
In the Create Salesforce Workflow popup, choose Gitlab.
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.
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.
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
After choosing the Salesforce template, choose the type of Git account as GitLab or GitHub.
Click the Accounts dropdown and choose an existing account.
The account credentials will be auto populated in the respective fields.
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.
Note:
Ensure to provide read permissions such as read_api, read_user, read_repository, read_registry for access token when using GitLab. For GitHub, ensure to provide repo and project permissions for access tokens.
Creating a Salesforce Pipeline
Info: Refer this section if your chosen template is for a Pipeline workflow.
Once the connection is successfully established for the Git repository, you can start building your pipeline workflow by specifying the source and destination Salesforce accounts.
To create a Salesforce Pipeline workflow:
In the Source Salesforce Account form, you can either choose to select an existing account or create a new one.
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. A test connection will be automatically established.
In the Destination Salesforce Account form, you can either choose to select an existing account or create a new one.To choose an existing account as the destination, 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.
Click Next. A test connection will be automatically established.
Click Launch Pipeline.
Once done, your pipeline is ready to be launched. Refer to the Launch Salesforce Workflows section to view the step-by-step instructions.
Creating a Salesforce Task
Info: Refer this section if your chosen template is for a task workflow
To create a Salesforce task:
In the Source Salesforce Account form, you can either choose to select an existing account or create a new one.
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.
Click Next. A test connection will be automatically established.
Click Launch Task.
Your pipeline is ready to be launched. Refer to the Launch Salesforce Workflows section to view the step-by-step instructions.
Launch Salesforce Workflows
Once you click Launch Pipeline/Launch Tasks in your workflow, you can initialize the execution by choosing the Repository and the Target Branch, and clicking Confirm Repository Settings.
Once done, you can trigger Pipelines for execution by launching the Pipelines using one of the following methods:
Run Configuration: This process involves a manual selection of the components to be migrated
XML/File Upload Process: This process involves the component selection by uploading the XML/CSV files
Launch using Run Configuration
Choose the pipeline run method as Add New Run Configuration.
Click Start New.
Under Component Types, select the required components for which the permissions need to be migrated.
Click Proceed with Selected Components.
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.
Package XML will be generated to start the execution. You can view the count of the components under the Component Counts tab.
Click Proceed.
The pipeline will begin its execution. A confirmation text A request to start this pipeline from the start has been submitted. Resetting pipeline status and then the pipeline will begin momentarily will be displayed.
Launch using XML/File Upload
Choose the pipeline run method as XML/File Upload Process.
Click Drop Files here or click to Select file and upload the XML/CSV file from your local machine.
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.
Click Proceed with files.
Package XML will be generated to start the execution. You can view the count of the components under the Component Counts tab.
Click Proceed. The pipeline will begin its execution.
The launched pipelines will be listed in the Home view. In addition, you can view them under the Workspace tab.
Supported Actions
In addition to creating and launching pipelines, here is a list of actions you can perform on them. For this, navigate to Workspace > Pipeline and click on the required pipeline name.
Note: You can only view and not edit the workflows steps of your pipeline under the Workflow tab in a Pipeline.
(i) View Pipeline Details and Logs
A Pipeline’s summary will provide the following details.
Basic details such as ID, DATE, etc
Pipeline logs displaying the execution details of each step and the step action
To view Pipeline Logs:
Open a Pipeline, and click the Summary tab.
Under Pipeline Logs, you can view the status of each pipeline action.
Click Console Output in the Action column, to view its console logs.
(ii) Rerun Pipelines
You can rerun any completed Salesforce pipeline, any number of times.
To rerun a Pipeline:
Open a Pipeline and click start pipeline.
Follow the Launch Salesforce Workflows section for further steps.
(iii) View Tasks details
If you have created any Salesforce tasks, the information is available to view under Workspace > Tasks.
View Unified Insights
Insights can be absolutely powerful for your business decisions, and as for deployment processes the insights can be helpful to know what’s going on in the delivery pipeline.
To view insight dashboards:
Login to Opsera, and click the Unified Insights tab.
A dashboard with a list of KPIs will be displayed.
The supported KPIs that provide insights are as follows:
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
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.
Duration by Stage: Displays the execution details of various steps of a Pipeline deployment
The dashboard measures the average time taken to execute each stage in a pipeline. The run value indicates the total number of times the step in a pipeline has been executed. The trend graph shows the trend in duration over a given period of time. Hover over a data point in the graph to view the average time taken, and executions for a single data point (day/week/month).
FAQS
How many days is the Opsera’s free trial?
The time period of the free trial is 15 days.Will I lose any of the work in my free trial when I choose a paid plan?
Any workflows developed as a part of the free trial will not be transferred to your paid plan account. This is because we tailored this free trial environment to be incredibly user friendly for you to get started with Opsera, and it differs from the paid plan’s environment.Can I rollback deployment changes?
Yes, you may quickly undo modifications on an opsera pipeline that has the old metadata from before deployment by utilizing the Backup step. Use our out-of-the-box template “Organization Sync Advanced” which has this backup step predefined.Can I create a custom pipeline template for my organization?
Yes, you can create pipelines from scratch based on your requirements using our Opsera’s paid plan version. It allows you to customize the steps as per your deployment needs. However, with the free trial, we offer five out-of-the-box templates for different Salesforce demands.Where can I view my Pipeline’s workflow details?
Once you have created your pipeline, you can view the step-by-step workflow by opening the Pipeline under Workspace > Pipelines.Is there a way to create new dashboards for Pipeline insights?
You can create new dashboards in Opsera, but not during the free trial. However, the Unified Insights tab gives you an understanding of the insights offered by Opsera.