CoreTegral launch a custom workflow

Do you want to use CoreTegral to launch a custom workflow whenever an event arrives from an automated equipment? This article explains one approach.

CoreTegral ships with a standard template that follows an approach that has been developed by Savantech consultants over the last few years. The approach is to model each job or batch of material (we call it a "Run") through the equipment with a workflow. Complex equipment that support multiple concurrent "Runs" simply have multiple concurrent workflows. This keeps the workflow relatively straightforward and sequential, but scales easily to support very complex multi-run scenarios. Low level tasks (e.g. detailed material handling) are abstracted away from the workflow to keep it easy to follow.

However, customers are not obliged to use this template, or approach. Perhaps they have their own way of doing things that has worked well over the years and suits the specific type of equipment and business rules in their facility. One such mechanism may be to simply listen to equipment events, and kick off a workflow for each one, which then drives the subsequent required control logic. This may be done at the SECS level, VFEI level, or based on any other interface in the system. The attached document provides an example (using VFEI events) of how to quickly create a configurable component that provides this functionality in 10 to 15 minutes. This highlights how the standardised configuration and management mechanisms embedded in CoreTegral enhances productivity by allowing the developer to focus entirely on the required functionality. Savantech is always looking for suggestions to improve CoreTegral, or suggestions for how-to articles.

Creating an Workflow Based Event Handler in CoreTegral (597 KB PDF Document)

‍