The Project Close Process workflow process aides the Project Manager in some routine close out tasks that accompany every project. Marking the project inactive starts the process and it will continue down one of two paths:

1. Once the project is inactive, the process will then check to see if there is no remaining estimate to complete (ETC) still on the project. If there is ETC leftover, then the process will go into a waiting state for 14 days to allow the project manager to cleanup or to cancel the process if it was done in error. After 14 days, the process will check to see if the project is active. If the project is active, then the process will end. However, if the project is still inactive, the process will continue with the closeout activities even if there is ETC still on the project.
2. If the project is marked inactive after the initial 14 days of waiting if applicable, then the process will immediately move to the closeout activities.

The closeout activities include:

• Turning off time entry for the project, tasks and project members
• Updates the ETC, proposed ETC, and pending estimates to 0
• Updates the task status and assignment status to Completed
• Sets the task, assignment and project finish dates to today’s date only if the finish dates are after the process run date
• Sets all Risks and Issues to Closed with a resolution of  “## This was closed automatically as part of the project close process ##”
• Set future hard allocation and allocation finish dates to today when the date is after today’s date

This training document is a Rego Consulting Quick Reference Guide to assist with the creation of Status Reports in Clarity’s Modern User Experience.  This doc references version 16.1 views. Document covers the creation of Status Reports via the Status Module as well as the Status Report Module. Detail is provided on the widgets that can be used within the Status Report canvas as well as instructions on how to configure the canvas. Detail is also provided on how to Preview and Publish status reports.

Converts one Investment type to another investment type. Functionality • One investment type instance converted to another investment type • Investment object level attributes are copied over by default • Investment sub-objects can be chosen to be copied • The attributes and sub-objects to be copied to must be api enabled • Can convert from non api enabled object like other work to api enabled Custom CIT • Attribute mapping does not support multivalued lookups yet • If auto-numbering is not enabled for target investment type of the sub-objects, an ID will be auto-generated. • Associated risks and issues will not be copied over • Target investment status will be "Unapproved" • If there are Mandatory target investment type attributes either o use a template to convert where having a value in the attribute is not mandatory or Have a default value in the mandatory field defined on the object • If effort task creation is enabled, the effort task will also be brought over. o The effort task will appear with custom code if a investment template is used for conversion • The allocations will extend to the finish of the new investment if investment template is used which has tasks • Almost 500 instances of sub-objects are supported at this point. • The values in lookups need to be active or the process will error out • All required attributes must be api enabled

This training document is a Rego Consulting Quick Reference Guide to assist with creation and management of resource Teams in Clarity’s Modern User Experience.  This doc references version 16.2.1 views. Document provides detail on how to create Teams and add resources to a Team. Instructions are provided on how to add resources by OBS and how to allocate a team to an investment. Team key points are provided with regard to Classic, Allocations, ETC and Financials.