Concepts
Templates and Stubs
Defining processes and executing them
Stubber separates the definition of a process from the execution of a process.
What is a template?
A template is where the process is defined in Stubber. Think of it as a blueprint for the process and a template for the stubs that will be created from it. A template is the defining structure.
What is a stub?
A stub represents a unique, working instance of a template, allowing the process to be carried out based on predefined actions. It is where the process is executed and run.
In addition to running the process, the stub provides a comprehensive summary of all actions, tasks, and notifications that have taken place, along with the current state of the stub. This detailed overview makes it easier to track the progression of the process, ensuring you know exactly what has been executed so far and the current state of the instance/stub.
The stub creates a controlled environment where you can review and test the process, identify any issues, and examine how the template operates in real-time. By offering complete visibility into the workings of a particular instance, the stub allows you to pinpoint and resolve problems, ensuring that your template functions exactly as intended.
Conceptual
- The is a one-to-many relationship between a template and its stubs. In familial relationship, the template would be the parent and the stubs its child
- Each template can have many stubs created from it
- Each stub is created from a single template
Practical
- The above is an example of a template used to define a "sales enquiry" and the stubs that are created from it
- The sales enquiry represents the process or procedure template that is followed
- The sales enquiries that are generated by the template the unique stubs
- Every stub has a unique stubref that is used to uniquely identify the stub
Platform
On the Stubber Platform there are 2 applications that are used to work with templates and stubs.
