Tuesday, July 28, 2009

Save button just got smarter

New feature to prevent inadvertent and unfortunate Save to an Asset’s properties.

As many of you know, we allow a tremendous degree of flexibility with respect to sequencing... when things are done. We do this, in order to support the very chaotic nature of how work flow occurs in our industry. The system tries to mange historical updates to Asset Utilization, even after that same Asset may already be Included on another Project(s).

There are however serious downside implications that come with this liberal functionality. For instance, there is no way for the system to understand why you would change the Damage Code, InCase or Location of an Asset in the future when it is keeping track of where it is today. And tracking the sequence it follows leading up to the Project in the Future where you elected to alter the Asset’s properties.

In an effort to prevent you from doing this “inadvertently”, the Edit screen for these properties now hides the SAVE button, until you actually Edit the data. As soon as you enter a value or select one of the drop down the SAVE button will appear. This allows you the freedom to view data without the fear of accidentally clicking the SAVE button. Your only choice is Cancel to close.

This change however, does not prevent you from making a change on a Project in the future. If you Edit data and then select SAVE, this action can cause your data to be corrupted on some reports. Only the passage of time to unlock the systems logic will eventually correct the issue.

Tip: Use real world logic when managing an Asset’s Damage, InCase and Location properties. Keep in mind a simple rule; does it make sense to give an Asset, Damage in the future when the Asset is being used on other Projects, not as far into the future?

Remember, the System does not retroactively update Damage on Projects with Open dates occurring before the Open Date of the Project you are in, even if the Open Date for both Projects in question are after today’s date. If we did not have this logic you could not go back in time and Edit data, to reconstruct your history, after the fact.