5 Replies Latest reply on May 3, 2012 4:35 AM by jennashaw

    Best method of capturing multiple sets of info (eg move form for multiple people)?

    Apprentice

      Hi Folk,

       

      We're trying to work out the best way to capture (and display) information on a move request for multiple people/computers....

       

      The two ways we can see that you could do this, is either by creating a collection to put all the information in, or by adding multiple (MULTIPLE!) new fields on the main object (Incident in this case)

       

       

      A collection has the advantage that you don't create anything in the collection until you need it, and doesn't clutter up your parent object, BUT it is awkward to get punters to enter the data.  They have to save the initial request, then add a 'move detail' for each move.

      It's also awkward for analysts to extract that info, in that it's spread across multiple entries in a collection, and not visible on the main object window.

       

       

      Adding fields (attributes) to the parent object means that you can have several 'moves' specified right there on the main window, but it means you have to add multiple sets of fields to the object (Incident, as I said).  So to show 5 'moves' you have to have 5 sets of fields to capture From Desk, To Desk, Asset, User, Phone etc.

      If you want 10 moves per form,you need 10 sets.... (yuck!)

       

      I also have to wonder whether adding lots of fields to your base object then starts to impact other processes based on that object - even if those new fields are not on the window, Landesk still seems to be querying the database for everything.

       

       

      Or alternatively, we might be barking up the wrong tree entirely.......

      (and yes, a design course is on the wish list)

       

      What do other organisations/people do for these types of requests?

       

       

      Cheers,

       

      Stu

      7.3 on oracle

        • 1. Re: Best method of capturing multiple sets of info (eg move form for multiple people)?
          gramsay Specialist

          We use the Change process for this. You can add multiple CIs as it's what it was designed to do.

          • 2. Re: Best method of capturing multiple sets of info (eg move form for multiple people)?
            gramsay Specialist

            Should have added we have a set of standard changes with pre-defined taks.

            • 3. Re: Best method of capturing multiple sets of info (eg move form for multiple people)?
              Apprentice

              Hi Stuart,

               

              I think Graham's answer would be easiest and smoothest.

               

              However, if you need to do this as a request for some reason, then I would definitely go with the collection, as you can have any number of moves per request.

               

              A collection has the advantage that you don't create anything in the collection until you need it, and doesn't clutter up your parent object, BUT it is awkward to get punters to enter the data.  They have to save the initial request, then add a 'move detail' for each move.

              It's also awkward for analysts to extract that info, in that it's spread across multiple entries in a collection, and not visible on the main object window.

               

              Regarding the above, first of all, to combat your ease of completion problem, you could have a new request attribute; a checkbox called "Move Required?" for example... Then if this is ticked, this triggers a notification giving the user a direct link to their Request and the Add Move Detail action.

               

              An example of the link you could use for this is here but I have used the Add Assignment action for this example...

              http://<webserver>/WebAccess/object/invokeFunction.rails?class_name=RequestManagement.Request&key={Guid}&function_name=AddAssignment

               

              Still a bit messy, but a little smoother as it tells the user what to do each time.

               

              On your second point you should be able to add your collection to the request window by dragging it onto your request window in designer. You can also set which attributes are displayed here by ammending the Results Output attributes on the Move Detail business object in designer.

               

              Hope this helps,

              Jenna

              • 4. Re: Best method of capturing multiple sets of info (eg move form for multiple people)?
                Apprentice

                HI Jenna/Graham,

                 

                We're not using change ATM, or CI's so it didn't occur to us to use CI's... worth looking into. 

                 

                We have just started using those direct links too, for another process, so if we *have to* we will look at that (can you put the link straight on the update window? - not as an action, but as a link)

                 

                On your second point you should be able to add your collection to the request window by dragging it onto your request window in designer

                 

                That just adds the collection as a tab/tree item doesn't it?  not really what we had in mind, as it is stuck down the bottom of the window, but if we only put minimal other info on the window it may be obvious....

                 

                 

                Ideally, what I'd love to see it (to borrow an object from my MS Access hacking days) is a 'grid' object that allows you to show data from a related table in, um, tabular format ala Excel.

                 

                 

                Cheers,


                Stuart

                • 5. Re: Best method of capturing multiple sets of info (eg move form for multiple people)?
                  Apprentice

                  Hi Stuart,

                  I definitely think CIs will make your life easier!

                  However, re:

                  (can you put the link straight on the update window? - not as an action, but as a link)

                  The only way this would work is if you put it into the window as an action in your process, which should be possible.

                   

                  The latter may be doable but having a collection will complicate that. If you have a relationship (which you will have to) between your Move Detail and the Request, you can put any fields on the Request window from that, but obviously you can’t do that with a collection as each field has multiple records, hence where the collections section comes in at the bottom of your window.

                   

                  If your guys use the console you could use a crystal report to display this instead though? The guys put in the request reference and it shows all the details you want, as you want to format them. That could be a workaround if you use crystal.

                   

                  Good luck with it anyway! :-)