Hi Shubham Sinha 56,

To update the body section based on the Path step selected by the user, we created the hiringStep attribute below.

<aura:attribute name="hiringStep" type="String" default="Application"/>

Then we can use the onselect function from lightning:path to update the value of hiringStep attribute. First we retrieve the name of the step and user clicked on from the aura event attribute. Once we have the stepName, we can use that value to update the hiringStep attribute as such:

onselect : function (component, event, helper) {
        var stepName = event.getParam("detail").value;        
        component.set('v.hiringStep', stepName);
        helper.setPathButtonVisibility(component, stepName);
    }

In JobProcess.cmp we use aura:if to render the corresponding component based on the current value of hiringStep . This allows us to update the body on select. For example, when a user selects the ‘Phone screen’ step, the PhoneScreenInfo component will be rendered.

Lightning Data Service was used to pass data between all these different components. It’s built on highly efficient local storage that’s shared across all components that use it. Records loaded in Lightning Data Service are cached and shared across components. If a user updates a field on one component, that update is propagated automatically to other components listening to that event. To load and edit the record, simply include force:recordData in your markup:

<!--Lightning Data Service -->
    <force:recordData aura:id="recordLoader"
                      recordId="{! v.recordId }"
                      layoutType="FULL"
                      targetRecord="{! v.record }"
                      targetFields="{! v.simpleRecord }"
                      targetError="{! v.recordError }"
                      recordUpdated="{! c.recordUpdated }"
                      mode="EDIT"/>

Please mark it as best answer if it helps you to fix the issue.

Thank you!
Regards,
Suraj Tripathi