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)
Tickets managed by RSPCA which require review by Vertic will be categorised under the Epic RSPCA Internal Development and moved directly to Vertic Review.
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
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
Medium Impact updates are preferably included in the monthly release, however if they’re deemed to be high priority then they require approval via a weekly check in with the team to be released early.
Profiles
Flow updates
Validation rules
High Impact Updates
High Impact updates are required to go through a full development lifecycle, development is conducted in a DEV sandbox and released to the Full sandbox for business testing before being approved and release to Production in the monthly releases.
Final approval is agreed in the standard deployment meeting held before the monthly release which is scheduled for the last Tuesday of every month.
Apex class updates
Lightning component updates
New Flows