Data iteam

Teja K A
Tera Contributor

Hi community,

I am working on onboarding. To know more about User and HR profile creation on submitting the form,  I went through Data items and got stuck in All Upcoming Onboarding Tasks in data item.

                                       TejaKA_0-1695283358212.png

Can anyone explain me what exactly All Upcoming Onboarding Tasks(Data item) is doing?

and why Application is selected as HR Service Delivery for mobile only?

 

Thanks in advance.

 

1 ACCEPTED SOLUTION

JamesEcoStratus
Mega Guru

In ServiceNow, the "All Upcoming Onboarding Tasks" data item is typically a component of a workflow or process designed to streamline the employee onboarding journey. It plays a crucial role in gathering information about pending tasks or activities linked to the onboarding process for newly hired employees.

 

Here's a breakdown of its general functions:

  1. Data Collection: This data item is responsible for accumulating data related to tasks or activities that are essential during the onboarding process. These tasks can encompass various activities such as configuring email accounts, provisioning system access, conducting orientation sessions, and more.
  2. Status and Deadlines: It usually maintains information about the status of each task (e.g., pending, completed) and their associated deadlines or due dates. This data is critical for tracking the progress of onboarding tasks and ensuring they are completed within the designated timelines.
  3. Assignment: The data item may also include details regarding task ownership. This means specifying who is responsible for each task, which could include HR personnel, the IT department, managers, or other relevant parties.
  4. Integration: Depending on the setup and configuration, this data item might be integrated with other ServiceNow modules or applications. This integration helps in automating task assignments, notifications, and approval processes as part of the overall onboarding workflow.

 

After reviewing your script, It looks like there are a few syntax and logical issues, and I’ve supplied an update version below.

 

Here's a corrected version:

 

JamesEcoStratus_0-1695349059577.png

 

 

Here's what has been corrected:

  1. I fixed a typo in the method name. It should be hr_LifecycleMobileUtils instead of hr_LifecycleMobileUtlis.
  2. I added a missing var declaration for taskSysIds to store the sys_id values of the tasks.
  3. I used the map function to extract the sys_id values from the tasks array and then joined them using join(",") to create a comma-separated list of sys_id values.
  4. I fixed the queryString assignment to correctly concatenate the sys_idIN...^ORDERBYdue_date query.

Please TEST this corrected script in your ServiceNow subprod instance. It should work as expected to generate the desired query string for "All Upcoming OnBoarding Tasks."

 

As for your second query about the application being designated as "HR Service Delivery" for mobile-only access, please note that specific configuration choices can vary depending on factors such as the ServiceNow version, specific requirements, and environmental configurations.

 

In a general context, selecting "HR Service Delivery" for mobile-only access could serve the following purposes:

  1. Mobile Accessibility: The "HR Service Delivery" application may offer features and functionalities that are optimized for mobile devices. By setting it as mobile-only, your organization ensures that HR-related tasks and processes are easily accessible and user-friendly for both employees and HR personnel when using mobile devices.
  2. Customization: Organizations often customize their ServiceNow instances to provide tailored mobile experiences for particular applications or modules. This customization aims to enhance efficiency and user experience when accessing HR services through mobile devices.

 

It's important to note that the specific ServiceNow configuration can vary widely among organizations and ServiceNow versions. For precise insights into your organization's ServiceNow setup, version, and environmental requirements, it is recommended to consult with your ServiceNow administrator or IT team. They can offer specific details and considerations based on your unique implementation.

 

Good Luck,

 

James @Ecostratus

If you found this response helpful, please consider marking it as "Helpful" or "Correct."

 

View solution in original post

1 REPLY 1

JamesEcoStratus
Mega Guru

In ServiceNow, the "All Upcoming Onboarding Tasks" data item is typically a component of a workflow or process designed to streamline the employee onboarding journey. It plays a crucial role in gathering information about pending tasks or activities linked to the onboarding process for newly hired employees.

 

Here's a breakdown of its general functions:

  1. Data Collection: This data item is responsible for accumulating data related to tasks or activities that are essential during the onboarding process. These tasks can encompass various activities such as configuring email accounts, provisioning system access, conducting orientation sessions, and more.
  2. Status and Deadlines: It usually maintains information about the status of each task (e.g., pending, completed) and their associated deadlines or due dates. This data is critical for tracking the progress of onboarding tasks and ensuring they are completed within the designated timelines.
  3. Assignment: The data item may also include details regarding task ownership. This means specifying who is responsible for each task, which could include HR personnel, the IT department, managers, or other relevant parties.
  4. Integration: Depending on the setup and configuration, this data item might be integrated with other ServiceNow modules or applications. This integration helps in automating task assignments, notifications, and approval processes as part of the overall onboarding workflow.

 

After reviewing your script, It looks like there are a few syntax and logical issues, and I’ve supplied an update version below.

 

Here's a corrected version:

 

JamesEcoStratus_0-1695349059577.png

 

 

Here's what has been corrected:

  1. I fixed a typo in the method name. It should be hr_LifecycleMobileUtils instead of hr_LifecycleMobileUtlis.
  2. I added a missing var declaration for taskSysIds to store the sys_id values of the tasks.
  3. I used the map function to extract the sys_id values from the tasks array and then joined them using join(",") to create a comma-separated list of sys_id values.
  4. I fixed the queryString assignment to correctly concatenate the sys_idIN...^ORDERBYdue_date query.

Please TEST this corrected script in your ServiceNow subprod instance. It should work as expected to generate the desired query string for "All Upcoming OnBoarding Tasks."

 

As for your second query about the application being designated as "HR Service Delivery" for mobile-only access, please note that specific configuration choices can vary depending on factors such as the ServiceNow version, specific requirements, and environmental configurations.

 

In a general context, selecting "HR Service Delivery" for mobile-only access could serve the following purposes:

  1. Mobile Accessibility: The "HR Service Delivery" application may offer features and functionalities that are optimized for mobile devices. By setting it as mobile-only, your organization ensures that HR-related tasks and processes are easily accessible and user-friendly for both employees and HR personnel when using mobile devices.
  2. Customization: Organizations often customize their ServiceNow instances to provide tailored mobile experiences for particular applications or modules. This customization aims to enhance efficiency and user experience when accessing HR services through mobile devices.

 

It's important to note that the specific ServiceNow configuration can vary widely among organizations and ServiceNow versions. For precise insights into your organization's ServiceNow setup, version, and environmental requirements, it is recommended to consult with your ServiceNow administrator or IT team. They can offer specific details and considerations based on your unique implementation.

 

Good Luck,

 

James @Ecostratus

If you found this response helpful, please consider marking it as "Helpful" or "Correct."