Usage
LOV Type | Lov Description | LOV Code | LOV Attribute 1 | LOV Attribute 2 |
|---|---|---|---|---|
ROLE | Description of the role | Specific Code that will match value in Role Table | Sorting order | ERP Internal ID for this Role |
Examples
LOV Type | Lov Description | LOV Code | LOV Attribute 1 | LOV Attribute 2 |
|---|---|---|---|---|
ROLE | Administrator | ADMINISTRATOR | 1 | 3 |
ROLE | Manager | MANAGER | 2 | 4 |
ROLE | Operator | OPERATOR | 3 | 5 |
The LOV Table relates to the ROLE table in ShipHawk WMS which is defined as follows:
Role Name | Role Definition |
|---|---|
The LOV Code being used for this role | A JSON Object which describes this role |
Example:
Role Name | Role Definition (see sample bject below) |
|---|---|
ADMINISTRATOR | {“UnAuthorizedForms”: [“none”],”UnAuthorizedOptions”: [“none”]} |
It is very useful to use a JSON Editor to compose/validate this data, and then post into this table. It is intended that this data is established once at the beginning of a project since it is rarely changed.
Below is a sample Role Definition:
{
"UnAuthorizedForms": [
"Pack",
"Count",
"Search"
],
"UnAuthorizedOptions": [
"ReviewResults",
"ResolveCounts",
"SearchforPOASN"
]
}