complexType "tns:AccountConstructionType"
Namespace:
Content:
complex, 9 elements
Defined:
globally in common-1.xsd; see XML source
Includes:
definitions of 9 elements
Used:
XML Representation Summary
<...>
   
Content: 
tns:description?, tns:extension?, (tns:resourceRef? | tns:resource?), (tns:type? | tns:typeExpression?), tns:condition?, tns:attribute*, tns:entitlement*
</...>
Content Model Elements (9):
tns:attribute (in tns:accountConstruction), tns:condition, tns:description, tns:entitlement (in tns:accountConstruction), tns:extension, tns:resource (type tns:ResourceType), tns:resourceRef (type tns:ObjectReferenceType), tns:type (type xsd:string), tns:typeExpression (type tns:ExpressionType)
All Direct / Indirect Based Elements (1):
tns:accountConstruction (type tns:AccountConstructionType)
Known Usage Locations
XML Source (see within schema source)
<xsd:complexType name="AccountConstructionType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="tns:description"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="c:extension"/>
<xsd:choice>
<xsd:element minOccurs="0" name="resourceRef" type="c:ObjectReferenceType">
<xsd:annotation>
<xsd:documentation>
Reference to a resource that
should host the
implied account.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="resource" type="tns:ResourceType">
<xsd:annotation>
<xsd:documentation>
Resource that should host the
implied account.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:choice>
<xsd:element minOccurs="0" name="type" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Type of account that should be created on the
resource.

This must point to the a valid
accountType
definition in
the resource
object (in schemaHandling section).

This element is
optional. If not
specified then the account
type
marked as default
in the resource
definition should be used.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="typeExpression" type="c:ExpressionType">
<xsd:annotation>
<xsd:documentation>
Expression that determines type of account that
should be created on the resource.
TODO: more

The
variables should
be set as follows:
$user - the user that this account will belong
to
$assignment - an assignemt
that is
assigning the
object in which
context is this expression
evaluated (e.g. assignment of role)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element minOccurs="0" ref="c:condition">
<xsd:annotation>
<xsd:documentation>
The account is implied only if the condition is
evaluated to true.
If condition is not present, it
is
assumed to be
true.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="tns:ValueConstructionType">
<xsd:annotation>
<xsd:documentation>
Account attribute values implied by
this role.
When the role is assigned
the attributes specified
below
should
be
assigned values specified below.

When the role is unassigned, the
values specified below should be
removed unless
some other role
is
still specifying them.

TODO: this is very simplistic now.
Later we
need flags for
value
removal,
authoritativeness, merging
approach,
etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="entitlement" type="tns:EntitlementConstructionType">
<xsd:annotation>
<xsd:documentation>
Assignments implied by this role.
When the role
is assigned the
assignable types (groups, native
roles)
specified
below should
be assigned to the account.

When the role is
unassigned, the
assignable types specified
below
should be
unassigned
unless some
other role is still specifying them.

TODO: this is very
simplistic now.
Later
we need flags for value
removal,
authoritativeness, merging
approach, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 9/9)
tns:attribute
Type:
tns:ValueConstructionType, complex content
Defined:
locally within (this) tns:AccountConstructionType complexType
Account attribute values implied by this role. When the role is assigned the attributes specified below should be assigned values specified below. When the role is unassigned, the values specified below should be removed unless some other role is still specifying them. TODO: this is very simplistic now. Later we need flags for value removal, authoritativeness, merging approach, etc.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="tns:ValueConstructionType">
<xsd:annotation>
<xsd:documentation>
Account attribute values implied by
this role.
When the role is assigned
the attributes specified
below
should
be
assigned values specified below.

When the role is unassigned, the
values specified below should be
removed unless
some other role
is
still specifying them.

TODO: this is very simplistic now.
Later we
need flags for
value
removal,
authoritativeness, merging
approach,
etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:condition
Type:
tns:ExpressionType, complex content
Defined:
by reference within (this) tns:AccountConstructionType complexType
The account is implied only if the condition is evaluated to true. If condition is not present, it is assumed to be true.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="c:condition">
<xsd:annotation>
<xsd:documentation>
The account is implied only if the condition is
evaluated to true.
If condition is not present, it
is
assumed to be
true.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:description
Type:
xsd:string, simple content
Defined:
by reference within (this) tns:AccountConstructionType complexType
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" ref="tns:description"/>

tns:entitlement
Type:
Defined:
locally within (this) tns:AccountConstructionType complexType
Assignments implied by this role. When the role is assigned the assignable types (groups, native roles) specified below should be assigned to the account. When the role is unassigned, the assignable types specified below should be unassigned unless some other role is still specifying them. TODO: this is very simplistic now. Later we need flags for value removal, authoritativeness, merging approach, etc.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="entitlement" type="tns:EntitlementConstructionType">
<xsd:annotation>
<xsd:documentation>
Assignments implied by this role.
When the role
is assigned the
assignable types (groups, native
roles)
specified
below should
be assigned to the account.

When the role is
unassigned, the
assignable types specified
below
should be
unassigned
unless some
other role is still specifying them.

TODO: this is very
simplistic now.
Later
we need flags for value
removal,
authoritativeness, merging
approach, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:extension
Type:
anonymous complexType, complex content
Defined:
by reference within (this) tns:AccountConstructionType complexType
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" ref="c:extension"/>

tns:resource
Type:
tns:ResourceType, complex content
Defined:
locally within (this) tns:AccountConstructionType complexType
Resource that should host the implied account.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="resource" type="tns:ResourceType">
<xsd:annotation>
<xsd:documentation>
Resource that should host the
implied account.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:resourceRef
Type:
tns:ObjectReferenceType, complex content
Defined:
locally within (this) tns:AccountConstructionType complexType
Reference to a resource that should host the implied account.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="resourceRef" type="c:ObjectReferenceType">
<xsd:annotation>
<xsd:documentation>
Reference to a resource that
should host the
implied account.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:type
Type:
xsd:string, simple content
Defined:
locally within (this) tns:AccountConstructionType complexType
Type of account that should be created on the resource. This must point to the a valid accountType definition in the resource object (in schemaHandling section). This element is optional. If not specified then the account type marked as default in the resource definition should be used.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="type" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Type of account that should be created on the
resource.

This must point to the a valid
accountType
definition in
the resource
object (in schemaHandling section).

This element is
optional. If not
specified then the account
type
marked as default
in the resource
definition should be used.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:typeExpression
Type:
tns:ExpressionType, complex content
Defined:
locally within (this) tns:AccountConstructionType complexType
Expression that determines type of account that should be created on the resource. TODO: more The variables should be set as follows: $user - the user that this account will belong to $assignment - an assignemt that is assigning the object in which context is this expression evaluated (e.g. assignment of role)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="typeExpression" type="c:ExpressionType">
<xsd:annotation>
<xsd:documentation>
Expression that determines type of account that
should be created on the resource.
TODO: more

The
variables should
be set as follows:
$user - the user that this account will belong
to
$assignment - an assignemt
that is
assigning the
object in which
context is this expression
evaluated (e.g. assignment of role)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/