noCV
BAPIPAGE-101 · Define query semantics

Define supported shipment filters and their exact semantics

Practice briefTaskFoundational

Different clients interpret date ranges and empty status lists differently.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
API design

Estimated field mix

  • API design100%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Project context

A fictional logistics platform lists shipments for partner dashboards. Offset pagination duplicates records during updates, while unrestricted filters create expensive database queries.

Setup prerequisites

  • Create a local shipment dataset with synthetic tenants, equal timestamps, and concurrent update fixtures.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Specify inclusive and exclusive boundaries.
  • Distinguish absent from empty filters.
  • Reject unsupported filter properties.

Implementation constraints

  • Use UTC instants for timestamp filters.

Verification to include

  • Exercise a boundary timestamp.
  • Reject an empty status list if the contract declares it invalid.

Deliverables

  • Filter contract.

Rollout and recovery

Publish explicit examples before replacing legacy behavior.

Value of the work

For the engineer: Practice cursor design, query contracts, and consistency/performance tradeoffs.

For the team: Provide predictable list APIs that remain bounded and preserve tenant scope.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.