|
When a toner alert is triggered (either automatically, based on the settings above or manually by a portal user), if the alert is put into the Outstanding Requests queue within the portal Consumable Management tab, when Jim2 next queries the portal for any alerts (every hour is the default), the request will be moved from the Outstanding Requests queue to the Actioned Requests queue.
As part of the process, Jim2 updates the request comment with the Jim2 B2B ID and moves the status to Actioned.
At the same time, the alert is processed by the Jim2 eBusiness queue and a job is created.
|
|
It is important that one or more staff within your organisation have a pinned eBusiness Queue list to alert them to any inbound processing errors that may need attention. Whilst errors are rare, it is best practice to have the eBusiness Queue list visible and managed.
|
When creating toner jobs, Jim2 uses the following logic:
1.Match the alert serial number to the Jim2 Asset (copier, MFP, etc.)
2.Check if there is an existing consumable supply job on a status of Booked for the Asset.
▪If found, the additional toner will be added to the existing job.
▪If found, but the job is on a status other than Booked, a new job is created.
When an existing job is found on a status other than Booked, a comment is added to both the new and existing job, ensuring users are aware of both jobs. This can help cut down on freight costs by allowing consolidation of purchase orders and delivery when possible.
|