Question

2
Replies
90
Views
STEWM Member since 2006 5 posts
PEGA
Posted: 3 years ago
Last activity: 3 years 5 months ago
Closed
Solved

Looking for way to minimize manual labor on XML data model update imports

We've imported an xml data model (attached to thread) into our Enterprise layer. It comes from a data governance group. They will periodically send us an updated xml model to import.However, upon the first import, we had to manually change it so Pega could use it. I'll detail our changes below, but suffice it to say, we dread the next update they send us. Is there a better, less labor intensive, way deal with this problem?

Following are the issues we had with data model after the import:

1. Pega is including namespace for attributes when it shouldn't. Schema defines the attributes to not be qualified with namespace.

<xs:schema attributeFormDefault="unqualified"

elementFormDefault="qualified"

targetNamespace="http://ACORD.org/Standards/Life/2"

xmlns:ns2="http://ACORD.org/Standards/Life/2"

xmlns:xs="http://www.w3.org/2001/XMLSchema">

2. For date time fields, the parse and XML stream rules have datetime type. We get an ACORD time format and Pega XSD datetime format is unable to parse the datetime and throws an exception.

3. Pega is unable to work well with elements which following naming pattern such as "<xs:element name="com.CompanyName.OtherCoverage">".

***Updated by moderator: Lochan to add group tag, SR Exists***

***Updated by Moderator: Marissa to add SR details***

Low-Code App Development SR Created SR Exists
Moderation Team has archived post
Share this page LinkedIn