1 person found this helpful
- Which vRO version is this?
- When you rerun the workflow and get validation failure - are you launching a new workflow execution, or re-running a previous workflow execution?
- What is the type of the attribute you get validation errors for - securestring, normal string, or something else?
- Could you prepare and attach a small sample workflow + configuration element that demonstrate the problem, so we can try to reproduce it in our environments?
In general, you can disable validations in the client (Tools > User preferences > Workflows), but not per individual validation check.
Up until now.. I got the errors after importing the package in vRO.
I got these randomly from boolean attibutes and secure string password one too.
I got error when running a new execution workflow.
We have Orchestrator 7.5 embedded in vRA.
Before I was using the attributes configured on the workflow itself and did not get this issue...
It only happens when placing these as configuration elements.
I attached some screenshot.
Thanks for your help.
Finally I was able to workaround it.
As I am not using username / password, I removed the binding from the Configuration element and just leave these empty in the workflow.
Validation passes... So if another need to use password, then they can set the correct value in the configuration element and bind these again.
Thanks for you help.