A signed digital contract automatically becomes a purchase order, which automatically becomes a production order executed by a Minecraft bot.
1) Purchase Requisition
- A purchase requisition is created in Dynamics 365.
- It contains data:
- Product
- Quantity
- Unit price
- Total price
- The requisition enters an Approval Signing stage.



2) Approval Signing using OneFlow
- When the requisition reaches the signing stage, a Power Automate flow is triggered.
- The flow:
- Sends requisition data (product, qty, prices) to a child flow
- Creates a OneFlow contract
- Adds required participants (approver / counterparty)
- Publishes the contract for digital signing
- The approver signs directly in OneFlow.
- Contract status updates are sent back via OneFlow triggers.

3) Purchase Order and Purchase Order Lines Creation
- When the OneFlow contract is fully signed:
- A Power Automate flow triggered by “contract updated” runs
- Contract details are retrieved
- Product, quantity, and pricing are extracted
- The flow then:
- Creates a Purchase Order header in Dynamics 365
- Creates corresponding Purchase Order lines
- The Purchase Order is now an approved, system-generated transaction based on the signed contract.

How it triggers the rest of the solution : Production Order and Minecraft Bot Execution
- The approved Purchase Order triggers creation of a Production Order.
- The Production Order:
- Reads the Bill of Materials
- Determines required resources
- A Minecraft bot is started:
- Enters the Minecraft world
- Mines, crafts, and gathers required materials
- Completes the production task
- When finished:
- Status is sent back to Dynamics 365
- The Production Order is completed/closed
In short;
We have a automated flow to create production order with an approval flow integrated with OneFlow,
and thats why we deserve the Go with the flow badge and OneFlow sponsor badge

____-
Cepheo Crafting Creepers