Skip to content
EN

Request

Last updated

A request is the workflow that applies changes to an item after review and approval before they are published. You create a request from an item on the Content screen and list and review requests on the Request screen in the left menu.

A request has one of the following four statuses.

StatusMeaning
DRAFTA draft state
WAITINGWaiting for a reviewer’s approval
APPROVEDApproved by a reviewer, and the target items have been published
CLOSEDClosed without approval. It can be reopened

A request is in WAITING as soon as it is created. DRAFT cannot be chosen at creation.

ItemContent
TitleThe name that identifies the request. Required
DescriptionA description of what the request contains
ReviewersThe people who approve it. At least one must be specified
Target itemsThe items included in this request, and their versions. Editing an item after the request was created does not add that change to the existing request
StateOne of the statuses above
Created ByThe person who created the request
Created AtThe date and time it was created

The list on the Request screen shows the following eight columns.

  • A column with no header: the icon that opens the detail screen
  • The number of comments (the header is a message icon)
  • Title
  • State
  • Created By
  • Reviewers
  • Created At
  • Updated At

When you open the list, it is filtered to the WAITING state. The list can be filtered by state, created by, and reviewers. For created by and reviewers, you can choose between narrowing to yourself and showing all.

A reviewer can do the following with a request.

  • Approve: approves the request. On approval, the target items are published.
  • Close: closes and ends the request. A closed request can be reopened.

A request can be approved by a user in a role that has the approval permission and who is assigned as a reviewer for that request. Closing and reopening are determined by permissions separate from approval. For what each role can do, see Roles and permissions.

Whether publishing an item goes through a request is determined by the request requirement setting of the project.

  • A user in a role for which a request is required does not publish items directly; they create a request and send it to review.
  • A user in a role for which a request is not required can publish items directly if they have the publish permission. Without the publish permission, an item cannot be published even when no request is required.

While an item’s status is REVIEW or Published & REVIEW, that item cannot be published and no new request can be created for it. The target items are published at the moment the request is approved.

Comments can be posted on a request. For details, see Comment.