Namespace: |
|
Content: |
complex, 4 elements |
Defined: |
globally in common-1.xsd; see XML source |
Includes: |
definitions of 4 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||
<...> | |||||
|
|||||
</...> |
<xsd:complexType name="SynchronizationType"> <xsd:annotation> <xsd:documentation> Defines a synchronization properties (configuration) for a resource. TODO: add reconciliation setup (later) </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation> Flag indicating if the synchronization is enabled. If it is not, the synchronization process will be suspended. If enabled, the synchronization should pull in even the changes that were done during disabled synchronization (limitations may apply, such as the legth of history logs on the resource). Disabling synchronization means that it will not be executed automatically (e.g. polling resource in regular intervals). The synchronization may still be executed explicitly (manually), even if it is disabled. If this flag is not present, but a valid synchronization setup is found (which usually means valid "synchrnization" element), the synchronization is assumed to be enabled. This flag is meant to act as a tool to temprarily disable synchronizatoin without loosing the configuration and and state. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Correlation expression. It should return a list of candadate user entries that may be owners of a particular account. Correlation is an rough but an efficient way how to relate the account to a user. The correlation expression is in fact just a search filter. If correlation search returns more that one entries, confirmation expression will be executed for each of them. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Confirmation expression. The arguments are an account and a candidate owner (user). The confirmation expressions should return true if the user should be owner of the account. It should return false if the user cannot be owner of the account. The evaluation of the confirmation expression may be relativelly inefficient, as it will only be run for candidate entries returned by correlation expression. The expression variables should be set as follows: $user - the candidate user object (one of the results of correlation expression) $account - the changed account object </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Reaction to a synchronization situation. Situation identifier must be unique in this set (i.e. a situation definition may occur only once for each situation). If there is no definition for a particular situation, there will be no reaction ("do nothing"). The set of situation reactions is considered to be unordered. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:sequence> <xsd:annotation> <xsd:documentation> Defines a particular synchronization situation. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Defines an action to take when a situation is encountered. If there is no action for a particular situation, there will be no reaction ("do nothing"). There may be sevaral actions defined here. In such case all the actions will be executed in the order as they are defined here. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:sequence> <xsd:any maxOccurs="unbounded" minOccurs="0" processContents="lax"> <xsd:annotation> <xsd:documentation> Action parameters. TODO </xsd:documentation> </xsd:annotation> </xsd:any> </xsd:sequence> <xsd:annotation> <xsd:documentation> Action identifier (URL) TODO </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> |
Type: |
tns:ExpressionType, complex content |
Defined: |
<xsd:element minOccurs="0" name="confirmation" type="c:ExpressionType"> <xsd:annotation> <xsd:documentation> Confirmation expression. The arguments are an account and a candidate owner (user). The confirmation expressions should return true if the user should be owner of the account. It should return false if the user cannot be owner of the account. The evaluation of the confirmation expression may be relativelly inefficient, as it will only be run for candidate entries returned by correlation expression. The expression variables should be set as follows: $user - the candidate user object (one of the results of correlation expression) $account - the changed account object </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:QueryType, complex content |
Defined: |
<xsd:element minOccurs="0" name="correlation" type="c:QueryType"> <xsd:annotation> <xsd:documentation> Correlation expression. It should return a list of candadate user entries that may be owners of a particular account. Correlation is an rough but an efficient way how to relate the account to a user. The correlation expression is in fact just a search filter. If correlation search returns more that one entries, confirmation expression will be executed for each of them. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:boolean, simple content |
Default: |
"true" |
Defined: |
<xsd:element default="true" minOccurs="0" name="enabled" type="xsd:boolean"> <xsd:annotation> <xsd:documentation> Flag indicating if the synchronization is enabled. If it is not, the synchronization process will be suspended. If enabled, the synchronization should pull in even the changes that were done during disabled synchronization (limitations may apply, such as the legth of history logs on the resource). Disabling synchronization means that it will not be executed automatically (e.g. polling resource in regular intervals). The synchronization may still be executed explicitly (manually), even if it is disabled. If this flag is not present, but a valid synchronization setup is found (which usually means valid "synchrnization" element), the synchronization is assumed to be enabled. This flag is meant to act as a tool to temprarily disable synchronizatoin without loosing the configuration and and state. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reaction"> <xsd:annotation> <xsd:documentation> Reaction to a synchronization situation. Situation identifier must be unique in this set (i.e. a situation definition may occur only once for each situation). If there is no definition for a particular situation, there will be no reaction ("do nothing"). The set of situation reactions is considered to be unordered. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:sequence> <xsd:annotation> <xsd:documentation> Defines a particular synchronization situation. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Defines an action to take when a situation is encountered. If there is no action for a particular situation, there will be no reaction ("do nothing"). There may be sevaral actions defined here. In such case all the actions will be executed in the order as they are defined here. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:sequence> <xsd:any maxOccurs="unbounded" minOccurs="0" processContents="lax"> <xsd:annotation> <xsd:documentation> Action parameters. TODO </xsd:documentation> </xsd:annotation> </xsd:any> </xsd:sequence> <xsd:annotation> <xsd:documentation> Action identifier (URL) TODO </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </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/ |