1. We have a TNA Database in the (local) Environment. All TNA Data is stored in the Database from all TNA Devices
2. We have a LinkSOFT Database in the (local) Environment. This is used for TNA  Data import only. All TNA Data is imported from the TNA Database into LinkSOFT Database
3. No Employees are maintained in the LinkSOFT Database on the (local) Environment
4. All Data in 2 above is then sent to LinkSOFT Cloud Environment via LinkSOFT API

With Reference to Case L12844, we Added "Start Date" to TNA Mapping and restrict TNA Import Data based on Employee Mapping and "START DATE"

Issue:

1. HRM License needs to be issued on the (local) Environment to access the Time Management menu for Employee Mapping
2. Employees are not kept in the LinkSOFT Database in the (local) Environment therefore we cannot create Employee Mapping

Hi Vineshwar,

I have changed the case group from "software defect" to "Support" as this issue is related to a specific business case where you want to map employees but do not want to maintain employees. The Priority has also changed from High to Medium. Refer to Helpdesk Guidelines on Priority and Group allocation.

Here are my comments, please review them with Sitla and send a meeting request for next week Tuesday at 2 PM AEST to discuss them:

1. You stated that you want to do Employee Mapping, but do not want to maintain employees. This is not possible as you need the Employee Record to do the mapping. We will need to design a new form which allows FREE TEXT EMPLOYEE Mapping if you want to do this. We can discuss this further in the meeting.
2. One option is to do the Mapping in the Cloud Environment and use the backup to process your TNA filters. This will be tedious but is a workaround.
3. A second  workaround would be to use the File Import TNA Mapping function to create your mapping records

Review comments and send a meeting request. I have added Sitla to the notifications as well.

1. The change will be available in version: 14.60

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Added a "batch mode employee mapping form" that allows you to add Employee Mapping without the Employee code being validated

3. Affected Areas:

1. Menu: Time Setup

4. The issue was caused by:

1. Change to allow TNA mapping without Employee Validation

5. Other Relevant Notes: You still need at least one Employee Licence on the Local TNA database so you have access to the "Time Setup" menu
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT