Jump to

• Request
• Response
• Examples

Get all missing time cards for a project

get

/fscmRestApi/resources/11.13.18.05/projectInsights/{ProjectId}/child/MissingTimeCards

Request

Path Parameters

• ProjectId(required): integer(int64)
  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

• dependency: string
  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>
• expand: string
  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).
• fields: string
  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
• finder: string
  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 the missing time card with the specified primary key.
    Finder Variables
  • findByResourceId Finds the missing time cards for the resource with the specified resource identifier.
    Finder Variables
    • ResourceId; integer; The unique identifier of the project enterprise labor resource.
• limit: integer
  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.
• links: string
  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
  
• offset: integer
  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.
• onlyData: boolean
  The resource item payload will be filtered in order to contain only data (no links section, for example).
• orderBy: string
  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
• q: string
  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:
  

  • CategoryCodeForFiveWeeksAgo; string; The code that represents the categorization of the missing time card for the week ending five weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryCodeForFourWeeksAgo; string; The code that represents the categorization of the missing time card for the week ending four weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryCodeForOneWeekAgo; string; The code that represents the categorization of the missing time card for the week ending one week ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryCodeForThreeWeeksAgo; string; The code that represents the categorization of the missing time card for the week ending three weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryCodeForTwoWeeksAgo; string; The code that represents the categorization of the missing time card for the week ending two weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryForFiveWeeksAgo; string; The categorization of the missing time card for the week ending five weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryForFourWeeksAgo; string; The categorization of the missing time card for the week ending four weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryForOneWeekAgo; string; The categorization of the missing time card for the week ending one week ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryForThreeWeeksAgo; string; The categorization of the missing time card for the week ending three weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CategoryForTwoWeeksAgo; string; The categorization of the missing time card for the week ending two weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentCodeForFiveWeeksAgo; string; The code that represents the additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentCodeForFourWeeksAgo; string; The code that represents the additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentCodeForOneWeekAgo; string; The code that represents the additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentCodeForThreeWeeksAgo; string; The code that represents the additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentCodeForTwoWeeksAgo; string; The code that represents the additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentForFiveWeeksAgo; string; Additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentForFourWeeksAgo; string; Additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentForOneWeekAgo; string; Additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentForThreeWeeksAgo; string; Additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CommentForTwoWeeksAgo; string; Additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • CreatedBy; string; The user who created the record.
  • CreationDate; string; The date when the record was created.
  • DefaultHoursFiveWeeksAgo; number; The default hours for the week ending five weeks ago for the resource and project.
  • DefaultHoursFourWeeksAgo; number; The default hours for the week ending four weeks ago for the resource and project.
  • DefaultHoursOneWeekAgo; number; The default hours for the week ending one week ago for the resource and project.
  • DefaultHoursThreeWeeksAgo; number; The default hours for the week ending three weeks ago for the resource and project.
  • DefaultHoursTwoWeeksAgo; number; The default hours for the week ending two weeks ago for the resource and project.
  • LastUpdateDate; string; The date when the record was last updated.
  • LastUpdatedBy; string; The user who last updated the record.
  • ResourceId; integer; The unique identifier of the project enterprise labor resource.
  • ResourceName; string; The name of the project enterprise labor resource.
  • ScheduledHoursFiveWeeksAgo; number; The effort in hours for the week ending five weeks ago for the resource and project.
  • ScheduledHoursFourWeeksAgo; number; The effort in hours for the week ending four weeks ago for the resource and project.
  • ScheduledHoursOneWeekAgo; number; The effort in hours for the week ending one week ago for the resource and project.
  • ScheduledHoursThreeWeeksAgo; number; The effort in hours for the week ending three weeks ago for the resource and project.
  • ScheduledHoursTwoWeeksAgo; number; The effort in hours for the week ending two weeks ago for the resource and project.
  • TimeCardHoursFiveWeeksAgo; number; The effort in hours reported on a time card for the week ending five weeks ago for the resource and project.
  • TimeCardHoursFourWeeksAgo; number; The effort in hours reported on a time card for the week ending four weeks ago for the resource and project.
  • TimeCardHoursOneWeekAgo; number; The effort in hours reported on a time card for the week ending one week ago for the resource and project.
  • TimeCardHoursThreeWeeksAgo; number; The effort in hours reported on a time card for the week ending three weeks ago for the resource and project.
  • TimeCardHoursTwoWeeksAgo; number; The effort in hours reported on a time card for the week ending two weeks ago for the resource and project.
