...
Detail:
Clients are able to load Kits to be used by Seko360 per DC or revise an exiting Kit. This is done at a DC level as there may be different “Component SKU’s” and quantities required to be used depending on the DC the kit are created in.
...
Summary:
“Push Dispatch Confirmation Service” service (V7) supporting additional product related data
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
The new version of the “Push Dispatch Confirmation Service” service (V7) now supports pushing the following additional product related data on each line:
ProductDescription
ProductColour
ProductGrossWeight
ProductSize
...
Summary:
Ability to disable clients that no longer use iHub
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Company table now has additional fields to support 'disabled' state
'Maintain Clients' was renamed to Active Clients and now shows just active clients.
User with appropriate permissions can now disable a client
'Disabled' state means that client will have all it's API credentials switched off. Also, disabled clients are excluded from all the scheduled processing.
New 'Disabled clients' menu was added, visible only for users with appropriate permissions. It shows just disabled, read-only clients, with the ability to delete.
New permission added. 'Disable Clients', assigned by default to 'Root' role. Only roles with that permission are able to disable clients and to see disabled clients
It's now impossible to set disabled client as active
Disabled clients are excluded from all the filters
Activities for disabled clients are still accessible for auditing purposes
Fixed issue with the clients deletion - associated users check was not working
...