Back Forward Connect REST form
Completing the Service tab

  1. About 
  2. New 
  3. Service 
  4. Methods 
  5. History 
  6. More.. 

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.

NoteThis URL can change over time, or can change when you move between a test system and a production system. However, after the RuleSet version containing this connector rule is locked, you cannot update this field. If your application needs to override the value in this field, complete the EndPointURL parameter of the Connect-REST method in the connector activity that calls this connector rule.

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

SmartPrompt is available.Specify the source or the type of source of the value:

  • Clipboard — Map from the page name or property on the clipboard specified by the Map From Key field.
  • Constant — The data is a fixed value that does not change.
Map From Key

SmartPrompt is available.Specify the key to locate the property in the source specified in the Map From field.

  • If the Map From value is Clipboard, enter the property name from which the data is mapped at runtime.
  • If the Map From value is Constant, enter the value of the constant surrounded by double quote characters.

NoteUsage: 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

SmartPrompt is available.Required, if Use Authentication? is selected. Select the Authentication Profile that contains the authentication details required by the remote service.

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

SmartPrompt is available.Optional. Select a property to hold the status code of the Connect-REST method. The literal value Good identifies success. You can use the standard property @baseclass.pyStatusValue.

Status Message Property

SmartPrompt is available.Optional. Select a property to hold status descriptions or return values from the external system returned by the Connect-REST method. You can use the standard property @baseclass.pyStatusMessage.

This field is disabled and ignored at runtime when the Intended for field is set to queuing.

Error Handler Flow

SmartPrompt is available.Optional. Identify a flow rule to route work items that cannot continue in its current flow because this connector rule was unable to connect to the external system. The default flow rule Work-.ConnectionProblem provides one approach for handling such problems. See Handling connector exceptions.

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

SmartPrompt is available.Optional. Select:

  • immediate execution — the REST connector executes synchronously; the calling activity waits for results.
  • queuing (response will not be available) — the REST connector executes asynchronously, with calls placed in a queue. The calling activity continues without waiting for results.

Queuing, when selected, occurs only if also specified in the Connect-REST method.

Request Processor

SmartPrompt is available.Optional. If you selected queuing for the Intended for field, identify here a Connect Request Processor data instance that defines the classes and other characteristics of the queued connector requests, and for which the RuleSet key part matches the RuleSet of this Connect REST rule.

Simulations

Click to create a simulator for this connect rule. See Connect Simulators.

Up About Connect REST rules