Download Copado Admin: A Comprehensive Guide to Salesforce DevOps and more Exams Biology in PDF only on Docsity!
Copado Admin -
General with
complete
verified
solutions (latest
update already
passed)
DevOps - answer Combination of practices that automate and enable greater effectiveness in the process of building and running software. It combines the technical practices of Continuous Delivery with the business practices of lean management and lean product development. Change Set Limitations (4) - answer 1. Cannot search components by name or type
- Not all components are available
- All components in one list
- Does not enable continuous delivery
Sandbox Refresh Problems (4) - answer Metadata Loss Scrambled Emails Data Loss Full Sandboxes can only be refreshed once a month Metadata Loss - answer When all the work in progress in a sandbox will be overwritten after the refresh Scrambled Emails - answer Whenever a sandbox is refreshed, user email addresses are modified in the sandbox so that production users don't receive automatically generated email messages from the sandbox Data Loss - answer Unless you're refreshing a full sandbox or partial copy, all the data will be lost and you will need to recreate it for testing purposes Salesforce DevOps Challenges - answer 1. Change Set Limitations
- Difficult to keep environments in Sync
- Lack of History Tracking
- Difficulty for teams to collaborate
- No standard tool or process for managing salesforce changes
- Limited set of quality checks on Changes
- Lack of monitoring and compliance
- Migrating data from multiple objects is tedious
- Difficult to identify and unblock bottlenecks
- Insufficient Quality and Frequency of Releases
- No holistic view Copado - answer A scalable Salesforce-native application that can be downloaded and installed in an Org and provides a complete system to plan, track and carry out DevOps activities and add value in every stage of the Salesforce DevOps process
Copado Permissioner Work Manager - answer Agile tool Intended to streamline agile development at every phase of the project Sprint Wall - answer Agile tool to manage sprints in agile way. View provides useful information about the status of the sprint and a whole picture of its content Agile Dashboards - answer Out-of-the-box dashboards to better monitor the work of your team Copado Permissioner - answer Agile tool that allows you to have more granular control over permission set assignments to users Quality Assurance Tools (3) - answer Static Code Analysis Selenium Validation Deployments Static Code Analysis - answer Type of quality check that analyzes code to find inefficiencies and detect common errors in the code -Code scans can be performed on-demand or automated to be run at a scheduled time -The analysis can inspect all the code of a certain environment or only the content added to a user story -Code review findings are stored as records Selenium - answer Analysis tool that executes automated regression tests. Comes with Selenium step recorder extension called Copado Recorder Validation Deployments - answer Ensure that the validation deployment is made out of the merged components thus avoiding unpleasant surprises. Can be used for individual story or entire releases.
Copado Recorder - answer Translates simple point-and-click activity into effective UI tests without requiring your team to know Selenium or write lines of code Compliance Hub - answer Monitoring and compliance tool that scans all the metadata changes made in your environments in order to spot and identify security breaches -can choose which metadata types you want to be monitored and enforce compliance rules according to your business needs -can set a severity for each rule based on how critical the rule is for your company Copado Continuous Delivery - answer Continuous Delivery tool that enables scheduling of promotions and back promotions and automate quality gates Non-Metadata Component Types (that Copado can Deploy) (6) - answer Manual Pre/Post Deployment Tasks Relational Data Velocity Configurations Custom Setting Values Apex Anonymous Scripts Users Copado Data Deploy - answer Tool to create point-and-click data templates with no technical knowledge in order to build relational queries 360 Vision Tools (3) - answer DevOps 360 Value Stream Maps DevOps Analytics DevOps 360 - answer Tool that accurately measure the performance of your Salesforce implementation
Release - answer lets you group user stories to promote them together and also keep track of the version of changes that your Salesforce application experiences after every deployment -Creating a release is not required when working in Copado, but it will help you organize your versions and track the progress of the app -The release must be linked to a project Commit Changes Button - answer Button on user story used to access Git Client When committing changes in a user story, the changes are committed into a new user story feature branch Commit Process - answer 1. Click 'Commit Changes' button on User Story Record
- Copado commits changes to new US feature branch -naming convention: feature/US- -feature branch (default) is created out of branch specified in the Main Branch field of the pipeline record -Copado verifies if changes exist in metadata/ if feature branch exists Commit Flow: Branch Exists, Metadata Different - answer New Version of metadata is added to the existing feature branch Commit Flow: Branch New, Metadata Different - answer 1. New Commit record created with commit ID and added to user story
- Feature branch pushed to repository, committing the changes and merging the feature branch with the org branch Commit Flow: Branch Exists, Metadata Same - answer Git won't generate a commit Id and Copado will create a commit record with the status, 'No changes' Commit Flow: Branch New, Metadata Same - answer 1. Feature branch is NOT pushed to repository
- Commit record created with the status, 'No changes' Metadata Types in Selection field - answer a multi-picklist that summarizes the metadata types of the components that were committed Commit Changes Page NOTE - answer When committing changes, the correct Org Credential must be used. Environment where changes were performed must correspond with the credential used. Commit Changes Page: Relevant Fields (3) - answer 1. Git Snapshot Name (Git SS tied too the Org credential used to retrieve the metadata from the source environment)
- Commit Message (editable but pre-populated with US number and title)
- Git Operation (type of Git operation according t the changes that need to be linked to the user story) Git Operation Types (4) - answer 1. Commit Files → Standard commit, used to link changes (e.g. create or update a field)
- Recommit → Commit again previously committed components
- Destructive Changes → Commit deletions, used to deploy a deletion (e.g. deleting a field)
- Full Profiles and Permission Sets → Used when committing Full Profiles or Permission Sets including all level security Git Operation Restriction custom setting - answer Used to restrict users and profiles to access only certain Git operations (user restriction checked first, then profile, then organization) Commit Changes Page: Metadata Grid - answer Select Metadata Section → select the metadata you want to commit to the feature branch -Copado keeps a metadata index of each Salesforce Org Maximize Icon → increases number of rows displayed
Commit Changes Page: Filters - answer 1. Can change the filtering method and drill down data on the following fields -Name -Created By -Last Modified By
- Can specify specific date and drill down data on the following fields -Last Modified Date -Created Date Where can Git Commits be reviewed? - answer 1. User Story Commits related list
- User story Selections Section
- Git Repository Commit Statuses (3) - answer Complete → changes were successfully committed to the User Story feature branch and associated with the User Story No Changes → When committing the selected components, Copado detected that the version of the components in the source org was identical to the version in Git, therefore, changes were not associated with the User Story Failed → Indicates that an error occurred while performing the commit (e.g branch name misspelled). ---Copado will always send you an email with the specific error to help you troubleshoot the issue View in Git - answer Link field on user story that opens feature branch in Git Latest Commit Date - answer Date under user story selections grid that shows when the latest commit was executed for the user story
Promotion - answer container used to deploy one or multiple user stories following a specific pipeline Promotion Branch - answer a copy of the destination environment branch where all the related user stories feature branches are merged -naming convention: promotion/{promotion.name-deployment.name} Why is a promotion branch created from the destination branch? - answer to keep the existing changes in the destination while adding new contributions of developers to it User Story Merge order - answer based on the User Story Reference field in ascending order yet you can override this behavior and define a custom merge order Promotion NOTE - answer When user stories are promoted, Copado will locate the destination environment based on the pipeline configured in the project or the release's record Promotion Page: Relevant Fields (7) - answer Release → Release linked to the user story Project → Project that will designate the Pipeline to which the user story belongs Source Environment & Source Credentials → The credentials of the Source Environment that should be used when creating a deployment Destination Environment & Destination Credentials → will be auto- populated based on the pipeline related to the project/project's release and the available credentials owned by the running user Order User Stories By → Lets you override the default User Story Reference ordering to a different user story field with asc or desc ordering -This field is also present in Pipeline
- Promotion Record Update (copado)
- User Story Environment Update (copado) Promotion Flow: Manual Promotion (12) - answer 1. Flag stories to promote (user)
- Create promotion record (user)
- Promotion Definition (user)
- Deployment record creation (user)
- Deployment step creation (copado)
- Promotion Branch reaction (copado)
- Merge feature branch into promotion branch (copado)
- Start Deployment (user)
- SFDC Deployment Execution (copado)
- Target Branch Update (copado)
- Promotion Record Update (copado)
- User Story Environment Update (copado) Promotion Flow Step: Promotion Definition - answer -Selection of the Project linked to the pipeline that will automatically set the destination environment. -Selection of the Source Environment holding the user stories ready to be promoted. -Selection of the user stories to deploy. Promotion Flow Step: Deployment Record Creation - answer Creation of a deployment record along with its corresponding deployment steps. The deployment steps are the steps that are executed during the deployment of the changes to the destination Org. Promotion Flow Step: Creation of a Promotion Branch - answer The creation of a promotion branch out of the destination environment guarantees that existing changes in the destination environment are not accidentally overwritten by peers.
Promotion Flow Step: Merge of the User Stories Feature Branches into the Promotion Branch - answer By merging the changes of the user stories into the promotion branch, to ensure that existing changes and new changes can integrate properly into the destination environment. Promotion Flow Step: Execution of the Deployment Steps - answer Creation of a Job that reads metadata changes on the promotion branch and deploys them to the destination salesforce environment. Promotion Flow Step: Merge of the Promotion Branch into the Destination Branch - answer This secures that metadata changes deployed to the destination environment are reflected as well in the destination branch. Promotion Flow Step: Final Records Update - answer -Promotion and deployment records status are updated to Completed. -Since the user stories are now sitting on a new environment, the Source Environment field of each user story is updated. Initiating a Promotion (2) - answer Promote and Deploy → migrate user stories separately from one environment to another -Promote and Deploy Checkbox on user story record -FOR SINGLE USER STORY Ready to Promote → mark user stories as ready to promote to group them together in one promotion -FOR MULTIPLE USER STORIES Creating a Promotion (6) - answer 1. Check the required user stories as Ready to Promote
- Open the Promotion tab and press New, fill in all the fields marked as required and save
- Navigate to the add user stories tab and select the user stories
- Click 'Add Selected User stories' button
-No changes are merged towards the destination branch Deployments: Validate a User Story - answer 1. Click 'Validate Changes' from US record
- Intermediary page opens and displays progress
- Copado creates Promotion and Deployment records in Salesforce and a Promotion branch in Git
- Once complete, user is redirected to user story
- Navigate to Validation Deployment Results sectin on US to navigate to latest promotion and deployment records Deployments: Validate Multiple User Stories - answer 1. Click on Create Deployment from a promotion record
- Click submit - Copado creates deployment record in SF and a promotion branch in Git
- Navigate to the deployment record from the promotion related list
- Execute the deployment Successful deployment actions (4) - answer 1. The promotion branch will be merged into the destination branch.
- The deployment and promotion status will be set to Completed Successfully and Completed respectively.
- All the user stories included in the promotion will be moved to the next environment in the pipeline.
- The previous org credential will be replaced by the org credential of the following environment. What is the outcome of a promotion with errors? - answer -No changes will be pushed to the destination branch in Git. -The deployment status will be set to Completed with Errors. -The user stories included in the deployment will remain in the same environment.
Steps to review promotion errors (3) - answer 1. Open promotion record from the related User Story
- Navigate to the deployment record
- Click on the red flag icon in the deployment step - results tab will open where all deployment results are listed Failed deployment: Next Steps - answer 1. Troubleshoot errors and recommit changes to same user story
- Click 'Create Deployment' button on promotion record (new promotion branch will be created) (same steps for failed validation deployment) Successful Validation Deployment: Next Steps - answer 1. Open deployment record and locate the Git Promotion Step
- Open the Git Promotion Step and uncheck the CheckOnly checkbox (and save)
- Click on Deploy, and then Deploy all to start the deployment job Version Control - answer Tracks changes over time in a file or a set of files that are stored in a specific location, known as repository. Every modification in a file is recorded along with information about who made the change and the reason behind it. Version Control: Benefits (4) - answer 1. Backup --> multiple versions exist so one can easily roll back changes
- History--> helps troubleshoot bugs and compare changes over time
- Better understanding --> required notes with description
- Better collaboration --> branch based structure allows for independent work-streams that can all be merged together Version Control: Core Elements (5) - answer Files Git Commit Git Branch
Version Control Concepts: Feature Branch - answer Isolated branch with User Story changes Version Control Concepts: Promotion Branch - answer Isolated branch that is created from the destination branch. An intermediate branch that drives deployment to next/prior org in the flow. Version Control Concepts: Org Branch - answer Branch linked to the environment where you have applied the changes -each SF environment is tied to a branch in the repository Version Control Concepts: Destination Branch - answer Branch linked to the org where changes will be deployed Promotion Process - answer 1. Commit user story - feature branch will be created from the main branch in the pipeline (usually master)
- Copado merges feature branch into the Org Branch where the changes were made
- Create pull request from US t compare changes against the destination branch
- When story is promoted, a promotion branch is created out of the destination branch
- Feature branch is merged with promotion branch -if multiple user stories were included in promotion, the feature branches will be merged sequentially into the promotion branch
- Execute Deployment - promotion branch will merge with destination branch Copado Branching Strategy: Benefits (3) - answer Isolated Individual work → Isolating the Promotion and Feature branches gives more flexibility
Time Saving → Copado eliminates manual work; automating the creation of the Feature and Promotion branches as well as the merge between these branches, the merge of the Feature branch into the Source branch and the merge of the Promotion branch into the Destination branch. Traceability → Copado follows a naming convention for the branches it creates so that they can be easily located in the repository Component Specifications: Profiles - answer When committing a profile without specifying any other components, only active system permissions will be retrieved. This is the standard Metadata API behavior and applies to new or existing Profiles. Component Specifications: Permission Sets - answer When committing a Permission Set, Copado carries over only active system permissions, unless other components are selected. Deploying Profiles/ Permission Sets: Considerations (3) - answer 1. Both profile/PS and component need to be included in the same Commit to update access levels on that component
- If the related component does not exist in the destination environment, both the profile/permission set and the component should be marked as Selected
- To update permissions in Prof/PS without migrating any work in progress from related component, mark the Retrieve Only checkbox for that component To retrieve all the dependencies in a single commit use the 'Full Profiles & Permission Sets' git operation Retrieve Only - answer Option that allows permissions to be updated without committing or deploying the related component
