Overview
In TeamDynamix, every knowledge article follows a structured workflow from creation to publication. Two fields, Draft Status and Status, show where an article is in that workflow and who is responsible for the next step.
Understanding these fields ensures that all articles in Maverick OneStop are properly reviewed, approved, and published.
Learn more:
How Article Versions Work
When you edit an article in TeamDynamix, you are not changing the live version immediately. Instead, the system opens a working version of the article where you can make and save changes.
While the working version is in progress or under review, the published version remains visible to users.
- The working version is tracked by the Draft Status field.
- The published version (the live article) is tracked by the Status field.
Once the working version is approved, it either replaces the published version automatically (for existing articles) or becomes ready for publishing (for new articles).
Draft Status Field
The Draft Status field tracks the progress of the working version of an article, from initial draft through approval or retirement.
|
Draft Status
|
Meaning
|
Behavior for New Articles
|
Behavior for Existing Articles
|
|
Not Submitted
|
A working version exists but has not been sent for approval.
|
Advanced Publishers can create and save new working versions that are not visible to users until submitted.
|
Contributors, Publishers, and Advanced Publishers can edit existing articles and save changes without affecting the published version.
|
|
Submitted
|
The working version has been submitted for approval.
|
Sent to an Approver for review.
|
Sent to an Approver for review.
|
|
Approved
|
The working version has been approved by an Approver.
|
Once approved, the Advanced Publisher must click Publish to Knowledge Base to make the article live.
|
Once approved, the working version automatically replaces the published version.
|
|
Rejected
|
The working version was not approved and was returned for edits.
|
Returned to the Advanced Publisher for revisions. After edits, they click Update Article to resubmit for approval.
|
Returned to the Contributor, Publisher, or Advanced Publisher for revisions and resubmission. The current published version remains visible.
|
|
Pending
|
Indicates an update to a published article is waiting for approval.
|
Not used for new articles.
|
The current published version remains visible while the working version is in review.
|
|
(blank)
|
Used when an article has been archived and no longer has a working version.
|
Not applicable.
|
Indicates that the article is fully retired and no longer editable.
|
Status Field
The Status field reflects the state of the published (live) version of the article—what users currently see in Maverick OneStop.
|
Status
|
Meaning
|
|
Approved
|
The article is live and visible to its intended audience.
|
|
Rejected
|
The article has not been approved and is not visible to users.
|
|
Archived
|
The article has been retired and removed from public view. Its Draft Status becomes blank because no working version exists.
|
|
(blank)
|
This is a new article that has not yet been published.
|
How the Fields Work Together
|
Draft Status
(Working Version)
|
Status (Published Version)
|
What This Means
|
|
Not Submitted
|
(blank)
|
The working version exists but has not been submitted for approval.
|
|
Submitted
|
(blank)
|
The working version has been submitted and is awaiting approval.
|
|
Approved
|
(blank)
|
For new articles: Approver approves → Advanced Publisher publishes. For existing articles: the approved working version automatically replaces the live version.
|
|
Pending
|
Approved
|
An updated working version is waiting for approval while the current published version stays visible.
|
|
Rejected
|
Approved
|
The working version was rejected. The published version remains visible.
|
|
(blank)
|
Rejected
|
A new article was rejected and no new working version has been created yet. The article is not visible to users until a new version is submitted and approved.
|
|
(blank)
|
Approved
|
The article is live and has no active working version being edited.
|
|
(blank)
|
Archived
|
The article has been retired. Only Approvers can archive articles. Submit a ticket to request this.
|
|
Not Submitted
|
Approved
|
Edits have been saved as a draft on a published article but not submitted for approval yet. The current live version remains visible.
|
Important Note for Rejected New Articles
When a new article is rejected and later resubmitted for approval, clicking Approve does not automatically update both fields. The Approver must click Approve and then also go into the article and manually change the Status in the settings tab of the article from Rejected to Approved.
Workflow Summary
|
Scenario
|
What Happens
|
Who Acts
|
|
New Article Created
|
Working version created → Not Submitted → Submitted → Approved → Advanced Publisher clicks Publish to Knowledge Base to make it live.
|
Advanced Publisher → Approver → Advanced Publisher
|
|
Edit to Existing Article
|
A working version is created for editing → Clicks Update Article → Pending → Approved → The approved working version automatically replaces the live article.
|
Contributor, Publisher, or Advanced Publisher → Approver
|
|
Rejected Draft (New Article)
|
Working version rejected → Editor revises → Clicks Update Article → Approver approves draft status → Approves manually updates status to Approved → Advanced Publisher publishes.
|
Approver → Advanced Publisher → Approver → Advanced Publisher
|
|
Rejected Draft (Existing Article)
|
Working version rejected → Editor revises → Clicks Update Article → Approver approves → Changes go live automatically.
|
Approver → Contributor, Publisher, or Advanced Publisher → Approver
|
|
Archived Article
|
Article retired. Status = Archived, Draft Status = (blank) because no working version exists.
|
Approver (via ticket request)
|
Restoring Previous Versions
Approvers can view and restore previous versions of a knowledge article if content needs to be reverted or recovered. To request a restoration, submit a ticket to the Solutions Center, and an Approver will review and restore the appropriate version.
When a version is restored, it becomes the new working version and follows the standard approval workflow before going live again.
Still Need Help?
Visit the IT Solutions Center page to view current hours, locations, and contact information.