Set a workflow scratchpad variable

The workflow scratchpad is ServiceNow's solution to stateful data sharing across workflow activities. Unlike workflow variables which require formal definition and input/output mapping, the scratchpad lets you dynamically store and retrieve values using simple property assignment. Most developers initially try passing data through workflow variables or re-querying the record, but the scratchpad persists automatically across the entire workflow execution without additional database hits or complex variable mappings.

When to use this

• When you need to cache expensive lookups (manager chains, department calculations) for reuse in multiple activities
• When tracking original field values before workflow modifications for audit trails or rollback scenarios
• When conditional logic in later activities depends on calculations or decisions made in earlier activities
• When building approval chains dynamically where the sequence depends on business logic executed during workflow execution

When NOT to use this

• Don't use this for user-visible data — scratchpad values aren't accessible in catalog item forms or approval forms. Use formal workflow variables instead.
• Don't use this for cross-workflow communication — scratchpad scope is limited to a single workflow execution context. Use record fields or custom tables.
• Don't store large objects or binary data — scratchpad is serialized to the workflow context record and impacts performance with oversized payloads.
• Don't rely on scratchpad for error recovery — if the workflow fails and restarts, scratchpad data from failed execution isn't guaranteed to persist.

Key behaviors and gotchas

• Scratchpad persists automatically — you don't need to explicitly save it, but values are lost if the workflow engine restarts between activities
• GlideRecord objects can't be stored directly — you'll get [object Object] back. Store sys_id values or use getDisplayValue() for strings
• Complex objects serialize as JSON internally, so functions and prototypes are stripped — stick to plain data structures
• Undefined scratchpad properties return undefined, not null — use typeof checks or default values with ||
• Scratchpad is workflow-instance specific — parallel workflows on the same record maintain separate scratchpad namespaces
• Values persist across workflow pause/resume cycles, making it reliable for long-running approval workflows with wait conditions