By setting anonymous access on a project, end users will not be required to login to the application website when requesting Context-Sensitive Help. When anonymous access is enabled, the anonymous user and the All Users group will be added to the End User role.
By providing optional group-based filtering to a project, you can identify the content to which end users will have access. For more information, refer to Creating and Updating Groups.
By limiting the number of major document versions that are stored per project, you can ensure your authors have access to current versions by eliminating any outdated versions. In addition, you can elect to remove additional versions, which can save space on the database server by removing unnecessary content. Major versions are designated by a 0 in the first decimal place of a version indicator (for example, 4.0).
A project administrator can specify assessment score tracking; as well as settings for authors, allowing them to create ad-hoc workflows, and allowing them to specify website context. A project administrator can also restrict check in, check out, delete, and rollback functionality to the owner or administrator for content assigned to them.
By enabling the automatic creation of Edit Content Tasks for changed transactions, you can verify and update content as needed when transactions are changed. For more information, refer to Transaction Change Notifications.
By default, projects do not automatically have the above options enabled.
Enabling Project Settings
- Click the Projects button on the left.
- Click on the name of the project to edit.
- Click Edit Properties on the left menu.
- Choose from the following options:
Maximum versions to store
Enter the number of major versions to store on the Server. The number must be greater than 0.
Remove additional versions now
Select this option to remove excess major versions. This option is available only if the Maximum major versions to store field contains a number greater than 0.
This function permanently deletes non-inclusive versions from the database server.
Allow all authors to delete content
Select this option to allow all authors to delete content in this project.
Allow owners to delete content
Select this option to allow only content owners to delete content in this project.
Allow Authors to Assign Website Context
Select this option to allow authors to assign website context for the documents in this project.
Allow Authors to Initiate Ad-Hoc Workflows
Select this option to allow an author to enable an ad-hoc workflow.
Automatically create an Edit Content Task for changed transactions
Select this option to automatically create an Edit Content Task for changed transactions. For more information, refer to Transaction Change Notifications.
The content owner will be assigned the edit content task and notified via email when the task is created.
Enable Anonymous Access
Select this option to enable anonymous access for the project.
NOTE: If this option is not available, contact the system administrator.
Enable Assessment Score Tracking
Select this option to enable assessment score tracking for the project.
Assessment scores are tracked for courses and simulations with templates that have SCORM 1.2 or SCORM 2004 packaging enabled. For more information, refer to Specifying New Template Settings: Publications.
Enable review mode for published output that has been completed successfully
Select this option to enable review mode for published output. Review mode stops the Server from storing any SCORM related data if a course or simulation is completed successfully or the assessment is passed. SCORM data for all simulation modes will be stored in the database.
Enable Group-Based Filtering
Select this option to enable group-based filtering for the project.
Limit content editing to administrators, owners, and current workflow approver
Select this option to restrict check in, check out, delete, and rollback functionality to the content owner or administrator for content assigned to them.
- Click Save.
Viewing Project Reports
- Navigate to your project page.
- In the Details section, select a report from the drop-down list.
- Perform one of the following options:
If You Want To
Select a different report
Select a different report from the drop-down list.
Export the selected report
- Click Export.
- Select an export format and click OK.
Sort the report
Click on a report heading to sort the report on that field. For example, click Owner to sort the report by document owners.
Viewing the Project Status
The project status is available on the main project page. Administrators can view the total number of documents in the project and the number of documents in each status. In addition, a pie chart graphically displays the project status. Clicking on a slice of the pie chart will filter the currently displayed report, shown below the status, to show only documents in the selected status. Authors can view documents, charts, and reports for documents that they own.
The project status is not automatically refreshed. Status information is pulled from the cache instead of re-running the report each time the page is accessed. Caches help prevent performance issues that may result when running reports. Caches are user specific and are deleted when a user account is deleted. For more information on refreshing the project status, refer to Refreshing the Project Status.
The following statuses are available:
- Not Started - Includes tasks that have not been checked in, tasks with a status of Open, and Info Pak placeholders without content.
- Under Development -Includes tasks that have been checked in by the task owner and are not in a workflow or have a Published status. Info Pak documents without content are also included.
- Under Review - Includes content that is currently in a workflow, including Info Pak documents.
- Published - Includes content whose current version is published and the website context is assigned. This includes Info Pak placeholders or documents with content.
- Expired - Includes documents whose retention policy has expired.
- Under Revision - - Includes documents that have been previously published, but whose current version is not published and does not have assigned website context. . Also includes migrated documents that are still using Info Pak content. Documents in the Under Revision status are included in the Published Content Report.
The project status is not automatically refreshed each time the page is accessed. Status information is pulled from a cache created the first time a page is accessed. The cache is deleted when a user account is deleted, when the Server dashboard is reset, or by refreshing the project status.
- Navigate to your project page.
- In the Status section, click Refresh.
Deleting a Project
Deleting a project will delete all content in both the document library and website; all associated project groups; and the security policies, custom configurations, and modified properties of the project.
A deleted project is not sent to the recycle bin. A deleted project cannot be restored.
- Click the Projects button.
- Click on the project name to go to the project cover page.
- Click Delete Project on the left menu.
- Read the instructions carefully to determine if you want to delete the project or simply remove access to the project.
- Click I still want to delete.
- Click Delete it already!.