Skip to main content


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

Configuring email notifications on the orchestration server

Updated on December 13, 2021

You can optionally configure email notifications on the orchestration server. For example, users can receive emails when pre-merge criteria are not met and the system cannot create a deployment.

To configure the orchestration server to send emails, complete the following steps:
  1. ​​Use the Email wizard to configure an email account and listener by clicking Designer StudioIntegrationEmailEmail Wizard.
    This email account sends notifications to users when events occur, for example, if there are merge conflicts. For detailed information, see the procedure for “Configuring an email account that receives email and creates or manages work” in Entering email information in the Email wizard
  2. From the What would you like to do? list, select Receive an email and create/manage a work object.
  3. From the What is the class of your work type? list, select Pega-Pipeline-CD.
  4. From the What is your starting flow name? list, select NewWork.
  5. From the What is your organization? list, select the organization that is associated with the work item.
  6. In the What Ruleset? field, select the ruleset that contains the generated email service rule.
    This ruleset applies to the work class.
  7. In the What RuleSet Version? field, select the version of the ruleset for the generated email service rule.
  8. Click Next to configure the email listener.
  9. In the Email Account Name field, enter Pega-Pipeline-CD, which is the name of the email account that the listener references for incoming and outgoing email.
  10. In the Email Listener Name field, enter the name of the email listener.
    Begin the name with a letter, and use only letters, numbers, the ampersand character (&), and hyphens.
  11. In the Folder Name field, enter the name of the email folder that the listener monitors.
    Typically, this folder is INBOX.
  12. In the Service Package field, enter the name of the service package to be deployed.
    Begin the name with a letter, and use only letters, numbers, and hyphens to form an identifier.
  13. In the Service Class field, enter the service class name.
  14. In the Requestor User ID field, press the Down arrow key, and select the operator ID of the release manager operator.
  15. In the Requestor Password field, enter the password for the release manager operator.
  16. In the Requestor User ID field, enter the operator ID that the email service uses when it runs.
  17. In the Password field, enter the password for the operator ID.
  18. Click Next to continue the wizard and configure the service package.
    For more information, see Configuring the service package in the Email wizard.
  19. After you complete the wizard, enable the listener that you created in the Email Wizard.
    For more information, see Starting a listener.
  • Understanding email notifications

    Emails are also preconfigured with information about each notification type. For example, when a deployment failure occurs, the email that is sent provides information, such as the pipeline name and URL of the system on which the deployment failure occurred.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us