Support

Usage guide: Employee onboarding - Workday

This page outlines various ways to use the pack, including use case examples.

Administrators can refer to the Configuration guide : Employee onboarding -Workday to set up and customize the installed content.

The Employee onboarding - Workday library pack enables EUC teams to:

  • Ensure device and network readiness by verifying VPN status and addressing common access blockers early.

  • Resolve login issues proactively through targeted workflows that assist employees with account, password, or 1Password-related problems.

  • Guide employees smoothly through Workday onboarding tasks using contextual Adopt guides tailored to common HR actions.

  • Empower employees to signal progress by manually notifying their manager via a workflow when onboarding is complete.

  • Reduce dependency on IT teams for common onboarding challenges, improving operational efficiency.

  • Improve the employee experience by delivering a clear, reliable, and supportive onboarding journey from day one.

In addition, this library pack offers preconfigured remote actions, self-healing, and campaigns to take action and drive awareness.

Library pack uses

Jump to Use cases on this page to see relevant scenario applications.

Use the library pack content for the following purposes.

Visibility

The Employee onboarding - Workday workflow is the starting point of this library pack. It will be launched on devices of new employees as part of their onboarding process.

Use cases

In addition to the relevant use cases covered below, you may uncover other troubleshooting scenarios specific to your environment.

Check employee authentication to the corporate VPN

Before the employee can start their onboarding process through the HR portal, it is essential to ensure that the VPN application on their device is configured correctly and that they have authenticated successfully. If authentication issues are detected, the workflow will guide them through the authentication process, and an ITSM ticket will be created if this cannot be resolved.

  1. The remote action "Get ZScaler status" is run on the device to check whether ZScaler is running.

  2. If not, the remote action "Start ZScaler" is run on the device.

  3. After a short delay, this check is repeated. If ZScaler could not be started, then an ITSM ticket is created, and the workflow terminates.

  1. If ZScaler is running correctly, the output of "Get ZScaler status" is checked again.

  2. If ZScaler errors are detected, the ITSM ticket is updated, and the workflow terminates.

  3. If ZScaler is not authenticated, a campaign is launched and the employee is asked to re-authenticate. If they request assistance, an ITSM ticket is created, and the workflow terminates.

  4. If they confirm that they have authenticated, the workflow will check the ZScaler status once more.

  5. If they are still not authenticated, an ITSM ticket is created, and the workflow terminates.

  6. If authentication is successful, the workflow continues.

Start employee onboarding

After ensuring that the employee's device is functioning properly and that they are authenticated with the VPN, the onboarding process can now begin. This involves redirecting the employee to the HR portal.

Once a new employee arrives at the Workday homepage, an Adopt onboarding guide will automatically launch and guide them through the onboarding process. At present, this guide will have to be created and implemented manually, but an installable guide is planned for a later revision of this pack.

  1. It has been confirmed that the employee is authenticated correctly with the VPN.

  2. A welcome campaign is sent to the employee inviting them to visit the HR portal (in this case, Workday) to complete the onboarding process.

  3. The campaign's status is checked. If the employee cancelled the campaign, an ITSM ticket is created advising that the Workday registration may not be complete. The workflow will then terminate.

  4. If the campaign was answered fully, it is assumed that the employee followed the link to Workday.

  5. An Entra ID request is made to determine the employee's manager.

  6. An MS Teams message is then sent to their manager to inform them that their onboarding introduction is complete.

  7. The workflow terminates.

Resolve missing 1Password browser extension

If an employee has been sent their new credentials for Workday via the 1Password utility, they will have issues logging in for the first time if this utility is not present on their device in the form of a web extension.

  1. The employee launches Workday and is presented with the login screen.

  2. They do not know their login credentials as these have been shared with them via 1Password.

  3. The 1Password browser extension is not installed or enabled on their device.

  4. The Adopt guide "Browser extension missing" is configured to run automatically in Workday and the guide appears when it detects that the 1Password extension is missing.

  1. The employee is prompted to click a button to resolve the issue.

  2. This launches the Workflow 'Browser extension enforcement'

  3. This workflow will detect the default browser in use on the device and run a remote action to install all corporate browser extensions.

  1. Checks are made within the workflow and if this process is successful, the employee is sent a campaign to let them know that their missing extension has been installed.

RELATED TOPICS

Last updated

Was this helpful?