cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

getFieldValue() behavior in Trigger.

kjain2
12-Amethyst

getFieldValue() behavior in Trigger.

Hi Community,

 

One situation wanted to share with you, might be you have already seen this or any prior experience:-

 

If we add an attribute let's say Field1 to any type let's say "Test Plan" and then set some value to this attribute(Field1).

 

E.g.

Test Plan 12345

Field1 is set to value "abc".

 

After setting value remove that attribute from the type but IssueFieldBean.getFieldValue(Attribute) still returns the value.

Now Field1 is removed from Test Plan visible Fields. 

In any trigger that gets the issue Bean of Test Plan 12345 if we execute:-

IssueFieldBean.getFieldValue(Field1) it gives "abc" for item 12345 let's say.

 

Instead as per me getFieldValue() function first should check whether field is really visible on type or not or?

 

Feel free to give your thoughts on this or if there is any architectural explanation.

 

Vielen Dank / Many Thanks,

Kapil Jain

1 REPLY 1

Thanks for finding this!

Announcements

Windchill RVS Users


Please take our

Windchill RV&S Authoring with Formula Editor Survey