I'm using a legacy transform in ACS 6.2 together with a custom actions, that processes new documents. Basically, documents are converted (via folder rules) to searchable PDFs (by use of OCRMyPDF). With transition to ACS 7.0, this is not working anymore, because the transform mechanism changed towards T-Engines and former (deprecated) transform classes have been removed.
Now, I'm trying to migrate this to the new transform API. I already managed to move the conversion process (OCR) to it's own independant T-Engine, which runs just fine when used with it's embedded test form. The piece I'm missing currently, is how I wire this to the custom action used in the folder rule. I followed a ton of posts, blogs, github content already, but didn't find the right clue yet.
As this is probably quite a common use case, I wonder what I overlooked... I would welcome some hints or references to some documents/examples.
The referenced action gives me a first impression how this could work. Unfortunately, the code is using the older SDK 3.0 and does not work with 7.0 (SDK 4.1). Quite a few things seem to have changed there.
Do you know of any other actions example utilizing SDK 4.1 (and idealy some T-Engine)?
(Hopefully) final question: Where can I find information how to interface with a T-Engine from my custom action? Are there any high-level (transformer) API classes available to handle the REST calls implicitly, or do I need to handle the REST stuff on my own?
Any java code examples (not necessarily actions) are very welcome.