Remote resolvers and email triggers

You can choose a resolver who is not an authorized user of the local database. You can do this because DCS extends the user list to include a user-definable set of names from extusers.dft.

This file contains a list of external user names (one name per line). Blank lines and lines starting with the comment character (#) are ignored. The external user names are the user IDs of the users as defined in other databases.

In Rational Change, change requests and tasks are always assigned to local resolvers. Thus, email triggers only have to handle local user names, and setup email aliases for the local user names.

In DCS, however, the change request or task resolver can be at a remote database. Moreover, this user possibly does not exist at the local site. Therefore you must either set up email aliases for such remote users, or adapt the trigger scripts to pass the target dbid. You must consider this possibility when constructing email addresses.

The email notification text can need to include the DCM dbid of the database in which the change request or task is modifiable. By default, the notification text includes the path of the database from which the assignment was made. However, the change request or task can only be modifiable in another database. The trigger script is not able to automatically determine the path of the remote database. Hence, the notification would possibly have to include only the DCM dbid. The trigger script would possibly have to test the dbid and map it to the appropriate remote database path.


Feedback