The resources administration consists of the creation of new resources (users), companies, and groups, and updating them as needed.
One Resource document is necessary for each user of the application. A resource may be created even if there is no corresponding user, for example, to represent a generic resource (customer, project leader, developer, etc.) in a project template. The resource document allows specifying the resource license, type, rates, and distribution profile (among other things). It is in the 'Resources' database where the match is done between the purchased and used licenses (see Licenses information).
Cerri Project can also manage 'generic resources', which are virtual resources that allow for better management of project templates and long-term planning. See the 'Resource management' principles for more information about generic resources.
The Company document allows grouping resources by company and defining default rates for a company location. If company rates are to be used, ensure companies and the corresponding Rates setup documents are created before creating resources. Company locations are also used to limit the scope of public holidays.
For the On-premise version, the Group document allows defining the company Directory groups usable for document distribution and access rights. This is especially useful when the company's Directory contains many groups.
Since Cerri Project is a multi-database system, all resources (resources, companies, and groups) are published from the 'Resources' database into the other databases through the resource's destinations.
If the rates in Rates setup documents are modified, it is possible to update the rates directly in all Resource documents:
The Resource documents are updated only if the 'Import the rates' parameter is enabled.
Once updated, resources must be published in the destination databases if needed.
To facilitate updating existing resources, multiple resources can be modified simultaneously directly from the 'All' views menu under the 'Resources' tab.
The Destinations field is one example and is described in the Publishing section.
Some key data, for resources only, can be changed directly from the views, through the Actions menu --> Modify the resources:
To create generic resources based on the resource types defined in the General setup document of the 'Resources' database. To do so:
All resources (Resource, Company, and Group documents) must be published in the destination databases to access and use them.
1. Important Note: Each time a Resource, Company, or Group document is saved, it is automatically published in the listed destination databases.
2. Important Note: 'Timesheets' databases can be selected as a destination in Company and Group documents but are not published there since they are not used in 'Timesheets.'
To manage changes in a resource's Lotus Notes username:
The resource's name is updated in all the destinations databases of the resource, including the 'Resource' document in the 'Resources' database where the action was done. The plans (Gantt) in the 'Projects' modules.
New first name | The resource's updated first name. |
New last name | The resource's updated last name. |
New initial | The resource's updated initial. |
New email address | If required, the resource's updated email address. |
New external ID | If required, the resources's updated external ID. |
New user name | The resource's updated username. The common name part is computed based on the other fields. |
Note: This operation may take time, depending on the number of destination databases and documents. It scans all fields in each document (except 'Timesheets') to ensure the name is updated everywhere.
To replace a resource in one or more databases:
Resource to replace | The database name. Single-selection field. Mandatory. |
Within the database | The resource to be replaced. Retrieved from the resource document. Not editable. |
Replace with | The new resources from the 'Resources' database. |
To change a password: