Sub-status - "Enabling Supplier" issue

[Gavin James - SDDC]

Morning,

I'm currently setting up a Sub-status on the Service Manager,  see the Sub-status in question below,   I can see you can "Enable Suppliers" so I have turned this to yes, thinking that when the sub-status is selected on the Service Manager (within a call)  the Service Manager will allow you to connect the supplier to the support call.   I've looked on the Wiki pages but can't find any details around the "Enable Suppliers" button so not entirely sure if my expectation is correct, and if my assumption is what should actually happen?  

But secondly, when I do select the Sub-status on the Service Manage (within a support call)  I get the below error, do you know what I'm doing wrong? 

 

 

[Guest Ehsan]

Hi @Gavin James - SDDC,

The Supplier sub-status feature is driven through assets.

Through an asset, you can associate a Supplier. In the example above, I have added Acme Computers as a supplier for the iMac Pro 21.5 inch asset.

 

When viewing the contract for the Acme Computers supplier, I can see the associated asset. Please note that I have configured a Target Working Time per Event as well, to allow the sub-status configuration.

 

When managing my request, I have associated the iMac Pro 21.5 inch asset to the request. Thereafter, when choosing the supplier sub-status, I can select the available supplier and contract.

You should then see a section called Active Supplier Event on the right-side that provides information on the target. As I have configured the event to run for 60 minutes, you can see the target is set to 1 hr.

I hope this helps.

Ehsan

 

[James Ainsworth]

Additional documentation can be found on the Hornbill Wiki within the Supplier Manager documentation located here.  Expand each section to read requirements and how to set up.  Let us know if you have any further questions.

 

 

[Gavin James - SDDC]

Thanks for the support, I'm off and running with this now.

Gavin

[HGrigsby]

Hi 

I keep getting the same message, though it has worked before a couple of times before.  It is something I have gone back to and now get the error again.   I've looked  through the suggestions above it all looks like it is set up correctly. (and  hasn't changed since it worked before)

Any suggestions would be much appreciated

Helen