.. _plar_(hotdial)_workflows:

PLAR (Hotdial) Workflows
------------------------

When adding a new Hotdial Phone (PLAR configuration), the following
workflow is executed:

1. A Unified CM route partition is created with:

   a. Name set to the Hotdial Phone selected, prefixed with "HotdialPT-". For example:
      "HotdialPT-SEP000000000000".
   
#. A Unified CM CSS is created with:

   a. Name set to the Hotdial Phone selected, prefixed with "HotdialCSS-". For example:
      "HotdialPT-CSS000000000000".
   #. The Partition created above is made a member of the CSS.

#. A Unified CM translation pattern is created with:

   a. Partition name is set to the Partition added, prefixed with "HotdialPT-",
      for example: "HotdialPT-SEP000000000000".
   #. Calling Search Space Name set to the selected Destination Dialing CSS.
   #. Called Party Transformation Mask is set to the selected Hotdial Destination Pattern.
   #. Route Option is set to Route this pattern.
   #. Urgent Priority is enabled.
#. The Unified CM phone selected is updated as follows:

   a. For SIP Phones only, a SIP Dial rule is created and the phone is set to use
      the SIP Dial Rule.
   #. CSS name is set to the "HotdialCSS-" added for the Phone.
   #. Hotline Device is set to true if the phone is marked as a Hotline Device by
      the user on the input form.


VOSS Automate automatically resets the phone when required.

When deleting PLAR (Hotdial) for a Phone (deleting the PLAR configuration),
the following workflow is executed:

1. Update Phone CSS to the original CSS.
#. Delete the Hotdial Translation pattern.
#. Delete the Hotdial CSS.
#. Delete the Hotdial Route Partition.
#. For SIP Phones only, the device is updated to use a Dial Rule of "None", and
   the Dial Rule is deleted.