Question
Lanit
RU
Last activity: 17 Jul 2017 16:46 EDT
Using DSS value for Schema URL in Parse XML rule
I'm trying to use DSS in Schema URL in Parse XML rule. Something like that:
@(Pega-RULES:Utilities).getDataSystemSetting("UCLPCRMInt", "SB/Int/ESB/ESBSettings/CRM/XSDBaseUrl") + "/ProcessLegalLoanApplication/ProcessLegalLoanApplicationMessageElements.xsd"
DSS contains base URL, the second part of this string is differenet for every Parse XML. Can PRPC handle this value?
I found this article https://community.pega.com/support/support-articles/support-dynamic-system-setting-schema-url-parse-xml, but it is for version 6.2.
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
GB
Pegasystems Inc.
GB
Hi Ilya,
What version of PRPC are you on here ? I am pretty sure that (at least up to 7.1.7) - that the SCHEMA field for PARSE XML rules is a 'fixed string' - it will not try and interpret an 'Expression' nor a "Global Resource Setting" type : https://pdn.pega.com/integration/how-to-reduce-maintenance-of-service-rules-and-listeners-with-global-resource-settings
It may have been enhanced in 7.1.8 - but I would have to check.
Thanks,
John
Lanit
RU
We are using 7.1.8
Accepted Solution
Pegasystems Inc.
GB
OK Ilya - I don't think this facility exists in 7.1.8 - but I only checked empirically on my system - and I may have made a mistake - somebody else may be able to correct me.
This is what I tried:
I put in a '=' Global Resource style string like this:
And created an activity to create the TestPage with a single TestProp set to the SOAP XSD: http://www.w3.org/2001/12/soap-envelope
So I have this CLIPBOARD page sitting in memory:
OK Ilya - I don't think this facility exists in 7.1.8 - but I only checked empirically on my system - and I may have made a mistake - somebody else may be able to correct me.
This is what I tried:
I put in a '=' Global Resource style string like this:
And created an activity to create the TestPage with a single TestProp set to the SOAP XSD: http://www.w3.org/2001/12/soap-envelope
So I have this CLIPBOARD page sitting in memory:
I stole a SOAP ENVELOPE from the web : SOAP Example
And tried to validate this SOAP ENVELOPE with the this (making sure I had switched my "XML validation" to 'always').
And I get this:
<?xml version="1.0"?> <pagedata> <pxObjClass>GCS-GCSApp-Work</pxObjClass> <pzStatus>false</pzStatus> <PZ__>** Error Found: cvc-elt.1: Cannot find the declaration of element 'soap:Envelope'.</PZ__> </pagedata>
Which *suggests* that the XSD was not located*
If I change my Parse XML rule to have the XSD 'hardcoded' to the URL, I get an actual validation message:
<?xml version="1.0"?> <pagedata> <pxObjClass>GCS-GCSApp-Work</pxObjClass> <pzStatus>false</pzStatus> <PZ__>** Error Found: cvc-complex-type.3.2.2: Attribute 'soap:encodingStyle' is not allowed to appear in element 'soap:Envelope'.</PZ__> </pagedata>
*as I said - it may be my test is invalid (perhaps the Page 'MyTestPage' is not valid?) - but it looks likely to me that this mechanism is not available for this particular PRPC setting unfortunately.
We probably need to get an ENH/FEEDBACK item in for this - for later versions of the product - sounds like it could be useful to have.
Lanit
RU
Hi John,
Yes, you are right! We can use this syntax and validation works correct.
Thank you!
Kind regards,
Ilya Fedotochkin
OK Ilya - I don't think this facility exists in 7.1.8 - but I only checked empirically on my system - and I may have made a mistake - somebody else may be able to correct me.
This is what I tried:
I put in a '=' Global Resource style string like this:
And created an activity to create the TestPage with a single TestProp set to the SOAP XSD: http://www.w3.org/2001/12/soap-envelope
So I have this CLIPBOARD page sitting in memory:
OK Ilya - I don't think this facility exists in 7.1.8 - but I only checked empirically on my system - and I may have made a mistake - somebody else may be able to correct me.
This is what I tried:
I put in a '=' Global Resource style string like this:
And created an activity to create the TestPage with a single TestProp set to the SOAP XSD: http://www.w3.org/2001/12/soap-envelope
So I have this CLIPBOARD page sitting in memory:
I stole a SOAP ENVELOPE from the web : SOAP Example
And tried to validate this SOAP ENVELOPE with the this (making sure I had switched my "XML validation" to 'always').
And I get this:
Which *suggests* that the XSD was not located*
If I change my Parse XML rule to have the XSD 'hardcoded' to the URL, I get an actual validation message:
*as I said - it may be my test is invalid (perhaps the Page 'MyTestPage' is not valid?) - but it looks likely to me that this mechanism is not available for this particular PRPC setting unfortunately.
We probably need to get an ENH/FEEDBACK item in for this - for later versions of the product - sounds like it could be useful to have.