Prove and submit the adhesive put-away policy
Freeze the stores policy with the adhesive put-away rule, run StoresFlow's complete proof of every expected result and submit that exact release for independent review.
For authors
Freeze the stores policy with the adhesive put-away rule, run StoresFlow's complete proof of every expected result and submit that exact release for independent review.
Read these instructions on any device. Watch or practise a chapter on a desktop or laptop, with a desktop or mobile application layout. Demonstrations use sample data and simulated scanners.
Prove and submit the release
- Load the current StoresFlow draft
Load the current StoresFlow draft
Load the stores policy with the adhesive put-away rule and its reviewed expected results.
- Freeze the release candidate
Freeze the release candidate
Freeze the complete stores policy with its reviewed expected results. The candidate holds exactly the rule saved from the plain English proposal.
- Verify every expected result
Verify every expected result
Run StoresFlow’s complete check of every expected result. StoresFlow keeps the proof with this exact candidate.
- Read the proof result
Read the proof result
Read the proof. All six examples give the expected result, and the adhesive put-away rule is reached by an example.
- Check the put-away results
Check the put-away results
Check the put-away examples: known adhesive goes to Adhesive cabinet (R-02) by the new rule, and the other two stay at Assembly fasteners (R-01) by default.
- Assemble the exact release proposal
Assemble the exact release proposal
Keep the complete stores policy, its independent expected results and the proof together in one exact release proposal.
- Request independent release review
Request independent release review
Submit this exact stores policy for a separate person to review. This does not activate it.
The exact release is submitted. A separate reviewer decides; activation is a separate action.