Operator ID form
|
|
Complete this tab to identify this user, including a name and organization. The access groups affect which RuleSets and versions the user can access and the portal layout presented.
Optionally, you can associate a photograph, graphic, or other image with this operator.
Optional. You can associate an image (such as a photo or icon) with this operator. By default, this image appears in the Profile display and in the Designer Studio newsfeed. Your application can include this image in other situations. (For instructions, see More about Image Content data instances.)
If no image is associated with an operator ID, a default image from the binary file rule images.dialogprofileimage.gif
appears.
Field |
Description |
Operator Image |
For best results:
When you save the Operator ID form, PRPC creates an image content data instance (Data-Content-Image class) to hold the uploaded image file; the image is not part of the Operator ID instance. If you later delete an Operator ID instance, any associated image content data instance is also deleted. If you copy an Operator ID instance using Save As.., the newly created Operator ID instance is not linked to the image. Property .pyImageFileName links the Operator ID to an image content data instance. Click Delete Image to end the connection to an image content data instance, and return to the default image. This does not delete the Data-Content-Image instance. |
Optional. Identify one or more access groups for this operator. Mark one as the primary or initial access group by selecting a radio button.
Field |
Description |
Access Groups |
|
Select the name of an access group (a Data-Admin-Operator-AccessGroup instance) for this user. You can specify multiple access groups. When more than one group is listed, designate one as the user's default group by clicking the radio button next to that group. If this operator is to use a composite portal to enter work items, and is to enter work items for multiple applications, create a distinct access group for each application, and list them all here. See How to create a composite portal. If the data instance identified in the Name or Division field does not reference an access group based on an application RuleSet, this field is required. |