complexType "tns:AssignmentType"
Namespace:
Content:
complex, 4 elements
Defined:
globally in common-1.xsd; see XML source
Includes:
definitions of 4 elements
Used:
XML Representation Summary
<...>
   
Content: 
(tns:target | tns:targetRef | tns:accountConstruction), tns:activation?
</...>
Content Model Elements (4):
tns:accountConstruction (type tns:AccountConstructionType), tns:activation (type tns:ActivationType), tns:target (in tns:assignment), tns:targetRef (in tns:assignment)
All Direct / Indirect Based Elements (1):
tns:assignment (type tns:AssignmentType)
Known Usage Locations
Annotation
Generic assignments of one object to another object. This will usually be assignment of a role to a user, assignment of an organizational unit, team or whatever. It may also be used to assing role to another role, creating a role hierarchy. Assignment is an abstract concept. It can be anything that gives the "receptor" object additional access rights, privileges, capabilities or similar ability or right. But it may also constraint the object with policy, e.g. to impelemt separation of duties. Roles, organizations and privileges in IDM system are examples of assignments. The assignemtn may target either existing IDM object (such as a role) or abstract resource account that may or may not exist. In case of resource objects it is constrained to accounts, as accoutns are the only resource objects that can be assigned to a user. Other resource objects (entitlements) can be assigned to accounts, but not to users. TODO: constraints
XML Source (see within schema source)
<xsd:complexType name="AssignmentType">
<xsd:annotation>
<xsd:documentation>
Generic assignments of one object to another object.
This will usually be assignment of a role to a user, assignment of an
organizational unit, team or whatever. It may also be used to assing
role to another role, creating a role hierarchy.

Assignment is an abstract concept. It can be anything that
gives the "receptor" object additional access rights, privileges,
capabilities or similar ability or right. But it may also constraint
the object with policy, e.g. to impelemt separation of duties. Roles,
organizations and privileges in IDM system are examples of assignments.

The assignemtn may target either existing IDM object (such as a role)
or abstract resource account that may or may not exist. In case of resource
objects it is constrained to accounts, as accoutns are the only resource objects
that can be assigned to a user. Other resource objects (entitlements) can
be assigned to accounts, but not to users.

TODO: constraints
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:element name="target" type="tns:ObjectType">
<xsd:annotation>
<xsd:documentation>
TODO: target
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="targetRef" type="c:ObjectReferenceType">
<xsd:annotation>
<xsd:documentation>
TODO: target ref
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element minOccurs="0" name="activation" type="tns:ActivationType"/>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 4/4)
tns:accountConstruction
Type:
Defined:
locally within (this) tns:AssignmentType complexType
TODO
XML Source (see within schema source)
<xsd:element name="accountConstruction" type="tns:AccountConstructionType">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:activation
Type:
tns:ActivationType, complex content
Defined:
locally within (this) tns:AssignmentType complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" name="activation" type="tns:ActivationType"/>

tns:target
Type:
tns:ObjectType, complex content
Defined:
locally within (this) tns:AssignmentType complexType
TODO: target
XML Source (see within schema source)
<xsd:element name="target" type="tns:ObjectType">
<xsd:annotation>
<xsd:documentation>
TODO: target
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:targetRef
Type:
tns:ObjectReferenceType, complex content
Defined:
locally within (this) tns:AssignmentType complexType
TODO: target ref
XML Source (see within schema source)
<xsd:element name="targetRef" type="c:ObjectReferenceType">
<xsd:annotation>
<xsd:documentation>
TODO: target ref
</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/