Session 9: Validation Rules Current validation pains
Opportunities
- Company name does not match with address for account contact on opportunity
- In Orion, associated with account, need a corporate address (as opposed to individual address, such as home office)
- Ship-to vs. corporate address
- Ship-to needed for territory assignment and tax
- CCI form US only (Customer Contact Information)
- We will mirror account/contact structure from Orion
New AL
- Sales e-mail changes after request for paperwork comes through.
- Company name changes means re-validation of account
- Standard to non-standard paperwork changes
- System needs to reduce “sloppiness”
- How to re-start process if deal changes
- Avoid email changes
Upgrades
- Person requesting does not match designated SAS rep on account
- Need to track both in Salesforce (requestor and SAS rep)
- Load SAS rep data from GIDB
- Effective date – not filled in; 15thor last day of month, but some exceptions
- Quantities - 0 or value doesn’t get updated as deal evolves; can fix 0’s, but hard to catch mis-matches
- Could we link user count to deal amount; lock one field if the other changes
- Eventually: should be able to calculate upgrade amount in Salesforce for standard deals (account for proration, begin dates, rounding, etc.)
- C-Calcexists for fee calculation (application under Contracts
- Jon’s pricing has specific rounding for certain territories
- Wish: standard calculator that sales can use from within SFDC; ask Jon: what calculator do you want your sales people to use?
- No default OS
- Split indicated, but secondary opportunity not included.
- PO number enter, but PO provided. Way for sales to indicate that there is no PO attachment.
- Some accounts require a PO to invoice. Business rule in GIDB at product level
- To process, BO needs PO or email approval from site rep
- Antoine: if email is sent from SFDC approval can be tracked back into SFDC
Requirements
- Checking split checkbox should trigger creation of secondary opportunity and math should be accurate. There is a formula for upgrade splits. In all cases, splits should add to invoice amount.
SalesforceValidation RulesRe: Session 9: Validation RulesCarol Gretz: Operations receives an email generated from Salesforce.com indicating that opportunity is ready for Paperwork. After receiving this email and prior to us sending the paperwork back to the Sales Team, we will receive emails from Sales giving us additional informaiton about the opportunity, such as, change address, change user count, change amount, etc. This places an extra burden on Operations as we need to comprehend not only the original request but be sure we accomodated all the other changes we received via email after the fact.
Re: Session 9: Validation RulesCan someone in Operations give me a bit more context around this item: "Sales e-mail changes after request for paperwork comes through." Is this a situation where the email is sent from SFDC requesting paperwork, and then sales will send an email with additional details or request to cancel? Just making sure I understand completely before building a proposed solution. @kathycobb or Carol? (not sure which Carol account is yours)
Re: Session 9: Validation RulesValidation rule to check close date and ensure opportunities aren’t created with a close date greater than one year ahead and 120 days prior is rested and ready for production July 5th. Based on input from Jon Weisz.
