James, one idea, if your common workflow was wrapped with HandleHttpRequest and
HandleHttpResponse you can reuse them (calling with invokeHttp) since you pass
all the parameters in the request and your workflow use them as attributes.
Your common workflow behaves like a Micro Service.
Of
Thank you Joe and Oleg. Reference-able Process Groups sounds like it would
address what we intend to do, without using templates. Which would be fine
and which would presumably serve the same purpose. How far off in the
future is this feature? Six months? A year?
NiFi has a rich and powerful tool
I am happy to do this Oleg. Thank you very much for your reply.
Cheers,
Jim
On Thu, Mar 9, 2017 at 6:56 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Jim
>
> I see where you’re going with this and I do believe that it is a valuable
> enterprise feature. Unfortunately, template
Jim
I see where you’re going with this and I do believe that it is a valuable
enterprise feature. Unfortunately, template XML files are not the bootstrap
source of the flow such as flow.gz file. They are only used for
save/move/migrate/etc., which means any modifications to them are not going
