Is it possible to overrule required field on Parts Save using PX?

Is it possible to overrule the required field on Parts Save using PX? 

If the condition is Yes then it is Required and if Condition is No then the Field is not required.

Add Comment
3 Answer(s)

While setting the field to required in the attribute setup is one way to get the field filled, there are other options which may allow you to set this field to not required for the use of the PX.
During the release cycle of any object you may put in requirements that will look for field values to be included.  What you pose here is an extremely flexible requirement that will stipulate if the field requires an input or not.  To deal with this you can set the attribute to not required and have the PX control the requirement in an attribute that may not be accessed or seen by anyone (using read level privileges).  By using the workflow criteria you can key off of that field and either allow the workflow to move forward or throw an error.
This is one possibility.
For example
I have a field that will stipulate WEEE Compliance when required.
The PX will bring over the requirement and set an attribute (we will call it WEEE requirements for this example) to ‘Yes’
Now, when we enter the release workflow, the criteria looks for this value and now needs the WEEE Compliance field to not be NULL

Agile Angel Answered on June 18, 2015.

Hi Patrick Lawrence,

I understood what you are saying, I also followed the same way, But my requirement is attribute is Required field and i need to overrule based on Criteria i.e another required field value should be “Yes”

on June 18, 2015.
Add Comment

Hi Patrick Lawrence,

Thanks for the explanation.
But my requirement is different, While creating the part the field should appear as Required field, But this required field is based on another required field which will tell it is required or not.

Example:
Field1 Required   “Yes/No List Field”   and Field 2  Required  “Multi Text Field”
This Multi Text Field 2 is mandatory, if I select Field1 Required selected as Yes.

I handled this using PX on the Next Part Save.  Where my Field1 is Required field and Field 2 is not Required field So on the Next Save or Edit and Save it will check if Field1 is Yes then Field2 is mandatory else not.
But if user cancel the Part, then there  is chances of user missing the field2 

I hope you understand my requirement.

Thanks
Divakar

Agile Talent Answered on June 18, 2015.
Add Comment

Divakar,

Unfortunately there is no conditional field requirements in Agile PLM such that you may find in other enterprise applications such as SFDC where you can easily handle this type of requirement.

The best you can do here is to manage this through the workflow criteria in the following manner;
IF ‘Field1’ is ‘Yes’ AND ‘Field2’ is NOTNULL then you may enter the workflow
additionally
IF ‘Field1’ is ‘No’ then you may enter the workflow

These two criteria would stop anyone from entering the workflow if your requirement is not meant.  Since there is no information that Agile will tell you if the workflow is not enabled (such that ‘Field1’ is set to ‘Yes’ yet ‘Field2’ remains NULL) you can add a validation PX that would better express the missing information.  Something akin to an ‘Actions’ menu PX that would better explain the error to the user. 

One other thing on my mind is that is ‘Field2’ is indeed NEVER mandatory unless ‘Field1’ is set to ‘Yes’ then you could hide ‘Field2’ using read level rights until ‘Field1’ is set to ‘Yes’… this may cause the user to take note of the additional requirement when faced with the new field suddenly popping up on the object.  Just a thought of course.

Agile Angel Answered on June 22, 2015.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.