The Owner clause is optional when creating an object. If you do not include one, MQL will assume the owner is the current user, which is defined by the present context. This means that the System and Business Administrators can create objects for other users by first setting the context to that of the desired user and then creating the desired objects, or using the Owner clause:
The owner of an object can be assigned special access in the policy. The user who is assigned ownership of an object has access privileges defined in the Owner subclause of the policy. That user can be an individual, a group, or a role. If the user name you give in the Owner clause is not found, an error message will result. If that occurs, use the List User command to check for the presence and spelling of the user name. Names are case-sensitive and must be spelled using the same mixture of uppercase and lowercase letters. For example, the following object definition assigns the role “Software Developer” as the owner of a business object titled “Graphics Display Routine:”
In this example, the administrator might not have a specific name of a user to assign to the business object. Therefore, the name of a role is used. All persons assigned the role of Software Developer can access the object as the owner. At a later time, a Person can be reassigned as the owner according to the reassign access rules specified in the governing policy. The owner clause is also used to search for objects owned by a particular user or to assign items to particular user:
The Owner clause uses wildcard characters in a way similar to the Businessobject clause. You can also use multiple values to define the pattern. You can search for both the first and last name of an owner. |