Exporting Job Submission Statuses Through Integration

Customers can get the appropriate customer-defined job submission statuses for candidate submissions, exported through integration.

In the Taleo Career Section product, it is possible to configure job submission statuses to describe the current progression state of a candidate submission. These job submission statuses are displayed to external candidates, internal candidates, referrers or agents.

An entity hierarchy is available in the Recruiting integration offering: "ApplicationStatusesByContext". The entities in this hierarchy are available for export through TCC, TCB and Web services.

Below is a description of these entities.

ApplicationStatusesByContext

• Collection of items (ApplicationStatusByContext).

• Child entity of the Application entity.

ApplicationStatusbyContext

• Represents a job submission status for one type of user (external candidates, internal candidates, referrers, agents).

• Describes a status defined by the customer or one of the default statuses provided by Taleo (depending on if a customized status for this context has been configured).

• Parent entity for ApplicationStatusByContextDefinition and ApplicationStatusByContextUserType.

ApplicationStatusByContextDefinition

• Contains the name and description of a specific status.

• Contains the following fields:

  • Name: Name of the returned status. This name does not take into consideration customer-specific customizations that may have been done on the name of the Taleo default statuses (customizations done through support requests).

  • CustomizedName: Same as "Name" but takes into consideration customer-specific customizations that may have been done on the name of the Taleo default statuses (customizations done through support requests). If no customizations have been made on the Taleo default statuses, it contains the same value as the "Name" field.

  • Description: Description of the returned status (description provided by the administrator). The text from this field is in rich text format and can include links, images, bold text, etc.

ApplicationStatusByContextUserType

• Identifies the type of user (external candidates, internal candidates, referrers, agents) for which a status is targeted.

• Contains the following fields:

  • Description: Description of the type of user to which this status applies. Possible values: External Candidate, Internal Candidate, Referrer, Agent.

  • Number: Number representing the type of user to which this status applies. Possible values: 1 (External Candidate), 2 (Internal Candidate), 3 (Referrer), 4 (Agent).

Below is a sample output.

Important Information

When exporting field values from the ApplicationStatusByContextDefinition entity, if different locale (language) filterings are applied to the fields from this entity, the output may not contain the locales that were requested. To avoid this situation, make sure to set the same locale filtering on all multilingual fields from the ApplicationStatusByContextDefinition entity.

The order in which the four possible statuses (ApplicationStatusbyContext ) are returned in the export output will not always be the same if running the same export query multiple times. For example, when using the export output, do not rely on the external candidate status to be returned first. Always validate the user type for which a status applies to.

It is recommended to always use the CustomizedName field value of the ApplicationStatusByContextDefinition entity instead of the Name field value. If no customer-specific customizations have been done on the names of the Taleo default statuses, both fields will have the same value. If customizations have been made, only CustomizedName will take those customizations into consideration. The only reason to use the Name field would be if you want the standard Taleo default statuses, ignoring customizations made to the text for those default statuses.