If a user is unable to access an application in HotWax Commerce, the issue might be related to permissions or facility associations.
Verify if the user belongs to the correct security group that has permission to view the specific application. Users must be part of a security group with the appropriate permissions to avoid unauthorized access.
Ensure the user has the necessary view permissions for the application view. Here are the permissions the administrator can give users to view any application:
Note: These permissions only allow users to view the app. Additional permissions would be required for them to perform any other operations.
If the user lacks the necessary view permissions, the administrator can follow these steps to grant access. to learn how to grant permissions to user groups.
If a user cannot access a BOPIS or fulfillment app application, they might need to be added to a facility. The administrator can follow these steps to add the user to a facility:
To add a user to a facility, follow these steps:
RECEIVING_APP_VIEW
View Receiving App
THRESHOLD_APP_VIEW
View Threshold Management App
USERS_APP_VIEW
View Users App
BOPIS_APP_VIEW
View BOPIS App
FACILITIES_APP_VIEW
View Facilities App
FULFILLMENT_APP_VIEW
View Fulfillment App
IMPORT_APP_VIEW
View Import App
INVCOUNT_APP_VIEW
View Inventory Count App
PREORDER_APP_VIEW
View Preorder App
These Troubleshooting document contains the common issues user may face when creating or managing user
When importing employee data into OMS, specific issues may occur that can prevent a successful bulk import. This guide will assist you in troubleshooting and resolving common problems that may arise during the employee import process.
When importing employee data into OMS, various errors can occur due to issues in the CSV file or system conflicts. It is essential to recognize and address specific errors to ensure a smooth import process.
Missing mandatory fields in the CSV file
Duplicate employee entries
Incorrect format of email or external ID
Security group not recognized
The issues with importing employees are generally related to specific data formatting errors or missing fields in the CSV file. Below is an analysis of common causes:
Missing mandatory fields – Ensure that the CSV contains all the required fields: first name, last name, security group, username, password, email ID (for password reset), and external ID (if provided).
Duplicate employee entries – If an employee already exists in the system with the same external ID or username, the import may fail.
Invalid format for email or external ID – Ensure that the email follows the standard format (e.g., [email protected]), and external ID (if used) is unique.
Access the OMS platform using your credentials.
Once logged in, go to the EXIM menu.
Under the Relationship category, click on Employee.
If you cannot find the Employee link under the EXIM menu:
Navigate to Settings.
Click on Data Manager Config.
In the search bar, type IMP_EMPLOYEE.
This will direct you to the correct configuration page for employee imports.
In the Employee Import screen, upload your CSV file containing the employee data.
The CSV should include the following fields:
First name
Last name
Security group
Username
Ensure that all mandatory fields are present and formatted correctly.
Check for duplicates or missing information.
Once validated, proceed with the import.
If any errors occur during the import, review the logs provided by the system.
Identify the issue based on the error message and adjust the CSV file accordingly.
Re-upload the corrected CSV file to complete the import.
After the import is complete, verify that the employees have been added to the system correctly by:
Navigating to the Employees screen under the Relationship category in OMS.
Checking that all imported employees appear in the system with the correct details.
Incorrect username or password format – The username should follow the specified pattern, and the password should meet the security requirements (e.g., minimum length, special characters).
Email ID (for password reset)
External ID (if provided)
