Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

PegaRULES Process Commander 6.1 Announcement - Integration

Suggest edit Updated on July 10, 2012

6.1 incorporates these enhancements in integration facilities:

  • SOAP services — When SOAP or dotNet services processing encounters a fault, the reply fault message can be based on an XML stream rule, and is no longer limited to a fixed text value. See How to customize SOAP fault messages.
  • SOAP services — SOAP services and dotNet services can accept requests that have binary file attachments, and can include binary file attachments in responses. See How to process a binary file with a SOAP service.
  • Gadgets— Landing page gadgets in the IntegrationIntegrationcategory help you access or configure integration facilities, including:
    • Incoming and outgoing email
    • Integration resources and accelerators
  • Email support — Incoming email that cannot be processed can be automatically forwarded.
  • Email support — You can configure outbound email accounts with distinct "from" and "reply-to" email addresses.
  • How to create properties for the columns of an external database table (6.1).
  • SOAP connectors — The Connector and Metadata wizard correctly processes WSDL files that use the "XSD substitution" feature to support dynamically varying structures. See XSD type and element substitution and the Connector and Metadata Accelerator
  • Connect HTTP — HTTP connectors can be configured to follow HTTP redirections.
  • Email Encryption — Your application can decrypt incoming email and encrypt outgoing email using customizable keystores. See How to send encrypted email
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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