Create contact permissions for a subtype in ClaimCenter

Procedure

Start Guidewire Studio for ClaimCenter.
At a command prompt, navigate to the ClaimCenter installation folder and enter the following command:
```
gwb studio
```
In the Project window, navigate to configuration > config > Extensions > Typelist.
Double-click SystemPermissionType.ttx to open this typelist in the editor.

For each of the following contact permission typecodes, right-click an existing typecode and choose Add new > typecode. Then enter the information for the new typecode.

New Code	Name	Description
`companyvendorcreate`	Create company vendor contacts	Permission to create company vendor contacts
`companyvendoredit`	Edit company vendor contacts	Permission to edit company vendor contacts
`companyvendordelete`	Delete company vendor contacts	Permission to delete company vendor contacts
`companyvendorview`	View company vendor contacts	Permission to view company vendor contacts
`personvendorcreate`	Create person vendor contacts	Permission to create person vendor contacts
`personvendoredit`	Edit person vendor contacts	Permission to edit person vendor contacts
`personvendordelete`	Delete person vendor contacts	Permission to delete person vendor contacts
`personvendorview`	View person vendor contacts	Permission to view person vendor contacts

In the Project window, navigate to configuration > config > security and double-click security-config.xml.

Associate the new permissions with a Contact subtype in the security-config.xml file.

For example, add the new typecodes for the Vendor and VendorPerson contact subtype permissions to the ContactPermissions element as follows:

<ContactPermissions>
...
  <ContactSubtypeAccessProfile entity="CompanyVendor">
    <ContactCreatePermission permission="companyvendorcreate"/>
    <ContactEditPermission permission="companyvendoredit"/>
    <ContactDeletePermission permission="companyvendordelete"/>
    <ContactViewPermission permission="companyvendorview"/>
  </ContactSubtypeAccessProfile>  
  <ContactSubtypeAccessProfile entity="PersonVendor">
    <ContactCreatePermission permission="personvendorcreate"/>
    <ContactEditPermission permission="personvendoredit"/>
    <ContactDeletePermission permission="personvendordelete"/>
    <ContactViewPermission permission="personvendorview"/>
  </ContactSubtypeAccessProfile>  
...
</ContactPermissions>

Stop the ClaimCenter server, regenerate the data and security dictionaries, and then restart ClaimCenter, as follows:
1. If ClaimCenter is running, open a command prompt in the ClaimCenter installation folder and then enter the following command:
```
gwb stopServer
```
2. To verify that the new permissions are correct, at a command prompt, navigate to the ClaimCenter installation folder and regenerate the data and security dictionaries:
```
gwb genDataDictionary
```
3. After you get a successful build of the dictionaries, restart ClaimCenter:
```
gwb runServer
```
Add the new permissions to a user role. For example:
1. Log in to ClaimCenter as a user that has the User Admin role, such as user name su with password gw.
2. Click the Administration tab.
3. Click Users & Security > Roles in the sidebar.
4. Click Add Role.
  The New Role screen opens.
5. For Name, enter Vendor Admin.
6. For Description, enter Manages vendor contacts. Requires Clerical role as well.
7. Click Add to add a new permission.
8. Click the new field and choose the Create company vendor contacts permission from the drop-down list.
9. Repeat step g and step h for each of the following permissions, substituting the actual permission for Create company vendor contacts in step h:
  - Create person vendor contacts
  - Delete company vendor contacts
  - Delete person vendor contacts
  - Edit company vendor contacts
  - Edit person vendor contacts
  - View company vendor contacts
  - View person vendor contacts
10. Click Update to add the new role.
Remove the abview permission from the Clerical role.

Note: Removing this permission is a quick way to test the new Vendor Admin role. With abview removed, using the Clerical role in conjunction with Vendor Admin makes it possible to limit users with the two roles from viewing non-vendor contacts. However, after this change, users who have the Clerical role and no other will be unable to view any contacts. For this change to be permanent, another role with abview permission would need to be created and then used in conjunction with the Clerical role for all previous Clerical users.
1. Click the Administration tab.
2. Click Users & Security > Roles in the sidebar.
3. Click Clerical and then click Edit.
4. Click the Code column heading to list abview at the top.
5. Click the check box for abview, and then click Remove.
6. Click Update to save your changes.
Create a new user for the role.
1. Click Actions > New User.
  The New User screen opens.
2. For First name, enter Devra.
3. For Last name, enter Rajan.
4. For User name, enter drajan.
5. For Password and Confirm Password, enter gw.
6. Under Roles, click Add, and then click the Name field. Choose Vendor Admin from the drop-down list.
7. Under Roles, click Add again, and then click the Name field. Choose Clerical from the drop-down list.
8. Under Groups, click Add and then click the Group field. Choose a group from the list, such as the sample data group Western Regional Claims Center.
9. Click Update to create the new user.
Log out.

For example, if you logged in as su, on the Options menu , click Log Out Super User.
Log in as drajan with password gw.
Verify that this user can create a new CompanyVendor or PersonVendor subtype and have it saved in ContactManager without being pending.
Verify that this user can edit and delete contacts of these types and have the changes saved in ContactManager without the contacts being made pending.
Verify that in an Address Book search, this user can click in the search results and see details only for CompanyVendor and PersonVendor contact subtypes and not for non-vendor subtypes. For example, clicking a contact of type Company or Person displays a message saying that you do not have permission to view the contact detail popup.