3 Replies Latest reply on Jan 7, 2014 4:38 AM by jasoncadman

    Add collection items to request prior to Service Catalogue checkout.

    jasoncadman Expert

      Morning All


      Is it possible to add collection items to a request prior to checking out? I have an autoprompt action instance for the collection items but you have to checkout and then go back into the request to add them. It makes the process a bit disjointed even though I have a notification with a link sent to the requester to go back into the request and add the collection items. Once you click check out i think that it's reasonable to assume the request process has started


      It looks like it will work properly with the shopping cart functionality disabled or if I add the request on its own via the Request Service option (even though i don't like going back to the service screen with the Request Service action still there) rather than the Add to Cart button but that also causes confusion as then some you will be able to add to cart and one will not


      It would be handy to have the autoprompt action kick in before i check out but the request isn't created then so i'm guessing that's the reason why that's not possible.


      It might work if i could disable the Add to Cart button for just this service request as other requests utilise the cart functionality prettty well.


      It looks like an option may be to add the attributes to the request window itself but that's also a bit tricky as there 4 different types of collection information required and there may be upto 20 items of different types in total


      Arg! Stuck. As one door closes another one slams shut!


      Hope that makes some sort of sense. Any help appreciated


      Thank you



        • 1. Re: Add collection items to request prior to Service Catalogue checkout.

          Hi Jason,


          Unfortunately no, (and yes, you're right) you can't add collection items to a record that does not yet exist; the Request is only created when you check out.  This is also why process dependent features (eg. autoprompt) wont work either.


          As for selectively enabling the shopping cart for different services, this isn't possible either by design, although you could raise an ER.


          If you were to put all the collection attributes directly on the Request window, you could try using dynamic windows to only display the attributes you need to display for the given Service.  Depending on how many attributes you need to show/hide/make mandatory/etc your calculation could become rather large...


          Hope that helps!




          • 2. Re: Add collection items to request prior to Service Catalogue checkout.
            jasoncadman Expert

            Hi Jon


            Thanks for your reply


            Dynamic windows was the way that I was thinking of going but if i put this into context you can see why i don't really want to go down the route of adding each one to the request object.


            It's an equipment move request and each item to move needs to be specified (PC, printer, phone, other) and for each type of equipment there may be upto 20 items. Different items types have different things that need to be specified e.g. phone number, PC socket number etc. so this means that i need to create 20 of these for each equipment type and then use dynamic window rules to make them appear and also to make the correct attributes appear for each equipment type that will be added.


            Now I haven't tried this yet but that is going to be a rather large and complicated calculation as well as a lot of attribute creation. It just feels like a really horrible way of doing it


            I can't think of another way of doing it though

            • 3. Re: Add collection items to request prior to Service Catalogue checkout.
              jasoncadman Expert

              I suppose that another way of doing it would be add each equipment type move as a Configuration Item in the Service catalogue, but this would mean that for each item that was being moved there would be lot of repeated information i.e. "move from location", "move to location" and you would need to repeat this for each item. There is also quite a bit of header information such as the Cost of the Move and authorisation for the spend which would be a nonsense to carry out for each item to be moved.


              I don't think that a bundle would work either as there would be different items in the bundle each time. A bundle that you could configure on the fly would be ideal and I think is the closest description.


              Think aloud..... a general Move Equipment Service listed separately to all of the equipment types that could need moving might work, but then we would have to deal with a single move as separate requests which would get really messy and admin heavy. It needs to to be one Configuration Item with items attached to it i think.


              Hmmmm........... any thoughts?