posts/vro-how-to-use-external-validations/

[giscus[bot]]

posts/vro-how-to-use-external-validations/

Problem

https://www.clouddepth.com/posts/vro-how-to-use-external-validations/

[dennis2vsteaks]

Hi clouddepth,

do you have any examples how to use input validations on custom forms when using external source actions with service broker ?

[unbreakabl3]

Hi @dennis2vsteaks ,
I think this article is exactly what you need. Or maybe I didn't get properly your question. Do you have an example with some details of what exactly you want do? :)

[dennis2vsteaks]

Hi Leo,
see my screenshots.. I have created a catalog item with service broker based on a vro workflow. On top of that catalog item , I am using a custom form what is using a vro action for one of the input fields. This is working all fine, however service broker is complaining about non-validatable (Input Validation) for my Form action. I have tried to make a validation action for this however service broker is still giving me a warning. Do you know how to get this properly working.. (I have to delete the screenshots again after you have read my post)

[unbreakabl3]

Got it. Let me take a look.

[unbreakabl3]

Hi, @dennis2vsteaks
So, I think I have an answer. It may be worth to create a small article about that, so more people will see it. Is that ok with you?

[dennis2vsteaks]

yes, sure .. go for it ;)

[unbreakabl3]

Hi @dennis2vsteaks ,
please take a look here: https://www.clouddepth.com/posts/vra-service-broker-input-validation-warning/

[dennis2vsteaks]

Hi Leo,
Thanks for the new blog, however it does not explain to me how to use the validation actions what can be used on top of the inputs of the custom form itself. The General Validation Warning message I understand but that is not the part I was looking for.
I think the answers lies somewhere in the validations section of the custom form..

What I would expect is that when you use it correctly it will change the external action from non-validatable to validatable

[unbreakabl3]

Hi,

I’m glad I’m not the only one thinking this way! 😁
I would expect the same, but unfortunately, as far as I know (at least for now), this is just how it’s implemented. The “non-validatable” doesn’t really do anything—it’s purely cosmetic. Its only purpose is to give you a heads-up: “Be aware…”.

[dennis2vsteaks]

hmm so my expectiation to this new feature is to high.. that's a bit dissapointing

What is than the purpose at all for these External validations on custom forms.. I don't get it..

The below is the only documentation I was able to fine about it..

https://techdocs.broadcom.com/us/en/vmware-cis/private-ai/foundation-with-nvidia/5-2/service-broker-custom-forms-learn-more-about-service-broker-custom-forms.html

https://techdocs.broadcom.com/us/en/vmware-cis/private-ai/foundation-with-nvidia/5-2/validate-workflow-inputs.html

[unbreakabl3]

The purpose is to tell you to be aware that if the workflow you're developing may/will be consumed via API, you need to make sure the provided input's values in API's body JSON are correct/matching the inputs in the action element in the workflow. If you will consume this service catalog item only via vRA's GUI, you can ignore it by clicking on "I UNDERSTAND".