====== The Deployments Portal ======

The Deployments Portal allows the engineering team to set the status of deployments/migrations as they happen meaning team leaders and others within the project team can get accurate status information at any time. Deployments are only listed once they reach a state of //5 - Deploy Ready//.

The Admin user must have the Schedule Groups allocated in the //Assignments and Deployments Portal// tab of the Admin properties in order to see the deployments for the Schedule Groups in this Portal. They must also have the correct corresponding Asset Locations assigned as well as the security permissions within the project structure. 

As with the other Admin Portals the Assignments Portal is supported in the latest versions of Internet Explorer and Google Chrome.

====== Navigating the Deployments Portal ======

The header bar of the Deployments Portal shows the project structure path and Schedule Group name along with the Project Manager and Primary Contact name and telephone numbers if configured. The footer bar is where you can select which Schedule Group (or point in the project structure) that you have permission to, that the deployment records are that you are managing. Deployments are listed in the main part of the page with successful deployments indicated with a tick on the right and failed deployments indicated with a cross. Overdue deployments will have the date on the left highlighted red.

The second drop down list in the footer bar allows you to filter the view of the records listed. The view filters are:
  * today (default)
  * tomorrow
  * next 7 days
  * overdue
  * select date  (displays a further list with the dates of the deployment window from which you can select. The list of records is only those that are incomplete)
  * select data - all (as select date but the list of records includes succeeded and failed deployments also)
  * all

Clicking on the Build Sheets button will download a single PDF file of all the Build Sheets of the selected view.

{{:dms:deploymentsportal.png?nolink|}}


====== Succeeding and Failing Deployments ======

Selecting a record from the list will reveal the deployment options:

{{:dms:deploymentsportal_selected.png?nolink|}}

^  Deployment Menu  ^  Description  ^
|Deployment Succeeded|Click on Deployment Succeeded to open the Deployment Succeeded window. The date, time and name of the DTL Portal user are recorded against the deployment. |
|Deployment Failed |If the deployment/build process fails you can record it here with a reason code. The codes are the Fail Codes created in DMS Console Setup.  Once a deployment has been recorded as failed it can only be rescheduled using DMS Console. |
|Notes |You can view all notes against a deployment and add additional ones. |
|Build Sheet |Individual deployment build sheets can be produced using this button. |


===== Deployment Succeeded =====
When the //Deployment Succeeded// button is pressed the proceeding action depends on the deployment type and whether Asset Tracking is enabled for the deployment(s) or not.

Deployment Types //Rebuild// and //Return// will simply reveal an  OK/Cancel confirmation dialogue regardless of whether Asset Tracking is active for the deployment.

For Deployment Types //New// and //Replace// with Asset Tracking enabled where new assets have been assigned to the deployments when the Deployment Succeeded button is pressed the Deployment Succeeded OK/Cancel dialogue is revealed showing the details of the preselected asset.

Where new assets have not been assigned to the deployments when the Deployment Succeeded button is pressed a list of unassigned assets is shown from which to choose the asset used for the deployment/migration. The list is from the upstream asset location to the Deployment Location for the Schedule Group.

For Deployment Types //New// and //Replace// with Asset Tracking disabled when the Deployment Succeeded button is pressed the Deployment Succeeded OK/Cancel dialogue is revealed and prompts the user to create the new asset by selecting the model and entering the computer name, serial number and asset tag.

Selecting a //New// or //Replace// deployment once it is succeeded will reveal the //Edit Computer// and //Notes// buttons. Whether an asset was pre-assigned or not the computer name and/or asset tag can be edited. Notes can be viewed or or new Notes added.


===== Deployment Failed =====

When the Deployment Failed button is pressed the user is presented with the [[dms:configuring_dms#fail codes|preconfigured Fail Codes]] from which to choose. It is important to ensure all Admin Users know which fail codes to use as certain codes may be used to generate other actions or even charges.