Salesforce Configuration / Customization Dependencies and Best Practices

To ensure that the Salesforce setup will be transferred as expected to Pitcher, there is a set of dependencies and best practices that should be followed:

• Required fields: Use page layout Required Fields as much as possible. The second best thing is the simple Validation Rules. APEX should only be used if absolutely necessary as APEX codes are run only during online sync.

• Visibility: For object visibility, you should use Private OWD with Sharing Rules.

• Performance:

  • # of Accounts per rep should be 2.000 accounts top. There is no hard limit but it will increase sync time.

  • # of Contacts per rep should be 2.000 accounts top. There is no hard limit but it will increase sync time.

  • Try to avoid many record types/page layouts, the less the better"

• User access  

  • Not to assign IP ranges/domains on user names so Pitcher can assist User access

  • Enable "Login as" access

• Lighting / Visual Force Pages:  Don't use Lightning Components/Visual Pages as those won't come down with Pitcher Zero automatically

• Sorting in Related Lists: The sorting of Pitcher Zero related lists is determined in the Layout of the Default / Master Layout of an object in Salesforce and not in the layout that is assigned to that Account

• Record Type Record type access: Assign Record types at profile level, not at permission set level