1 Reply Latest reply on Mar 13, 2012 6:52 AM by karenpeacock

    Clearing a string value through automated process


      I have a process that deals with a Laptop being booked in for a warranty claim and then raising it to a insurance claim, the process relies on the warranty claim being booked into a slot number (KarenP kind enough to write this one up http://forum.landesk.com/support/docs/DOC-24283).  However using the guide I am unboking the laptop when the laptop is passed to insurance this works the way intended in the Guide but what I also need to do is the Field displaying the Slot Number I want to clear this field as well so in the next process when it gets to the Condition to check for slot it will not show the previous slot number therefore making sure the technician does not just click save therefore double booking a slot.

        • 1. Re: Clearing a string value through automated process
          karenpeacock SupportEmployee

          Hi Shaun


          I'm just trying to think of a quick way you can achieve this without me being able to look at your db, as my memory of my document steps has faded in the last few months.  If you'd prefer someone takes a look at your database and gives you more specific advice then I would suggest raising a support case with your provider.


          I am wondering if you can achieve what you want, in a slightly different way, by adding in another pre-condition?  Perhaps something to check whether the Slot currently selected on the Request window is already marked as booked.  If it is booked then you are not given the book action - so this precondition needs to be placed in your process before the manual book action.  Perhaps you might need a label on your window that says "You will need to clear the slot field before you can book a slot".


          Apart from this, if you wanted the field to clear automatically, I think we would need a bit more of a rethink of the design because the way we implemented this was to keep all values on the one Request window and then use the actions to update the CI.  As it is all on the Request window, the values will remain from previous actions.  If you didn't want this you'd have to look at using actions which store information in a collection object.  I think it would need quite a bit of a redesign though.


          Best wishes