It would be nice if there was some sort of toggle option when running with feature caching as to whether a custom transformer produced a single output cache (like a collapsed bookmark) or if every transformer within it had a cache (current behaviour).
I can see the latter being useful when actual developing the custom transformer, but in most cases I don't care about the interim portions of the custom transformer, when developing a workspace that uses one.
I could put a bookmark around each custom transformer and collapse it, but that becomes tedious when there are several (dozens) of custom transformers.
Open
Feature caching and custom transformers
+40- Contributor
+4- Contributor
Good ideas. I'd like to see an ability to override the feature caching, with a workbench specific toggle. So when I quickly load a workbench before I leave the office in the evening and press run and completely forget to turn off feature caching, this workspace runner workbench knows to not use caching.
+16- Contributor
I would also like to see partial runs enabled for embedded custom transformers. It's not currently possible (FME 2019.0) to initiate a partial run from inside a custom transformer - it can only be done from the main workspace. (See this related Idea: https://knowledge.safe.com/idea/91290/allow-partial-runs-inside-custom-tranformers.html)
+18- Safer
The following idea has been merged into this idea:
All the votes have been transferred into this idea.
All the votes have been transferred into this idea.
+18- Safer
The following idea has been merged into this idea:
All the votes have been transferred into this idea.
All the votes have been transferred into this idea.
+18- Safer
The following idea has been merged into this idea:
All the votes have been transferred into this idea.
All the votes have been transferred into this idea.