Add a filtering criteria to an executive user.
Both executive and the executive assistant can run this command.
The response is either SuccessResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Delete a filtering criteria from an executive user.
Both executive and the executive assistant can run this command.
The response is either SuccessResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Get the assistant setting and the list of assistants assigned to an executive.
The response is either UserExecutiveGetAssistantsResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Response to the UserExecutiveGetAssistantsRequest.
Contains the assistant setting and a table of assigned assistants.
The table has column headings: "User Id", "Last Name", "First Name", "Hiragana Last Name",
"Hiragana First Name", "Phone Number", "Extension", "Department", "Email Address" and "Opt-in".
The possible values for "Opt-in" column are "true" and "false".
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCIResponse' super type was not found in this schema. Some elements and attributes may be missing. -->
Get a list of users that can be assigned to an executive.
Searching for users by group only makes sense when the executive user is part of an Enterprise.
The response is either UserExecutiveGetAvailableAssistantListResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Response to the UserExecutiveGetAvailableAssistantListResponse.
Contains a table with column headings: "User Id", "Last Name", "First Name", "Hiragana Last Name",
"Hiragana First Name", "Phone Number", "Extension", "Department" and "Email Address".
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCIResponse' super type was not found in this schema. Some elements and attributes may be missing. -->
Get the filtering setting and the list of filtering criteria defined for an executive user.
Both executive and the executive assistant can run this command.
The response is either UserExecutiveGetFilteringResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Response to the UserExecutiveGetFilteringRequest.
Contains the filtering setting and a table of filtering criteria.
The criteria table's column headings are: "Is Active", "Criteria Name", "Time Schedule", "Calls From",
"Filter" and "Holiday Schedule".
The "Filter" column can contain "true" or "false".
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCIResponse' super type was not found in this schema. Some elements and attributes may be missing. -->
Get a filtering criteria for an executive user.
Both executive and the executive assistant can run this command.
The response is either UserExecutiveGetSelectiveCriteriaResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Get the screening and alerting setting of an executive. Both executive and the executive assistant can run this command.
The response is either UserExecutiveGetScreeningAlertingResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Request to modify the assistant setting and the list of assistants assigned to an executive user.
The response is either SuccessResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Modify the filtering setting for an executive user.
Both executive and the executive assistant can run this command.
The response is either SuccessResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Modify a filtering selective criteria for an executive.
Both executive and the executive assistant can run this command.
The response is either SuccessResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
Modify the screening and alerting setting of an executive.
Both executive and the executive assistant can run this command.
The response is either SuccessResponse or ErrorResponse.
Application Data
<asDataModeSupported>
true
</asDataModeSupported><hssDataModeSupported>
false
</hssDataModeSupported>
XML Instance Representation
<...>
<!-- 'OCICommand' super type was not found in this schema. Some elements and attributes may be missing. -->
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.