Which option can help identify why a feature was rejected?

Which option can help identify why a feature was rejected?

• A. The Translation Log
• B. The Rejected port with fme_rejection_code attribute
• C. The Parameter Editor dialog
• D. The Navigator window

Answer: (B)

When a feature doesn’t pass a step in an FME workflow, it goes to the Rejected port and is labeled with an fme_rejection_code attribute. That single code tells you exactly why the feature was rejected, so you can map it to the specific reason (such as a value outside allowed range, missing required attribute, or a type mismatch) and diagnose the issue quickly. You can inspect this attribute on the rejected feature via the Attribute Manager or by examining the Rejected port with an inspector. The Translation Log gives a general view of what happened during the run but isn’t as precise for per-feature rejection reasons. The Parameter Editor dialog is for changing transformer parameters, and the Navigator window is for browsing data flow—neither directly reveals the rejection reason for a feature.

When a feature doesn’t pass a step in an FME workflow, it goes to the Rejected port and is labeled with an fme_rejection_code attribute. That single code tells you exactly why the feature was rejected, so you can map it to the specific reason (such as a value outside allowed range, missing required attribute, or a type mismatch) and diagnose the issue quickly. You can inspect this attribute on the rejected feature via the Attribute Manager or by examining the Rejected port with an inspector. The Translation Log gives a general view of what happened during the run but isn’t as precise for per-feature rejection reasons. The Parameter Editor dialog is for changing transformer parameters, and the Navigator window is for browsing data flow—neither directly reveals the rejection reason for a feature.