- The transformer doesn't have input ports. It outputs feature(s) after the main translation has completed.
- The transformer works only in the Main workflow. It does nothing in a custom transformer and custom format.
- The executing order of two or more ones should be controlled through their parameter settings.
Archived
Transformer that works after Completion of Translation
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.
<strong>This post is closed to further activity.</strong><br />
It may be a question with a best answer, an implemented idea, or just a post needing no comment.<br />
If you have a follow-up or related question, please <a href="https://community.safe.com/topic/new">post a new question or idea</a>.<br />
If there is a genuine update to be made, please contact us and request that the post is reopened.
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.
Yeah, I also think that adding the ability (option) to the Creator would be a simple and user friendly solution.
+19- Safer
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...
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
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.