• totalResults: boolean
  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

• Metadata-Context:
  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".
• REST-Framework-Version:
  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

• application/json

Default Response

The following table describes the default response for this task.

Headers

• Metadata-Context:
  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".
• REST-Framework-Version:
  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 : projectInsights-MissingTimeCards

Type: object

Show Source

• count(required): integer
  The number of resource instances returned in the current range.
• hasMore(required): boolean
  Indicates whether more resources are available on the server than the subset returned in the response. If the value is true, then there are more resources to retrieve from the server. The default value is false.
• items: array Items
  Title: Items

  The items in the collection.
• limit(required): integer
  The actual paging size used by the server.
• links(required): array Links
  Title: Links

  The link relations associated with the resource instance.
• offset(required): integer
  The offset value used in the current page.
• totalResults: integer
  The estimated row count when "?totalResults=true", otherwise the count is not included.

{
    "required":[
        "count",
        "hasMore",
        "limit",
        "links",
        "offset"
    ],
    "type":"object",
    "properties":{
        "totalResults":{
            "type":"integer",
            "description":"The estimated row count when \"?totalResults=true\", otherwise the count is not included."
        },
        "offset":{
            "type":"integer",
            "description":"The offset value used in the current page."
        },
        "count":{
            "type":"integer",
            "description":"The number of resource instances returned in the current range."
        },
        "hasMore":{
            "type":"boolean",
            "description":"Indicates whether more resources are available on the server than the subset returned in the response. If the value is true, then there are more resources to retrieve from the server. The default value is false."
        },
        "limit":{
            "type":"integer",
            "description":"The actual paging size used by the server."
        },
        "links":{
            "title":"Links",
            "type":"array",
            "description":"The link relations associated with the resource instance.",
            "items":{
                "$ref":"#/components/schemas/link"
            }
        },
        "items":{
            "title":"Items",
            "type":"array",
            "description":"The items in the collection.",
            "items":{
                "$ref":"#/components/schemas/projectInsights-MissingTimeCards-item-response"
            }
        }
    }
}

Nested Schema : Items

Type: array

Title: Items

The items in the collection.

Show Source

• Array of: object projectInsights-MissingTimeCards-item-response

{
    "title":"Items",
    "type":"array",
    "description":"The items in the collection.",
    "items":{
        "$ref":"#/components/schemas/projectInsights-MissingTimeCards-item-response"
    }
}

Nested Schema : Links

Type: array

Title: Links

The link relations associated with the resource instance.

Show Source

• Array of: object link

{
    "title":"Links",
    "type":"array",
    "description":"The link relations associated with the resource instance.",
    "items":{
        "$ref":"#/components/schemas/link"
    }
}

Nested Schema : projectInsights-MissingTimeCards-item-response

Type: object

Show Source

