Object ownership - HxGN SDx - Update 63 - Administration & Configuration

Administration and Configuration of HxGN SDx

Language
English
Product
HxGN SDx
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
10

An individual user or an owning group can own objects. For an object to be owned, it must have the ISPFOwnedObj interface because this interface has the relationships to the login user and the owning group. The owning group can have a relationship with a vault. When a file is attached to an object with an owning group associated to a vault, the file is placed in that vault. This is the simplest vault configuration, but other rules can be configured as described in Vault configuration.

ISPFOwnedObj interface and ownership relationship definitions

The ISPFOwnedObj interface controls the ownership of an object.

Functionality configured on ISPFOwnedObj

There are no methods configured on this interface because although many objects are owned, they do not all exhibit the same ownership behavior. There are dedicated commands for changing the ownership of an object, and these are related to more specialized interfaces.

When setting the ownership of an object, the set of owning groups available vary depending on the command being used. Most of operations restrict the set to those configured on the method's access group-role relationships for the selected role that the current user is using. Other commands, such as Change Owning Group, may be configured to allow the user to change the ownership to some other owning group to perform a handover from one group to the next. For more information, see Configure method access.

Methods that change object ownership

Creating/Updating an owned object

Commands such as Create and Revise use the Create form, which can have an owning group display item. The available set of owning groups is restricted to those configured on the user's role–access group relationship for the access group that is related to the method being run. This is exactly the same as the restriction of shortcut methods based on ownership as described later in this document. For example, the ENGINEER owing group might be configured on the Engineer role to DocUpdate access group relationship so any create methods using this access group would only present the ENGINEER owning group. At the same time the ENGINEER and OPEN TO ALL owning groups might be configured on the Engineer role to VIEWONLY access group so allowing them to see OPEN TO ALL items but not allow them to create documents with that owning group.

Commands like Revise are configured to only be available to users who have access to the owning group of the object.

Check out (on ISPFDocumentVersion)

This command is used to create a new version of the document owned by the current user. Files attached to this version are also transferred to the user's local computer.

This command is configured to only be available to users who have access to the owning group of the object.

Check in (on ISPFDocumentVersion)

This command is used to transfer the checked-out files back to the vault and remove the user's ownership relationship.

This command is configured to only be available to users who have access to the owning group of the object.

Change owning group

This command is used to change the owning group of an object. It can be configured to present the same restricted list of owning groups as on the create methods or all owning groups to which the user has access via all their roles (selected or not) in the object's configuration. It is restricted to the roles for the object's configuration because they may have different roles assignments, and hence set of owning groups, in different configurations.

This command is typically configured on a document or transmittal.

Change owning group and owner

This command is used to change the owning group or owner of an object. It can be configured to present different sets of owing groups as in the Change Owning Group command.

This command is configured on saved reports, saved queries, and file markups.

See Also

Owning group configuration