Get a step task

get

/hcmRestApi/resources/11.13.18.05/workerJourneys/{WorkerJourneyId}/child/allStepTasks/{allStepTasksUniqID}

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=
  • This is the hash key of the attributes which make up the composite key for the All Step Tasks resource and used to uniquely identify an instance of All Step Tasks. The client should not generate the hash key value. Instead, the client should query on the All Step Tasks collection resource in order to navigate to a specific instance of All Step Tasks to get the hash key.
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 : workerJourneys-allStepTasks-item-response
Type: object
Show Source
  • Title: Access Task
    Read Only: true
    Setting that determines if the signed in user can access the task.
  • Title: Access Attachments
    Read Only: true
    Setting that determines if the signed in user can access the task attachments.
  • Title: Access Comments
    Read Only: true
    Setting that determines if the signed in user can access the task comments.
  • Title: Access Contact Information
    Read Only: true
    Setting that determines if the signed in user can access the task contact details.
  • Title: Access Notes
    Read Only: true
    Setting that determines if the signed in user can access the task notes.
  • Title: Mark as Complete
    Read Only: true
    Setting that determines if the signed in user can mark the task as complete.
  • Title: Edit
    Read Only: true
    Setting that determines if the signed in user can edit the task.
  • Title: Edit Due Date
    Read Only: true
    Setting that determines if the signed in user can edit the due date of the task.
  • Title: Reassign
    Read Only: true
    Setting that determines if the signed in user can reassign the task.
  • Title: Mark as Not Applicable
    Read Only: true
    Setting that determines if the signed in user can mark the task as not applicable.
  • Title: Remove
    Read Only: true
    Setting that determines if the signed in user can remove the task.
  • Title: Reopen
    Read Only: true
    Setting that determines if the signed in user can reopen a completed task.
  • Title: Send Reminder
    Read Only: true
    Setting that determines if the signed in user can send a reminder for a task.
  • Title: URL
    Read Only: true
    Maximum Length: 1000
    URL associated with the task that's entered on the setup screen.
  • Title: Actual End Date
    Read Only: true
    End date of the task.
  • Title: Actual Start Date
    Read Only: true
    Date on which the task was opened.
  • Title: Allow Attachments
    Read Only: true
    Indicates whether attachments are enabled for a task. Valid values are Yes and No. The default value is No.
  • Title: Allow Comments
    Read Only: true
    Indicates whether comments are enabled for a task. Valid values are Yes and No. The default value is No.
  • Title: Enable Notes Title
    Read Only: true
    Indicates whether the Notes title is hidden or not. Valid values are Yes and No. The default value is No.
  • Title: Application Task
    Read Only: true
    Display name of the application task.
  • Title: Comments
    Read Only: true
    Maximum Length: 4000
    Comments for the task.
  • Title: Completed by Person Name
    Read Only: true
    Name of the person who completed the task.
  • Title: Completed by Person ID
    Read Only: true
    Person identifier of the person who completed the task.
  • Title: Completed On
    Read Only: true
    Date on which the task was completed.
  • Title: Configurable Form
    Read Only: true
    Maximum Length: 80
    Descriptive flexfield context code for configurable form task type.
  • Title: Deferred Task Start Date
    Read Only: true
    Start date for the deferred task.
  • Title: Preceding Task ID
    Read Only: true
    Primary key or unique identifier of the dependent task.
  • Title: Preceding Task
    Read Only: true
    Maximum Length: 240
    Name of the dependent task.
  • Title: Description
    Read Only: true
    Maximum Length: 4000
    Description of the task.
  • Links
  • Title: Name
    Read Only: true
    Maximum Length: 240
    Name of the journey task.
  • Title: Notes
    Read Only: true
    Notes for the task. The notes text is stored as a CLOB object. To use in the payload, the text should be converted to a base64 encoded string using either a conversion tool or a prerequisite script.
  • Title: Notes Title
    Read Only: true
    Maximum Length: 150
    Title of the Notes section in the task.
  • Read Only: true
    Indicates whether the external URL should open in the existing page or a new page. Valid values are Yes and No. The default value is No.
  • Title: Owner Name
    Read Only: true
    Person display name of task owner in case of single owner. Else, returns responsibility type name.
  • Title: Owner Person ID
    Read Only: true
    Identifier of the task owner. Applicable only in case of a single task owner.
  • Title: Owner Type
    Read Only: true
    Maximum Length: 30
    Task owner type.
  • Title: Owner
    Read Only: true
    Task owner type meaning.
  • Title: Worker Journey ID
    Read Only: true
    Unique identifier of the parent enterprise onboarding checklist.
  • Title: Performer Name
    Read Only: true
    Person display name of task performer in case of single performer. Else, returns responsibility type name.
  • Title: Performer Person ID
    Read Only: true
    Person identifier of the task performer. Applicable only in case of a single task performer.
  • Title: Performer Type
    Read Only: true
    Task performer type.
  • Title: Performer
    Read Only: true
    Task performer type meaning.
  • Title: Report Path
    Read Only: true
    Maximum Length: 1000
    Path to the report in BI Catalog.
  • Title: Required
    Read Only: true
    Maximum Length: 30
    Indicates whether the task is mandatory or optional. Valid values are Yes and No. The default value is No.
  • Title: Sequence
    Read Only: true
    Task display ordering sequence. Default is 1.
  • Title: IP Address of Signature
    Read Only: true
    Maximum Length: 120
    Internet protocol address where the electronic signature was provided.
  • Title: Date of Signature
    Read Only: true
    Date on which the electronic signature was provided for an electronic signature task.
  • Title: Email of Signer
    Read Only: true
    Maximum Length: 400
    Email address of the signer for an electronic signature task.
  • Title: Name of Signer
    Read Only: true
    Maximum Length: 120
    Name of the signer for an electronic signature task.
  • Read Only: true
    Name of the phase in a journey with multiple phases.
  • Read Only: true
    Sequence of the phase in a journey with multiple phases.
  • Title: Status Code
    Read Only: true
    Maximum Length: 60
    Code for the task status.
  • Title: Status Category
    Read Only: true
    Category of the status.
  • Title: Status
    Read Only: true
    Maximum Length: 80
    Status of the task.
  • Title: Subtype Code
    Read Only: true
    Maximum Length: 30
    Task action subtype code. Available only for I 9 and Electronic Signature task types.
  • Title: Subtype
    Read Only: true
    Task action subtype. Available only for I 9 and Electronic Signature task types.
  • Title: Target End Date
    Read Only: true
    Due date of the task.
  • Title: Target Start Date
    Read Only: true
    Expected initiation date of the task.
  • Title: Type Code
    Read Only: true
    Maximum Length: 80
    Code for the task action type.
  • Title: Type
    Read Only: true
    Maximum Length: 80
    Meaning of the task type.
  • Title: Journey Task ID
    Read Only: true
    Unique identifier of the journey task.
Back to Top