Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Cloud Lessons Learned

Updated on April 1, 2020
  • Make sure you have sufficient environments:
    • 2 Dev/Test (1 for IT and 1 for business strategy & logic)
    • QA, UAT and Performance / Simulation
    • Production
    • If needed: Pega DevOps/Deployment Manager, Pega BIX and Pega Agile Studio
  • Confirm access to all environments as soon as they are available
  • Make sure a Cloud email account has been established for sending notifications and reports from the application to client resources email addresses.
  • Confirm infrastructure nodes in PDC and Decisioning Services landing pages are in NORMAL status
  • Review and update as needed any Pega Agent settings and infrastructure DSS configurations
  • Ensure a Service Assurance Advisor (SAA) is assigned to assist
  • Kick off meetings with Pega Cloud Services, Project Team, Client:
    • Cloud provisioning Check List / Sales-to-Cloud Play /Sales-to-Service Play
    • Client SSL certificates for all environments
    • Processes for aligning cloud tiers to cloud routes
  • Pega Cloud is responsible for infrastructure – Project team is responsible for Application:
    • If it is accessed via Designer Studio, project team is responsible
  • End-to-end project management for cloud work (tasks, timelines and milestones) is a project responsibility:
    • Confirm all expectations and dates with all parties
    • Involve customer network and security teams from the beginning
    • Define roles, responsibilities and communications plans in advance between Project, Cloud and Customer teams
  • Understand how data will be accessed and managed and SFTP route configurations
    • Premise to cloud uploads and imports
    • Cloud to premise exports and downloads
  • Follow the rules:
    • SRs for all infrastructure work / follow-up / approvals
    • Make sure every developer has My Support Portal (MSP) account and can open product and cloud SRs
    • Make sure there are at least 2 designated Account Administrators in MSP that can be reached 24 x 7 to approve SRs (and set up new users.)
  • H-Fixes for Product SRs may need to wait until next “Patch Release”
  • Start testing – especially performance testing – as soon as services are configured

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us