Update an asset failure event

patch

/fscmRestApi/resources/11.13.18.05/assetFailureEvents/{FailureEventId}/child/failureInstances/{FailureInstanceId}/child/rootCauses/{RootCauseId}

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=
  • 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=
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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Cause Code ID
    Value that uniquely identifies the root cause code. The value is system generated and read-only.
  • Title: Failure Instance ID
    Value that uniquely identifies the failure instance. The value is system generated and read-only.
  • Title: Cause Code
    Abbreviation that uniquely identifies the root cause of failure. The root cause code is required and if entered must be a valid code. The code must use uppercase letters and alphanumeric.
  • Title: Comments
    Maximum Length: 2000
    Notes captured with free-text details about the causes and root cause of failure, or any other relevant data. This value is optional.
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 : assetFailureEvents-failureInstances-rootCauses-item-response
Type: object
Show Source
  • Title: Cause Code ID
    Value that uniquely identifies the root cause code. The value is system generated and read-only.
  • Read Only: true
    Maximum Length: 64
    User who created the failure root cause. The application automatically sets this value during creation. This attribute is read-only.
  • Read Only: true
    Date when the failure root cause is created. The application automatically sets this value during creation. This attribute is read-only.
  • Title: Failure Instance ID
    Value that uniquely identifies the failure instance. The value is system generated and read-only.
  • Read Only: true
    Date when the user most recently updated the failure root cause. The application automatically sets this value during creation. This attribute is read-only.
  • Read Only: true
    Maximum Length: 64
    User who most recently updated the failure root cause. The application assigns a value to this attribute during creation. This attribute is read-only.
  • Read Only: true
    Maximum Length: 32
    Login that the user used when updating the failure root cause. The application assigns a value to this attribute during creation. This attribute is read-only.
  • Links
  • Title: Cause Category Code
    Read Only: true
    Maximum Length: 30
    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: Cause Category Name
    Read Only: true
    Maximum Length: 255
    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: Cause Code
    Abbreviation that uniquely identifies the root cause of failure. The root cause code is required and if entered must be a valid code. The code must use uppercase letters and alphanumeric.
  • Title: Comments
    Maximum Length: 2000
    Notes captured with free-text details about the causes and root cause of failure, or any other relevant data. This value is optional.
  • Title: Cause Description
    Read Only: true
    Maximum Length: 540
    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: Root Cause ID
    Read Only: true
    Value that uniquely identifies the root cause. The value is system generated and read-only.
  • Title: Cause Name
    Read Only: true
    Maximum Length: 240
    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.
Back to Top