We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Pulling changes from dev sandboxes

Follow

Release Management
Implementation Guide

Index

    Core Setups
  • 1Overview
  • 2Installing Flosum
  • 3Setting up Flosum integration user
  • 4Connecting sandboxes to Flosum
  • 5Setting up users in Flosum
  • 6Setting org permissions
  • 7Decide on naming convention
  • 8Initialize the repository
  • 9Setting up workflow permissions
  • Application Development Flow
  • 10Pulling changes from dev sandboxes
  • 11Branching strategy
  • 12Conflict and Merge strategy
  • 13Static Code Analysis
  • 14Apex
  • 15Regression testing
  • 16Reference Architecture
  • Integrations
  • 17Jira
  • 18TFS/Azure Devops
  • 19Git Integrations
  • Compliance & Governance
  • 20Compliance & Governance

Please use the following criteria to improve the snapshot retrieval:

1. Specifying the component type, as shown in the screenshot below, improves the retrieval speed.

2017-08-01_11-42-03.jpg

 

2. If you know the prefix of the component name, the retrieval will be much faster.

2017-08-01_11-40-43.jpg

 

3. Comma separating component name or component type values allows you to pull all of them in the snapshot. A comma between multiple values in a row acts as an OR condition. 

SSArticle1.png

 

4. By default, Flosum does not pull managed package components into a snapshot. If you want managed package components to be pulled into a snapshot, you have to select the namespace on the snapshot creation screen as shown in the screenshot below. 

SSArticle2.png

 

5. There's no need to create a snapshot from scratch every time. If you would like to create a new snapshot with the same or similar conditions as a previously created snapshot, just open that snapshot and click on the "Recreate Snapshot" button.

SSArticle3.png

 

6. If a snapshot is not pulling in certain components, the reason might be that the OAuth connecting userid does not have access to that component or the component might have a malformed XML due to special characters etc. 

 

 

 

 

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful

Comments