Namespace: |
|
Type: |
|
Content: |
|
Defined: |
XML Representation Summary |
||||||
<tns:attribute | ||||||
|
||||||
> | ||||||
|
||||||
</tns:attribute> |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="tns:AttributeDescriptionType"> <xsd:annotation> <xsd:documentation> Specification of handling of an account attribute. This overrides annotations in the resource schema. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
|
Use: |
optional |
Defined: |
<xsd:attribute name="ref" type="xsd:QName"> <xsd:annotation> <xsd:documentation> Name of the property attribute (XSD element) that this definition describes. It must point to the first-level attribute in the resource schema that belongs to an object class that is being described here. </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
tns:AccessType, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="c:access"> <xsd:annotation> <xsd:documentation> Access to the attribute as defined by the system administrator or deployer. This can constrain the access defined by resource schema annotations. Specifying broader access that the resource connector can handle is an error. If no access is specified, it defaults to read-write. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:string, simple content |
Defined: |
<xsd:element maxOccurs="1" minOccurs="0" ref="tns:description"/> |
Type: |
xsd:boolean, simple content |
Default: |
"true" |
Defined: |
<xsd:element minOccurs="0" ref="tns:ignore"/> |
Type: |
tns:ValueAssignmentType, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="inbound" type="tns:ValueAssignmentType"> <xsd:annotation> <xsd:documentation> Defines how the attribute values are used (assigned) in case of information flow from resource to IDM, e.g. in case of synchronization, reconciliation or discovery. In case a source expression is used, the expression variables should be as follows: $user - the user to whom the account belongs $account - the account that has been changed (after the change) Explanation: This is not a "value construction" as it is not constructing a new attribute value. It is rather using attribute value that was set be someone else. A simpler way how to express the assignement is needed here, especially a simple way how to express assignment target. Some rules may use that information and we definitelly need that to generate correct relative change descriptions. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:string, simple content |
Defined: |
<xsd:element maxOccurs="1" minOccurs="0" ref="c:name"> <xsd:annotation> <xsd:documentation> Human readable name for the account attribute. This name may be displayd in tools and GUIs to provide more pleasant user experience, as the native attribute names may look quite frightening (especially in LDAP). </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ValueConstructionType, complex content |
Defined: |
<xsd:element maxOccurs="1" minOccurs="0" name="outbound" type="tns:ValueConstructionType"> <xsd:annotation> <xsd:documentation> Defines how the attribute value is constructed in case of information flow from IDM to the resource, e.g. in case of provisioning. This may be a static value or an expression. In case an expression is used, the expression variables should be as follows: $user - the user to whom the account belongs $account - the account to be changed Motivation: This is "value construction" type, it is using similar format that is used eleswhere in the system (e.g. in roles) and therefore a common expression processor can be used to process all of that. E.g. a single processor may take into a consideration both schema handling and dynamic attributes set by roles. </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:
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/ |