When content is submitted it starts a workflow process called "Contribute Article". The model includes tasks for updating, copying and archiving the article. These tasks can be carried out by the user group defined in the contribute form.
Note that these tasks won't appear until the content has been approved. The Contribute Form Configuration controls which tasks can be performed.
Users
By default these tasks are only available to the person who created the article.
In the form used to create the content, you can set a
Remember that tasks can only be assigned to one user at a time. If you claim the update task, no one else will have access to it until it is unclaimed (or reassigned using a tool like Task Management).
Updating Content
The update task links to a similar form to the one used to create the article. The fields are populated with the current values from the article in iCM (which may not be the values of the original submission) and can be updated. If approvals have been set up, any updates also have to go through the approval process before they appear on your site. Any media items uploaded with the original submission can also be updated.
Copy
Copying content is similar to updating it. The form is pre-filled with the details of the current content, but when submitted, creates a new version of the content rather than updating the original. This newly created content will also be subject to approvals, if configured.
Archive
The archive task links to a form where the user will have to confirm that they want to archive their submission, removing it from the site. In the current release archived content cannot be un-archived. While the article remains in iCM, its display settings are switched to "off" and the contribute process that created the article is terminated. Articles in iCM can be turned back on, but the link between the article and Contribute will be broken, so the article will have to be managed in iCM, just like regular content.
Additional Actions
Any number of additional tasks can be configured to appear. Existing examples include scheduling events and setting up default values for event tickets and packages. Each additional task is defined in the form that creates the new article, providing a task name and a form to link to. See Contribute Form Configuration for more information.
