I am trying to create a flow that simply:
- Reads the content of a URL which is a text file (its actually an ics calendar file)
- This will produce a document in Camunda
- Perform a simple regex search and replace on the content read
- Save the result into a file in Google Drive
- This of course requires a document as input
The first and last steps I know how to do. The middle step is where I am lost. There isn’t a lot of great documentation that I see on document processing. There are some functionality to do things like extract text from a document but I don’t see any thing to do much simpler processing of documents
I would likely write a worker to do it, instead of trying to do it with FEEL.
Hand the document off to a custom built worker, let the worker do its thing, and then get the updated document back.
I was thinking I would have to package the worker with it, but hadn’t considered just standing up a microservice (or in my case just part of an existing server). That should be easy enough.
The worker can reach into Camunda cluster, and ask “Is there any work of type ?”
It will then claim the work, and call the processing function, and respond back when the work is completed.
Writing workers (not necessarily microservices) would be a good habit to get into.