Skip to main content


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

Connect JMS form - Completing the Request tab

Updated on April 6, 2022

Use the Request tab to specify the contents of the outgoing request message. At runtime, Pega Platform maps the data from the clipboard (or other sources) to fields of the message header, message body, and parameter values.

Message Headers

FieldDescription
Field Optional. Select a message header field (JMSCorrelationID or JMSType).
DescriptionEnter a text description.
Map fromSelect how the system creates the selected request header value:
  • Clipboard — The system maps the data value from the property specified by the Map from key.
  • Constant — The system sends a fixed value.

If more choices appear, they identify a custom function rule in a MapFrom library. Review the function rule to determine what it does.

Map from key Specify the key to locating the property or rule in the source specified in the Map from field.
  • If you map from Clipboard, enter a property reference that is the source of the data.
  • If you map from Constant, enter a literal constant. To include blank spaces in your text string surround the constant with double quotation marks.

Message properties

Complete this section to define how Pega Platform is to assemble property values and literal values to form the request message.

FieldDescription
Data type Select the external Java data type of the parameter value: String, Integer, Byte, Float, Double, Int, Long, Short, or Boolean.
NameEnter a property reference that is the source of the value.
DescriptionOptional. Enter a short text description of this row of the array.
Map from Select how the system creates request parameter values. The choice you make for this field depends on what you selected for Data Type:
  • Clipboard — The system maps the data value to the scalar property specified by the Map from key.
  • Constant — The system sends a fixed value.
  • XML Stream — The system composes a stream of XML text, formatted by an XML Stream rule.
  • HTML Stream — The system composes a stream of HTML text, formatted by an HTML rule.

If more choices appear, they each identify a custom function rule in a MapFrom library. Review the function rule to determine what it does.

Map from key Enter additional details that complete the Map from mapping:
  • If you map from Clipboard, enter a property reference that is the source of the data.
  • If you map from Constant, enter a literal text string. To include blank spaces in your text string, surround the string with double quotation marks.
  • If you map from XML Stream, enter a Stream Name key part of the XML Stream rule that is generate the data. The system uses the Primary Page Class of the service as the Applies To key part.
  • If you map from HTML Stream, enter the Stream Name key part of the HTML rule that is to generate the data stream. The system uses the Primary Page Class of the service as the Applies To key part.
  • If you map from a Rule-Utility-Function from a MapFrom library, ither select the property that holds the value to be processed by the function or leave this field blank, as appropriate for the function.

Message data

Complete this section to identify the sources and mappings for the JMS request parameters. Working in the same way as the Message properties section, this section provides two additional data types: Bytes and JavaObject.

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