Sales Systems exists to support the GitLab field organization by providing reliable, scalable, and intuitive technology platforms for everyday use. Primarily working on Salesforce.com and its related business systems, our goal is to constantly deliver value in the form of features to our end users. We also act as the connective tissue between business and technology, gathering requirements from our internal customers, designing the technical specifications and executing on the delivery of the solution.
Below is a list of the different technical skill sets found on the Sales System team. Note: A Sales Systems team member might be using a mix of the following skills sets at any one time.
|Business Systems Architect||Project lead in charge of gathering business requirements from customers and developing them into technical specifications.|
|Business Systems Administrator||Business analyst experienced in Salesforce.com plaform configuration, process automation, and business workflows.|
|Business Systems Engineer||Software engineer experienced in Salesforce.com platform APEX development, API based integrations, and the software development life cycle.|
SalesSystems::Triagelabel by the Sales Systems team.
SalesSystems::Backloguntil it can be planned.
Before beginning work, make sure:
Change Managment Steps:
git checkout -b "SalesSystems-158".
SFDX: Deploy Source To Orgon the changed classes, triggers or pages.
SFDX: Retrieve Source From Orgon the changed objects or metadata.
git statusto make sure the changed files are the ones you expected.
git add [filename]or
git add *if you want to add all changed files.
git commit -m "Fixing Apex CPU Errors".
WIP:, and assign it to the Architect on the project.
WIP:status and merge the change.
SalesSystems-158and push to production.
git checkout masterthen
git pull. Always be pulling!
Note: We are continuing to move towards using Salesforce SFDX and GitLab CI/CD Pipelines