Get all absence types for a worker

get

/hcmRestApi/resources/11.13.18.05/absenceTypesLOV

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 all the absence types that match the specified primary key criteria..
      Finder Variables
      • CompositeKey; string; Unique combination identifier for the numeric identifier of the person and the person's work relationship, separated by an underscore.
    • findByWord Finds all the absence types that match the specified criteria. You need to specify the personId to get a result.
      Finder Variables
      • AbsenceTypeEffectiveDate; string; Effective date of the absence type. It defaults to current date.
      • FilterAttributes; string; Space separated list of fields to query on.
      • PersonId; integer; Unique numeric identifier for the person. You must specify this to get results.
      • SearchTerms; string; Search phrase to query with. It can be a single word or multiple words separated by space.
    • findDefaultAbsenceType Finds all the default absence types defined by the configuration option.
      Finder Variables
      • AbsenceTypeEffectiveDate; string; Effective date of the absence type. It defaults to current date.
      • LEFlag; string; Legal employer of the absence type.
      • PersonId; integer; Unique numeric identifier for the person.
  • 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:
    • AbsTypeWithEmployerName; string; Name of the absence type, if the employee has a single work relationship. For employees with multiple work relationships, it's name of the absence type and legal name of the employer, separated with a hyphen. For example: Vacation - Vision Corporation.
    • AbsenceTypeId; integer; Unique numeric identifier of the absence type.
    • AbsenceTypeName; string; Name of the absence type, such as Vacation.
    • BiddingFlag; boolean; Indicates whether bidding is enabled for the absence type. Valid values are Y and N. The default value is null.
    • CompositeKey; string; Unique combination identifier for the numeric identifier of the person and the person's work relationship that are separated by an underscore.
    • Description; string; Description of the absence type.
    • DisplaySequence; integer; Absence type display order for absence and bid entry.
    • EmployerId; integer; Unique numeric identifier of the employer.
    • EmployerName; string; Legal name of the employer, such as Vision Corporation.
    • LegislationCode; string; Legislation code of the legislative data group for the absence 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 : absenceTypesLOV
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : absenceTypesLOV-item-response
Type: object
Show Source
Back to Top