This Flosum User Guide will walk you through the features of Flosum, focusing on the core modules and their function in the overall system.
This Guide builds on information found in the Getting Started with Flosum - Trial Guide and the Flosum Implementation Guide and assumes you have a functioning Flosum org installation. If you have not yet read those Guides, or do not have a functioning Flosum installation, please refer to them to install Flosum and for introductory information before continuing with this Guide.
a) Flosum Architecture
In addition to being 100% Salesforce native, Flosum is engineered with a unique architecture that avoids pitfalls associated with traditional Salesforce application development. As you begin to implement Flosum in your development environment you will see how Flosum puts more control in the hands of both Administrators and Developers, making management and implementation of your development projects easier and faster.
b) Core Concepts
Flosum features are engineered around several core concepts of ALM. Each of these features is accessed through individual tabs of the Flosum application. The rest of this guide will introduce you to these features.
c) Browser Use
See our browser support article for information on types and best practices for browser use.
Flosum features are accessed through the application tabs. This section walks you through the functionality found on each of these tabs.
a) The Orgs Tab
The Orgs tab page is your window into each of the orgs you have connected to Flosum and enables you to monitor the progress of activities across these orgs. You can monitor details of deployments, commits, branching and other activities.
From the Orgs Tab you can use the New button to connect your orgs to Flosum.
Once connected you can drill down into each or your connected orgs to:
- Create and compare snapshots of your orgs
- Schedule automated test execution
- Assign permissions for org access
- Initiate Audit activities
- View detailed Deployment history for all deployment activities, whether from Snapshot or Patch
- View detailed log information for all activities
Snapshots retrieve the components that have changed in a source organization and are used as the basis for many of the actions available with Flosum. There is no need to recreate the snapshot each time you need to make a comparison – the snapshot remains until you delete it.
To find out how to get the most from Flosum snapshot capabilities, please see:
c) Branches Tab
Branches allow developers to work in parallel without disturbing the main trunk of the development tree. This parallel development is kept separate to enable developers to test out concepts or solutions in a smaller group and well-defined development area. Once the work is complete there are multiple avenues (commit to repository, transfer to patch, merge branch) for integrating the work back into the main code base. Branches are a component of Flosum's Version Control solution.
A Flosum Repository is the central database for tracking changes to your development orgs. The Repository is a component of the Version Control system, offering robust source control capabilities. The Repository is often referred to as the main line, trunk, master branch, or head of Version Control. When using Version Control, the Flosum Repository holds the most recent version of changes to code in production.
Flosum supports multiple repositories within the same Flosum installation, allowing you to manage multiple product releases easily within one Flosum application.
During deployment a rollback file is created. Flosum provides a Rollback mechanism so that if there is a failure, the changes are automatically rolled back. However, even if not, you can use the Rollback feature to activate the process of undoing unintended changes.
e) Commits Tab
On the Commits page you will see all the commits which were made to this org. You can drill down to get more information on each – the information is available to help manage your development process.
f) Builds Tab
Flosum provides a framework for Continuous Integration and Testing. The Builds tab is to ensure that any change to the repository is automatically tested without the need for manual intervention. Once automated builds are activated then Flosum will execute tests with each build and provide test results and analysis. As developers commit their changes frequently to the Repository and those changes are periodically deployed to production, there will be fewer integration issues.
g) Patches Tab
Patches provide a reliable and consistent method for deploying changes from one organization to another. Patches incorporate the functionality of changesets but are more powerful and easier to use. Advantages of Patches mitigate many existing deployment challenges. Follow these instructions to Create and Deploy a Patch.
Flosum provides all the reporting and visibility tools native to the Salesforce platform. Included with Flosum are a number of sample reports and dashboards that can give you insight into activities in your Flosum Salesforce ecosystem. These reports are built using the extensive Salesforce Report and Dashboards tools that you are already very familiar with. You can also customize reports and dashboards to your business needs.
j) Settings Tab
The Settings Tab is where you manage overall settings for the Flosum application.