Introduction

In one of the previous article (Loading Worker Record Using HDL Template) we have seen how to load Worker object using HDL files.

In this article we would try to identify which all data attributes can be modified. While there is no specific action name like UPDATE or CORRECTION mentioned in the data file we go with an assumption that if we keep the effective start and end dates same it would be CORRECTION operation while if we have a new effective start date it would be UPDATE action.

Create Worker

In the first step we would load the worker record.

And a quick search on Person Management (with Person Number as AH1) should show the record. On the Manage Person page we could see the Date of Birth is 01/01/1975

Scenario: Making Changes to WORKER Metadata

In the above file we have only used the minimum attributes and for the METADATA line it is only the Date of Birth field which can be modified without having an adverse impact on any other child entities. For this example we would change the Date of Birth value from 1975/01/01 to 1978/01/01 in the data file and retry the load. We have made the changes in the file and named the zipped file as UpdateDOB.zip

We may verify whether the changes have reflected by navigating to the Manage Person screen.

Scenario: Making Changes to PersonName Metadata in CORRECTION Mode

For this scenario we would make changes to the Person Name Metadata .The initial load did not had a Middle Name field populated. For this example we would add “CorrectionModeScenario” in the middle name field. We would name the zip file as PersonNameCorrectionModeUpdate

And when we verify the same from Manage Person page we should be able to view the change. The Middle Name field should be populated with the new value (CorrectionModeScenario for this example)

One should note that the Name History only shows one record (confirming that CORRECTION Mode changes have taken effect)

Scenario: Making Changes to PersonName Metadata in UPDATE Mode

In this case we would try to make changes to PersonName metadata. For this we would need to provide a new Effective Start Date (2018/02/01 for this example) and we would change the Middle name value to UpdateModeScenario.

We would name the zip file as PersonNameUpdateMode

And we should again do a quick verification by checking for the Name Attributes field (from Manage Person UI)

We can see that the Middle name value has changed and the Name History popup window shows that a new record got created starting 2018/02/01 which also confirms that the changes have been made in UPDATE mode.

Files Used Can Be downloaded from below links:

CreateWorker

UpdateDOB

PersonNameCorrectionModeUpdate

PersonNameUpdateMode

Inference / Summary

This is how we can perform UPDATE and CORRECTION actions using HDL data files. While I have only shown the changes taking person related METADATA entities one may perform similar operations for other entities like WORKRELATIONSHIP, WORKTERMS, ASSIGNMENT, WORKMEASURE etc.

Request you all to please try the different permutations and combinations from your side and feel free to share your views / observations and findings.

As from my side, I would try something from my end too and share in the next post.

Thanks for your time and hope this write-up was useful.                        

Ashish Harbhajanka

Add comment