Configuring and using ALM
These topics describe how to set up and configure an ALM schema for users to follow an ALM work process.
About this task
Before creating an ALM Project, several records must already exist. There are also records that cannot be created until after the Project is created.
You must first create an ALMAdmin record. To create this record, you must log in as admin.
The ALMAdmin record controls who is allowed to create project configuration-related records. Users who are not listed in the ALMAdmin record do not have the project configuration record types listed in the New record menu list. If you add your own user ID to the ALMAdmin record, you must then logout and then re-logon in order for the change to be effective in the client's menu selection list.
After you create the ALMAdmin record, you can add either the individual users or HCL Compass user groups who are allowed to create projects. Once you add other users to the ALMAdmin list, then those other users can also add other users to the ALMAdmin record. The mandatory field in this record is Members or Groups. The ALMAdmin record's set of members can perform all actions on all record types.
If the ALMAdmin member is not a HCL Compass SecurityAdministrator, they only see Projects and other SecurityContext protected records secured by SecurityPolicies of which they are members.
The ALM sample database can be used to create projects based on the sample projects, OpenUP Sample Project and Triage Sample Project. To use the sample data, you must first log in as Admin and add a set of users to the ALMAdmin record. Then, you must add HCL Compass user groups to the SecurityPolicy records OpenUP Security and Triage Security. You can run the All SecurityPolicy query to find these records. See Project security for information on how HCL Compass groups and SecurityPolicy records interact with projects and the team members who perform roles on the project.