mino98
Contributor
Contributor

Decision statement pulldown list

Jump to solution

I'm using vOrchestrator 4.0.0 build 4240, and I've noticed what i think it's a bug:

if I open up the Schema tab, select a "decision element" and try to edit the "Decision" tab, I can add/edit/delete properties but the decision statement pulldown list always remains empty. Explicatory image :

7076_7076.png

This problem is reproducible 100% of times, regardless of the variable type.

I've already tried uninstalling/reinstalling vorchestrator, is there anything i should do? am i doing anything stupid? is it a known bug, by any chanche?

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

check your release notes.

http://www.vmware.com/support/orchestrator/doc/vco_40_release_notes.html#miscissues - which was build 4240, see the following Known Issue:

"No input parameters are displayed in the drop-down menu for the Decision workflow schema element.

  • You cannot define or edit the decision statement because the possible input parameters are not visible on the Decision schema element's properties tab.


    Workaround: Use a Custom Decision schema element."

Also:

http://www.vmware.com/support/lcm102/doc/releasenotes_lcm102.html#whatsnew

"The LCM 1.0.2 release runs on an updated version of VMware vCenter

Orchestrator 4.0. To run LCM 1.0.2, you must install the version of

Orchestrator (4.0.0 Build 4439) that accompanies the LCM 1.0.2

download. See the vCenter Lifecycle Manager 1.0.2 Administration Guide for installation instructions."

So LCM 1.0.2 requires a newer build of VCO 4 (build 4439), which naturally will have some known issues resolved in it.

View solution in original post

0 Kudos
6 Replies
Burke-
VMware Employee
VMware Employee

If this were a bug, It looks like it is fixed in newer builds: (Screenshot taken from vCO 4.0.0 Build 4439- Distributed with LCM 1.0.2)

7077_7077.png

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
0 Kudos
mino98
Contributor
Contributor

I just downloaded vSphere again and uninstalled/reinstalled VCO with no result...

I also updated the JVM.

I'll try to open a support request Smiley Sad

0 Kudos
admin
Immortal
Immortal

check your release notes.

http://www.vmware.com/support/orchestrator/doc/vco_40_release_notes.html#miscissues - which was build 4240, see the following Known Issue:

"No input parameters are displayed in the drop-down menu for the Decision workflow schema element.

  • You cannot define or edit the decision statement because the possible input parameters are not visible on the Decision schema element's properties tab.


    Workaround: Use a Custom Decision schema element."

Also:

http://www.vmware.com/support/lcm102/doc/releasenotes_lcm102.html#whatsnew

"The LCM 1.0.2 release runs on an updated version of VMware vCenter

Orchestrator 4.0. To run LCM 1.0.2, you must install the version of

Orchestrator (4.0.0 Build 4439) that accompanies the LCM 1.0.2

download. See the vCenter Lifecycle Manager 1.0.2 Administration Guide for installation instructions."

So LCM 1.0.2 requires a newer build of VCO 4 (build 4439), which naturally will have some known issues resolved in it.

View solution in original post

0 Kudos
mino98
Contributor
Contributor

Ok thanks, I will now upgrade.

However, I find it a bit confusing that the build number of the VCO packaged with vSphere differs from that of the VCO packaged with LCM... Smiley Happy

0 Kudos
admin
Immortal
Immortal

As who else mentioned, this is a know issue and the work around is using the custome decision box, which takes the expected boolean return and branches to the next boxes.

If you feel strongly about seeing the decision box work, please contact VMware's support organization and obtain a patch.

Thanks,

Sia

0 Kudos
mino98
Contributor
Contributor

I already upgraded, that solved the problem.

0 Kudos