We are designing the integration between the APL systems and Reels and would like to clairfiy the supported integration patterns beyond direct Reels endoint API calls.
Specifically, does Reels support a pull based model, such as a scheduled / background job that periodically fetches data from external systems? Or is the expected approach a push-based model, where external systems invoke Reels APIs to submit data whenever rule processing is required?
Understanding this will help us finalize the integration.
We can configure webhooks from Data Fabric to trigger rules based on CRUD operations. Could you please share a specific use case for this requirement? That will help us identify the best approach to run scheduled workflows on Reels.
Thanks Shrinidhi.
Our requirement is that the reels should run on a scheduled basis to go and fetch data from the IDP(Intelligent Document Processing) based on the fetched data which is treated with a certain template of data and key words, Reels must call the appropriate system(Network of systems)
Scheduled execution in Trinity
If the rule does not require varying input parameters, a scheduled job can be configured in Trinity to execute the Reels rule, rule group, or workflow on a recurring basis.
API-driven execution via SSD
Alternatively, an API can be exposed in SSD that fetches data from source systems, and triggers the required rule, rule group, or workflow using the newly retrieved data. This API can then be invoked on a scheduled basis within SSD.