Get all work order links

get

/crmRestApi/resources/11.13.18.05/customerWorkOrders/{WoNumber}/child/WoLink

Request

Path Parameters
  • The alternate unique identifier of the work order. This value is system-generated, and is configured in the work order profile options SVC_WO_NUMBER PREFIX and SVC_WO_NUMBER_FORMAT. The default configuration is WO0000000000.
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
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey :Finds a work order link based on the specified work order link unique identifier.
      Finder Variables:
      • WoLinkId :The unique identifier of the work order link.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AssignmentConstraintCd; string; The code that identifies the assignment constraint set on the link template.
    • CreatedBy; string; The user who created the work order link.
    • CreationDate; string; The date and time of creating the work order link.
    • FirstWoId; integer; The unique identifier of the first work order in the link.
    • FirstWoNumber; string; Value that uniquely identifies the alternate unique identifier of the first work order. This value is system-generated, and is configured in the work order profile options SVC_WO_NUMBER PREFIX and SVC_WO_NUMBER_FORMAT. The default configuration is WO0000000000.
    • FirstWoScheduledDate; string; The date when the scheduled service will be performed for the first work order.
    • FirstWoScheduledTimeSlot; string; The time slot to perform the scheduled service for the first work order.
    • FirstWoStatusCd; string; Indicates the work order status code for the first work order.
    • FirstWoTitle; string; The title of the first work order.
    • FsFirstActivityId; integer; The unique identifier of the corresponding first activity in Oracle Field Service Cloud for the work order activity.
    • FsSecondActivityId; integer; The unique identifier of the corresponding second activity in Oracle Field Service Cloud for the work order activity.
    • LastUpdateDate; string; Indicates the date and time of last update for the work order link.
    • LastUpdateSourceCd; string; The source who last updated the work order link.
    • LastUpdatedBy; string; The user who last updated the work order link.
    • LinkTemplateCatCd; string; The code that identifies template category selected for this link template.
    • LinkTemplateCatDirFirstCd; string; The code that identifies template category direction for the first link in this link template.
    • LinkTemplateCatDirFirstCdMeaning; string; The meaning of the template category direction for the first link in this link template.
    • LinkTemplateCatDirSecondCd; string; The code that identifies template category direction for the second link in this link template.
    • LinkTemplateId; integer; The unique identifier of the link template in the link.
    • LinkTemplateNumber; string; Value that uniquely identifies the alternate unique identifier of the template number. This value can be system-generated, or can be configured. The default configuration is CDRM-0000000000.
    • LinkTypeDirectionCd; string; The code that identifies the direction of the link relationship, whether this link is for the first or second work order.
    • LinkTypeLabelFirst; string; The link type label that identifies the link for the first work order. This must exactly match the link label provided in the link template in Oracle Field Service.
    • LinkTypeLabelSecond; string; The link type label that identifies the link for the second work order. This must exactly match the link label provided in the link template in Oracle Field Service.
    • LinkTypeNameFirst; string; The link type name that identifies the link for the first work order.
    • LinkTypeNameSecond; string; The link type name that identifies the link for the second work order.
    • MaximumIntervalMinutes; integer; The default maximum interval in minutes.
    • MaximumIntervalTypeCd; string; The code that identifies the maximum interval type between work order set on the link template.
    • MaximumIntervalValue; integer; The actual maximum interval in minutes for this link.
    • MinimumIntervalMinutes; integer; The default minimum interval in minutes.
    • MinimumIntervalTypeCd; string; The code that identifies the minimum interval type between work order set on the link template.
    • MinimumIntervalValue; integer; The actual minimum interval in minutes for this link.
    • SchedulingConstraintCd; string; The code that identifies the scheduling constraint set on the link template.
    • SecondWoId; integer; The unique identifier of the second work order in the link.
    • SecondWoNumber; string; Value that uniquely identifies the alternate unique identifier of the second work order. This value is system-generated, and is configured in the work order profile options SVC_WO_NUMBER PREFIX and SVC_WO_NUMBER_FORMAT. The default configuration is WO0000000000.
    • SecondWoScheduledDate; string; The date of when the scheduled service will be performed for the second work order.
    • SecondWoScheduledTimeSlot; string; The time slot to perform the scheduled service for the second work order.
    • SecondWoStatusCd; string; Indicates the work order status code for the second work order.
    • SecondWoTitle; string; The title of the second work order.
    • TemplateActiveFlag; boolean; Indicates if link template for the link is active.
    • WoLinkId; integer; The unique identifier of the work order link.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 ()
Back to Top