Wednesday, December 7, 2011

You can’t be in two places at ONCE… anymore


Recently we uncovered a system bug that would allow a User to receive an Asset back at the close of the Project and then place that same Asset on Transshipment for the same Project.

The code always had a function saying ,  once you placed an Asset on  a Transshipment from a Project, that it was removed from the Receiving list for the Project. It did not however protect against the scenario where working out of chronological order a User marked an Asset received then returned to the Project and Transshipped the Asset. Mind you it may not have been the same User. And why they marked it Received when it was not really there is not the issue. We allowed it and it of course this created a real issue for the system as essentially the Asset was now in two places at the same time.

New code inspired by a very insightful User has now been added to the Edit Packing List screen. As the screen opens it asks itself,” do any of these Assets have a Receive back date for the contextual Project? “ If an Asset holds that value the screen elects to not display the Asset.

NOTE: Yes, if the Asset has been mistakenly received, then it will need to be Un-Received in order to make it visible and thus available to include on Transshipment.