Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Incorrect data being populated in eMDR xml

SA-8897

Summary



1. Medical History Start Date: In the activity “PrepareMedHistDataForeMDR”, in the step 4.1, The StartDate property is of Date type but the property value is of type text

2. In the activity “PrepareConcomitantDataForeMDR”, in step 2.0, We have the similar issue as mentioned in point 1.

3. For the field “F2 UF Importer Report Number”, In the activity “PrepareUserFacilityorImporterData”, the Importer Report Number is Hardcoded as “N/A”. Request your clarification on this.

4. For the field “F14 Manufacturer Name”, In the activity “PrepareUserFacilityOrImporterData”, In the Step 20 the manufacturer Name is mapped to .name. But the value is stored when we are giving .name.name (Note: We observed that .name is of type page and .name.name is value).

5. For the field “F14 Fax”, In the activity “PrepareUserFacilityOrImporterData”, In the Step 20 the Fax is not prefixed with “faxto:”. Whereas for the rest of the prepare activities it is observed that the “Faxto:” is prefixed wherever the mapping is done for fax.

6. For the field “F14 Email”, In the activity “PrepareUserFacilityOrImporterData”, In the Step 20 the Fax is not prefixed with “mailto:”. Whereas for the rest of the prepare activities it is observed that the “mailto:” is prefixed wherever the mapping is done for email.


Error Messages



Date formatting error and incorrect data in eMDR

Steps to Reproduce



Not Applicable

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.

1 & 2: New "Date" type properties are to be added in the respective data classes "PegaLS-FW-Data-AECPFW-MedHistory" and "PegaLS-FW-AECPFW-Data-Concomitants" . These properties are directly set to eMDR value properties without FormatDateTime 

3 to 6: Appropriate changes are to be made in "PrepareUserFacilityorImporterData" updated to populate correct data

Resolution



HFix-21785 resolves this.

Published January 31, 2016 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us