ServiceDesk 4.7.78 Update 03/18/14

The Special Situations Advisory (SSA) is designed to let you make a unique record, as applicable to a particular customer or address, involving some special situation as applicable to that customer or address (e.g., he's deadbeat, do not perform service for this person).  Whenever you are in a Callsheet and type in a name, address, telephone number or email that matches an applicable SSA item, you'll see references to that item (along with other references in the CstmrDbase showing).  These will be distinguished by the fact there are # signs in the line listing. 

Until now, it's been up to the user to visually notice such a listing, and volitionally click on it, to then review and take into account whatever is disclosed in the item.  The problem is, a user might fail to notice, or may not bother to volitionally review.  There was desire for the software to more directly "force" the user to notice.  That's what this improvement is about. 

When a user clicks to "Job/Sale" from a Callsheet, the system now checks for either a name or address match in the list of SSA items.  If there is a match, the user gets a message similar to this:

After being shown the SSA as applicable (and then closing it), they'll then get this:

The action from that point forward, of course, is obvious.  

A while back we added an option to export from the PartsPick form (Shift-Ctrl/F8) a summary of items needing moved for a particular tech (see entry below for Rel. 4.7.47; we added a button in the form's bottom-right corner).  Thereafter another user wanted the ability to do similarly, but for all techs, and via a single click for all.  For this (and though the addition was not then here announced), we added a button to the form's bottom-left corner):

This new button was thus significantly powerful, but still left some movements to be managed separately.  Specifically, its output accounted only the for the same items as directly managed via the PartsPick form, which by nature deals with moving special-order parts and spec-tagged inventory, but does not account for simple and standard inventory restock. 

That's what is addressed in this release. 

Output from this button will now include not just what's shown to be moved on the face of the PartsPick form.  It will also include what needs to be moved to the tech, by way of simple inventory restock.   More specifically, it will show what needs to be moved based on the Items-Recently-Used method. 

Additionally, when simple inventory restock is used from this venue, it will do one better than when using the same method via the InventoryControl form (F10).  In that form, there is at present no built-in mechanism by which the system remembers for you what was the last time you ran the process (and which, therefore, should be the "begin-date" for movements that trigger the next-new process).  Here in this context, the system explicitly remembers the last date and time, and offers it as default for the current process.