HDP deploying specific task doesn't get deployed to all dependent MUs

Document ID : KB000087227
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
There is no error message.

Patch level detected:Univiewer Console 6.2.00
Product Version: Dollar.Universe 6.2.0

Description :When we try to deploy a task that has a specific task that's running on multiple dependent MUs (HDP), the subtask gets only deployed on the first dependent MU.

Reproduction Procedure:

1- Create 3 Uprocs: TEST1, TEST2 and TEST3

2- Create 3 MUs: CFATHER, CSON1, CSON2
Make CSON1 and CSON2 dependent on CFATHER

3- Create a session TESTSES:
TEST1 (MU = SAME MU) --> TEST2 (MU = HDP = {C }
TEST1 (MU = SAME MU) --> TEST3 (MU = SAME MU }

4- Create a template task: TESTTASK where
TEMPLATE NAME = CFATHER
SESSION = TESTSES

5- Create a specific task TESTSPECTASK for the task above where
SESSION = TESTSES
UPROC= TEST2
TEMPLATE NAME is left blank (Since we don't know which MU to choose because of HDP)

6- Deploy TESTTASK:
Go back to the list of tasks, right click on TESTTASK and click on send to.
In the deployment menu, the source should automatically be set to TESTTASK.
The destination should be set to MU (Do not choose an MU from the list), and then at the end check the 2 boxes (Enable the following... AND use the MU/Template ...)
Click on next

--> You will notice that the subtask TESTSPECTASK gets only deployed on one of the two dependent MUs (It always chooses the first one in the MU dependency list).

The subtask should be deployed on both dependent MUs (MUSON1 and MUSON2)
Environment:
OS: All
Cause:
Cause type:
Defect
Root Cause: N/A
Resolution:
Update to the fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Component: Univiewer.Console
Version: Dollar.Universe 6.2.21
Additional Information:
Workaround :
N/A