Permission check expression parameters in ContactManager

Some Gosu permission check expressions require a parameter, and some do not.

For example, the ContactManager tag create permission check expression is the same as the ABContact create permission check expression: perm.ABContact.create. When this expression has a ContactTagType argument, the expression verifies that the user has permission to create a contact with this tag. The ContactTagType arguments for this expression in the base configuration support the following enumeration constants:

• ContactTagType.TC_CLIENT
• ContactTagType.TC_VENDOR
• ContactTagType.TC_CLAIMPARTY

For example, the expression perm.ABContact.create(ContactTagType.TC_CLIENT) verifies that the user has permission to create a new contact with the Client tag. If the user has anytagcreate permission, which grants permission for creating contacts with all contact tag types, this permission check returns true.

The contact and tag create permission expression can take an ABContact type or subtype parameter or a ContactTagType typecode specified as an enumeration constant. The contact and tag delete, edit, and view permission expressions take an ABContact instance as a parameter. All these expressions check for both contact and tag permissions, so no additional tag permission check expression is needed. These expressions are:

• perm.ABContact.create
• perm.ABContact.delete
• perm.ABContact.edit
• perm.ABContact.view

The following table lists the ContactManager contact and tag permission check expressions: