Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This article highlights Decision Logic’s Employee Onboarding feature.

Feature Overview

The Employee Onboarding feature is used to support integrations from 3rd parties to onboard new employees into Decision Logic’s platform.

The employee information is used in the following features:

Approval Process

Users will only see employees available for hire based on the Scope of their Profile set in Profile Maintenance.

Navigate to Operations > Labor Scheduling > Employee OnBoarding

  1. Click Approve.

  2. Complete the form. All fields with an asterisk are required.

  3. Select the Effective Date. The effective date will use the Hire Date from the image in Step 1.

  4. Click Approve.

Approved employees will transfer to the Employee Roster. If an employee already exists in Decision Logic, use Employee Roster for the store where
that employee is active to transfer the employee by adding a new store to the existing employee record.

  • Set the new store as primary when applicable.

Deleting a store from an employee record will remove historical labor reporting from that store’s payroll report history.

Validations and Alerts

  • Validate and alert which store the employee is already active

  • Terminated employees will appear as New Hire

  • SSN Check checks if SSN is in use at any store in the Decision Logic Database

  • POS ID Check: Checks if POS ID is already in use at the primary store assigned

  • Custom Fields: Checks Custom Fields flagged as required as configured via Employee Maintenance 

Table of Contents

For additional questions or assistance, please submit a support ticket by visiting the Decision Logic Service Center.

Unable to access this feature in the Decision Logic platform?

  • Contact your Decision Logic Administrator to make Scope and Security adjustments to your user profile and/or add new features.

  • Some features are client-specific.


  • No labels