Patrick Lawrence's Profile
Agile Angel
4194
Points

Questions
11

Answers
381

  • 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

    • 2282 views
    • 3 answers
    • 0 votes