Using P2 attributes for Exit Required Fields in a Workflow

Hi all,

I have, on my Parts class, three subclasses. So I´m building a Change Order with associated workflow where one of this subclasses will be the Affected Item.

On the Review statuses, on the Workflow Criteria, I’m using the default All Change Orders CriteriaUsage. On the Exit Required Fields, I then select this subclass as the Class on the pull-down menu and then I select an attribute named Parts.PageTwo.AttributeX.

Now, when I pull the workflow forward, it goes to the next Status even  AttributeX is blank and does not provide any error/warning.

Using the same logic, if I select a P3 attribute like Subclassname.AttributeY, the system checks if it is filled and, if it´s not, provides a good error message saying there are required fields missing and lists the AttributeY name (which is great!!).

I know that I could use the P2 attribute inside a special Workflow Criteria on the CriteriaUsage (where I would specify that AttributeX is not null), however, during the worflow execution, it would just provide the “no exit criteria matches…” error message and not provide an indication where the problem is.

Thanks in advance for any guidance you can provide me with in order to be able to use a P2 attribute on the Exit Required Fields.

Best regards,

Add Comment
14 Answer(s)

Clovis,

The criteria states what to do if the field is blank.  What should it do if the field if populated?  This seems to be your missing piece here.  You need to remember that the workflow criteria is simply an ‘if then’ statement as would not offer any error warnings.

If this field is required at exit you should see an error message on what is missing.

Agile Angel Answered on March 9, 2017.
Add Comment

Hi Patrick,

That’s the reason why I want to be able to put the attribute under the Exit Required Fields instead of placing it in a condition inside a special Workflow Criteria. I just want to check if it is blank and, if it is, then provide the error message “..required fields missing… “

Agile Talent Answered on March 9, 2017.
Add Comment

Ah, I thought that might have been the case.  And you are not seeing the part.page2  attribute or you are having trouble locating it?  Did you search for the attribute original attribute name such as part.page2.multitext?

Agile Angel Answered on March 9, 2017.
Add Comment

I have the attribute visible on the Exit Required Fields selection window, with the proper name (not multitextxxx). It is visible on the selected subclass, but not on the other two subclasses (although it also shows up on the Exit Required Fields selection window if I change the Class to the other two subclasses where it is not visible – weird, isn’t it??_

Agile Talent Answered on March 9, 2017.
Add Comment

Is page two enabled for that particular subclass?

Agile Angel Answered on March 9, 2017.
Add Comment

Yes it is – I can see everything (Title block, P2 and P3 attributes for this subclass)

Agile Talent Answered on March 9, 2017.

In fact, for all subclasses – I only switch the attribute visibility on/off on each particular subclass

on March 9, 2017.
Add Comment

Might be the criteria…. what class is the criteria for?  The part or the change?

Agile Angel Answered on March 9, 2017.
Add Comment

The CriteriaUsage on the workflow status is for the Change (All Change Orders). The Class I select on the Exit Required Fields is the part subclass

Agile Talent Answered on March 9, 2017.
Add Comment

I need to do some testing on my end…. hold on.

Agile Angel Answered on March 9, 2017.

Sure… Holding tight!! 🙂

on March 9, 2017.
Add Comment

What’s the page2 attribute original name (system default)?  Note that if the page2 field is a custom add, yes, you will not see it as an exit field in the picklist.

Agile Angel Answered on March 9, 2017.
Add Comment

Your Answer

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