ATS-CRM-ACT-013Offer work to a security role and reserve it by claim: Acceptance Test Set

ATS-CRM-ACT-013

Offer work to a security role and reserve it by claim: Acceptance Test Set

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Offer work to a security role and reserve it by claim: Acceptance Test Set

Coverage

Bound scenarios identify existing assertions; unbound scenarios remain proposed proof. Static inspection does not establish a passing execution.

Show evidence (sources, provenance, origins, pinned commits)

6 scenarios proving CAP-CRM-ACT-013; 5 bound to an existing test.

01 Create a role offer without a simultaneous holderapinegativetest

Proves: BR-CAP-CRM-ACT-013-01
Preconditions: A role has eligible users.
Steps: Create offers by custom reference and built-in key, then include both a holder and role.
Expected: Valid offers remain unassigned and the combined assignment fails.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#stores the role as the candidate role and leaves the task held by nobody
services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#stores a built-in role by its key
services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#refuses a create naming both an assignee and a role, naming the field, and writes nothing
services-crm:modules/tasks/tests/integration/db/tasks.table.integration.spec.js#refuses a task created both assigned to a person and offered to a role
Source: services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#stores the role as the candidate role and leaves the task held by nobody

02 Check role membership on unqueued claimsapinegativetest

Proves: BR-CAP-CRM-ACT-013-02
Preconditions: An offered task and a non-holder are available.
Steps: Attempt a non-holder claim and a built-in-role holder claim.
Expected: The non-holder is forbidden while the eligible holder succeeds.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#is refused 403 with the code task_claim_not_role_holder, and the task stays offered
services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#claims it: the key is resolved to the role, which the holder holds at the customer’s scope
services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#refuses a user who does not hold the role 403, code task_claim_not_role_holder
Source: services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#is refused 403 with the code task_claim_not_role_holder, and the task stays offered

03 Select one role holder in a claim raceapinegativetest

Proves: BR-CAP-CRM-ACT-013-03
Preconditions: Three users hold the candidate role.
Steps: Claim concurrently.
Expected: One user receives assignment and the others receive winner-specific conflicts.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/tasks/tests/integration/services/persistence/tasks.concurrency.integration.spec.js#refuses the other two 409 with the code task_claimed_by_other
services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#refuses the second holder 409, code task_claimed_by_other
Source: services-crm:modules/tasks/tests/integration/services/persistence/tasks.concurrency.integration.spec.js#refuses the other two 409 with the code task_claimed_by_other

04 Reoffer released work and clear reassigned offersapitest

Proves: BR-CAP-CRM-ACT-013-04 BR-CAP-CRM-ACT-013-05
Preconditions: A claimed task retains its candidate role.
Steps: Release it and assign a different holder.
Expected: Release preserves the offer and different-holder assignment clears it.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#keeps the candidate role, so the task is offered again
services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#clears the role when the task is given to somebody other than its holder
services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#keeps the role when the claimed task is handed back
services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#offers the task again on a release: nobody holds it, the role kept
Source: services-crm:modules/tasks/tests/integration/services/persistence/tasks.role-claim.integration.spec.js#keeps the candidate role, so the task is offered again

05 Page work offered to the current role holdingsapitest

Proves: BR-CAP-CRM-ACT-013-07
Preconditions: Some role offers are unassigned and one has been claimed.
Steps: Read and paginate offered work, then request an excessive page.
Expected: Eligible unclaimed tasks appear oldest first and pages above 200 fail.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/tasks/tests/integration/services/persistence/tasks.queries.integration.spec.js#answers the three tasks offered to the user’s roles, oldest first, then by id
services-crm:modules/tasks/tests/integration/services/persistence/tasks.queries.integration.spec.js#answers a page at most as long as the limit, with where it ended
services-crm:modules/tasks/tests/integration/services/persistence/tasks.queries.integration.spec.js#answers an empty page for a user who holds no role
services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#refuses a page longer than 200, 400
Source: services-crm:modules/tasks/tests/integration/services/persistence/tasks.queries.integration.spec.js#answers the three tasks offered to the user’s roles, oldest first, then by id

06 Expose role offers in a future console viewbrowserproposed

Proves: BR-CAP-CRM-ACT-013-09
Preconditions: The signed-in user holds the role named by an offered task.
Steps: Open Tasks and inspect offered-work access.
Expected: The proposed contract provides an offered-to-me view; that view is not implemented.
Data: Each run creates and isolates the records it needs.
Source: FND-CRM-ACT-010