Skip to main content
Solved

Testfilter doesn't register as incomplete when it has 'non-availible' attributes in a testclause?

  • November 28, 2018
  • 4 replies
  • 17 views

thijsknapen
Contributor
Forum|alt.badge.img+10

Hi,

 

My question might be more of a bug report. Anyway, I noticed that my workflow didn't register a specific testfilter as 'incomplete', whereas other transformers usually do so. If I open the testfilter and have a look at the testclauses, then I do indeed see the 'old'/ 'non-available' attributes marked in red...

 

Any others experiencing issues with this?

 

Kind regards,

 

Thijs

 

Best answer by markatsafe

@thijsknapen This issue has been fixed in FME 2018.1 and 2019. If an Tester or TestFilter has an invalid attribute it will now register as an Incomplete transformer and the properties 'cog' will turn red. This also affects other transformers that support conditional testing (AttributeManager, AttributeCreator).

If there are still specific cases where the transformer does not show as incomplete when there is an invalid or missing attribute then please file a case with support.

I have attached an example workspace (2018.1) to illustrate the new behaviour: invalidtestfilter.fmw

View original
Did this help you find an answer to your question?

4 replies

nielsgerrits
VIP
Forum|alt.badge.img+54

I would register this under Ideas, as this is more a missing feature than a not (correct) functioning one. (And I think you are right :-))

Adding printscreens help to clarify the problem. I guess you meant to address the TestFilter Parameters not getting red when the attribute is missing.

Red cogwheel indicates a problem.

No indication in TestFilter Parameters.

Red cell indicates a missing attribute.


thijsknapen
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • November 28, 2018
nielsgerrits wrote:

I would register this under Ideas, as this is more a missing feature than a not (correct) functioning one. (And I think you are right :-))

Adding printscreens help to clarify the problem. I guess you meant to address the TestFilter Parameters not getting red when the attribute is missing.

Red cogwheel indicates a problem.

No indication in TestFilter Parameters.

Red cell indicates a missing attribute.

Hi Niels, tnx for your answer. I agree that some printscreens would have been helpful, but as you have done so I hope it's clear now.

 

In regards to the question vs ideas section. Do you know if there is a way to transfer a question into an idea? If I would just post the item again in the ideas, the item would be scattered across two platforms, which isn't handy in my point of view.

(I might be able to delete this post after I've created the same item under ideas)

 


redgeographics
Celebrity
Forum|alt.badge.img+50
thijsknapen wrote:

Hi Niels, tnx for your answer. I agree that some printscreens would have been helpful, but as you have done so I hope it's clear now.

 

In regards to the question vs ideas section. Do you know if there is a way to transfer a question into an idea? If I would just post the item again in the ideas, the item would be scattered across two platforms, which isn't handy in my point of view.

(I might be able to delete this post after I've created the same item under ideas)

 

Maybe @NatalieAtSafe can do that (I can't, not even with my special powers)


Forum|alt.badge.img+2
  • Best Answer
  • November 28, 2018

@thijsknapen This issue has been fixed in FME 2018.1 and 2019. If an Tester or TestFilter has an invalid attribute it will now register as an Incomplete transformer and the properties 'cog' will turn red. This also affects other transformers that support conditional testing (AttributeManager, AttributeCreator).

If there are still specific cases where the transformer does not show as incomplete when there is an invalid or missing attribute then please file a case with support.

I have attached an example workspace (2018.1) to illustrate the new behaviour: invalidtestfilter.fmw


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings