The start of data processing activity is a critical transition point. For many teams, it’s a high-friction bottleneck that creates delays, introduces the potential for burdensome mistakes, and requires constant monitoring. 

Rampiva Automate – Premium Edition introduces several features that are designed to help address these issues, including simplifying Job Start, in-queue logic, and standardizing output.  

Recurring Jobs 

In traditional data processing workflows, there is a specific triggering event that causes data to be collected and then submitted to be processed.  

However, an automated environment can support more advanced scenarios. Several use cases, such as information governance or compliance monitoring, need to align with the creation of new data by the business. Rampiva Automate – Premium Edition supports these scenarios by allowing users to set up recurring data processing jobs.  

Supporting a similar level of activity in manual environments would force the team to choose between the number of jobs being executed and the degree to which each job fits the unique requirements of the project. Take, for example, a 30TB environment spread across 26 departments with separate retention obligations, naming conventions, security requirements and escalation paths. Processing all of the data created in the last 30 days to look for policy violations means 1 additional job per day or forcing false standardization across each department. 

Recurring Jobs enables both custom requirements and a higher operating tempo. 

Integrate With External Systems 

All Rampiva Automate editions come with an open API that can be called by external systems to trigger an action or to get an update from Rampiva. Also, it’s simple to create Workflow steps that can trigger actions in external systems. This is how we push data to SQL, manage Relativity and Discover uploads, etc. 

Rampiva Automate – Premium Edition goes one step further by allowing API keys, Webhooks and out-of-the-box connectors to Microsoft Flow. These features allow Rampiva users to push updates out to external systems, in addition to receiving them. The logic is “low code” and does not tax network resources like repeated API calls do. This two-way connection – combined with the standardized, high-quality, output that comes with automating data processing – encourages connectivity between Rampiva and other systems. 

Conditional Jobs 

Recurring Jobs are a specific (high impact) example of an underlying capability in Rampiva Automate – Premium Edition: being able to trigger jobs conditional on events. 

The passage of time (say, 30 days) is a condition that, when satisfied, triggers a specific Job. 

Another set of triggers can be activity within the Scheduler Job Queue itself. Failed jobs can be restarted with more memory, new jobs can be started when a “Direct-to-Rampiva” upload is completed or continuing a job that was reliant on external activity being completed first. 

Advanced Scheduling is not required for routine data processing activity. But, for teams that are trying to get the most out of their investment or drive new use cases, these features support a high-efficiency, high-quality, high-connection environment.