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.
Original Message:
Sent: Aug 28, 2024 05:42 AM
From: Martin Petkov
Subject: __tokenName not working with Service Broker
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?
Original Message:
Sent: Aug 27, 2024 02:53 AM
From: thork
Subject: __tokenName not working with Service Broker
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