• CategoryCodeForFiveWeeksAgo: string
  Title: Category Code for Five Weeks Old Missing Time Card

  Maximum Length: 30

  The code that represents the categorization of the missing time card for the week ending five weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryCodeForFourWeeksAgo: string
  Title: Category Code for Four Weeks Old Missing Time Card

  Maximum Length: 30

  The code that represents the categorization of the missing time card for the week ending four weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryCodeForOneWeekAgo: string
  Title: Category Code for One Week Old Missing Time Card

  Maximum Length: 30

  The code that represents the categorization of the missing time card for the week ending one week ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryCodeForThreeWeeksAgo: string
  Title: Category Code for Three Weeks Old Missing Time Card

  Maximum Length: 30

  The code that represents the categorization of the missing time card for the week ending three weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryCodeForTwoWeeksAgo: string
  Title: Category Code for Two Weeks Old Missing Time Card

  Maximum Length: 30

  The code that represents the categorization of the missing time card for the week ending two weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryForFiveWeeksAgo: string
  Title: Category for Five Weeks Old Missing Time Card

  The categorization of the missing time card for the week ending five weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryForFourWeeksAgo: string
  Title: Category for Four Weeks Old Missing Time Card

  The categorization of the missing time card for the week ending four weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryForOneWeekAgo: string
  Title: Category for One Week Old Missing Time Card

  The categorization of the missing time card for the week ending one week ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryForThreeWeeksAgo: string
  Title: Category for Three Weeks Old Missing Time Card

  The categorization of the missing time card for the week ending three weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CategoryForTwoWeeksAgo: string
  Title: Category for Two Weeks Old Missing Time Card

  The categorization of the missing time card for the week ending two weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentCodeForFiveWeeksAgo: string
  Title: Commentary Code for Five Weeks Old Time Card

  Maximum Length: 30

  The code that represents the additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentCodeForFourWeeksAgo: string
  Title: Commentary Code for Four Weeks Old Time Card

  Maximum Length: 30

  The code that represents the additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentCodeForOneWeekAgo: string
  Title: Commentary Code for One Week Old Time Card

  Maximum Length: 30

  The code that represents the additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentCodeForThreeWeeksAgo: string
  Title: Commentary Code for Three Weeks Old Time Card

  Maximum Length: 30

  The code that represents the additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentCodeForTwoWeeksAgo: string
  Title: Commentary Code for Two Weeks Old Time Card

  Maximum Length: 30

  The code that represents the additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentForFiveWeeksAgo: string
  Title: Commentary for Five Weeks Old Time Card

  Additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentForFourWeeksAgo: string
  Title: Commentary for Four Weeks Old Time Card

  Additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentForOneWeekAgo: string
  Title: Commentary for One Week Old Time Card

  Additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentForThreeWeeksAgo: string
  Title: Commentary for Three Weeks Old Time Card

  Additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CommentForTwoWeeksAgo: string
  Title: Commentary for Two Weeks Old Time Card

  Additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
• CreatedBy: string
  Title: Created By

  Maximum Length: 64

  The user who created the record.
• CreationDate: string (date-time)
  Title: Creation Date

  The date when the record was created.
• DefaultHoursFiveWeeksAgo: number
  Title: Default Hours Five Weeks Ago

  The default hours for the week ending five weeks ago for the resource and project.
• DefaultHoursFourWeeksAgo: number
  Title: Default Hours Four Weeks Ago

  The default hours for the week ending four weeks ago for the resource and project.
• DefaultHoursOneWeekAgo: number
  Title: Default Hours One Week Ago

  The default hours for the week ending one week ago for the resource and project.
• DefaultHoursThreeWeeksAgo: number
  Title: Default Hours Three Weeks Ago

  The default hours for the week ending three weeks ago for the resource and project.
• DefaultHoursTwoWeeksAgo: number
  Title: Default Hours Two Weeks Ago

  The default hours for the week ending two weeks ago for the resource and project.
• LastUpdateDate: string (date-time)
  Title: Last Update Date

  The date when the record was last updated.
• LastUpdatedBy: string
  Title: Last Updated By

  Maximum Length: 64

  The user who last updated the record.
• links: array Links
  Title: Links

  The link relations associated with the resource instance.
• ResourceId: integer (int64)
  Title: Resource ID

  Read Only: true

  The unique identifier of the project enterprise labor resource.
• ResourceName: string
  Title: Resource Name

  Read Only: true

  Maximum Length: 240

  The name of the project enterprise labor resource.
• ScheduledHoursFiveWeeksAgo: number
  Title: Scheduled Hours Five Weeks Ago

  The effort in hours for the week ending five weeks ago for the resource and project.
• ScheduledHoursFourWeeksAgo: number
  Title: Scheduled Hours Four Weeks Ago

  The effort in hours for the week ending four weeks ago for the resource and project.
• ScheduledHoursOneWeekAgo: number
  Title: Scheduled Hours One Week Ago

  The effort in hours for the week ending one week ago for the resource and project.
• ScheduledHoursThreeWeeksAgo: number
  Title: Scheduled Hours Three Weeks Ago

  The effort in hours for the week ending three weeks ago for the resource and project.
• ScheduledHoursTwoWeeksAgo: number
  Title: Scheduled Hours Two Weeks Ago

  The effort in hours for the week ending two weeks ago for the resource and project.
• TimeCardHoursFiveWeeksAgo: number
  Title: Time Card Hours Five Weeks Ago

  The effort in hours reported on a time card for the week ending five weeks ago for the resource and project.
