How to configure an Employee Clearance HR Task to collect input from the Opened for user?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Community,
I am working on an Employee Offboarding Lifecycle Event and have an activity called Employee Clearance.
My requirement is to send the request to the Opened for / Requested for employee when certain conditions are met, so that the employee can open the task from the Employee Center/portal and provide the required clearance information or what ever can be the appropriate solution.
I have already created the required custom fields on the HR Task table to store the employee's responses.
I would like guidance on the recommended configuration for the following:
How should the Employee Clearance activity/HR Task be configured so that the Opened for employee can provide input?
How can I expose the required HR Task fields to the employee in the portal?
Can UI Policies be used to show or hide fields dynamically based on the employee's responses?
Once the employee submits the information, how should the responses be stored on the corresponding HR Task record?
Is an HR Task template sufficient for this requirement, or is another configuration/component recommended for collecting employee input?
Any guidance on the recommended ServiceNow HRSD configuration or an example implementation would be really helpful.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @vmanojkumar ,
One suggestion would be to consider assigning the Employee Clearance HR Task directly to the employee using the Assigned to field instead of relying only on Opened for.
Since the employee is expected to provide the required clearance information, assigning the task to them would make them the responsible person for completing it.
You can then explore configuring the appropriate employee-facing HR Task experience in Employee Center, exposing the required custom fields and allowing the employee to submit their responses.
Please also ensure the necessary ACLs and HR Task visibility configurations are in place so that the employee can access and update only the intended task.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
The documentation does not describe a supported way to display custom HR Task fields to the employee in the portal. It points to other mechanisms for collecting employee input.
Employee tasks in a lifecycle event are assigned to the subject person of the lifecycle event case, so the employee receives the task through the activity itself and no manual routing to the Opened for person is needed. Confirm that the subject person and the Opened for person are the same on your offboarding case, otherwise the task may be assigned unexpectedly.
To configure the activity:
- Go to All > Lifecycle Events > Administration > Manage Lifecycle Events and open your offboarding event.
- On the Activity Sets tab, edit the Employee Clearance activity.
- Set the Activity type to Employee.
- Select an HR task template. The template populates fields on the HR task form when the task is created.
- Select Wait for generated task to complete if the activity should remain open until the employee finishes.
- Open the HR service behind the lifecycle event and select Show case to subject person. This is required in addition to the lifecycle event setting.
- On the lifecycle event, select Display activity sets to subject person if the employee should see the timeline.
For collecting answers, the documentation describes the task type on the template. With HR Service, completing the task creates an HR case, which must finish before the activity closes. With Submit Catalog Item, completing the task creates a request. A Take Survey option is also available, where a survey is selected for the user to complete. The task type that fits best is a matter of design judgment.
A template alone is not sufficient to collect structured input. The options worth considering are:
- A catalog item or HR service with a form, where the clearance questions are variables.
- A survey, if the answers are simple questions.
Branching questions are best handled in a catalog item or HR service form, since variables and catalog UI policies are designed for that purpose.
The documentation does not cover custom fields on the HR Task table displayed in the portal, UI Policies on those fields, or writing answers back to the HR Task. If you pursue that approach, test it in a sub-production instance first and build it in your own scope or an update set.
To refine this further, please share your release, whether you use Employee Center or Employee Center Pro, what the clearance questions look like, and whether the answers must be stored on the HR Task record itself.
Sources: