I would like to reuse some parts of a workspace in such a way that the combination/module of transformers is only written once but used by "many". I would like to reuse these "modules" so that it can be used by different streams.
A simple example to explain what I am after:
Imagine that I have created a group of transformers that conducts some wizardry, a module of sorts. How can I use this in such a way that it makes copies of a Feature, applies different amounts of "something" and then fans out the result in a file for each "something"?
I understand that the question is vague, I was hoping for suggestions for further reading so that I could try and understand the principles for this. Should I be looking at custom transformers? Child workspaces? Or is there an other way to achieve this?
Literally a custom transformer is what you need. Do a search on this site for that term and you should find plenty of resources. In brief, select your group of transformers and press Ctrl+T. Give the group a name. Now you have a transformer that you can re-use in any part of the workspace. To use it in multiple workspaces, use the Export as Custom Transformer tool (inside the custom transformer definition) to create a separate fmx file. That can be used in multiple workspace and shared among multiple users.
Technically you could create a series of workspaces and string them together, but I don't know if that's the best way of doing things. If you were processing large amounts of data on Server then it would help, because you could assign each workspace to a separate engine. But generally one workspace with custom transformers is how I'd look at this first of all.
Literally a custom transformer is what you need. Do a search on this site for that term and you should find plenty of resources. In brief, select your group of transformers and press Ctrl+T. Give the group a name. Now you have a transformer that you can re-use in any part of the workspace. To use it in multiple workspaces, use the Export as Custom Transformer tool (inside the custom transformer definition) to create a separate fmx file. That can be used in multiple workspace and shared among multiple users.
Technically you could create a series of workspaces and string them together, but I don't know if that's the best way of doing things. If you were processing large amounts of data on Server then it would help, because you could assign each workspace to a separate engine. But generally one workspace with custom transformers is how I'd look at this first of all.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
