These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Content Management System
- Features
- Publication
Publication
Track the path from approved item to observed publication.
OverviewScheduled items×
Content Management System · Publication
New
Scheduled items
Published waits for the content management system operator
| Number | Name | Publication date | Owner | Published URL | |
|---|---|---|---|---|---|
| CI-35222 | Item 451 | 09 Oct | PU-473 | ||
| CI-78445 | Item 790 | 09 Oct | PU-164 | ||
| CI-39070 | Item 869 | 08 Oct | PU-412 | ||
| CI-24495 | Item 526 | 25 Oct | PU-469 | ||
| CI-98604 | Item 689 | 17 Oct | PU-242 |
6 of 6 records
Item 451Content items · CI-35222
Publication date09 Oct
Published URLPU-473
What you can do
Track the path from approved item to observed publication
An approved item has a separate scheduling state and intended publication date. After the item is actually published, the team can record its published link, completion date and published item count. The content workspace also shows operation runs and ordered steps for a publishing action, keeping the input revision and result reference beside the editorial record.
How the work is organized
- Confirm approval. Check the review decision against the current source before moving the item to its planned date.
- Check the destination. Record a published link only after someone verifies what readers can open.
- Trace the attempt. Runs, ordered steps and attempts explain a failed or uncertain publishing result.
What to agree during setup
Agree which destination receives the content, who confirms a successful result and what external receipt should be retained. An execution attempt can fail or have an unknown result; the team should reconcile that state before trying the same action again. The operation key and source revision help identify a repeat request.
The team should rehearse its access rules with an operator, reviewer and administrator. Use an item from one organization and confirm that each person can see the record needed for their part of the work. Decide who resolves an ambiguous result and which person makes the final editorial decision.
Check the handoff on an actual case
Suppose an approved article is scheduled for a morning release. The operator checks the planned date and the approved source revision. After the publishing destination returns a link, the operator checks the live result and records that link on the item. If an attempt failed, they inspect the attempt reason and operation steps before retrying. A successful run and a published status answer different questions, and both deserve a check.
Before calling the handoff complete, compare the item status with its linked evidence and decision. The next person should be able to find the reason for the current state without relying on a message outside the record. If work must go back, assign a named person and preserve the previous outcome. Use the item number in the handoff so the recipient opens the same record, and check that the source revision still matches the decision under discussion.
What your team sees
- Scheduled items — See planned dates and owners for items ready to publish.
- Content Items Workspace — Inspect the selected item with its revision strip, decisions, state history and operation trace.
Follow the work through
Follow the editorial handoff and use the data model to check how the records connect.
What it keeps track of
Data model- Content items
- Editorial content items tracked through revision capture, independent review and publication.
- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
- Operation steps
- Ordered steps inside an operation run with input, output and external receipt state.
- Execution attempts
- Each recorded attempt to execute an approved action for a content item.
- State history
- Immutable workflow-written status transition history for each case.
Who uses it
Permissions- Content Management System Operator
- , Content Management System Administrator.
Set up Content Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.