|
|
Use the Service tab to identify the external system with which this connector rule communicates.
Field |
Description |
Resource Path |
Enter the URL of the external resource to which this rule connects.
This field supports the Global Resource Settings syntax (=.PageName.PropertyName). For more information, see Using the Global Resource Settings feature. |
Resource Params |
|
Name |
Enter the name of the resource parameter. |
Description |
Enter a short description of the resource parameter. |
Map From |
|
Map From Key |
|
Usage: If the Resource Path specified is http://restServiceHostName/CustomerDB/resources/entities.customer/{id}, the parameter id is the dynamic resource parameter that needs to be mapped to a Clipboard property or a Constant in the Resource Parameters section as described above.
Authentication |
|
Use Authentication? |
If selected, PRPC includes authentication credentials in the HTTP header of the message. |
Authentication Profile |
|
Connection |
|
Response Timeout |
Optional. Enter the number of milliseconds after which this rule times out with a failure message if it does not receive a response. Enter zero or leave blank to wait indefinitely. This field is disabled and ignored at runtime when the Intended for field is set to queuing. |
Maintain Session? |
Select to use HTTP token-passing as the mechanism for maintaining a stateful session with the Web service provider. If selected, enter a Connection ID value in the following field. This field is disabled and ignored at runtime when the Intended for field is set to queuing. |
Connection ID |
Optional. If the external system uses HTTP token passing to maintain stateful session data between requests, you can use this field to specify that a group of logically related connectors are to share a single session. Enter an arbitrary text value in this field, and enter the same text value in the other REST connector rules that are to share the session data. |
Error Handling |
|
Status Value Property |
|
Status Message Property |
This field is disabled and ignored at runtime when the Intended for field is set to queuing. |
Error Handler Flow |
|
You can allow connector requests from this Connect REST to be processed asynchronously in parallel with the calling activity, or in background by an agent. (The mode of execution of each connector request is determined by the Execution Mode parameter of the Connect-REST method, as enabled by the values in these two fields.)
Intended For |
Queuing, when selected, occurs only if also specified in the Connect-REST method. |
Request Processor |
|
Simulations |
Click to create a simulator for this connect rule. See Connect Simulators. |