complexType "tns:ActivationType"
Namespace:
Content:
complex, 3 elements
Defined:
globally in common-1.xsd; see XML source
Includes:
definitions of 3 elements
Used:
XML Representation Summary
<...>
   
Content: 
tns:enabled?, tns:validFrom?, tns:validTo?
</...>
Content Model Elements (3):
tns:enabled (type xsd:boolean), tns:validFrom (in tns:activation), tns:validTo (in tns:activation)
All Direct / Indirect Based Elements (1):
tns:activation (type tns:ActivationType)
Known Usage Locations
Annotation
Type that defines activation properties. Determines whether something is active (and working) or inactive (e.g. disabled). It applies to several object types. It may apply to user, account, assignement, etc. The data in this type define if the described concept is active, from when it is active and until when. The "active" means that it works. If something is not active, it should not work or not cause any effect. E.g. inactive user should not be able to log in or run any tasks, the non-active role should not be assigned and if assigned it should not be taken into account when computing the accounts.
XML Source (see within schema source)
<xsd:complexType name="ActivationType">
<xsd:annotation>
<xsd:documentation>
Type that defines activation properties. Determines whether something is active
(and working) or inactive (e.g. disabled).

It applies to several object types. It may apply to user, account, assignement, etc.
The data in this type define if the described concept is active, from when it is active
and until when. The "active" means that it works. If something is not active, it should
not work or not cause any effect. E.g. inactive user should not be able to log in or run
any tasks, the non-active role should not be assigned and if assigned it should not be
taken into account when computing the accounts.
</xsd:documentation>
<xsd:appinfo>
<a:propertyContainer/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="enabled" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Flag that indicates if the described concept is active.

true =&gt; active, enabled
flase =&gt; inactive, disabled

This defines the "administrative state", i.e. the administrator's decision.
If set, this flag overrides any other constraints in the activation type.
E.g. if this is set to true and the object is not yet valid (according to
validFrom below), the user should be considered active. If set to false the
user should be considered inactive regardless of other settings.

Therefore this flag does NOT define an actual state of
the object. It is a kind of "manual override".

If this flag is not present then the other constraints in the activation type
should be considered.

If not present and there are no other constraints in the activation type or if there
is no activation type at all then the values is assumed to be true, i.e. that the
described concept is active (enabled).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="validFrom" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
A date from which is should the object be considered active.
Not applied if the "enabled" flag is set to any value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="validTo" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
A date to which is should the object be considered active.
Not applied if the "enabled" flag is set to any value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 3/3)
tns:enabled
Type:
xsd:boolean, simple content
Defined:
locally within (this) tns:ActivationType complexType
Flag that indicates if the described concept is active. true => active, enabled flase => inactive, disabled This defines the "administrative state", i.e. the administrator's decision. If set, this flag overrides any other constraints in the activation type. E.g. if this is set to true and the object is not yet valid (according to validFrom below), the user should be considered active. If set to false the user should be considered inactive regardless of other settings. Therefore this flag does NOT define an actual state of the object. It is a kind of "manual override". If this flag is not present then the other constraints in the activation type should be considered. If not present and there are no other constraints in the activation type or if there is no activation type at all then the values is assumed to be true, i.e. that the described concept is active (enabled).
XML Source (see within schema source)
<xsd:element minOccurs="0" name="enabled" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Flag that indicates if the described concept is active.

true =&gt; active, enabled
flase =&gt; inactive, disabled

This defines the "administrative state", i.e. the administrator's decision.
If set, this flag overrides any other constraints in the activation type.
E.g. if this is set to true and the object is not yet valid (according to
validFrom below), the user should be considered active. If set to false the
user should be considered inactive regardless of other settings.

Therefore this flag does NOT define an actual state of
the object. It is a kind of "manual override".

If this flag is not present then the other constraints in the activation type
should be considered.

If not present and there are no other constraints in the activation type or if there
is no activation type at all then the values is assumed to be true, i.e. that the
described concept is active (enabled).
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:validFrom
Type:
xsd:dateTime, simple content
Defined:
locally within (this) tns:ActivationType complexType
A date from which is should the object be considered active. Not applied if the "enabled" flag is set to any value.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="validFrom" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
A date from which is should the object be considered active.
Not applied if the "enabled" flag is set to any value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:validTo
Type:
xsd:dateTime, simple content
Defined:
locally within (this) tns:ActivationType complexType
A date to which is should the object be considered active. Not applied if the "enabled" flag is set to any value.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="validTo" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
A date to which is should the object be considered active.
Not applied if the "enabled" flag is set to any value.
</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/