Continuous Processing with R-Tag
Continuous Processing is useful when you have an external process which has created some data records and you need to automatically generate and deliver reports based on these records. For example, if you have a software which generates invoices and you want R-Tag to detect when a new record is created, print/export a report based on the record, and send it to the right recipient, the record should be marked as processed to avoid further processing. Here are few examples of when continuous processing might be useful:
- Your company system generates records for orders, invoices, or statements. When a record is generated you need to run a report, export it to a file, and send it by email. You can define a data driven job in R-Tag, which will run every few seconds if there are new records. R-Tag will process them as described in the job. After each record is processed, R-Tag will mark it as processed and the record will be ignored durnig the next run.
- You may have an online system where customers request quotes. R-Tag will generate a quote and will send it to the right salesperson for approval.
- You may define a query which will generate a new order and send it to the right vendor. The new requested quantity will be saved to a table containing ordered but not received items and they will be counted during the next run.
Here is sample screen of a scenario when an order was generated by a 3rd party system and based on the customer's preferred language R-Tag will generate the order in either English, French, or Spanish, and will then send it to the customer and mark it as processed.
You can find more information about Continuous Processing in this document: http://r-tag.com/Content/Documents/R-TagContinuousProcessing.pdf