The process of converting a signup into an order involves specific conditions and manual steps to ensure smooth progression. This article explains the workflow and key statuses involved.
Solution Overview
-
Signups on Non-Deliverable Objects
When a signup is created, it is associated with objects in the Not Deliverable status. At this stage, the signup remains pending and does not transition to an order. -
Changing Object Status to "In Deployment"
- A manual step is required to change the object's status to In Deployment when it is decided that the object/address will be built.
- This action signals the start of the deployment phase.
-
Signup Transition to Order
- Once the object's status is set to In Deployment, the associated signup automatically transitions into an order within the system.
- This order remains inactive until the next step.
-
Activation of the Order
- The order will not be activated until the object is fully deployed, and its status changes to Deliverable.
- This ensures that only completed and ready-to-use objects result in active orders.
Key Notes
- The transition from signup to order depends on the object's status.
- Moving the object to In Deployment is a manual process, requiring deliberate action to confirm that the object will be built.
- The order's activation is conditional upon the object's readiness (status: Deliverable).
By following these steps, the system ensures an organized progression from signup to deployment and order activation.