Hi All,
I think the following will make you clear on the resolving of an alias value with respect to session scope,
Whenever we create a new session, the corresponding session config object could be able to carry out a default Alias Set object (I am hearing this first time J), the system will look into the session config object’s default alias set(basically it will look for a matching alias name) to resolve for a given alias name.
And the order by which the system will try to resolve is as follows,
• The server uses the alias set
defined for the session scope if that alias set is listed in
the policy object’s alias_set_ids attribute.
• If the session scope’s alias set isn’t found, the server
uses the alias set defined for the
user’s scope if it is in the alias_set_ids list.
• If the user scope’s alias set isn’t found, the server uses
the alias set defined for the
user’s default group if that alias set is in the alias_set_ids list.
• If the default group scope’s alias set isn’t found, the
server uses the alias set defined
for the system scope if that alias set is in the alias_set_ids list.
• If the system scope’s alias set isn’t found, the server
uses the first alias set listed in the
alias_set_ids attribute.
Shruthi, can you please forward this mail to our folks over there and please let me know their mail ids also.
Thanks and Regards,
Sudhakar Kanakaraj.
From: Kanakaraj,
Sudhakar
Sent: Wednesday, August 08, 2007
6:51 PM
To: Haridas,
Praveen; V Nagarajan, Sai
Subject: RE: Alias set in Session
Scope
Hi Praveen,
Yeah that’s valid point, but the question is how its resolving (based on what). Sai, you have an idea on this.

From: Haridas, Praveen
Sent: Wednesday, August 08, 2007
6:48 PM
To: Kanakaraj, Sudhakar
Subject:
Hi Sudhakar,
The scope of an Alias is the context in Documentum within which the system resolves the actual value for a given Alias name.
Session scope: The Alias Set for the life of a given Docbase session (session config object) helps the system resolve the actual value for an Alias.
This what I FEEL after going through it.
Thanks & Regards
Praveen Haridas
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.