Redlining & Batch Modification vs. In-Suite Authoring
The Tempo application offers two distinct features that allow operators and scientists to propose
or make modifications to procedures outside of the standard template editing workflow, while maintaining
a record of any changes made.
Each feature is scoped to a specific context: redlining applies to live procedure runs during batch
execution, while in-suite authoring (Designer Mode) applies only to procedures in draft status.
This article covers the following features:
- Redlining & Batch Modification
- What can be modified
- How redlines are recorded
- In-Suite Authoring (Designer Mode)
- What can be proposed
- How suggestions are accepted or rejected
- The core distinction between redlining and in-suite authoring
Redlining and in-suite authoring are related but separate features. Redlining occurs on live runs and
creates exceptions. In-suite authoring occurs on drafts and creates suggestions that require review
before becoming part of the template.
Redlining & Batch Modification
What: Making modifications to a procedure or batch while it is actively running.
When: A batch is live and in execution - the template is already locked.
Platform: iOS (6.5 SP1+), Web (coming in 8.0 - in development)
What you can modify:
| Entity | Status |
|---|---|
| Unit Operations | Shipped |
| Procedures | Shipped |
| Steps (as substeps) | Shipped |
| Basic Inputs | Shipped |
| Process Action Values (overrides) | Shipped |
| Sections | Unplanned |
| Complex Process Actions | Unplanned |
Key behavior:
- Changes apply to that run only and the original template is not touched
- Every redline is logged as an exception (based on configuration settings), capturing who made it and when
- Each org controls how the redlined addition exception type behaves via exception settings
- Thus, redlining does not trigger an exception unless the org has configured it to do so
- Enabled/disabled at the batch run level through configuration
- Redlining Enabled must be turned on at the batch run level - this is off by default and must be set when the batch run is configured
- Allow Batch Run Modification must also be enabled at the batch run level - this controls whether procedures and unit operations can be added during execution
In-Suite Authoring (Designer Mode)
What: Proposing edits to a draft procedure template from within the app.
When: The procedure is in draft.
Platform: iOS (6.5+), Web (coming in 8.0 - in development)
What you can propose:
| Entity | Status |
|---|---|
| Steps | Shipped |
| Basic Process Actions | Shipped |
| Unit Operations | Unplanned |
| Procedures | Unplanned |
| Sections | Unplanned |
| Complex Process Actions (fully formatted) | Unplanned |
| Process Action Values (overrides) | N/A |
Key behavior:
- Changes are suggestions (insert / update / delete), not immediate commits
- Each suggestion must be accepted or rejected before it becomes part of the template
- The procedure version must be in draft status - suggestions cannot be made on a released or retired version (this is enforced automatically, not a setting)
- User must be assigned to the procedure run
The Core Distinction
| Redlining | In-Suite Authoring | |
|---|---|---|
| Context | Live run data change | Draft template only recipe improvement |
| First released | 6.5 SP1 (iOS) | 6.5 (iOS) |
| Web support | Coming in 8.0 | Coming in 8.0 |
| Effect | Run-only, creates exceptions | Proposes template changes, requires review |