Working of Recruiting Digital Assistant using ODA

Recruiting Digital Assistant is build using ODA, Oracle chatbot technology platform.

ODA allows enterprises to create and deploy digital assistants for their users. With ODA, you create:

• Digital assistants, which are AI-driven interfaces that help users accomplish a variety of tasks in natural language conversations. For each digital assistant, you assemble one or more skills.

• Skills (formerly known as chatbots), focus on specific types of tasks, such as tracking inventory, submitting time cards, and creating expense reports.

  You can add skills to digital assistants or deploy them to a channel on their own. Intents allow your skill to understand what the user wants it to do. An intent categorizes typical user requests by the tasks and actions that your skill performs.

  For more details, refer to Oracle Digital Assistants and Skills.

  Note:

  Import Recruiting Digital Assistant using the Import Skill option from the Oracle Cloud website. This also imports the Recruiting Careers Skill.

  For more information, refer to the technical brief on Chatbot Integration Framework https://support.oracle.com/epmos/faces/DocumentDisplay?id=2558379.1 and Chatbot Install Guide.

  The Recruiting Careers Skill consists of the following intents:

• Greeting

• ViewApplicationStatus

• ViewSavedSearches

• ConfigUnresolvedIntent

• ShowFAQsByCategory

• WhatCanYouDo

• SearchJobs

• General Questions

• ContactUs

• Submitting Applications

• Job Searching

• Help

• Job Searching

• InvokeBot

• ViewAppNotification

• Announcement

• ExitMessage

Note:

Two type of intents are configured in Recruiting Careers Skill – Regular Intents and Answer Intents. Regular intents have reg as prefix and answer intents have ans as prefix to the name.

The entities associated with each intent are defined within the skill.

Entities	Associated Intents
HRS_ApplicationStatusEntity	ViewApplicationStatus
HRS_NotifStatusEntity	ViewAppNotification
HRS_NotifTypeEntity	ViewAppNotification

The services can be used to call relevant application functionality as part of a transaction or query. The Chatbot Integration Framework delivers some services that can be used to help the chatbot carry out various tasks that these services allow to perform. To integrate the chatbot with the application services, you need to create a proxy user. This proxy user is used for the chatbot to communicate with the application services.

Note:

HRS_ApplicationStatusEntity contains list of application statuses. This entity will need modification to suit requirements of the organization. For example, if “Candidate Application Status” feature is enabled for the organization. And organization has configured custom statuses. Then those statuses need to be mapped in this entity so that application statuses shown in chatbot are not different than those displayed in the candidate gateway.

The dialog flow definition is the model for the conversation itself, one that lets you choreograph the interaction between a skill and its users.

If users need to create new service, then they can use the Application Service Framework to create custom services.

For more information please refer to the documentation on Application Service Framework https://support.oracle.com/epmos/faces/DocumentDisplay?id=2557046.1

For more details, refer to Configure a Component Service and Enterprise Components: Understanding Application Service for Chatbot Integration Framework.

The Recruiting Digital Assistant is available only for users with the HRS External Chatbot User role.

Field or Control	Description
User Role	HRS External Chatbot User Note: For the chatbot to be visible, the user must be provided HRS External Chatbot User role.
Permission List	HCCPRS9000

Roles and permission lists are part of standard PeopleTools security administration, used to grant access to components and pages. Roles and permission lists are discussed in the PeopleTools: Security Administration documentation.

With Tools 8.59, the chatbot skill services (such as Absence, Employee Directory, and so forth) are REST API enabled to manage the Oracle Digital Assistant instances. For information on REST API, see Enterprise Components: Understanding REST API Endpoints for PeopleSoft, Enterprise Components: Understanding REST API Endpoints for PeopleSoft Job Search Services (hrsjobs), Enterprise Components: Understanding REST API Endpoints for PeopleSoft Generate Careers URL (hrsutilities) and Enterprise Components: Understanding REST API Endpoints for PeopleSoft Applicant Activity (hrsapplicantcgactivity).

For more information, please refer to the technical brief on PeopleSoft Recruiting Digital Assistant https://support.oracle.com/epmos/faces/DocumentDisplay?id=2741723.1.