cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

HOD/HR Able to Edit Job Information via Action Button Before Selecting Event/Reason

SatishPanda
Explorer
0 Kudos
214

Hi Experts,

We have a specific requirement from one of our customers.

Currently, HODs and HR are able to modify job information from the Action Button (top left corner) before selecting the event and event reasons. However, once the event and event reasons are chosen, the previously filled fields are being saved.

Issue Details:

  • HODs and HR can update any job information fields via the Action Button before specifying the event and event reasons.
  • After selecting the event and event reasons, the system is saving the changes made earlier, even though this should not occur until the event is confirmed.
  • Our rule specifies that fields should only become visible after the correct event reason is selected.
  • Currently, users can make changes to any fields before selecting the event reason, and these changes are being saved irrespective of the event reason chosen.

Expected Behavior:

  • Job information should only be saved and finalized once the event and event reasons are properly selected and confirmed.
  • Fields should become visible and editable only after the relevant event reason is selected.
  • Changes should be saved only after the correct event reason has been specified and confirmed.

Thank you.

Accepted Solutions (0)

Answers (1)

Answers (1)

james598keen
Newcomer
0 Kudos

@SatishPanda wrote:

Hi Experts,

We have a specific requirement from one of our customers.

Currently, HODs and HR are able to modify job information from the Action Button (top left corner) before selecting the event and event reasons. However, once the event and event reasons are chosen, the previously filled fields are being saved.

Issue Details:

  • HODs and HR can update any job information fields via the Action Button before specifying the event and event reasons.
  • After selecting the event and event reasons, the system is saving the changes made earlier, even though this should not occur until the event is confirmed.
  • Our rule specifies that fields should only become visible after the correct event reason is selected.
  • Currently, users can make changes to any fields before selecting the event reason, and these changes are being saved irrespective of the event reason chosen.

Expected Behavior:

  • Job information should only be saved and finalized once the event and event reasons are properly selected and confirmed.
  • Fields should become visible and editable only after the relevant event reason is selected.
  • Changes should be saved only after the correct event reason has been specified and confirmed.

Thank you.


Hello,
To address your issue: mypoints search

Current Problem:

  • HODs and HR can modify job information before selecting event reasons, and these changes are being saved immediately.

Expected Behavior:

  • Job information should only be saved after event and event reasons are confirmed.

  • Fields should be visible and editable only after selecting the event reason.

Solution:

  • Ensure job information changes are saved only upon confirmation of the event reason.

  • Adjust the system to make fields visible and editable only after the event reason is selected.

    Best Regards,
    James Keen