We Value Your Privacy

We use technology such as cookies on our website, and through our partners, to personalize content and ads, provide social media features, and analyse our traffic. To find out more, read our privacy policy and Cookie Policy. Please also see our Terms and Conditions of Use. By accepting these terms you agree to your information being processed by Inbox Insight, its Partners or future partners, that you are over 18, and may receive relevant communications through this website, phone, email and digital marketing. For more information on how we process your data, or to opt out, please read our privacy policy. Our policies and partners are subject to change so please check back regularly to stay up to date with our terms of use and processing.

Accept Terms Settings
x

Please Sign-In to Access this Report

To access other reports on the platform please sign in with your username and password, or register for a free account to get unlimited access and insight customized for you.

Report Prodly

The Essential Guide to Reference Data Management: CPQ edition

The advantage of Salesforce CPQ is it can be quickly configured with clicks not code. So why does it still take so long to make changes in Salesforce?

Well, point-and-click development is still development, and bugs in CPQ configuration can take down your mission revenue application. Admins rely on release management to prevent bugs, but it’s often a very manual, time consuming process to promote app changes from dev to sandbox to production.

Report Snap Shot

Download the guide to learn:

  • The revenue impact of bad CPQ deployments (and how to prevent them)
  • How to apply agile development to CPQ
  • A foolproof pre-deployment checklist

Related Content