• TimeCardHoursFourWeeksAgo: number
  Title: Time Card Hours Four Weeks Ago

  The effort in hours reported on a time card for the week ending four weeks ago for the resource and project.
• TimeCardHoursOneWeekAgo: number
  Title: Time Card Hours One Week Ago

  The effort in hours reported on a time card for the week ending one week ago for the resource and project.
• TimeCardHoursThreeWeeksAgo: number
  Title: Time Card Hours Three Weeks Ago

  The effort in hours reported on a time card for the week ending three weeks ago for the resource and project.
• TimeCardHoursTwoWeeksAgo: number
  Title: Time Card Hours Two Weeks Ago

  The effort in hours reported on a time card for the week ending two weeks ago for the resource and project.

{
    "type":"object",
    "properties":{
        "CreationDate":{
            "title":"Creation Date",
            "type":"string",
            "description":"The date when the record was created.",
            "format":"date-time",
            "nullable":false,
            "x-queryable":true
        },
        "DefaultHoursTwoWeeksAgo":{
            "title":"Default Hours Two Weeks Ago",
            "type":"number",
            "description":"The default hours for the week ending two weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "ResourceName":{
            "title":"Resource Name",
            "maxLength":"240",
            "type":"string",
            "description":"The name of the project enterprise labor resource.",
            "nullable":false,
            "readOnly":true,
            "x-queryable":true
        },
        "DefaultHoursThreeWeeksAgo":{
            "title":"Default Hours Three Weeks Ago",
            "type":"number",
            "description":"The default hours for the week ending three weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryForThreeWeeksAgo":{
            "title":"Category for Three Weeks Old Missing Time Card",
            "type":"string",
            "description":"The categorization of the missing time card for the week ending three weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentCodeForTwoWeeksAgo":{
            "title":"Commentary Code for Two Weeks Old Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "ScheduledHoursOneWeekAgo":{
            "title":"Scheduled Hours One Week Ago",
            "type":"number",
            "description":"The effort in hours for the week ending one week ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "DefaultHoursFiveWeeksAgo":{
            "title":"Default Hours Five Weeks Ago",
            "type":"number",
            "description":"The default hours for the week ending five weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "ScheduledHoursFourWeeksAgo":{
            "title":"Scheduled Hours Four Weeks Ago",
            "type":"number",
            "description":"The effort in hours for the week ending four weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentCodeForFourWeeksAgo":{
            "title":"Commentary Code for Four Weeks Old Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "DefaultHoursOneWeekAgo":{
            "title":"Default Hours One Week Ago",
            "type":"number",
            "description":"The default hours for the week ending one week ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "ScheduledHoursThreeWeeksAgo":{
            "title":"Scheduled Hours Three Weeks Ago",
            "type":"number",
            "description":"The effort in hours for the week ending three weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "TimeCardHoursTwoWeeksAgo":{
            "title":"Time Card Hours Two Weeks Ago",
            "type":"number",
            "description":"The effort in hours reported on a time card for the week ending two weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "TimeCardHoursThreeWeeksAgo":{
            "title":"Time Card Hours Three Weeks Ago",
            "type":"number",
            "description":"The effort in hours reported on a time card for the week ending three weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "ScheduledHoursFiveWeeksAgo":{
            "title":"Scheduled Hours Five Weeks Ago",
            "type":"number",
            "description":"The effort in hours for the week ending five weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryForTwoWeeksAgo":{
            "title":"Category for Two Weeks Old Missing Time Card",
            "type":"string",
            "description":"The categorization of the missing time card for the week ending two weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "ScheduledHoursTwoWeeksAgo":{
            "title":"Scheduled Hours Two Weeks Ago",
            "type":"number",
            "description":"The effort in hours for the week ending two weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "links":{
            "title":"Links",
            "type":"array",
            "description":"The link relations associated with the resource instance.",
            "items":{
                "$ref":"#/components/schemas/link"
            }
        },
        "LastUpdatedBy":{
            "title":"Last Updated By",
            "maxLength":"64",
            "type":"string",
            "description":"The user who last updated the record.",
            "nullable":false,
            "x-queryable":true
        },
        "CreatedBy":{
            "title":"Created By",
            "maxLength":"64",
            "type":"string",
            "description":"The user who created the record.",
            "nullable":false,
            "x-queryable":true
        },
        "TimeCardHoursFiveWeeksAgo":{
            "title":"Time Card Hours Five Weeks Ago",
            "type":"number",
            "description":"The effort in hours reported on a time card for the week ending five weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryForOneWeekAgo":{
            "title":"Category for One Week Old Missing Time Card",
            "type":"string",
            "description":"The categorization of the missing time card for the week ending one week ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentForOneWeekAgo":{
            "title":"Commentary for One Week Old Time Card",
            "type":"string",
            "description":"Additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentForThreeWeeksAgo":{
            "title":"Commentary for Three Weeks Old Time Card",
            "type":"string",
            "description":"Additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentCodeForOneWeekAgo":{
            "title":"Commentary Code for One Week Old Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentCodeForFiveWeeksAgo":{
            "title":"Commentary Code for Five Weeks Old Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryCodeForTwoWeeksAgo":{
            "title":"Category Code for Two Weeks Old Missing Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the categorization of the missing time card for the week ending two weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentForFiveWeeksAgo":{
            "title":"Commentary for Five Weeks Old Time Card",
            "type":"string",
            "description":"Additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "DefaultHoursFourWeeksAgo":{
            "title":"Default Hours Four Weeks Ago",
            "type":"number",
            "description":"The default hours for the week ending four weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "TimeCardHoursOneWeekAgo":{
            "title":"Time Card Hours One Week Ago",
            "type":"number",
            "description":"The effort in hours reported on a time card for the week ending one week ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryCodeForOneWeekAgo":{
            "title":"Category Code for One Week Old Missing Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the categorization of the missing time card for the week ending one week ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "TimeCardHoursFourWeeksAgo":{
            "title":"Time Card Hours Four Weeks Ago",
            "type":"number",
            "description":"The effort in hours reported on a time card for the week ending four weeks ago for the resource and project.",
            "nullable":true,
            "x-queryable":true
        },
        "ResourceId":{
            "title":"Resource ID",
            "type":"integer",
            "description":"The unique identifier of the project enterprise labor resource.",
            "format":"int64",
            "nullable":false,
            "readOnly":true,
            "x-hints":{
                "precision":"18"
            },
            "x-queryable":true
        },
        "CategoryForFourWeeksAgo":{
            "title":"Category for Four Weeks Old Missing Time Card",
            "type":"string",
            "description":"The categorization of the missing time card for the week ending four weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryCodeForThreeWeeksAgo":{
            "title":"Category Code for Three Weeks Old Missing Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the categorization of the missing time card for the week ending three weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryForFiveWeeksAgo":{
            "title":"Category for Five Weeks Old Missing Time Card",
            "type":"string",
            "description":"The categorization of the missing time card for the week ending five weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentForTwoWeeksAgo":{
            "title":"Commentary for Two Weeks Old Time Card",
            "type":"string",
            "description":"Additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentCodeForThreeWeeksAgo":{
            "title":"Commentary Code for Three Weeks Old Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CommentForFourWeeksAgo":{
            "title":"Commentary for Four Weeks Old Time Card",
            "type":"string",
            "description":"Additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryCodeForFiveWeeksAgo":{
            "title":"Category Code for Five Weeks Old Missing Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the categorization of the missing time card for the week ending five weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "CategoryCodeForFourWeeksAgo":{
            "title":"Category Code for Four Weeks Old Missing Time Card",
            "maxLength":"30",
            "type":"string",
            "description":"The code that represents the categorization of the missing time card for the week ending four weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.",
            "nullable":true,
            "x-queryable":true
        },
        "LastUpdateDate":{
            "title":"Last Update Date",
            "type":"string",
            "description":"The date when the record was last updated.",
            "format":"date-time",
            "nullable":false,
            "x-queryable":true
        }
    }
}

Nested Schema : Links

Type: array

Title: Links

The link relations associated with the resource instance.

Show Source

• Array of: object link

{
    "title":"Links",
    "type":"array",
    "description":"The link relations associated with the resource instance.",
    "items":{
        "$ref":"#/components/schemas/link"
    }
}

Nested Schema : link

Type: object

Show Source

• href: string
  Title: hyperlink reference

  The URI to the related resource.
• kind: string
  Title: kind

  Allowed Values: [ "collection", "item", "describe", "other" ]

  The kind of the related resource.
• name: string
  Title: name

  The name of the link to the related resource.
• properties: object properties
• rel: string
  Title: relation

  Allowed Values: [ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]

  The name of the relation to the resource instance. Example: self.

{
    "type":"object",
    "properties":{
        "kind":{
            "title":"kind",
            "type":"string",
            "description":"The kind of the related resource.",
            "enum":[
                "collection",
                "item",
                "describe",
                "other"
            ]
        },
        "rel":{
            "title":"relation",
            "type":"string",
            "description":"The name of the relation to the resource instance.  Example: self.",
            "enum":[
                "self",
                "lov",
                "parent",
                "canonical",
                "child",
                "enclosure",
                "action",
                "custom"
            ]
        },
        "name":{
            "title":"name",
            "type":"string",
            "description":"The name of the link to the related resource."
        },
        "href":{
            "title":"hyperlink reference",
            "type":"string",
            "description":"The URI to the related resource."
        },
        "properties":{
            "type":"object",
            "properties":{
                "changeIndicator":{
                    "type":"string",
                    "description":"Change indicator or the ETag value of the resource instance."
                }
            }
        }
    }
}

Nested Schema : properties

Type: object

Show Source

• changeIndicator: string
  Change indicator or the ETag value of the resource instance.

{
    "type":"object",
    "properties":{
        "changeIndicator":{
            "type":"string",
            "description":"Change indicator or the ETag value of the resource instance."
        }
    }
}

Back to Top

Examples

The following example shows how to get all missing time cards for a project by submitting a GET request on the REST resource using cURL.

curl --user ppm_cloud_user https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectInsights/300100061807448/child/MissingTimeCards

Response Body Example

The following shows an example of the response body in JSON format of all project templates.

{
  "items": [
    {
      "ResourceId": 300100023180799,
      "ResourceName": "George White",
      "DefaultHoursFiveWeeksAgo": 40,
      "ScheduledHoursFiveWeeksAgo": null,
      "TimeCardHoursFiveWeeksAgo": null,
      "CategoryForFiveWeeksAgo": null,
      "CategoryCodeForFiveWeeksAgo": null,
      "CommentForFiveWeeksAgo": null,
      "CommentCodeForFiveWeeksAgo": null,
      "DefaultHoursFourWeeksAgo": 40,
      "ScheduledHoursFourWeeksAgo": null,
      "TimeCardHoursFourWeeksAgo": null,
      "CategoryForFourWeeksAgo": null,
      "CategoryCodeForFourWeeksAgo": null,
      "CommentForFourWeeksAgo": null,
      "CommentCodeForFourWeeksAgo": null,
      "DefaultHoursThreeWeeksAgo": 40,
      "ScheduledHoursThreeWeeksAgo": null,
      "TimeCardHoursThreeWeeksAgo": 32,
      "CategoryForThreeWeeksAgo": "In Process",
      "CategoryCodeForThreeWeeksAgo": "ORA_PJS_IN_PROCESS",
      "CommentForThreeWeeksAgo": "Awaiting Processing",
      "CommentCodeForThreeWeeksAgo": "ORA_PJS_AWAITING_PROCESSING",
      "DefaultHoursTwoWeeksAgo": 40,
      "ScheduledHoursTwoWeeksAgo": null,
      "TimeCardHoursTwoWeeksAgo": 40,
      "CategoryForTwoWeeksAgo": null,
      "CategoryCodeForTwoWeeksAgo": null,
      "CommentForTwoWeeksAgo": "Hours less than scheduled",
      "CommentCodeForTwoWeeksAgo": "ORA_PJS_HOURS",
      "DefaultHoursOneWeekAgo": 40,
      "ScheduledHoursOneWeekAgo": null,
      "TimeCardHoursOneWeekAgo": null,
      "CategoryForOneWeekAgo": "Missing",
      "CategoryCodeForOneWeekAgo": "ORA_PJS_MISSING_TIMECARD",
      "CommentForOneWeekAgo": null,
      "CommentCodeForOneWeekAgo": null,
      "CreatedBy": "Lisa.Williams",
      "CreationDate": "2019-10-03T20:11:43+00:00",
      "LastUpdatedBy": "Lisa.Williams",
      "LastUpdateDate": "2019-10-03T20:11:43+00:00",
      "links": [
        ...
      ]
    }
  ...
]
}

Back to Top