Get all workorders

get

/fscmRestApi/resources/11.13.18.05/maintenanceWorkOrderServiceHistory

Request

Query Parameters
  • 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 resources according to the primary key.
      Finder Variables:
      • WorkOrderId; integer; Value that uniquely identifies the work order.
  • 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:
    • ActualCompletionDate; string; Date when the work order actually completes. The value of this attribute is set when the status of the work order is moved to completed.
    • ActualStartDate; string; Date when the work order actually starts. The value of this attribute is set when the first transaction is performed against the work order.
    • ClosedDate; string; Date when the work order is closed.
    • CreatedBy; string; Session login associated with the user who created the record.
    • CreationDate; string; Date when the record was created.
    • InventoryItemId; integer; Value that uniquely identifies the item that the work order asset references.
    • LastUpdateDate; string; Date when the record was most recently updated.
    • LastUpdatedBy; string; Session login associated with the user who most recently updated the record.
    • PlannedCompletionDate; string; Date when the work order is scheduled to complete. The default value is the system date.
    • PlannedStartDate; string; Date when the work order is scheduled to start. The default value is the system date.
    • ReleasedDate; string; Date when the work order is released.
    • WorkOrderDescription; string; Description of the work order. This is the text entered by the user, which briefly describes the work to be performed. This attribute is optional to create a work order.
    • WorkOrderId; integer; Value that uniquely identifies the work order. This attribute is read-only. The value of this attribute is derived from the work order number when the application creates the work order.
    • WorkOrderNumber; string; Number that identifies the work order. This number is unique in the organization. The user can manually assign the number when creating the work order, or allow the application to create a unique number from the numbering scheme that the following Plant parameters define: Work Order Prefix or Work Order Starting Number.
    • WorkOrderSubTypeCode; string; Abbreviation that uniquely identifies the work order subtype. The list of accepted values is defined in lookup type ORA_MNT_WO_SUB_TYPE.
    • WorkOrderTypeCode; string; Abbreviation that uniquely identifies the work order type. Valid values include CORRECTIVE or PREVENTIVE. A list of accepted values is defined in the lookup type ORA_MNT_WO_TYPE.
  • 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 ()
Root Schema : maintenanceWorkOrderServiceHistory
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : maintenanceWorkOrderServiceHistory-item-response
Type: object
Show Source
  • Title: Actual Completion Date
    Read Only: true
    Date when the work order actually completes. The value of this attribute is set when the status of the work order is moved to completed.
  • Title: Actual Start Date
    Read Only: true
    Date when the work order actually starts. The value of this attribute is set when the first transaction is performed against the work order.
  • Title: Closed Date
    Read Only: true
    Date when the work order is closed.
  • Read Only: true
    Maximum Length: 64
    Session login associated with the user who created the record.
  • Read Only: true
    Date when the record was created.
  • Title: Item
    Read Only: true
    Value that uniquely identifies the item that the work order asset references.
  • Read Only: true
    Date when the record was most recently updated.
  • Read Only: true
    Maximum Length: 64
    Session login associated with the user who most recently updated the record.
  • Links
  • Title: Completion Date
    Read Only: true
    Date when the work order is scheduled to complete. The default value is the system date.
  • Title: Start Date
    Read Only: true
    Date when the work order is scheduled to start. The default value is the system date.
  • Title: Released Date
    Read Only: true
    Date when the work order is released.
  • Title: Description
    Read Only: true
    Maximum Length: 240
    Description of the work order. This is the text entered by the user, which briefly describes the work to be performed. This attribute is optional to create a work order.
  • Read Only: true
    Value that uniquely identifies the work order. This attribute is read-only. The value of this attribute is derived from the work order number when the application creates the work order.
  • Title: Work Order
    Read Only: true
    Maximum Length: 120
    Number that identifies the work order. This number is unique in the organization. The user can manually assign the number when creating the work order, or allow the application to create a unique number from the numbering scheme that the following Plant parameters define: Work Order Prefix or Work Order Starting Number.
  • Title: Subtype
    Read Only: true
    Maximum Length: 30
    Abbreviation that uniquely identifies the work order subtype. The list of accepted values is defined in lookup type ORA_MNT_WO_SUB_TYPE.
  • Title: Type
    Read Only: true
    Maximum Length: 30
    Abbreviation that uniquely identifies the work order type. Valid values include CORRECTIVE or PREVENTIVE. A list of accepted values is defined in the lookup type ORA_MNT_WO_TYPE.
Back to Top