Skip to main content
Archived

Transformer that works after Completion of Translation

Related products:Transformers
siennaatsafe
david_r
takashi
tcrossman
muzhnasto
+17
  • siennaatsafe
    siennaatsafe
  • david_r
    david_r
  • takashi
    takashi
  • tcrossman
    tcrossman
  • muzhnasto
    muzhnasto
  • davideagle
    davideagle
  • esko
    esko
  • keoe
  • ascollins1
    ascollins1
  • bakkermans
  • vince.pellerito
  • giosp
    giosp
  • lancec
    lancec
  • wicki
    wicki
  • krlem
    krlem
  • deanrother
  • denniswilhelm
    denniswilhelm
  • battlezone77
  • mi_o
    mi_o
  • rhansen
  • christophe
  • stewartatsafe
    stewartatsafe

takashi
Influencer
It might be useful if there was a transformer that kicks a post process after completion of the main translation. A potential use case is to upload writers' outputs to a web server in the same workspace without writing shutdown script. The FeatureWriter coming in FME 2016 may also be used to embed such a post process into a workspace, but the expected transformer can be used not only for writers' outputs but also for outputs from transformers such as XMLFormatter.
  1. The transformer doesn't have input ports. It outputs feature(s) after the main translation has completed.
  2. The transformer works only in the Main workflow. It does nothing in a custom transformer and custom format.
  3. The executing order of two or more ones should be controlled through their parameter settings.
Adding the ability to some existing starter transformers (e.g. Creator, PythonCreator, SQLCreator) is also a choice.
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

5 replies

david_r
Celebrity
  • November 26, 2015
Agreed, I have also suggested this some time ago. In particular, I'd like an option for this in the Creator, where it runs just before the shutdown script.

takashi
Influencer
  • Author
  • November 26, 2015

Yeah, I also think that adding the ability (option) to the Creator would be a simple and user friendly solution.


fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • March 13, 2016

Just rereading this one. We have a "create at end" currently in the creator. But I think what you need here is to ensure that this fires AFTER all the other transformers in the whole workflow are done? Couldn't guarantee the writers are done (but could guarantee the FeatureWriters are). Just have to figure out how it interacts or is different than the current "Create At End" option in the Creator...


takashi
Influencer
  • Author
  • March 13, 2016

Yes, the Creator with "Create At End" would start creating features after the readers have finished reading all features. However, it could start working even if the translation has not been completed, if there was a blocking transformer in the workflow.

The expected transformer (or option) should guarantee that it starts creating features after the translation was completed. i.e. just before the shutdown process, as David mentioned.

One of advantages would be that the user can embed a shutdown-like process into the workspace without scripting.


Hi, I vote for this, I asked exactly the same behavior some days ago (I didn't find this thread):

https://knowledge.safe.com/questions/89794/run-sql-whenever-the-workspace-stops.html

 


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