Is it possible to use a repository reference in the Schema URL reference for a Parse XML rule’s validation? If so, what is the syntax?
Customer curently has file:///path/schemaname.xsd for a reference to the local file system, but they are migrating to the Pega Cloud. We have not identified a suitable web server to host the resources, and would like to manage the content in the repository.
@healj Did you manage to find solution for this?
@VenkateshG8536 as part of modernisation assessment the client has taken a close look at the implementation and has concluded that the XSD validation is redundant. Their implementation catches both schema validation errors and XML transformation errors and reports them in the same way. They have decided to remove the XSD reference in modernisation as they have no recorded schema validation errors in production. The only context this is set is for XML payloads for SOAP messages on the client’s ESB. This is a deprecated integration mechanism that will be replaced by a web services gateway over time.
As I understand, the answer is no for versions up to Pega Infinity 23.2. This field does not support the repository reference syntax.
@healj please see the answer provided in question Parse XML schema URL repository path.
Note: I’m aware that we are still waiting for a response from our engineering teams for the following question:
“*Does Cloud3 offer any capability for hosting files that need to be accessed via standard URL’*s?”
Based on the provided context, Pega Cloud 3 does not offer the capability to host files that need to be accessed via standard URLs.
Using repository APIs in your application > Pega Cloud Services File Storage note