SoftTech AI Registry
Oracle · Oracle Fusion Cloud Human Capital Management

Person Data Assistant

Oracle documents Person Data Assistant as a preconfigured AI Agent Studio workflow agent template in Oracle Fusion Cloud HCM that retrieves and, for documented person objects, creates, updates and deletes a user's own person data and other workers' person data in a conversational experience. Oracle states in update 26D that it replaces the deprecated Personal Information Assistant and Person Legislative Information supervisor agent templates. Access is granted through a specific duty role, role-based data security is honoured, and where HCM approvals are enabled changes take effect only after approval.

Recorded characteristics

Function
Oracle documents Person Data Assistant as a preconfigured template delivered in Oracle AI Agent Studio for Fusion Applications and deployed as a workflow agent. Oracle describes a two-tier structure within one capability: the Person Data Assistant workflow agent uses child workflow agents to manage supported data areas and invokes the Personal Information Assistant, now positioned as a child supervisor agent, for the remaining capabilities. Child workflow agents were introduced for Name, National Identifier and Ethnicity in update 26C and extended in update 26D to Demographic Info, Religion, Biographical Info, Citizenship, Passport, Visa and Permit and Driver's License. In update 26D Oracle states that the Personal Information Assistant (ORA_PERSONAL_INFORMATION_ASSISTANT) and Person Legislative Information (ORA_PERSON_LEGISLATIVE_INFORMATION) supervisor agent templates are deprecated and that the Person Data Assistant replaces these templates and is recommended for all new development. The documented interaction is conversational: a user asks in natural language about, or requests a change to, person information for themselves or for another worker; where a request concerns another worker the agent performs a worker search, which Oracle states moved from the supervisor agent into the overall workflow in 26D, and Oracle's worked example shows the agent asking the user to confirm that this is the right person and asking for the effective date of the change before it makes the update and displays a confirmation message. Write authority established by current Oracle documentation is per object: create, update and delete for National Identifier, Ethnicity, Demographic Info, Religion, Citizenship, Passport and Driver's License; update and delete for Name; update only for Biographical Info, where Oracle states the agent can only update biographical information and cannot create or delete it; create and update for Visa and Permit, where Oracle states delete is not supported in this release; and create, update and delete for Email and Phone, handled by the Personal Information Assistant child supervisor agent. Addresses and family and emergency contacts are retrieve-only, with the agent providing deep links for objects not yet supported for update. Flexfields can be retrieved but Oracle states they are not supported for create, update or delete. In update 26D Oracle states the agent can handle requests involving multiple people or multiple supported data objects in a single conversation, relaxing the 26C limitation of one person and one object at a time. Where HCM approvals are enabled Oracle states that changes are routed for approval and take effect only after approval; the approval decision itself is made by the deterministic HCM approval workflow and its human approvers, not by the agent. The highest authority established for the agent itself is submitting or applying changes to the documented effective-dated person records within the invoking user's role-based data security. Downstream consequences of a person-data change, such as payroll, benefits, tax, identity provisioning, notifications or integrations, are not attributed to this capability, and Oracle does not document the agent changing compensation, job, position, employment status, payroll or payment method data. Marital status is handled as an attribute within the demographic workflow following the deprecation of the separate Person Legislative Information agent; Oracle's separately listed personal payment method and document record AI features are catalogued as distinct features and are not part of this capability.
Data access
Oracle documents the agent reading and, where supported, writing person business objects in Fusion HCM corresponding to the Personal Details, Identification Info and Contact Info pages: Name, Demographic Info, Religion, Ethnicity, Biographical Info, National Identifier, Email, Phone, Citizenship, Passport, Visa and Permit and Driver's License, plus retrieve-only access to addresses and to family and emergency contacts, and retrieve-only access to flexfield values. Oracle states that role-based data security is honoured and that users only see the data their role permits. Oracle also documents that National Identifier is not masked in agent responses even though it is masked in the user interface, that religion values hidden in some countries by built-in page templates can still be returned by the agent, and that in update 26D the agent does not allow users to view, create, update or delete ethnicity information for a listed set of legislations. Oracle documents no independent access to data outside these person objects for this capability.
Actions
Can take actions
External actions
Unknown
Human confirmation
Conditional
Permission basis
User permissions
Administrative control
Oracle documents that the Person Data Assistant is a preconfigured template from which administrators create their own agent, that a role must be explicitly granted access to the agent by an AI Studio Administrator, and that the Person Data Assistant Access Duty (ORA_PER_PERSON_DATA_ASSISTANT_ACCESS_DUTY) duty role is included in the seeded Human Resource Specialist role and must be added to other roles such as Employee, Line Manager or a custom Human Resource Specialist role to grant access. Line managers and custom roles also need Use REST Service - Worker Searches V2. Environment prerequisites include specified configurations arranged through Oracle Support and setting the Enable Security Console External Application Integration (ORA_ASE_SAS_INTEGRATION_ENABLED) profile option to Yes with permission groups enabled for the appropriate roles. Oracle documents that HCM approval rules govern whether changes take effect immediately or after approval. To prevent unwanted fields appearing, Oracle documents prompt guardrails and scoping data by creating a custom agent that excludes the business object or uses a trimmed-down version of the business object without restricted attributes. Oracle also documents what is not honoured: localization rules and customer business rules built in Visual Builder Studio are not enforced by the agent, and differences between the Me and My Client Groups versions of the page, such as sections that exclude Add or Edit buttons, are not honoured.
Default state
Disabled
Availability
Oracle documents Person Data Assistant as introduced in Fusion Cloud HCM update 26C, where it is described as a new workflow-based design replacing the previous Personal Information Assistant as the recommended template for new development, and extended in update 26D, where the Personal Information Assistant and Person Legislative Information templates are stated to be deprecated. The 26D enhancement feature is tagged by Oracle as an AI agent and Idea Lab feature. Oracle documents legislation-specific behaviour for ethnicity and legislation-specific marital status values but publishes no consolidated list of supported countries or languages for this capability in the documentation reviewed.
Licensing
Oracle does not state a separate licence, subscription or credit requirement specific to Person Data Assistant in the documentation reviewed, so licensing is not established.
External model or provider
Not established
Limitations and uncertainty
Oracle does not identify the underlying model or model provider for Person Data Assistant, so the model and provider are not established; Oracle notes only that token limits vary by the model in use and that overly large combined inputs may cause truncated or failed responses. Human confirmation is recorded as conditional: Oracle's worked examples show the agent confirming worker identity and asking for an effective date before making an update, and approval routing applies only where HCM approvals are enabled, but Oracle does not document a distinct review-and-submit preview step preceding every write. External action capability is recorded as unknown: no Oracle page reviewed establishes that the agent sends email or SMS, calls external services or writes to external systems, and the only outward behaviour documented is deep links back into Fusion HCM pages; silence is not treated as confirmation that external action is impossible. Permission basis is recorded as user permissions because Oracle states role-based data security is honoured and access is gated by the invoking user's roles and duty role; no separate runtime agent identity is documented, though Oracle states that page-level business rules and Visual Builder Studio customizations are not enforced, so agent behaviour can exceed what the user interface exposes. Invocation is documented only as conversational; autonomous, scheduled or event-driven invocation of this agent is not established. Audit, history or reporting of agent-initiated transactions is not established, nor is handling of disability data. Documented limitations include that the agent does not return workers whose hire date is in the future, does not support advanced worker-search filtering such as finding workers by location, does not support flexfield writes, does not support editing an in-flight transaction pending approval and instead provides a deep link, does not support comments or attachments for approval-enabled updates, does not make approval notifications viewable, does not support updating name and changing name style when a worker has multiple work relationships, will not update a name unless a local name is supplied where local name is required, and restricts users to current and future records rather than historical records, using the session date as the effective date for a user's own data. The earlier Personal Information Assistant and Person Legislative Information Assistant are recorded here as provenance of the current capability rather than as separate registry records, and no registry change event is created for that pre-baseline history.

Evidence