The documentation below is organized by feature. Each section will have links to the appropriate business process page, the relevant inputs and outputs for the feature, as well as references to the specific logic that processes the input and outputs.
Please see the dedicated ARR Technical Documentation Page
Please see the dedicated Gainsight Technical Documentation Page
More information to come. If you need a new field brought into Xactly please leverage the
AddFieldToXactlySales issue template in the Sales Systems Project
Business Process this supports: Territory Success Planning
Overview: The goal of TSP is to keep a set of staging fields consistently up to date from a variety of data sources, then at given intervals copy these values to the "Actual" set of fields for general use. This allows for us to constantly receive changes but only apply those changes in a controlled fashion. This also allows us to easily track exceptions. Note: This project was originally referred to as ATAM, which is why the API names of the fields reference that instead of TSP.
Logic Locations: AccountJob.cls
Inputs: DataFox, Zoominfo, Manually Entered Address & Employee Data, Account Parenting Hierarchy
Outputs: Here is the outline between two sets of fields we are setting on the Account object. The Staging(TSP / ATAM) fields are set nightly via an APEX job. Actuals are set at given intervals found in the business documentation.
|Data Name||Actual - Field API Name||TSP - Field API Name|
Business Process this supports: Landed Addressable Market (LAM)
Overview: LAM is a measure of how much more expansion or growth we can achieve with the customers we already have. This value is calculated in Salesforce daily based on several inputs.
Inputs: Zuora, Zoominfo,LinkedIn, Manually Entered Employee Data, Account Parenting Hierarchy,
Outputs: Here are the various fields used in the solution, along with how they are set.
The LAM calculation runs in three parts:
|Data Name||Actual - Field API Name||Data Type||Set By|
|LAM Tier (Industry)||LAM_Tier_Industry__c||Formula||SFDC|
|LAM Tier (Dev Count)||LAM_Tier__c||Formula||SFDC|
|LAM Seat (Industry)||LAM_Seat_Industry__c||Formula||SFDC|
|LAM Seat (Dev Count)||LAM_Seat__c||Formula||SFDC|
|LAM Price (Industry)||LAM_Price_Industry__c||Formula||SFDC|
|LAM Price (Dev Count)||LAM_Price__c||Formula||SFDC|
|LAM Max (Industry)||LAM_Max_Industry__c||Formula||SFDC|
|LAM Max (Dev Count)||LAM_Max__c||Formula||SFDC|
|LAM Dev Count||LAM_Dev_Count__c||Formula||SFDC|
|LAM: Ultimate Annualized Seat Price||LAM_Ultimate_Annualized_Seat_Price__c||Formula||SFDC|
|LAM:Ult. Avg Seat Price, this Account||LAM_Ult_Avg_Seat_Price_this_Account__c||Formula||SFDC|
|LAM:Starter Avg Seat Price, this Account||LAM_Starter_Avg_Seat_Price_this_Account__c||Formula||SFDC|
|LAM: Starter Annualized Seat Price||LAM_Starter_Annualized_Seat_Price__c||Formula||SFDC|
|LAM: Prevalent Tier Avg Price, this Acct||LAM_Prevalent_Tier_Avg_Price_this_Acct__c||Formula||SFDC|
|LAM: Prevalent Tier Avg Price, Acct Fam||LAM_Prevalent_Tier_Avg_Price_Acct_Fam__c||Formula||SFDC|
|LAM:Premium Avg Seat Price, this Account||LAM_Premium_Avg_Seat_Price_this_Account__c||Formula||SFDC|
|LAM: Premium Annualized Seat Price||LAM_Premium_Annualized_Seat_Price__c||Formula||SFDC|
|LAM: Est Dev Percent by Industry||LAM_Est_Dev_Percent_by_Industry__c||Formula||SFDC|
|LAM: Count of Ultimate Subscriptions||LAM_Count_of_Ultimate_Subscriptions__c||Currency||AccountJob|
|LAM: Count of Ultimate Subs, Acct Family||LAM_Count_of_Ultimate_Subs_Acct_Family__c||Currency||AccountJob_SetParentLAMFields|
|LAM: Count of Starter Subscriptions||LAM_Count_of_Starter_Subscriptions__c||Currency||AccountJob|
|LAM: Count of Starter Subs, Acct Family||LAM_Count_of_Starter_Subs_Acct_Family__c||Currency||AccountJob_SetParentLAMFields|
|LAM: Count of Premium Subscriptions||LAM_Count_of_Premium_Subscriptions__c||Currency||AccountJob|
|LAM: Count of Premium Subs, Acct Family||LAM_Count_of_Premium_Subs_Acct_Family__c||Currency||AccountJob_SetParentLAMFields|
|LAM:Aggregate Annual Ultimate Seat Price||LAM_Aggregate_Annual_Ultimate_Seat_Price__c||Currency||AccountJob_SetParentLAMFields|
|LAM: Aggregate Annual Starter Seat Price||LAM_Aggregate_Annual_Starter_Seat_Price__c||Currency||AccountJob_SetParentLAMFields|
|LAM: Aggregate Annual Premium Seat Price||LAM_Aggregate_Annual_Premium_Seat_Price__c||Currency||AccountJob_SetParentLAMFields|
|LAM: Acct Below Land Line||LAM_Acct_Below_Cut_Line_Form__c||Formula||SFDC|
|CARR (Acct Family)||CARR_Acct_Family__c||Formula||SFDC|
|CMRR (Acct Family)||CMRR_All_Child_Accounts__c||Currency||AccountJob_SetParentLAMFields|
|Ultimate license count||Ultimate_License_Count__c||Number||AccountJob|
|Starter license count||Starter_License_Count__c||Number||AccountJob|
|Prevalent Tier (Account)||Prevalent_Tier__c||Formula||SFDC|
|Prevalent Tier (Hierarchy)||Prevalent_Tier_Hierarchy__c||Formula||SFDC|
|Premium license count||Premium_License_Count__c||Number||AccountJob|
|Parent LAM: Aggregate Developer Count||Aggregate_Developer_Count__c||Formula||SFDC|
|Estimated Developer Count||Estimated_Developer_Count__c||Formula||SFDC|
|Parent LAM: Sum Ultimate Seat Price||Parent_LAM_Sum_Ultimate_Seat_Price__c||Currency||AccountJob_SetParentLAMFields|
|Parent LAM: Sum Starter Seat Price||Parent_LAM_Sum_Starter_Seat_Price__c||Currency||AccountJob_SetParentLAMFields|
|Parent LAM: Sum Premium Seat Price||Parent_LAM_Sum_Premium_Seat_Price__c||Currency||AccountJob_SetParentLAMFields|
|Parent LAM: Sum of Num of Licenses||Parent_LAM_Sum_of_Num_of_Licenses__c||Number||AccountJob_SetParentLAMFields|
|Parent LAM: Max ZI Number of Developers||Parent_LAM_Max_ZI_Number_of_Developers__c||Number||AccountJob_SetParentLAMFields|
|Parent LAM: Max Potential Users||Parent_LAM_Max_Potential_Users__c||Number||AccountJob_SetParentLAMFields|
|Parent LAM: LinkedIn Developer Count||Parent_LAM_Max_Decision_Makers_LinkedIn__c||Number||AccountJob_SetParentLAMFields|
|Parent LAM: Industry (Acct Heirarchy)||Parent_LAM_Industry_Acct_Heirarchy__c||Picklist||AccountJob_SetParentLAMFields|
|Parent LAM: Count of Ultimate Subs||Parent_LAM_Count_of_Ultimate_Subs__c||Number||AccountJob_SetParentLAMFields|
|Parent LAM: Count of Starter Subs||Parent_LAM_Count_of_Starter_Subs__c||Number||AccountJob_SetParentLAMFields|
|Parent LAM: Count of Premium Subs||Parent_LAM_Count_of_Premium_Subs__c||Number||AccountJob_SetParentLAMFields|
Business Process this supports: This supports our contact ownership rules
Overview: The goal of the Contact Ownership code is to ensure that contacts are owned by the appropriate user within salesforce in an automated fashion so that contact ownership is maintained without any work needed by team members.
Logic Locations: ContactJob Code Units:
Inputs: Contact Owner, Account Owner, Account SDR Assigned, Account Type, Sales Segment
Outputs: Contact Owner
Please see our internal document for details.
For manual sharing of opportunity record, please refer Field Operations handbook here
Business Process this supports: Discount Approvals
Overview: According to the Deal Approval Matrix Quotes must have discounts approved by different management levels depending on discount percentage and term length. To achieve this, we have written automation to stamp a quote with each potential approver, revised the code that determines which approvals are required, and revised the actual approval process in Salesforce.
Quote Management Stamp When a Quote is inserted, get the owner of the related Opportunity. Then, find the manager of the owner and the manager of the manager for each manager, five managers down. Record the first active Regional Director, Area Sales Manager, and Vice President on the Quote. These lookup fields will be used in the Approval Process, if needed.
Quote Approval Code This is a table of the Quote (API Name: zqu__Quote__c) fields that trigger quoteApprovals to recalculate and what must happen to them.
|Field API Name||What Must Happen|
If any of these events happen, all "Required_Approvals" fields (Required_Approvals_From_CEO__c, Required_Approvals_From_CFO__c, Required_Approvals_From_CRO__c, Required_Approvals_From_CS__c, Required_Approvals_From_Legal__c, Required_Approvals_From_VP_of_Channel__c, Required_Approvals_From_VP_of_Sales_RD__c, Required_Approvals_From_RD__c, Required_Approvals_From_ASM__c) are cleared. These are the rich text area fields that show which management levels need to approve the Quote on the page layouts. Then, all relevant Quote Rate Plan Charges (API Name: zqu__QuoteRatePlanCharge__c) related to the Quote are queried, these are what hold the term, product, and discount information we need to determine what approvals are required. Following the Deal Approval Matrix, we determine what level of management the Quote Rate Plan Charge needs and stamp the correct "Required_Approvals" fields with the discount percentage, type, and term. Similar logic is then run for any Quote Rate Plan Charges related to Professional Services products. Finally, the Quote's Approval_Stage__c field records whether it needs approval, doesn't need approval, or has been approved.
Quote Approval Process This utilizes Salesforce's built-in Approval Process functionality. We have two Approval Processes for Zuora Quotes, the first for undiscounted, and the other for ones with discounts. The Quote must be submitted using the "Submit for Approval" button on the page layout to enter the correct Approval Process.
Business Process this supports: The field needs a streamlined process to address their concerns on specific salesforce records within salesforce. This is also used by the finance team to help address record specific billing issues, as well as the Community Advocate team to manage the influx of requests the team receives.
Overview: The goal of the Chatter To Cases functionality is to allow a streamlined communication channel that the field can leverage while also providing a streamlined case management system for the supporting team members to manage the requests that are sent to them from the field. If a team member uses an appropriate tag in salesforce a salesforce case record will automatically be created. Once these records are created supporting team members can work through the respective cases that are created to address the needs and concerns of the field team.
Inputs: Chatter text within Salesforce
Outputs: Salesforce Case Records
Logic Locations: Code Units:
@SMB Flat Renewals
@Partner Help Desk
Steps to add a Group:
Originfield on the case object
ChatterFeedItemClassto monitor for the use of the Chatter Group in chatters within Salesforce
CaseClassto include the new groups Id so that it updates the case owner what ownd by this queue.
Business Process this supports The sales cycle, if a GitLab sales rep encounters an issue that requires legal knowledge, opinion, or action.
Overview A sales rep can quickly and easily create a Case for our legal team directly from an Opportunity's page layout in Salesforce. The legal team has access to a Salesforce dashboard to see how many Cases have been created for them, how many are in their name, etc. Clicking the "Legal Request" button on each Opportunity's page will bring the user to a page that asks a few questions that the legal team would like to know. Once the page is submitted, a Case is created with the Origin marked as "Legal Request." The legal team has dashboards that view Cases with Origin equal to "Legal Request" and can assign and take action from there.
Business Process this supports The sales cycle and the financial processes around deals.
Overview We are now ensuring Opportunities in Salesforce have only one Quote that is marked as Primary. If multiple Quotes are being inserted under an Opportunity marked as primary in the same transaction, only the first in the list will be the primary. If a Quote is being inserted as primary, and there is an existing primary Quote, the existing will become not-primary and the incoming will be the new primary. If more than one Quote under the same Opportunity is being updated to become primary in the same transaction, an error message will prevent the update. A primary quote will not be allowed to be deleted. To change which Quote is primary, simply navigate to the Quote you want to be primary and update it as such, the previous primary Quote will automatically be updated to no longer be primary.
Business Process this supports The sales cycle and analytics.
Overview The goal of this functionality is to capture the progression of an opportunity through the stages in the sales process. To support this, a checkbox and date stamp will be automatically populated for each stage as the opportunity advances and or moves back in stage. The tracking begins at stage 0-Pending Acceptance. In the event an opportunity advances forward and skips stages, all of the skipped stages will be stamped with the same date as the resting stage. In the event of Closed Lost and Unqualified, the checks and dates will only apply for the stages that were actually met. To avoid data loss and confusion, the stage progression tracking will only run once, the first time through the stages.
Business Process this supports The Sales Finance & Analytics
Overview The goal is to have a static opportunity population in salesforce once the opportunity close date is past accounting close date ( which is 10th day of the month) so it ties to everything that was reported to the Board. And to ensure the bookings data don't change as there are other downstream implications such as Commissions Calculation, Booking Reporting & Adaptive Bookings Data,need to build a mechanism to lock the booking related opportunity fields after green light from Deal Desk & Finance. If there are any minor adjustments ( if needed ) to historical periods we have specific permission sets to make the appropriate changes.
Business Process this supports: In order to provide reliable and accurate historical data to the analytics team, the sales organization and to the company as a whole we need to ensure that historical opportunities and relevant information on opportunities is not changed once the opportunity is closed.
Overview: The goal of this blocking logic is to close a backdoor that Salesforce has built into the system. While we have a number of validation rules in place to prevent information from changing on closed opportunities it is possible to change historical opportunity owners (as well as fields that are derived from the owner field) while transferring accounts. Anyone who could have been able to change the owner on an account would have been able change historical opportunity data that they would not be able to edit otherwise. This logic still allows users to complete this account ownership transfer without any impact to historical opportunities while also allowing the various business teams at GitLab to manually update the owners of opportunities at month close.
Inputs: Account records that are changing ownership
Outputs: Reverts opportunity owners to their original owners if the user attempted to change them
Logic Locations: Code Units:
Business Process this supports: New vs Connected New vs Growth
Overview: The goal of the Order Type system is to determine a given Opportunity's relationship with the business. Did it start a new customer relationship, cross into a related segment of the customer, or grow an existing relationship.
Logic Locations: AccountJob.cls
Inputs: Salesforce Account Hierarchy, Salesforce Opportunity Close Date and Stage.
Outputs: Populates the Order Type field on the Opportunity with New - First Order, New - Connected or Growth based on the following logic:
|New - First Order||The First Closed Won Opportunity in an Account Family.|
|New - Connected||The First Closed Won Opportunity on an individual Account, that is not the first one in the Account Family.|
|Growth||All opportunities that follow the
Business Process this supports: Sales Segmentation
Overview: Leads should be sorted into different Sales Segments based on their company's employee count so the appropriate salesperson can pursue them. We have a number of different information sources to get company size, so we must also establish a hierarchy for them.
|Info Source||Salesforce Lead Field API Name|
Logic Locations: LeadClass.cls Code Unit:
Business Process this supports: Command of The Message
Overview: This Visualforce page and supporting controller provide the sales team with an easy to use button on their opportunities to populate the needed information.
Please see our internal document for details.
Business Process this supports: This supports our professional services team. They leverage Mavenlink projects to coordinate their projects, the hours they spend on each project and their associated tasks, schedules and more.
Overview: The following sections of code control the process by which Mavenlink projects in Salesforce are created, which in turn are then pushed over to Mavenlink by leveraging an extension class that was provided by Mavenlink. Currently a Mavenlink Project is created when one of the following scenarios is met
Business Process this supports: This supports the automatic creation validation of our opportunity split that supports our compensation team. This helps ensure that our team members are compensated for the opportunities that they are associated with in an automated fashion
Opportunity - Incremental ACV 2split type
Sales Development Representatives/
Primary Solutions Architect/
Channel Manager: Base split automation rules
Technical Account ManagerSpecial Use Cases
Channel ManagerSpecial Use Cases
null/Emptyare assumed to be the same role and are summed accordingly.
Sales Development Representatives,
Primary Solutions Architect.
Channel Managersare not included in this Validation rule because they are not paid until after the close, the validation rule would conflict with existing automations and because it is expected that Channel Managers will never have a split Opportunity.
General Automation Notes
Business Process this supports: Decommission Opportunity Process
Overview: For this process to function properly there is a button that has been added to the Opportunity layout. This button should only be visible to users who should be working on our bookings (Deal Desk, Finance Users, etc.). This button, when clicked, updated a checkbox on that opportunity to mark it as a refunded opportunity. If the button is clicked for an already refunded Opportunity, the user will be presented with an error informing them that the refund has already been completed.
Selecting this checkbox on an Opportunity causes the Opportuntiy trigger to execute a method which will create a full clone of the existing opportunity. Additionally, if the owner of the original opportunity is no longer active, the refund opportunity owner is updated to that user's Manager. If that manager is also no longer active, then the refund opportunity is assigned to the user who triggered the process.
The action does change several values on the Opportunity, mostly to update a number of fields to null or override fields are used to negate our bookings numbers. Specific changes include:
The values in the following fields will be carried over and flipped to negative on the refund opportunity (i.e. grab the value from the originating opportunity, and stamp the inverse on the refund opportunity created via button):
The values in the following fields will be carried over as is from the originating opportunity:
Note: Because this process uses a checkbox field, it is also possible to trigger refunds through a data load or similar mass update.
Business Process this supports: This supports the Deal Desk process of processing Credit Opportunities and Contract Reset Opportunities. See the Sales Order Processing Handbook Page
Total_Net_ARR_Credit__con the related Contract Reset Opportunuty is updated to be the Sum of the Net ARR of any Credit Opportunity that meets our criteria. Some of the changes that may cause this code to run would be:
Business Process this supports: Sales Cycle & Operations Tracking Sales Qualified Source in the Opportunity
Overview: There are times in which we may need to override Sales Qualified Source. In this event, we have a system that will allow this. This ability is limited to James Harrison and Colleen Farris. To override Sales Qualified Source, enabling user with perform the following steps:
Once this is complete, a validation rule will prohibit anyone other than the above mentioned users from editing this field. All automation that updates this field includes criteria that excludes them from firing if the Override SQS checkbox is checked.
Business Process this supports: This automation maintains the correct Channel Manager on Opportunities. This is important for tracking which Channel Manager gets compensated on which Opportunity.
Please see our internal document for details.
Business Process this supports: This process supports our TAM Team Tracking Alignment and Compensation. See the business handbook section Coming Soon
[Comp] TAM Team(
Technical Account Manager(
[Comp] TAM Team(
2. New - Connected,
5. Churn - Partial,
6. Churn - Final
Business Process this supports: Digital Journey - In order to deliver the digital journey enablement series to new customers, we need a way to identify contact roles for certain personas in the business to receive the right material.
Overview: For the Commercial and Enterprise markets, we will require identifying the GitLab admins at each Account at the time of Opportunity approval submission. When the “Submit for Approval” button is clicked in the Opportunity, logic will run the check criteria (defined below) on if a GitLab Admin is required and if there is currently one defined. Providing a GitLab Admin is defined by having at least one contact on the Account that has
Role CONTAIN GitLab Admin. Note: This contact can have other roles defined in this field in addition to GitLab Admin.
There will be Salesforce validation checks at stages 4+ to ensure at least one
gitlab admin has been identified to support the account via Digital Programs. At Stages 4+ and deal close and if the criteria below is met, there are two potential results:
Criteria to enter this logic:
Web Portal Purchaseis Unchecked (false value)
Order Type 2.0is 1. New - First Order OR 2. New - Connected OR 3. Growth OR 4. Contraction
Please see our internal document for details.
Business Process this supports: Sales tracks their next steps in the
Next Steps field. It is important to have a historical log of these "Next Steps" values so that they can be referenced in the future. We have created a system to streamline this process so that sales will only need to update what the true "Next Step" is and the system will log the historical data.
Overview: On the Opportunity, when the
Next Steps field is updated, the previous value of this field will be stamped into the
Next Steps History field. This will be complete with a timestamp and will keep the previously existing value of
Next Steps History to keep a full log.
Criteria to enter this logic:
Next Stepshas been changed/updated OR the Opportunity has just been created.
Next Stepsprevious value was not a "blank" value.
SalesSystems 1Password Vault
Business Process this supports: Finance Systems Team implements a new Collections Management Tool (Tesorio). Tesorio will be connected to Zuora and get most of the data it needs to manage running process which also requires Tesorio to be integrated with Salesforce to get some additional data on the customer accounts (i.e. account owner).
Overview: Tesorio integrates with Salesforce using REST APIs. The integration requires a Connected App to be created within Salesforce. The data import from Salesforce are:
Business Process this supports: Sales Cycle & All Operations
Overview: Email alerts are emails generated by an automated process and sent to designated recipients. These actions consist of the standard text and list of recipients for an email. Email alerts are associated with processes, flows, workflow rules & approval processes. Here is the Email Alert Document which lists all the email alerts with associated automation details, email template details & target audience information that are sent from the Salesforce instance. To request deactivating and/or updating these emails alerts for business reasons please create an issue in SalesSystems Board for Systems Team Member to review & make necessary updates.
Business Process this supports: Sales Cycle - Late Renewal Notification & Auto Close Process
Overview: To keep the Sales Pipeline clean and for a systematic way to notify opportunity owners (and their managers) of renewal opportunities that are at risk of lapsing, automatically close late renewals that fall out of adherence to our Bookings Policy. This automation triggers for all Open Renewal Opportunities based on Quote Start Date in the opportunity. There is an exception process that is built into this functionality as well. This allows Sales Ops to accept exceptions for this automation that would exptend the window of when an Opportunity is automatically Closed Lost to
90 days after the Opportunity Quote Start Date. This is acchomplished by checking the
Exempt Late Renewal Automation checkbox on the relevant Opportunity.
This logic is included in the
OpportunityJob to trigger the action (Field Update) & alert. The recipients who receive these emails are Opportunity Owner, Opportunity Owner's Manager & ISR. Specific templates have been created to match up with the notifications. The field updates made to the
Admin Poke field are used to trigger
Troops to send email alerts to the SAs(Primary Solution Architect).
To request updating these emails alerts/recipients/actions, please create an issue in SalesSystems Board for Systems Team Member to review & make necessary updates.
Here is the config table for the automation logic for reference:
|For Open Renewal Opportunity Only||Email Template ID used||Logic[Quote Date in Opportunity]||Field Update||Email Alerts Sent To||Troops Alerts Sent To|
|First Notification - Email Alert - 15 days prior to Quote Start Date||00X4M00000121nCUAQ||Today = Quote Start Date - 15 Days||Admin Poke = 15 days prior lapsed renewal alert1 sent||Opportunity owner, ISR, opp owner manager||SAs|
|Second Notification - Email Alert - Day of Quote Start Date||00X4M00000121nFUAQ||Today = Quote Start Date||Admin Poke = on the day lapsed renewal alert2 sent||Opportunity owner, ISR, opp owner manager||SAs|
|Third Notification - Email Alert -30 days after Quote Start Date||00X4M00000121nDUAQ||Today = Quote Start Date + 30 Days||Admin Poke = 30 days prior lapsed renewal alert3 sent||Opportunity owner, ISR, opp owner manager||SAs|
|Final Notification - Email Alert + Closed Lost Update -46 days after Quote Start Date||00X4M00000121nEUAQ||Today = Quote Start Date + 46 Days||Admin Poke = opp closed lapsed renewal alert4 sent, Opportunity Stage = Closed Lost, Closed Lost/Unqualified Reason = Other, Closed Lost/Unqualified Details = Auto closed lapsed renewal||Opportunity owner, ISR, opp owner manager||SAs|
|For Renewal Opportunities with Exceptions Only||Email Template ID used||Logic[Quote Date in Opportunity]||Field Update||Email Alerts Sent To||Troops Alerts Sent To|
|First Notification - Email Alert - 30 days prior to Late Renewal Exception Expiration Date||00X8X000002aJxm||Today = Late Renewal Exception Expiration Date - 30 Days||Admin Poke = 30 days before late renewal exception expiration||Opportunity owner, ISR, opp owner manager||N/A|
|Second Notification - Email Alert - 15 days prior to Late Renewal Exception Expiration Date||00X8X000002aJxr||Today = Late Renewal Exception Expiration Date - 15||Admin Poke = 15 days before late renewal exception expiration||Opportunity owner, ISR, opp owner manager||N/A|
|Final Notification - Email Alert + Closed Lost Update on Late Renewal Exception Expiration Date||00X8X000002aJxw||Today = Late Renewal Exception Expiration Date||Admin Poke = 0 days before late renewal exception expiration, opp closed, Opportunity Stage = Closed Lost, Closed Lost/Unqualified Reason = Other, Closed Lost/Unqualified Details = Auto closed lapsed renewal||Opportunity owner, ISR, opp owner manager||N/A|
Business Process this supports: This supports the sales compensation and forecasting processes. This process is used to identify Opportunities that should be compensated for a New Logo.
Overview: This process maintains the values on two field on the Opportunity Recrod,
New_Logo_Override_Clari__c. As the names suggest the
Comp_New_Logo_Override__c is a field that feeds into the Compensation process and is leveraged by the compensation team in Xactly and
New_Logo_Override_Clari__c is a corresponding field that shares similar characteristics as the Comp field but feeds directly into Clari for forecasting needs.
Business Process this supports: This is the process of how the Pub Sec Type (
PubSec_Type__c) is determined on an account. This is important in order to determine Public Sector status on the basis of account demogrpahic information instead of ownership.
Overview: The criteria that is used to determine if an account is Public Sector or not is based on the inputs listed below. Additionally if the Account needs to be over written to a Pub Sec type that is different from what the job is producing that is possible using the