Assign Default Process Owners
Purpose and strict scope
Execute Assign Default Process Owners in the Risk and Security deployment plan. The normal assignment flow generates customer-reviewable default-owner proposals for selected Level 2 processes, using functional workforce evidence first and Business Unit information only as optional supporting context. It fills only unassigned members in the selected Level 2 scope. A configured owner remains informational unless the consultant explicitly requests UPDATE or RESET for that named Level 2 process. The customer approves, rejects, or edits every proposal before a later live run applies any decision.
Consultant-facing review and decisions
Follow the offering Consultant Interaction Contract. Use a compact Markdown table for every owner-coverage and owner decision. The initial coverage review contains Business process, Current default owner, Current result, and Work on this process?. The candidate review contains Business process, Proposed owner, Recommendation basis, and Decision. The final approval table contains Business process, Operation, Approved owner, Current result, and Approval. RESET rows show No assigned owner in the approved-owner column.
For coverage, a Level 2 row is an aggregate, never a root-row result. Before showing or refreshing the table, derive its owner names, unassigned members, and current result from every member in that Level 2 scope. A table that uses only a root owner, including when a consultant asks to update or re-read the list, is invalid and must be re-read and re-rendered.
Do not ask the consultant to open, edit, or approve a JSON review file. Their chat or table confirmation is recorded internally. For an unavailable lookup, state the business impact, confirm that no owner was proposed or assigned, and give one safe next action.
Usage
Use this skill when planning, sequencing, or validating the Assign Default Process Owners setup task under Assign Initial Users.
Required upstream skill
Require the verified coverage result from the parent Risk Administrator Assignment Verification, which Assign Initial Users invokes first for the selected project and environment. It verifies both that organization coverage exists and that the authenticated user is ready through Risk Administrator or IT Security Manager access. If the authenticated user needs access, the parent prepares and verifies the one explicitly approved Risk Administrator assignment before routing here.
This nested skill is never an independent entry point. When a consultant asks
to run Assign Default Process Owners directly, route the request back to
Assign Initial Users in prerequisite mode. Before any process, owner,
Business Unit, worker, hierarchy, or user read, require current parent evidence
for the same project and environment that records both
organization_coverage=true and runner_access_ready=true. A pending,
blocked, stale, cross-environment, or incomplete prerequisite result is not
evidence. Keep the parent gate active until it reaches its decision or verified
result; do not start owner discovery in parallel or disclose the internal reason
for the hold. After verification, resume this child as the sole active
workflow.
Stage 0 — Risk Management search prerequisite
After the parent gate and before any owner-coverage inventory, delegate the
Risk Management search prerequisite to
core.fusion-api.apps-common.profile-options. Read the exact profile
definition, its Site capability metadata, and its Site value through that Core
skill. Read the task-local lookup contract
before preparing the Core request.
The Site capability is usable only when exactly one Site metadata row reports that it is both enabled and updatable. The child-level Site metadata is the capability source for this task; do not infer capability from missing parent-level flags. Treat a missing Site value or a value other than the required enabled value as disabled.
When the setting is already enabled, retain only redacted evidence—the environment, prerequisite outcome, Core request references, and verification outcome—and continue directly to Stage 1 without a consultant message. Do not persist the profile code, raw value, endpoint, privileges, or response body in the project record.
When it is disabled, show only this approval table and wait for a fresh confirmation:
| Setting | Business impact | Proposed change | Approval |
|---|---|---|---|
| Risk Management search | Default-owner recommendations cannot begin | Enable the setting for the environment | Pending approval |
Ask: “Approve enabling Risk Management search for this environment?” On approval, have the Profile Options Core skill re-read the Site capability and current Site value, then create a missing Site value or update an existing disabled value through its supported route. The Core skill owns the change selection and execution. This child must not construct, submit, or retry a profile-option request. Re-read through Core and require the enabled Site value before beginning Stage 1.
If the profile cannot be read, the Site capability is missing or not updatable, approval is withheld, the Core change fails, or final verification does not confirm the enabled setting, stop before owner coverage. State that Risk Management search could not be confirmed for this environment, that no default-owner review or assignment was started, and ask the consultant to have an administrator enable the setting and then resume this task. Do not expose profile codes, values, endpoints, or privilege mechanics.
Core execution delegation
Delegate the Stage 0 profile-definition, Site-capability, Site-value, and any
approved Site-value change exclusively to
core.fusion-api.apps-common.profile-options. That Core skill owns its
supported create/update choice, its REST client, OAuth, token cache,
transport, and no-retry behavior. This child records only redacted phase
evidence and never imports, launches, or emulates an HTTP or OAuth client for
the prerequisite.
Prepare the exact Business Unit, worker, hierarchy, user, process-property,
and approved owner-assignment requests here, then defer every Fusion and BOSS
execution to core.fusion-api.rest-api-client. The Core skill owns selection
and execution of its Python client, OAuth, token caches, transport, retry, and
response handling. This skill and its helpers must not import, launch, or
emulate that client.
Use returned Core results for matching, candidate scoring, approval-plan construction, verification, and redacted project reporting.
The Consultant Interaction Contract governs every consultant-visible message, including commentary. Internal collection progress is never a consultant outcome. Complete it silently; before a coverage table, required decision, approval, or genuine business blocker is ready, do not explain why internal work is continuing. When a progress update is unavoidable, use the contract's neutral sentence verbatim.
This rule also applies when a read must be retried or cannot continue. Never explain session setup, service scope, authorization mechanics, query or filter construction, shell quoting, request plans, or collection mechanics to a consultant. Return only the contract's neutral progress sentence until a complete business review, required decision, or genuine business-facing exception is ready.
Use scripts/expand_worker_manager_requests.py only to expand confirmed
Business Units into the next deterministic batch of worker-assignment,
manager-hierarchy, user, and public-worker requests. It does not match
Business Units, select owners, interpret customer decisions, prepare creates,
or verify assignments. It has no HTTP, OAuth, Core-client, or Fusion imports.
Read the Core-result-bundle contract
before using it. Core performs every external request.
Worker-assignment and manager-hierarchy requests are paginated reads. The
helper emits $limit=500 and $offset=0 for the first page, then advances the
offset by the non-empty returned page size while hasMore=true. A nonempty
page shorter than the requested page size may be treated as final when the
continuation flag is absent; every other missing or malformed continuation
signal, or an empty continuing page, blocks the affected stage. The helper does
not prepare hierarchy reads until every confirmed Business Unit assignment page
is complete, and does not prepare manager/user reads until every hierarchy page
is complete.
The matching and proposal stages are preview-only. The separate apply stage may create approved default owners only after a current-state preflight and a fresh, exact-plan approval. It must not provision Risk Power Users or perform work owned by another deployment skill.
Stage 1 — Review current default-owner coverage
Begin only after Stage 0 records a current verified prerequisite result for the
same project and environment. Before asking which business processes to work
on, retrieve the complete seeded Level 2
process inventory and the complete current default-owner inventory through
core.fusion-api.rest-api-client. Do not request Business Unit, worker, or
hierarchy information yet. If either inventory is incomplete, unavailable, or
ambiguous after the declared reads, stop with a business-facing exception; do
not present a partial coverage table or expose the internal reason that a
complete review could not be produced.
Start both collection streams at $offset=0 with $limit=100. For either
stream, when hasMore=true, advance the offset by the nonempty returned page
size and request the next page with the same filter, fields, and sort order.
Continue until the Boolean value hasMore=false. A literal Boolean false is
a completed final page; do not treat it as absent when displaying or evaluating
the result. A missing or malformed continuation signal, an empty page with
hasMore=true, or a repeated/unstable page blocks the coverage review; do not
infer that the remaining inventory is empty.
Inspect the continuation value with a Boolean-safe check. In particular, do
not use a fallback expression such as jq '.hasMore // "missing"': that
operator replaces a valid false with the fallback value. Test the field's
type and value separately, or read the Boolean directly. A returned Boolean
false completes the inventory and requires the complete coverage table next.
Prepare these reads as an internal Core request manifest, retaining the exact
query property names $filter, $limit, $offset, and $sortBy. Before the
first request, validate that $limit is 100 and $offset is 0; do not
construct a separate shell command whose quoting could alter those names.
GET /api/boss/data/objects/ora/riskMgmtRisk/core/v1/referenceDataValues
?$filter=referenceCode!='SOURCE.ORA.ORA' AND referenceCode!='SOLUTION.FND.ORA' AND attributeCode='PROCESSES.ORA'
&$fields=valueCode,referenceCode,attributeCode,levelOne,levelTwo,levelThree,description
&$limit=100
&$offset=0
&$sortBy=levelTwo:asc,referenceCode:asc
GET /api/boss/data/objects/ora/riskMgmtRisk/core/v1/referenceDataValueProperties/$views/detailed
?$limit=100
&$offset=0
&$sortBy=valueCode:asc
referenceDataValues is the provided ReferenceDataValue business object;
it does not include user-defined reference data. Do not substitute the
allReferenceDataValues extraction, which unions provided and user-defined
records. Form the consultant inventory only from its distinct levelTwo
values and establish the corresponding Level 2 scope using the documented
seeded Common-process rule. For each Level 2 row, first collect every catalog
record with the same validated levelTwo into one exact-valueCode set. A
repeated valueCode, a missing canonical member name, or any other nonunique
member identity blocks that row and requires a fresh catalog read; do not
silently collapse it. Identify any self-named member whose normalized canonical
process name equals the normalized Level 2 name. Exactly one such member is an
optional root marker for display and is not added again. No self-named member
means the scope has no root marker and remains valid; more than one is
ambiguous and blocks the row. Join every unique scope member to its current
owner record by
valueCode, using only the completed owner-properties inventory from the same
coverage run. A member is assigned only when exactly one matching property has
defaultOwnerType USER or GROUP and a nonblank defaultOwnerCode. No
property, or a property with a blank/null owner code, is unassigned. Treat
duplicate properties, an unsupported type with a nonblank code, or incomplete
evidence as ambiguous; block the coverage row rather than inferring its state.
Never expose a member valueCode or defaultOwnerCode.
For an assigned USER owner, use the owner-properties view's readable
defaultOwnerUser.name; for an assigned GROUP owner, use
defaultOwnerGroup.name. Otherwise use the returned readable owner label or
Configured owner only when no readable name is returned. The
Current default owner cell aggregates distinct assigned readable owners from
all scope members in stable sorted, comma-separated order. The root owner alone
must never determine the row's current owner or current result. If any scope
members are unassigned, append Unassigned (<reference codes>). Use each
unassigned member's nonblank catalog referenceCode, including for an optional
marked root, sorted by normalized value. The root marker remains internal scope
metadata and has no special display suffix. Do not remove distinct members
because their displayed Reference Codes match. If an unassigned member has no
usable Reference Code, block the coverage row and require a fresh catalog read;
do not fall back to a process name, hierarchy/category value, or valueCode.
Every consultant-facing table is Level 2 process-level only. Use only the fields declared for that table type in Consultant-facing review and decisions. The initial coverage table's Current default owner cell may show the allowed unassigned reference codes above. Do not add member identities, counts, states, action results, or any other member-derived column or cell.
Render one complete consultant table in the chat response before asking for a process selection. Persisting the table as an artifact, or describing it in prose, does not satisfy this gate. Include every considered process, including the ones already configured, and do not replace the table with a count, bullet list, or missing-owner summary. Do not start Audit Policies, active-module identification, algorithm publication, or Risk Power User work while this table awaits a selection:
| Business process | Current default owner | Current result | Work on this process? |
|---|---|---|---|
<Level 2 process> |
<comma-separated assigned owner names or usernames; Unassigned (<reference codes>) when applicable> |
Already configured, Default owner needed, or Partially assigned |
Not applicable, Pending selection, or explicitly requested UPDATE / RESET |
A process with an existing owner is informative only in the normal assignment flow. Do not offer replacement or reset choices merely because an owner is present. The normal CREATE operation may be selected for a Level 2 row that has one or more unassigned scope members; it creates owners only for those members and preserves all configured members. Accept replacement or reset only when the consultant explicitly requests one of these individually named actions:
- UPDATE, CHANGE, MODIFY or REPLACE: name the source owner and a separately validated, approved replacement owner. Replace only scope members whose exact internal owner type and owner code still match that source owner. Leave unassigned and differently owned members unchanged.
- RESET, REMOVE or DELETE: delete every existing default-owner property in the Level 2 scope; already-unassigned members remain unchanged.
Record the requested operation alongside the exact selected Level 2 process. A missing, blank, or unrecognized operation means no change to configured members. Internally, every approved decision records the selected Level 2 process, operation, reviewed per-member state, and hidden member action plan; the plan contains each exact member identity once. Before approval and again before the first write, reject a plan that repeats a member identity rather than issuing duplicate bulk requests. CREATE and UPDATE also record the replacement owner and UPDATE records the exact source owner. RESET records no replacement owner. The customer approval table remains Level 2-only and uses only its declared approval fields. Retain created, updated, preserved, reset, and unchanged counts only in the hidden action plan and redacted receipt.
For the normal assignment flow, ask plainly: “Which processes with one or more unassigned members would you like to work on?” If no such process or explicit existing-owner operation is selected, report that no changes are needed and stop. Do not request more input at this point: begin functional candidate discovery only for CREATE and explicit UPDATE targets. Do not ask for mapping documents, permission to generate a mapping, or a Business Unit.
If the consultant later asks which processes are available or still need an owner, re-render the same Markdown table filtered to Default owner needed or Partially assigned rows. Do not answer with a count-labelled bullet list. The filtered table still uses Business process, Current default owner, Current result, and Work on this process? columns, with no process-record count.
Stage 2 — Build a candidate population for selected processes
For selected unassigned CREATE processes and explicitly requested UPDATE processes only, build a read-only candidate population. RESET requires no candidate population. A Business Unit is useful evidence about a workforce population; it is not, by itself, evidence that a person owns the selected process.
Start the default route immediately from the selected process, without asking
the consultant for a Business Unit or a Business Unit-to-process mapping. Use
core.fusion-api.rest-api-client to first obtain the active-department catalog
defined in ora-resource/ora_reference_lookups.md. Reuse that completed
catalog for every selected process in the same unchanged workflow; do not read
it again for each process.
Assess department name and available department context semantically against the selected process's business purpose, product domain, and any explicit customer process-function evidence. This is a fuzzy business comparison, not an exact-title or keyword search: customer job titles and department names vary and must not be treated as a fixed catalog. Retain only direct functional department matches. A senior title, a Business Unit name, location, or an adjacent function alone is not a direct functional match.
For each retained department, use its exact returned department name in the
bounded primary-worker finder defined in the lookup reference. Read only those
worker results in stable 100-row pages to completion. Do not retrieve the
unfiltered publicWorkers collection and do not expand every worker into
hierarchy or identity reads. If direct functional departments produce no viable
candidate, evaluate adjacent departments only as a separate, lower-confidence
fallback and record why they are adjacent rather than direct.
The semantic assessment must consider the full functional context, not only shared words. A customer-specific department may be relevant to a selected process even when it does not contain a predefined title. Record the business rationale for every retained department and candidate, and classify its support using the existing functional fit tiers before ranking.
Customer mapping material remains optional supporting evidence. If it is available, resolve supplied Business Unit names against the authoritative catalog using exact then normalized names only, and retain a unique effective match with workers as supporting evidence. Do not ask the consultant to approve or provide a mapping, and do not use a Business Unit as the primary discovery route. Exclude a matched Business Unit that has no workers unless the consultant explicitly asks to inspect it.
If the department-bounded worker lookup and optional supporting evidence produce no eligible worker, present a concise exception table. Offer an exact Fusion username or an HCM-administrator validation of the relevant worker function; do not ask for a Business Unit mapping. Do not claim that a Business Unit has no owner; only state that the available workforce information did not support a recommendation.
Retain the returned worker identities, any resolved Business Unit context, and process-function evidence internally. Do not present a Business Unit decision table unless the consultant explicitly asks to compare an ambiguity. The first normal consultant output after process selection is the completed owner-candidate review.
The completed process_catalog remains the directly provided
referenceDataValues result and resolves each selected L2 name to one row.
Reconfirm through the completed process_owner_properties inventory that each
CREATE target remains unassigned and each explicit UPDATE or RESET target has
one current owner property. Candidate discovery applies only to CREATE and
UPDATE. Never use the allReferenceDataValues union extraction as an alternate
match source.
Stage 3 — Propose owners from functional and organizational evidence
Use the resolved candidate population to identify active, eligible owner candidates. The default discovery route obtains workforce and reporting evidence through Core, then ranks only verified candidates. It does not ask a consultant to choose a management tier before the initial review.
If the consultant identifies an intended owner by an exact Fusion username,
first validate the exact account is active through the Fusion SCIM Users read.
That completes the account-active check. Do not use the HCM userAccounts
resource to validate a direct owner. Then resolve that exact username through
the BOSS user collection before requesting worker or reporting information. A
single BOSS result with the same name and a guid is a
supported direct owner candidate: use its guid as the internally retained
owner code and the exact supplied username as the consultant decision-table
label. A public-worker display-name lookup is not required for this direct
candidate route. This route replaces hierarchy analysis for that proposed
owner; it does not require a person, manager, department, or assignment record
and does not authorize an assignment. Zero, multiple, inactive, or
incomplete matches require correction and never fall back to a guessed
identity.
Use verified reporting relationships as organizational evidence, not as a proxy for functional accountability. The default request scope remains the existing closest-resolvable-manager review through three levels; it supplies a bounded candidate population and does not itself choose the owner. A consultant may request another supported hierarchy strategy only as a later refinement.
Pass the verified worker identifiers from the department-bounded worker lookup to
scripts/expand_worker_manager_requests.py with one
--candidate-worker-id per candidate to produce the next deterministic Core
request batch. Do not supply --confirmed-mappings for this default route.
Rerun it after every returned Core batch until it produces no further requests.
It obtains the bounded manager-hierarchy evidence and BOSS user identities only
for the department-bounded candidates and any returned managers. Use a
uniquely resolved BOSS username as the initial candidate label. The optional
Business Unit evidence route may continue to use --confirmed-mappings; it is
never a consultant-facing prerequisite.
From that completed set, build a small deterministic shortlist for each selected
process and deduplicate it across processes. Retain any candidate with explicit
process-function evidence first, then retain up to three additional verified
organizational candidates ordered by nearer reporting context, represented
worker assignments, and stable username; include candidates tied at the cutoff.
This is an enrichment limit only, not the final owner ranking. Ask
core.fusion-api.rest-api-client to enrich only those shortlisted candidates
with the documented HCM assignment fields. The Core skill performs every HCM
request; this skill does not construct an HTTP client or make a request. Use
returned job, department, position, manager, and direct-report evidence only
when it is present and verified. Retain the corresponding restricted decision
evidence internally.
For a consultant-supplied exact username, pass each name through
--proposed-owner-username without --confirmed-mappings. The helper requests
only the bounded BOSS identity lookup. Use the exact supplied username as the
readable label after the active-SCIM and BOSS-identity checks succeed. Do not
request HCM userAccounts, public-worker profiles, worker assignments, or
reporting hierarchy for that direct-candidate path.
Candidate-analysis completion barrier
Do not present owner proposals, candidate choices, an approval request, or a statement that hierarchy analysis is complete while any request produced by the helper remains outstanding. Complete the entire read sequence first: worker assignments, every returned worker's hierarchy, every candidate manager's BOSS user identity. A direct exact-username candidate completes after its active-SCIM and unique BOSS identity checks. Also read current process-owner properties before reporting a proposal. Only after evaluating the complete result set may the skill present one of:
- a supported owner proposal for an unconfigured process;
- an explicit customer-choice tie; or
- an already-configured or no-candidate exception.
After the Business Unit selection, keep the skill execution active while Core request batches are running. Begin with one deterministic level-one reporting read before requesting the remaining workers and requested levels. An authorization, transport, malformed-result, or other Core failure stops before the larger batch and produces the corresponding business-facing exception.
A successful empty final hierarchy result is completed data for that worker, not evidence that access is unavailable. Continue through all requested workers and levels. If no reporting relationships are returned after the full set completes, present this exception table and no owner proposal:
| Item | Business impact | Current result | Next action |
|---|---|---|---|
<selected business process> |
No supported default-owner recommendation is available | No reporting relationships were returned | Provide an exact Fusion username or ask the HCM administrator to validate reporting relationships and functional worker information |
Continue from each returned batch to the next dependent batch without yielding a final response that merely says analysis is in progress. Return to the consultant only for a completed review, a non-recoverable read/authentication blocker, or a required decision.
hierarchy.selection defaults to LOWEST_RESOLVABLE, which requests levels 1
through levels_to_inspect (three by default). FROM_LEVEL requires a positive
starting_manager_level; TOP omits it and retrieves full hierarchy rows to
evaluate the requested number of highest levels.
After the shortlisted candidate enrichment is complete, build the restricted
evidence record and run scripts/rank_owner_candidates.py. It ranks candidates
in these orderable evidence tiers:
- direct responsibility for the selected process or function;
- leadership of the matching functional department;
- matching job or position evidence;
- verified organizational reporting context; then
- verified Business Unit context.
Within a tier, prefer explicit active/effective evidence, management responsibility, nearer reporting context, greater direct-report context when available, and finally stable username ordering. Stable ordering is only for repeatability: when multiple candidates share the strongest evidence tier, show them as equivalent alternatives and require the consultant to select one.
Do not infer a direct functional match from an absent field, a Business Unit name, or seniority alone. Process-specific functional evidence must come from customer material, an explicit customer correction, or returned workforce data that supports the stated match. When only organizational or Business Unit evidence is available, present a Low-confidence proposal or alternatives rather than claiming confirmed ownership.
Present the completed candidate review in this table. Omit an unavailable job or department value instead of treating it as an error:
| Business process | Candidate | Job / department | Fit | Confidence | Why this person | Decision |
|---|
The review can show one top candidate and an alternate, or equivalent candidates when a consultant choice is required. A recommendation remains a proposal; it does not assign an owner.
Candidate review refinement
When the consultant requests the next likely candidate, a lower organizational level, or a comparison, preserve the selected process and completed evidence. Exclude only the prior candidate when requested and rerun the same local ranking rule. Reuse the retained department catalog, shortlist, and enrichment evidence; do not repeat unrelated Business Unit, worker, or hierarchy reads. If the consultant asks for additional candidate detail, enrich only the newly shortlisted verified candidate through Core. The exact-username route remains available at every point and validates the specified person without recommendation ranking.
The review files cannot be in project/, because they contain customer
identity data. Project artifacts retain only redacted counts, status, and
exceptions. mapping_basis.mode is FUNCTIONAL_DISCOVERY for the normal
selected-process route; it can also be CUSTOMER_DOCUMENTS when optional
customer material supplied supporting context.
GET-only candidate analysis
The Core-managed preview reads the following BOSS and Fusion HCM resources. The process and
current-owner inventories use the same ordered 100-row coverage pages completed
in Stage 1; do not re-read or re-paginate them until apply preflight. The UI
process catalog is authoritative for the L2 target: it must be the direct
provided referenceDataValues result. Match the confirmed process name to
levelTwo, then resolve its complete Level 2 scope. Its owner display and
current result must aggregate every scope member. Treat an ambiguous scope as
an ambiguity for customer review rather than excluding the UI process.
- The paginated
process_catalogandprocess_owner_propertiesresults defined in Stage 1. Expand each selected Level 2 target from the same validated unique-valueCodeset used for its coverage row. If exactly one self-named root exists, mark it within that set; never append it separately. A scope with no self-named root remains valid. A duplicate member identity or multiple roots stops the scope before candidate review or mutation selection. Before selecting a mutation, classify each member from the current property inventory asABSENT_PROPERTY(no row),EMPTY_PROPERTY(exactly one supported USER/GROUP row with a blank/null owner code), orASSIGNED_PROPERTY(exactly one supported USER/GROUP row with a nonblank owner code). Treat duplicate rows, an unsupported nonblank owner type, a missing required identity, incomplete evidence, or any other shape that cannot establish one of those states as ambiguous and not mutable. A normal CREATE action targets onlyABSENT_PROPERTYandEMPTY_PROPERTYmembers. An explicit UPDATE targets only members whose exact internal owner type/code matches the reviewed source owner. An explicit RESET targets every member with a valid assigned owner tuple; empty properties are already unassigned and remain unchanged. All remaining members are preserved. - The active HCM department catalog, using
departmentsLovwithq=Status='A',fields=OrganizationId,Name,EffectiveStartDate,EffectiveEndDate,Status,onlyData=true,limit=100,orderBy=Name:asc, and a stable offset sequence. Complete it once and semantically select direct functional departments for each requested process. Do not use a fixed title list or a consultant-supplied Business Unit filter. - The primary-worker
publicWorkersfinder for each retained department, using the exact returnedDepartmentNameandOnlyPrimaryAssignmentFlag=true, withlimit=100and stable offsets. This is the only normal worker-population read. Do not retrieve the unfiltered worker collection. Deduplicate returned numericPersonIdvalues before hierarchy expansion. managerHierarchyfor every department-bounded worker and every requested manager level. For a level-based review,personIdandmanagerLevelare numeric BOSS values: usepersonId=<PersonId> and managerLevel=<level>. TheTOPreview may request full hierarchy rows withpersonId=<PersonId>.- BOSS
usersto resolve each department-bounded worker and hierarchy candidate to the stable BOSS user GUID and verified username. Use that username as the reviewable candidate label. - For only the unique shortlisted candidate identities, read the documented
public-worker and primary-assignment fields through
core.fusion-api.rest-api-client. Retain available display name, job, department, position, manager, and direct-report evidence. Do not expand this enrichment to every worker in a Business Unit, and do not exclude a verified candidate whose optional HCM data is unavailable. - When the operator requests candidate role enrichment, enrich candidates from
the Fusion user-account resource in small batches, using
GET /hcmRestApi/resources/11.13.18.05/userAccountswith a batchedq=Username='...' OR ...filter andexpand=userAccountRoles. Use the normal Fusion OAuth audience and report unavailable or unmapped accounts without blocking the hierarchy preview. This is optional role enrichment only; it is never part of exact-owner validation and cannot block a direct-owner proposal.
Role counts and broad administration never establish functional responsibility or break a functional-evidence tie.
The same owner may be recommended for more than one Level 2 process. Each Level 2 target receives its own proposal and customer decision; candidates are not deduplicated across Level 2 targets.
The review output shows the process context, supported candidate set, functional and organizational evidence, recommendation or equivalent alternatives, and a pending customer decision for every proposal. Print every candidate option in the consultant table defined above. A candidate table is decision-support output only; the customer still selects or approves the owner explicitly. Keep request bodies and internal owner identifiers out of this table.
Candidate evidence enrichment
The default preview enriches only the bounded shortlist, not every returned
worker. Delegate the following GET-only Fusion HCM reads to
core.fusion-api.rest-api-client; the Core skill performs them and returns the
restricted result. First read the candidate's public-worker identity, then the
candidate's assignments:
GET /hcmRestApi/resources/11.13.18.05/publicWorkers/{PersonId}/child/assignments
?fields=AssignmentId,PrimaryAssignmentFlag,JobName,DepartmentName,ManagerName
&onlyData=true
Use the assignment with PrimaryAssignmentFlag=true when returned. To retrieve
manager display context when it is needed for a shortlisted candidate, delegate:
GET /hcmRestApi/resources/11.13.18.05/publicWorkers/{PersonId}/child/assignments/{AssignmentId}/child/managers
Use only returned and relevant details as ranking evidence. An unavailable
manager, assignment, department, position, or person-detail response is not a
reason to discard an otherwise verified candidate; it lowers confidence and is
shown as unavailable. Store candidate details only in restricted decision
evidence, not under project/; they never replace customer approval.
Approval and live execution
Record an explicit table or chat approval for each reviewed Level 2 proposal and each explicit Level 2 existing-owner operation. For a customer-resolved tie, retain the reviewed candidate list and selected internal owner identity. Validate that selection here before continuing. The apply preview re-reads the whole selected scope, rebuilds the hidden member action plan from its unique member set, and shows one business-labelled Level 2 row using the declared approval-table fields. A repeated member identity or multiple roots cancels the scope. A live apply may use only that unchanged approved plan.
Every owner-property mutation uses the documented BOSS bulk endpoint. Do not use collection POST, PATCH, an item endpoint, or an inferred multi-member bulk contract. The recorded contract supports one changed unique scope member per request:
POST /api/boss/data/objects/ora/riskMgmtRisk/core/v1/referenceDataValueProperties/$bulk
{
"items": [
{"$operation": "CREATE", "valueCode": "<member_value_code>", "defaultOwnerType": "USER|GROUP", "defaultOwnerCode": "<approved_owner_code>"}
]
}
Use that CREATE payload only for a member that has no current owner property.
For an unassigned member with exactly one empty property, Core must instead
verify its $id equals its valueCode and that its owner code is still
blank/null, then use the documented DELETE/CREATE request below to replace the
empty property. If the property gained a nonblank code, is missing a matching
$id, or is nonunique, cancel that member and require a new review and
approval. For an explicit UPDATE, Core must verify exactly one current property whose
$id equals its valueCode, and whose internal owner type/code exactly
matches the reviewed source owner. The replacement request uses that identity:
POST /api/boss/data/objects/ora/riskMgmtRisk/core/v1/referenceDataValueProperties/$bulk
{
"items": [
{"$operation": "DELETE", "$id": "<member_value_code>"},
{"$operation": "CREATE", "valueCode": "<member_value_code>", "defaultOwnerType": "USER|GROUP", "defaultOwnerCode": "<approved_owner_code>"}
]
}
An explicit UPDATE changes only members that still match its reviewed source
owner; an unassigned member, including one with an empty property, or a member
owned by anyone else is preserved. An explicit RESET needs the same verified
$id for every member with a valid assigned owner tuple and submits one
one-item bulk request containing only
{"$operation":"DELETE","$id":"<member_value_code>"}. An absent RESET
member or an empty-property RESET member is unchanged. A nonmatching $id,
nonunique property, or any changed member state cancels that member and
requires a new review and approval.
Before the customer approves application, re-read the full Level 2 scope and rebuild the aggregate action
…(truncated)