HR Lifecycle Event Approval Activity Not Triggering When HR Case Is Created Through Employee Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Everyone,
I have configured an HR Lifecycle Event in HRSD and mapped it to the respective HR Service, Topic Detail, and Category.
The lifecycle event is working as expected when I create an HR case directly from the native ServiceNow interface. All lifecycle activities, including the approval activity, are triggered correctly.
However, I am facing an issue when I execute the complete process through the Employee Center (ESC) portal.
Steps followed:
- Created an HR case through a Record Producer in the Employee Center portal.
- Verified that the HR case was created successfully in the appropriate HR Case table.
- Verified that the HR Service mapping and other relevant field mappings are correct.
- Impersonated the assigned HR Agent and completed the initial HR Task.
- After completing the task, the next activity in the lifecycle should trigger a Manager Approval.
Issue:
When the initial HR Task is completed through the ESC portal workflow, the next lifecycle activity gets triggered, but the approval record is not generated.
Interestingly, the same lifecycle configuration works perfectly when the HR case is created and processed through the native ServiceNow interface.
My questions:
- Is there any difference in how HR Lifecycle Events process activities when an HR case is created through a Record Producer versus the native interface?
- Could this issue be related to the Record Producer configuration, HR Service mapping, lifecycle event context, or the way the HR Task is completed?
- Are there any additional configurations or conditions required to ensure that approval activities are generated when the lifecycle is executed through Employee Center?
Has anyone encountered a similar issue or can suggest what I should investigate to resolve this?
Any suggestions or guidance would be greatly appreciated.
Thanks in advance!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello @DGiri
Your approval activity may be failing because of differences in how the case is created, rather than how the task is completed. A Record Producer may populate fields differently from the native form. If the approval depends on the Subject Person's manager or another user reference, missing or incorrect values could prevent the expected approval from being generated.
- Open the HR case and navigate to Lifecycle Events > Lifecycle Events Cases > Activity Set Execution. Check the Activity Set Context and review the approval activity status and execution details.
- Compare the Subject Person, Opened For, and Requested For fields on the Employee Center case against a working native case.
- Confirm that the manager field is populated on the Subject Person's user record.
- Open your Record Producer script and verify that it correctly sets the required fields, including Subject Person and HR Service.
- Check the approval activity configuration for the approver source, such as "Subject Person's Manager", and review its conditions.
- Check the Missing any approver and Missing all approvers settings to understand how missing approvers are handled.
- Review the lifecycle event execution details and system logs around the time the initial HR Task was completed.
Also, verify that the HR Service has the correct Lifecycle Event configuration. Since the process works through the native interface, compare the relevant case field values and approval configuration in both scenarios before making any custom changes.
If you share the approval activity status and approver configuration, it will help narrow down the issue.