Page a saved query's records for another application
What It Does
Accounting or Marketing requests a population page or count for a named person in a workspace. Remote invocation is enabled only through the corresponding configured lifecycle participant.
The Flow
Invoke the application-specific live function with the operation, workspace, person and source question or embedded definition. Validate the invocation and reconstruct an eligible person context before opening the saved source. Check the current definition and population restrictions, substitute permissible defaults and order by record identity. Execute a bounded page or count with its fingerprint and continuation; Marketing field reads use the person context too.
When Something Fails
Function failures or throttling return control to the caller’s retry policy. This read does not persist a population snapshot. Return structured access or payload refusal codes. No population is returned after refusal. Refuse an invalid population source without execution. The caller receives no partial successful page. Database faults propagate to the invoking workflow. Another attempt can observe intervening record changes.
Idempotency and Concurrency
A cursor binds ordering and the query fingerprint; changed criteria reject it. Retrying the cursor does not freeze records or guarantee identical values while the underlying data changes. Accounting has its dedicated single-concurrency invocation boundary; Marketing uses its configured environment limit. Population pages obey the statement timeout.