Skip to main content
Archived

Rejected Feature Handling on transformer level

Related products:FME Form
  • September 1, 2020
  • 2 replies
  • 25 views
A

Personally, I'm always a bit cautious when allowing workspaces to continue translation upon rejected features, since they might mess things up down the line in the workspace. I'd like to see a rejected feature handling on transformer level rather than just being able to set it for the whole workspace!

Any workarounds/ideas/input? :)

    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    2 replies

    ebygomm
    Evangelist
    Forum|alt.badge.img+51
    • ebygommEvangelist
    • Evangelist
    • September 2, 2020

    You can 'handle' Rejected Features using the Rejected Port. If you are expecting rejections from a certain transformer but don't want the workspace to terminate, if you link up the rejected feature port to a logger/writer/further workflow the workspace won't terminate even if set to Terminate on Rejected Features

     

    tomf
    Supporter
    Forum|alt.badge.img+23
    • tomfSupporter
    • Supporter
    • January 14, 2021

    Or even a junction. As long as the Rejected port is connected FME won't terminate

    Community Stats

    32,756
    Posts
    124,208
    Replies
    41,269
    Members
    Terms & ConditionsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.