Overview

An ExpertiseUserScope is an entity that is used to define subsets of users in the system that the Expertise service operates on. These named, identifiable subsets of users can be used for multiple purposes including:

  • During a brokered expertise search request issues by an end-user, the user can control the subset of users among which the system is to find a user with matching expertise and dispatch ane xpertise request to. The user does this by selecting one or more ExpertiseUserScope objects that have been created apriori by an administrator (a user with TACIT_MGR privilege) and have been granted access to the user.
Please see the base class for further details.

The ExpertiseUserScope object has a mandatory name attribute, an optional description, an included list of entities, and an excluded list of entities. It also inherits other attributes from entity. The Accessors that can be specified in the include or exclude list can only be one of the following:

  • OganizationUser: Explicitly specified users
  • Group: All user members of the group - direct and indirect - will be included/excluded. As new members are added/removed from the group, the ExpertiseUserScope will reflect that change.
  • DynamicGroup: All user members qualifying the OrganizationUserFilter underlying the DynamicGroup will be included/excluded. As new users qualify to be added/removed from the group, the ExpertiseUserScope will reflect that change.
  • AllUsersGroup: All the users in the system are included/excluded. As new users are created/deleted, the ExpertiseUserScope will reflect that change.

The include and exclude lists obey the following precedence rules:

  • If a user is in the exclude list via any of the above-mentioned accessors, that user will not be a part of the scope.
  • If a user is not found in the exclude list, the system evaluates the include list. If the user is found in the include list via any of the above-mentioned accessors, the user becomes a part of the scope. Else, the user is not part of the scope.

Members

Show inherited members

Projections
Name Type Required Description

attachedMarkers

marker[]

Set of marker elements associated with the entity.

attachedReminders

reminder[]

List of reminders attached to the entity

attachedSubscriptions

subscription[]

List of subscriptions attached to the entity

collabId

beeId

CollabId of the snapshot

createdOn

dateTime

Entity's creation date

creator

actor

The actor that created this entity

deleted

boolean

Deletion flag. If this property is set to true the entity is deleted.

description

string

Description for the Entity Scope.

excludeEntities

beeId<organizationUser>[]

Entities with are excluded from the Expertise User Scope.

includeEntities

beeId<accessor>[]

Entities that are included in the Expertise User Scope is returned

modifiedBy

actor

The actor that last modified the entity

modifiedOn

dateTime

The date when entity was last modified

name

string

Name of the entity.

parent

entity

The parent for this entity.

snapshotId

string

Contains the snapshot identifier for this snapshot. Snapshot identifiers are used to implement optimistic locking on the server.

Hierarchy

Inherits From

Examples

Below are examples in XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.

XML Example

(show inherited members)

<obh:expertiseUserScope xsi:type="obh:expertiseUserScope" xmlns:obh="http://www.oracle.com/beehive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <attachedMarkers>your_marker_0</attachedMarkers>
        <attachedMarkers>your_marker_1</attachedMarkers>
        <attachedMarkers>your_marker_2</attachedMarkers>
        <attachedReminders>your_reminder_0</attachedReminders>
        <attachedReminders>your_reminder_1</attachedReminders>
        <attachedReminders>your_reminder_2</attachedReminders>
        <attachedSubscriptions>your_subscription_0</attachedSubscriptions>
        <attachedSubscriptions>your_subscription_1</attachedSubscriptions>
        <attachedSubscriptions>your_subscription_2</attachedSubscriptions>
        <collabId>your_beeId_0</collabId>
        <createdOn>your_dateTime_0</createdOn>
        <creator>your_actor_0</creator>
        <deleted>your_boolean_0</deleted>
        <description>your_string_0</description>
        <excludeEntities>your_beeId_0</excludeEntities>
        <excludeEntities>your_beeId_1</excludeEntities>
        <excludeEntities>your_beeId_2</excludeEntities>
        <includeEntities>your_beeId_0</includeEntities>
        <includeEntities>your_beeId_1</includeEntities>
        <includeEntities>your_beeId_2</includeEntities>
        <modifiedBy>your_actor_0</modifiedBy>
        <modifiedOn>your_dateTime_0</modifiedOn>
        <name>your_string_0</name>
        <parent>your_entity_0</parent>
        <snapshotId>your_string_0</snapshotId>
</obh:expertiseUserScope>

Referenced By Representaions

Not Referenced Directly by Representations