24C - OPTIMIZE OBSOLETE GEOGRAPHY HIERARCHIES

Summary:

Post using this action to update Recruiting objects using hierarchies, We observed already created requisitions still hold the ended hierarchy node id and it did not got updated to Newly created Geography node ID. Can you please help us understand what is the expected functionality with this feature ?

feature link -

Steps performed:

Created new Hierarchy from existing one.

Updates couple of new location on the Hierarchy

Activated the Hierarchy

Ran the "Load and Index Master Geography Hierarchy" ESS job

Executed the newly given action "Update Objects to Latest Nodes" and it is successful.

Validated the Geography node ID from backend table for already created requisitions and it holds the same old value, where as newly created requisitions are getting updated with New Node ID.