Development Processes
- Matt Romeo
This article details the agreed development processes between RSPCA and Vertic.
RSPCA Internal Updates
RSPCA Internal Updates are updates implemented by the RSPCA Team.
The role of the RSPCA Team is to manage:
All Low Impact updates
Medium Impact updates with escalation to Vertic where required with detailed requirements (eg. user stories, screenshots, desired outcomes, etc.)
Detailed requirements on High Impact updates for approval with ownership of approved tickets for development where capability is available (eg. Flows)
Ticket Management
Tickets managed by RSPCA which require review by Vertic will be categorised under the Epic RSPCA Internal Development and moved directly to Vertic Review.
Tickets which require AnimalOS Package development will be created in the AP Project Board.
Tickets which require standard Salesforce development will be created in the RAS Project Board.
AnimalOS Package Updates Approval Process
Low Impact Updates
Low Impact updates are defined as configuration updates which have a low impact on the integrity of the system and do not need to go through the full development lifecycle.
They can be released in production based on an internal approval process which consists of <approval process>.
List views
Reports
Picklist values
Page layouts
Lightning Pages
Low Impact updates must be released in Production and the Full (Einstein) sandbox. This is to ensure that we don’t have misalignments with our deployment processes.
Medium Impact Updates
Profiles
Flow updates
Validation rules
New fields
High Impact Updates
Apex class updates
Lightning component updates
New Flows
FULL Sandbox Refresh Process
<insert process>
Sandbox Development Diagram
<insert process>
Feature Request Approval Process
<insert process>
Specification Approval Process