Get an event subscriber

get

/fscmRestApi/resources/11.13.18.05/eventSetups/{EventId}/child/eventSubscribers/{EventSubscriberId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : eventSetups-eventSubscribers-item-response
Type: object
Show Source
  • Title: Event Subscriber ID
    Read Only: true
    The unique identifier for the subscriber to an event.
  • Event Subscriber Timing Rules
    Title: Event Subscriber Timing Rules
    The event subscriber timing rules resource provides information on the timing rules for the event subscriber trigger, in relation to the event date. For example, a timing rule could be 2 days before event date.
  • Title: External Indicator
    Read Only: true
    Maximum Length: 1
    Indicates if the target is external, for example, an external SOAP service.
  • Links
  • Title: Payload Target Code
    Read Only: true
    Maximum Length: 30
    The code for the payload target referenced in the target configuration data.
  • Title: Payload Target ID
    Read Only: true
    The resource which will provide the payload information required to process the event successfully.
  • Title: Predefined Data Indicator
    Read Only: true
    Indicates whether the associated row is predefined.
  • Title: Target Code
    Maximum Length: 30
    The code for the target referenced in the target configuration data.
  • Title: Target Description
    Read Only: true
    Maximum Length: 240
    The description of the event subscriber target.
  • Title: Target ID
    The identifier for the subscriber in the target configuration data.
  • Title: Target Name
    Read Only: true
    Maximum Length: 50
    The name of the event subscriber target, such as Communication.
Nested Schema : Event Subscriber Timing Rules
Type: array
Title: Event Subscriber Timing Rules
The event subscriber timing rules resource provides information on the timing rules for the event subscriber trigger, in relation to the event date. For example, a timing rule could be 2 days before event date.
Show Source
Nested Schema : eventSetups-eventSubscribers-eventSubscriberTimingRules-item-response
Type: object
Show Source
  • Title: Event Subscriber Timing Rule ID
    Read Only: true
    The unique identifier for the timing rule associated with the subscriber of an event.
  • Links
  • Title: Predefined Data Indicator
    Read Only: true
    Indicates whether the associated row is predefined.
  • Title: Timing Rule Count
    The counter to keep track of how many times a particular rule has been triggered.
  • Title: Timing Rule Type Code
    Maximum Length: 30
    The code that indicates the timing rule type, for example, ORA_HEY_DAYS and ORA_HEY_MONTHS. A list of accepted values is defined in the lookup type ORA_HEY_PERIOD_TYPE.
  • Title: Timing Rule Type Code Meaning
    Read Only: true
    Maximum Length: 80
    The meaning of the timing rule type code. For example, days for ORA_HEY_DAYS and months for ORA_HEY_MONTHS. A list of accepted values is defined in the lookup type ORA_HEY_PERIOD_TYPE.
  • Title: Transaction Code
    Maximum Length: 30
    The communication setup code that's associated with the timing rule.
Back to Top