Page 2 attribute modify event

I want to validate a mandatory Part Page 2 attribute value such that if it is updated with Yes/No then another attribute in Part Page 2 should be made mandatory. Which event can I utilize to ensure that the script runs every time the Part Page 2  attribute is updated the required validation is executed for another Part Page 2 attribute?

Agile User Asked on November 25, 2019 in Software Development Kit (API).
Add Comment
1 Answer(s)

You can accomplish this without an event.  Using field level read you could make the second field appear when a given value is made on the first.  Then using the criteria on the workflow matching the value in the first field, make the second field mandatory for exit.

Agile Angel Answered on November 25, 2019.

Thank Patrick for the response. Let me test this out and confirm if it meets the desired behavior. I have not used Enforced Field Level Read before due to stated performance impact. Have you come across any performance issues for end users by using this Privilege ?

on November 26, 2019.


We use “Enforce Field level Read” for all our external users and we haven’t seen any performance issues. We are on 936

– Raj


on November 26, 2019.


Thank you for your valuable inputs. I validated the configuration as you mentioned for Enforce Field Level Read and it works well on display. However, there are multiple clicks involved if user has to update the value for mandatory attribute from No to Yes.

First,  user has to edit the part and modify the value for mandatory attribute from No to Yes and Save. This will enable dependent Page 2 attribute to be visible.

Second,  User has to edit the part again and update the dependent Page 2 attribute with required value. Ideally, it should be possible with first edit.

Note: The user already has modify privilege for the dependent Page 2 attribute but unable to view the attribute during first edit when mandatory attribute is set to No.

Also, it is requested that the user is alerted during part save if the dependent value is not populated in case mandatory attribute is set to Yes. This may not be possible through this approach.

Would Update Title Block event work for pre-validation of Page 2 mandatory and inter-dependent attributes when the user clicks on Save during item creation and later on for update? Please suggest.


@Raj – Thank you for the confirmation

on December 9, 2019.
Add Comment

Your Answer

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