Skip to main content
Archived

Connector With On/Off Param Options

Related products:FME Form
  • December 6, 2019
  • 3 replies
  • 52 views
robotix
Contributor
Forum|alt.badge.img+10

Occasionally its nice to turn off a segment of an integration without having to modify and redeploy the entire integration.

A simple example scenario would be:

-Currently we trigger the workspace jobs with .bat files on a schedule and use the parameter references within.

-When 'x' happens in an integration do 'a', 'b', and 'c' [which are different transformations connected to 'x'].

-I no longer want 'b' to happen when 'x' happens.

-So I go to the connector param reference and set to off --ConnectorB "Off".

-If I ever want 'b' to happen again I can set it back to --ConnectorB "On".


I know, I know, there are probably other ways to do this. But isn't this easier? :)

This could be an option for some transformations also.

    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.

    3 replies

    erik_jan
    Contributor
    Forum|alt.badge.img+26
    • erik_janContributor
    • Contributor
    • December 6, 2019

    This looks very much like the option to enable/disable connections in a Workspace.

    That option is available in the mouse menu, after selecting a connection or transformer or feature type.

    Have a look at that option.

    It even has a short key (Ctrl-E).

    robotix
    Contributor
    Forum|alt.badge.img+10
    • robotixContributor
    • Author
    • Contributor
    • December 9, 2019

    Thanks, but I understand how to enable and disable connections.

    How do you do it with a published parameter? That is the suggestion.

    When we promote our integrations to production we set them to read only and use a .bat file with params to run the workspace. In this scenario, I don't want to edit the workspace because it is in production.

    erik_jan
    Contributor
    Forum|alt.badge.img+26
    • erik_janContributor
    • Contributor
    • December 9, 2019

    Ah, I see.

    I have used published parameters (e.g. ENVIRONENT) before in combination with a Tester or TestFilter to bypass sections that are only for DEV or TEST.

    Community Stats

    32,724
    Posts
    124,146
    Replies
    41,210
    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.