Skip to content
Glacis Help Center home
InboxAsk a human

Operating Procedure Manager

The Operating Procedure Manager app lets your workflows assign SOPs to records and react to SOP lifecycle events. Use these nodes to automate multi-step business processes.

SOP Assigned (Trigger)

Starts the workflow when an SOP is assigned to a record (order, shipment, etc.).

When to use it: Sending a notification when a procedure is kicked off, initializing data for the first step, setting up document storage.

Output: SOP name, instance ID, the record it's assigned to, and any execution context passed at assignment.

SOP Step Status Updated (Trigger)

Starts the workflow when an SOP step changes status — for example, from Planned to In Progress, or from In Progress to Completed.

When to use it: Triggering the next phase of work when a milestone is reached, sending notifications when steps complete, escalating if a step stays in progress too long.

Output: Step name, old status, new status, the SOP instance, and the underlying record.

Configuration: You can filter by specific SOP, specific step, or specific status transition (e.g., only fire when a step is completed).

Assign SOP (Action)

Assigns an SOP to a record — creating an SOP instance with all the defined steps.

When to use it: Automatically assigning the right operating procedure when an order is created, a shipment is booked, or a specific condition is met.

Update SOP Step Status (Action)

Changes the status of an SOP step programmatically — for example, marking a step as completed when a document is uploaded, or moving a step to In Progress when a condition is met.

When to use it: Automating step progression based on events — document uploads, deadline arrivals, or data from external systems.

Need help?

If you have questions or run into issues, we're here to help: