To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Our requirement is to build flows so manager can be guided through the transfer action
Summary:
Managers use self-service capability in HCM to do transfer action for employees and they choose a transfer reason based on the change. Currently, we have issues in the process where managers select one action reason and update fields that they don’t need to and sometimes don’t action the fields that are necessary for the transfer action to complete. The issues arise more for managers who do transfer actions rarely.
Our aim is to build multiple transfer journeys that guide managers through different transfer action reasons available. In addition to providing information to Manager on the action that they are doing, we want to hide the fields that is not necessary for the action and provide only those fields that are necessary for that specific action. This would reduce the number of errors and would make the life of managers and HR specialists easier. This would also provide a better way to collect the data and use it in Analytics to understand the trends better.