Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using Connectors
  9. System Services, Listeners and Connectors

2. Design

2. Design

Defining Actions

Defining Actions

On the Actions tab, you can create and describe one or more actions associated with a service connector.
The following image shows the
Actions
tab:
Choose the row you want to edit and then enter the following information in the Action details tab:
Click
+
to add a new row.
  • Action Name
    : (required) Enter the name that appears in lists when referencing this Action in service connectors and connections. Do not use spaces or special characters in this name.
  • Category
    : If you have many service connectors, each with multiple actions, you can create categories to help users navigate within
    processes
    .
  • Fail on HTTP error
    : Check this option if you want Process Designer to acknowledge that an error occurred when you send a request to a server using this action. For more information see Checking for HTTP Errors.
  • Max Redirects
    : Specifies the maximum number of redirects that an action can make. When an action accesses an endpoint, the endpoint might redirect the action to another endpoint. Enter a value to control the number of redirects.
    The default
    Max Redirects
    value is 100.
    Enter
    0
    to disable redirects.
    For example, if you enter
    3
    , the service connector action makes a maximum of three redirects and receives three redirect responses from the endpoint. If the endpoint requests a fourth redirect response, you see an error message.
  • Preemptive Auth
    : Sends authentication details, that is, user credentials, along with a request to an endpoint. Select
    Preemptive Auth
    when you know that an endpoint requires authentication. If you do not select
    Preemptive Auth
    and the endpoint requires authentication, the following events occur:
    1. The service connector sends a request to the endpoint.
    2. The endpoint requests authentication.
    3. The service connector sends user credentials to the endpoint.
    If you select
    Preemptive Auth
    and the endpoint requires authentication, you avoid an extra request.
  • Action Type
    : You can select one of the following action types for each action. Refer to Shared Service Actions for more information.
    • General
      actions are published for use only with a particular service connector.
    • Abstract
      actions are not published but can be shared with other actions, that is, made available for reuse as a template for other actions.
    • Inherited
      actions inherit properties from an Abstract action.
  • Description
    : Enter a description or notes about this action.
For each action, specify additional details on the
Input
,
Binding
,
Output
, and
Test Results
tabs.


Updated February 11, 2021