JNY-ACC-PRD-004 Console corrections preserve API-configured selling settings
Markdown Planning / Accounting / Products / Selling Settings / Journey Story An API client configures selling information before finance corrects the catalogue through the console. The journey follows rename, withdrawal and explicit clearing to distinguish preservation from removal. Some hidden settings are supported by observed form behavior rather than the browser test’s narrower feature assertions.
Show evidence (sources, provenance, origins, pinned commits)Goal Retain configured purchase ceilings, tasks, bands, components and messaging through later catalogue corrections. Screens /console/{tenantId}/configuration/accounting/products/{id} /console/{tenantId}/configuration/accounting/products Steps # Surface Action Capability Expected Provenance 1 createProductCreate a product with a customer ceiling, task instructions, discount bands, shared confirmation, fee and notes. CAP-ACC-PRD-012The response retains the configured feature values. test 2 updateProductSupply ticket and programme components with allocation prices. CAP-ACC-PRD-011Valid quantity-weighted allocation saves within the product’s price limits. test 3 /console/{tenantId}/configuration/accounting/products/{id}Rename the product through its console editor. CAP-ACC-PRD-004Hidden ceiling, confirmation and component controls do not discard loaded settings. observed 4 /console/{tenantId}/configuration/accounting/productsDeactivate it from the catalogue row. CAP-ACC-PRD-004The tested ceiling, tasks, bands, fee and notes remain stored on the inactive product. test 5 updateProductClear selling features with empty settings through the API. CAP-ACC-PRD-013The response shows cleared features and rejects empty arrays for list features. test
Alternate and Failure Paths Path From step Condition Path taken Outcome Provenance alternate 1 The product uses owned confirmation content. Ask Platform to validate and save content during the product transaction. Platform refusal rolls back product writes, but later commit failure can leave changed content. test failure 1 Discount bands share quantity ten. Reject the conflicting bands and identify them. No product creation survives. test failure 1 A task uses a missing CRM type. Reject the unavailable task type. No product creation survives. test
Assertions Id Statement Provenance 01The tested ceiling, tasks, quantity bands, fee and notes survive rename and deactivation. test 02Rejected empty list writes leave the product version unchanged. test
End-to-end policy: required: API settings must survive console corrections across hidden and visible controls.
← Previous Journey JNY-ACC-PRD-003 · Finance configures valid donation and audience pricing Next Journey → JNY-ACC-PRD-005 · Finance completes revenue treatment and missing setups