What ext. XSD structure (tags, attributes) is supported by "Connector and Metadata Wizard (legacy)" to get Pega data model?
We are looking for a reproducible easy way to get from external XSD files that represent data models to a data model in Pega that can be referenced and used directly in App Studio. Connector and Metadata Wizard looks promising.
What XSD structure, tags, attributes are supported by that wizard and to what data model structure are these mapped in Pega?
This wizard seems to parse XSD files and generates data model from that.
What is the meaning of "legacy" in it? Is it deprecated?
I can import existing XSDs successfully, but in these there are tags like>
- <element name="technical ID">
- <annotation>
- <documentation>
- <name>"human readable name"</name>
- <definition>...</definition>
- etc...
- <documentation>
- <annotation>
First obstacle is that the annotation tags and substructures are ignored by Wizard
The technical ID in element attribute "name" is imported as property ID in Pega, but it is not well suited for App Studio property identification.
The human readable name (documented in XSD in annotations) is ideal for our property "short description", which is used as default "label" in App Studio when accessing it in view design.
We are looking for a reproducible easy way to get from external XSD files that represent data models to a data model in Pega that can be referenced and used directly in App Studio. Connector and Metadata Wizard looks promising.
What XSD structure, tags, attributes are supported by that wizard and to what data model structure are these mapped in Pega?
This wizard seems to parse XSD files and generates data model from that.
What is the meaning of "legacy" in it? Is it deprecated?
I can import existing XSDs successfully, but in these there are tags like>
- <element name="technical ID">
- <annotation>
- <documentation>
- <name>"human readable name"</name>
- <definition>...</definition>
- etc...
- <documentation>
- <annotation>
First obstacle is that the annotation tags and substructures are ignored by Wizard
The technical ID in element attribute "name" is imported as property ID in Pega, but it is not well suited for App Studio property identification.
The human readable name (documented in XSD in annotations) is ideal for our property "short description", which is used as default "label" in App Studio when accessing it in view design.
Is there an XSD structure supported where Pega Wizard uses both XSD attributes and maps XSD's element attribute "name" to Pega property's ID and human readable name to Pega property's short description?
Does Connector and Metadata Wizard use a transformation file that can be adapted?
What other good approach do we have for importing XSD-based data models to make them Pega's data model?
Markus