Once you have created the drop order to get a a connection, you can follow up and manage the connection workflow process.
 It's done through the menu "Connect!", option "Pending drops" option.
There you'll get a report of your requested connections (drops). Certain roles do have also a tab available to see requests from others.
It is intended that this report provides follow-up to all pending requests, so they can be completed within the scope of the objectives agreeded (for example., 2 weeks), either by completing the provision, postpone or reject the request and provide a breif comment for that action (for example, not viable, need to wait for some pre-requisites, ...).
So it is advised to work proactively on this report to manage the requests properly on time and maintaing the queue as clean and short as possible.
To support this, at the very end of every row of the provided report, the authorized accounts for managing the drop order will obtain options for either:
- Schedule the request.
The form will be filled with the agreeded slot for deploying the connection, and eventually be assigned to someone who has been accredited with the installer role for the area you are in. - Execute the request so gets completed and becomes a service.
The form will get all the needed information from the drop execution, such as where is connected and how is executed, quality signal metrics etc. Will also provide a capability to configure easily the the terminal connected (ONU), which is usually a router located at someone's house. - Reject the request.
In case that the execution is not poossible for whatever reason or can't be postponed, requests can be rejected and provide a brief description of the reason.
Once the process for getting a connection is completed, the request is not longer seen at this report and becomes a service, so can be managed later on at the "Services" options provided.