VMware Aria Automation Orchestrator

 View Only
  • 1.  __tokenName not working with Service Broker

    Posted Aug 27, 2024 09:39 AM

    Hello, 

    I use the input __tokenName in my vRO workflow. When I add the workflow to the Service Broker, it is not submitted, and throws the exception that __ is not allowed. 

    Is there a workaround on how to use __tokenName in the Service Broker, or preferable how to set it directly in the workflow (not as an input) - I have found a single link about it, but it does not longer work :/

    Regards, K



  • 2.  RE: __tokenName not working with Service Broker

    Broadcom Employee
    Posted Aug 28, 2024 09:03 AM

    User-defined input properties with a double underscore are forbidden. The double underscore is reserved for system metadata. 

    Anyways, can you tell me more about this property? Where is the value supposed to come from if you don't want it to be an input?




  • 3.  RE: __tokenName not working with Service Broker

    Posted Aug 29, 2024 11:02 AM

    When using it in vRO, where it is working fine, you can set the value in the input as a conditional value taken from another input field. E.g I can set / rename the workflow run for a specific task. E.g. Change Request Number + Server Name + System Owner specified as input variables. The can be combined so the __tokenName is eg. "Some Random Text - CH123456 - MYSERVER01 - Bobby". It will give a good overview of the workflows run, and is working fine if the workflow is initiated in vRO. It is not possible if the same workflow is initiated via the Service Broker, as __tokenName is imported as in invalid input property. 

    My question was then, if I can use the __tokenName (concatenated by different input fields), I was looking for a workaround to rename the workflow run, from the workflow itself in vRO.




  • 4.  RE: __tokenName not working with Service Broker

    Posted Aug 28, 2024 09:24 AM

    Hey,

    I believe you cannot achieve this using Service Broker. It will work if the workflow is triggered directly in vRO. Could you please explain your use case?



    ------------------------------
    If you find the answer helpful, please click on the RECOMMEND button.

    Please visit my blog to get more information: https://www.clouddepth.com
    ------------------------------



  • 5.  RE: __tokenName not working with Service Broker

    Posted Aug 30, 2024 06:20 AM

    it's not a solution but workaround (AFAIK it's not normally possible).

    Create new little workflow, called via ServiceBroker, then this workflow will call your 'main' workflow with __tokenName specified...