Defaults

[barbhenry]

Sometimes a default should not be an option. When this is the case, it would be great to have a hard stop in place. Say for instance the name of the service writer should be a hard stop. The person entering the information can not go any further until a name is entered.

[ricmorin]

While this sounds like a good idea in theory, I doubt it would work well in the real world. Software users don't tend to like being locked into a single way of doing things. They like options.

That being said, I'd vote for an user option to do this, switchable at the config level to prevent MY users from moving forward unless a particular field was filled.

[murraymotive]

That being said, I'd vote for an user option to do this, switchable at the config level to prevent MY users from moving forward unless a particular field was filled.

+1 +1 +1 +1
I want options everywhere... EVERYWHERE!

[Johnny5]

Does everyone know the service writer is auto populated on the order if it is defined for the User in Setup / Default Settings?

[ricmorin]

That's a good point, JD. When you apply a default Service Writer while logged in as a certain user, that default SW populates all the SW fields automatically.

Logged in as Ric

USER1.PNG (20.2 KiB) Viewed 2430 times

Set default SW here while logged in as Ric

USER2.PNG (6.03 KiB) Viewed 2430 times

[Rich]

Does everyone know the service writer is auto populated on the order if it is defined for the User in Setup / Default Settings?

Bingo! "My" work station is assigned to me. The server is assigned to Chuck. I know that if I use his computer it shows he started it. When he is gone on vacation (or if I am) I switch the user to the appropriate user.