Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Best way to make fields required based on status

From: holli.parris (2017-03-08 16:01)

Trying to find the best way to make certain fields required before changing status to COMP on task lines. They shouldn't be required while in INPRG, APPR, or WAPPR status. Anybody done this?


From: maximal (2017-03-08 18:56)

---In MAXIMO@yahoogroups.com, <holli.parris@urs.com> wrote :
Trying to find the best way to make certain fields required before changing status to COMP on task lines. They shouldn't be required while in INPRG, APPR, or WAPPR status. Anybody done this?
Workflow or automation script. I think you might be able to make them required on a status change that is saved, but not before.

-C





From: dennis_belandres (2017-03-08 14:04)

You should be able to create a condition like "istask=1 and
status='comp'", create an attribute restriction for your field to be
required through security group settings, then associate the condition.
It will not show a yellow asterisk to the required field but it should
prompt the user to fill out the required attribute when user tries to
complete work order without filling out the field.
Regards,
Dennis Belandres

The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.