element Service-Archive-Descriptor
diagram wp_diagrams/wp_p101.png
namespace http://service.archive.wp.n2.tibco.com
properties
content complex
children wp:channels wp:version
annotation
documentation
Root element of work presentation deployment schema
source <xs:element name="Service-Archive-Descriptor">
  <xs:annotation>
    <xs:documentation>Root element of work presentation deployment schema</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="channels">
        <xs:annotation>
          <xs:documentation>Channels are presenation channels which are client-specific. One or more channels can be deployed at the same time during deployment</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="channel" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>Channel is a presentation channel.At least one channel needs to be specified during deployment.It is possible to just deploy the channel without deploying the assosciate resources or can be a full fledged channel deployment with associated work model type and its resources</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="description" type="xs:string" nillable="true" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>Description of the channel that is getting deployed.
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="target-channel-type" type="ct:ChannelType">
                    <xs:annotation>
                      <xs:documentation>Target channel type indicates the client type of channel for viewing the presentation. EMAIL channel is a channel type which might be capable of displaying JSP/Forms/MS-Word type of presentations.
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="presentation-channel-type" type="ct:PresentationType">
                    <xs:annotation>
                      <xs:documentation>presentation type specifies the rendering engine type for the presentation.It can be something like JSP,GI,RCP..etc
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="implementation-type" type="ct:ImplementationType">
                    <xs:annotation>
                      <xs:documentation>Implementation type specifies the fulfillment type of the presentation.This fulfillment type can be a server push/pull
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="work-type" minOccurs="0" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:documentation>WorkModel type is the work type/work model type defined in BRM.It is assumed that in runtime that work types/ work model types are already deployed and activated before the work presentation request is made.Same work model type can be associated to different presentation forms based on the channel specified. </xs:documentation>
                    </xs:annotation>
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
                          <xs:annotation>
                            <xs:documentation>
It is a
provision
to add
custom
properties
to the
work
model
type
which
can be
interpreted
by the
Work
Presenation
Deployment
Analyser
</xs:documentation>
                          </xs:annotation>
                        </xs:element>
                        <xs:choice>
                          <xs:element name="form" type="wp:formType">
                            <xs:annotation>
                              <xs:documentation>
Form
indicates
the
presentation
resource
that
needs
to
be
displayed
for
this
particular
work
type
request
</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="page-flow" type="wp:pageFlowType" nillable="false"/>
                          <xs:element name="extension-config" type="wp:channelExtentionType"/>
                          <xs:element name="page-flow-ref" type="wp:pageFlowRefType"/>
                        </xs:choice>
                      </xs:sequence>
                      <xs:attribute name="guid" type="xs:string" use="required"/>
                      <xs:attribute name="name" type="xs:string" use="optional"/>
                      <xs:attribute name="version" type="xs:string" use="optional"/>
                    </xs:complexType>
                  </xs:element>
                  <xs:element name="domain" type="xs:string" minOccurs="0"/>
                  <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>It is a provision to add custom properties to the work model type which can be interpreted by the Work Presenation Deployment Analyser.
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="extension-config" type="wp:channelExtentionType" nillable="true" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>Defines extended channel information, for example, Email Channel, or for a channel not yet implemented in WP.
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="business-service" type="wp:businessServiceType" minOccurs="0" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:documentation>Defines pageflow business service form related resources.
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="page-flow" type="wp:pageFlowType" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="version" type="xs:string" use="optional"/>
                <xs:attribute name="channelId" type="xs:string" use="required"/>
                <xs:attribute name="name" type="xs:string" use="optional"/>
                <xs:attribute name="defaultChannel" type="xs:boolean">
                  <xs:annotation>
                    <xs:documentation>Is this a default channel for the target channel type. Note there should be only one default channel per channel type.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="version" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element Service-Archive-Descriptor/channels
diagram wp_diagrams/wp_p102.png
namespace http://service.archive.wp.n2.tibco.com
properties
content complex
children wp:channel
annotation
documentation
Channels are presenation channels which are client-specific. One or more channels can be deployed at the same time during deployment
source <xs:element name="channels">
  <xs:annotation>
    <xs:documentation>Channels are presenation channels which are client-specific. One or more channels can be deployed at the same time during deployment</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="channel" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Channel is a presentation channel.At least one channel needs to be specified during deployment.It is possible to just deploy the channel without deploying the assosciate resources or can be a full fledged channel deployment with associated work model type and its resources</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="description" type="xs:string" nillable="true" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Description of the channel that is getting deployed.
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="target-channel-type" type="ct:ChannelType">
              <xs:annotation>
                <xs:documentation>Target channel type indicates the client type of channel for viewing the presentation. EMAIL channel is a channel type which might be capable of displaying JSP/Forms/MS-Word type of presentations.
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="presentation-channel-type" type="ct:PresentationType">
              <xs:annotation>
                <xs:documentation>presentation type specifies the rendering engine type for the presentation.It can be something like JSP,GI,RCP..etc
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="implementation-type" type="ct:ImplementationType">
              <xs:annotation>
                <xs:documentation>Implementation type specifies the fulfillment type of the presentation.This fulfillment type can be a server push/pull
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="work-type" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>WorkModel type is the work type/work model type defined in BRM.It is assumed that in runtime that work types/ work model types are already deployed and activated before the work presentation request is made.Same work model type can be associated to different presentation forms based on the channel specified. </xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>
It is a
provision
to add
custom
properties
to the
work
model
type
which
can be
interpreted
by the
Work
Presenation
Deployment
Analyser
</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:choice>
                    <xs:element name="form" type="wp:formType">
                      <xs:annotation>
                        <xs:documentation>
Form
indicates
the
presentation
resource
that
needs
to
be
displayed
for
this
particular
work
type
request
</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="page-flow" type="wp:pageFlowType" nillable="false"/>
                    <xs:element name="extension-config" type="wp:channelExtentionType"/>
                    <xs:element name="page-flow-ref" type="wp:pageFlowRefType"/>
                  </xs:choice>
                </xs:sequence>
                <xs:attribute name="guid" type="xs:string" use="required"/>
                <xs:attribute name="name" type="xs:string" use="optional"/>
                <xs:attribute name="version" type="xs:string" use="optional"/>
              </xs:complexType>
            </xs:element>
            <xs:element name="domain" type="xs:string" minOccurs="0"/>
            <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
              <xs:annotation>
                <xs:documentation>It is a provision to add custom properties to the work model type which can be interpreted by the Work Presenation Deployment Analyser.
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="extension-config" type="wp:channelExtentionType" nillable="true" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Defines extended channel information, for example, Email Channel, or for a channel not yet implemented in WP.
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="business-service" type="wp:businessServiceType" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>Defines pageflow business service form related resources.
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="page-flow" type="wp:pageFlowType" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
          <xs:attribute name="version" type="xs:string" use="optional"/>
          <xs:attribute name="channelId" type="xs:string" use="required"/>
          <xs:attribute name="name" type="xs:string" use="optional"/>
          <xs:attribute name="defaultChannel" type="xs:boolean">
            <xs:annotation>
              <xs:documentation>Is this a default channel for the target channel type. Note there should be only one default channel per channel type.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element Service-Archive-Descriptor/channels/channel
diagram wp_diagrams/wp_p103.png
namespace http://service.archive.wp.n2.tibco.com
properties
minOcc 1
maxOcc unbounded
content complex
children wp:description wp:target-channel-type wp:presentation-channel-type wp:implementation-type wp:work-type wp:domain wp:extended-properties wp:extension-config wp:business-service wp:page-flow
attributes
Name  Type  Use  Default  Fixed  Annotation
version  xs:string  optional      
channelId  xs:string  required      
name  xs:string  optional      
defaultChannel  xs:boolean        
documentation
Is this a default channel for the target channel type. Note there should be only one default channel per channel type.
annotation
documentation
Channel is a presentation channel.At least one channel needs to be specified during deployment.It is possible to just deploy the channel without deploying the assosciate resources or can be a full fledged channel deployment with associated work model type and its resources
source <xs:element name="channel" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Channel is a presentation channel.At least one channel needs to be specified during deployment.It is possible to just deploy the channel without deploying the assosciate resources or can be a full fledged channel deployment with associated work model type and its resources</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="description" type="xs:string" nillable="true" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Description of the channel that is getting deployed.
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="target-channel-type" type="ct:ChannelType">
        <xs:annotation>
          <xs:documentation>Target channel type indicates the client type of channel for viewing the presentation. EMAIL channel is a channel type which might be capable of displaying JSP/Forms/MS-Word type of presentations.
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="presentation-channel-type" type="ct:PresentationType">
        <xs:annotation>
          <xs:documentation>presentation type specifies the rendering engine type for the presentation.It can be something like JSP,GI,RCP..etc
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="implementation-type" type="ct:ImplementationType">
        <xs:annotation>
          <xs:documentation>Implementation type specifies the fulfillment type of the presentation.This fulfillment type can be a server push/pull
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="work-type" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>WorkModel type is the work type/work model type defined in BRM.It is assumed that in runtime that work types/ work model types are already deployed and activated before the work presentation request is made.Same work model type can be associated to different presentation forms based on the channel specified. </xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
              <xs:annotation>
                <xs:documentation>
It is a
provision
to add
custom
properties
to the
work
model
type
which
can be
interpreted
by the
Work
Presenation
Deployment
Analyser
</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:choice>
              <xs:element name="form" type="wp:formType">
                <xs:annotation>
                  <xs:documentation>
Form
indicates
the
presentation
resource
that
needs
to
be
displayed
for
this
particular
work
type
request
</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="page-flow" type="wp:pageFlowType" nillable="false"/>
              <xs:element name="extension-config" type="wp:channelExtentionType"/>
              <xs:element name="page-flow-ref" type="wp:pageFlowRefType"/>
            </xs:choice>
          </xs:sequence>
          <xs:attribute name="guid" type="xs:string" use="required"/>
          <xs:attribute name="name" type="xs:string" use="optional"/>
          <xs:attribute name="version" type="xs:string" use="optional"/>
        </xs:complexType>
      </xs:element>
      <xs:element name="domain" type="xs:string" minOccurs="0"/>
      <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
        <xs:annotation>
          <xs:documentation>It is a provision to add custom properties to the work model type which can be interpreted by the Work Presenation Deployment Analyser.
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="extension-config" type="wp:channelExtentionType" nillable="true" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Defines extended channel information, for example, Email Channel, or for a channel not yet implemented in WP.
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="business-service" type="wp:businessServiceType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Defines pageflow business service form related resources.
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="page-flow" type="wp:pageFlowType" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
    <xs:attribute name="version" type="xs:string" use="optional"/>
    <xs:attribute name="channelId" type="xs:string" use="required"/>
    <xs:attribute name="name" type="xs:string" use="optional"/>
    <xs:attribute name="defaultChannel" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>Is this a default channel for the target channel type. Note there should be only one default channel per channel type.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

attribute Service-Archive-Descriptor/channels/channel/@version
type xs:string
properties
use optional
source <xs:attribute name="version" type="xs:string" use="optional"/>

attribute Service-Archive-Descriptor/channels/channel/@channelId
type xs:string
properties
use required
source <xs:attribute name="channelId" type="xs:string" use="required"/>

attribute Service-Archive-Descriptor/channels/channel/@name
type xs:string
properties
use optional
source <xs:attribute name="name" type="xs:string" use="optional"/>

attribute Service-Archive-Descriptor/channels/channel/@defaultChannel
type xs:boolean
annotation
documentation
Is this a default channel for the target channel type. Note there should be only one default channel per channel type.
source <xs:attribute name="defaultChannel" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Is this a default channel for the target channel type. Note there should be only one default channel per channel type.</xs:documentation>
  </xs:annotation>
</xs:attribute>

element Service-Archive-Descriptor/channels/channel/description
diagram wp_diagrams/wp_p104.png
namespace http://service.archive.wp.n2.tibco.com
type xs:string
properties
minOcc 0
maxOcc 1
content simple
nillable true
annotation
documentation
Description of the channel that is getting deployed.
source <xs:element name="description" type="xs:string" nillable="true" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Description of the channel that is getting deployed.
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/target-channel-type
diagram wp_diagrams/wp_p105.png
namespace http://service.archive.wp.n2.tibco.com
type ChannelType
properties
content simple
facets
Kind Value Annotation
enumeration JSPChannel
enumeration GIChannel
enumeration PageflowChannel
enumeration EmailChannel
enumeration RssChannel
enumeration openspaceChannel
enumeration MobileChannel
annotation
documentation
Target channel type indicates the client type of channel for viewing the presentation. EMAIL channel is a channel type which might be capable of displaying JSP/Forms/MS-Word type of presentations.
source <xs:element name="target-channel-type" type="ct:ChannelType">
  <xs:annotation>
    <xs:documentation>Target channel type indicates the client type of channel for viewing the presentation. EMAIL channel is a channel type which might be capable of displaying JSP/Forms/MS-Word type of presentations.
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/presentation-channel-type
diagram wp_diagrams/wp_p106.png
namespace http://service.archive.wp.n2.tibco.com
type PresentationType
properties
content simple
facets
Kind Value Annotation
enumeration JSP
enumeration GI
enumeration Pageflow
enumeration Email
enumeration Rss
enumeration GWT
enumeration iPhone
annotation
documentation
presentation type specifies the rendering engine type for the presentation.It can be something like JSP,GI,RCP..etc
source <xs:element name="presentation-channel-type" type="ct:PresentationType">
  <xs:annotation>
    <xs:documentation>presentation type specifies the rendering engine type for the presentation.It can be something like JSP,GI,RCP..etc
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/implementation-type
diagram wp_diagrams/wp_p107.png
namespace http://service.archive.wp.n2.tibco.com
type ImplementationType
properties
content simple
facets
Kind Value Annotation
enumeration Pull
enumeration Push
annotation
documentation
Implementation type specifies the fulfillment type of the presentation.This fulfillment type can be a server push/pull
source <xs:element name="implementation-type" type="ct:ImplementationType">
  <xs:annotation>
    <xs:documentation>Implementation type specifies the fulfillment type of the presentation.This fulfillment type can be a server push/pull
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/work-type
diagram wp_diagrams/wp_p108.png
namespace http://service.archive.wp.n2.tibco.com
properties
minOcc 0
maxOcc unbounded
content complex
children wp:extended-properties wp:form wp:page-flow wp:extension-config wp:page-flow-ref
attributes
Name  Type  Use  Default  Fixed  Annotation
guid  xs:string  required      
name  xs:string  optional      
version  xs:string  optional      
annotation
documentation
WorkModel type is the work type/work model type defined in BRM.It is assumed that in runtime that work types/ work model types are already deployed and activated before the work presentation request is made.Same work model type can be associated to different presentation forms based on the channel specified.
source <xs:element name="work-type" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>WorkModel type is the work type/work model type defined in BRM.It is assumed that in runtime that work types/ work model types are already deployed and activated before the work presentation request is made.Same work model type can be associated to different presentation forms based on the channel specified. </xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
        <xs:annotation>
          <xs:documentation>
It is a
provision
to add
custom
properties
to the
work
model
type
which
can be
interpreted
by the
Work
Presenation
Deployment
Analyser
</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:choice>
        <xs:element name="form" type="wp:formType">
          <xs:annotation>
            <xs:documentation>
Form
indicates
the
presentation
resource
that
needs
to
be
displayed
for
this
particular
work
type
request
</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="page-flow" type="wp:pageFlowType" nillable="false"/>
        <xs:element name="extension-config" type="wp:channelExtentionType"/>
        <xs:element name="page-flow-ref" type="wp:pageFlowRefType"/>
      </xs:choice>
    </xs:sequence>
    <xs:attribute name="guid" type="xs:string" use="required"/>
    <xs:attribute name="name" type="xs:string" use="optional"/>
    <xs:attribute name="version" type="xs:string" use="optional"/>
  </xs:complexType>
</xs:element>

attribute Service-Archive-Descriptor/channels/channel/work-type/@guid
type xs:string
properties
use required
source <xs:attribute name="guid" type="xs:string" use="required"/>

attribute Service-Archive-Descriptor/channels/channel/work-type/@name
type xs:string
properties
use optional
source <xs:attribute name="name" type="xs:string" use="optional"/>

attribute Service-Archive-Descriptor/channels/channel/work-type/@version
type xs:string
properties
use optional
source <xs:attribute name="version" type="xs:string" use="optional"/>

element Service-Archive-Descriptor/channels/channel/work-type/extended-properties
diagram wp_diagrams/wp_p109.png
namespace http://service.archive.wp.n2.tibco.com
type wp:extendedPropertiesType
properties
minOcc 0
maxOcc 1
content complex
nillable true
children wp:property
annotation
documentation

It is a
provision
to add
custom
properties
to the
work
model
type
which
can be
interpreted
by the
Work
Presenation
Deployment
Analyser
source <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
  <xs:annotation>
    <xs:documentation>
It is a
provision
to add
custom
properties
to the
work
model
type
which
can be
interpreted
by the
Work
Presenation
Deployment
Analyser
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/work-type/form
diagram wp_diagrams/wp_p110.png
namespace http://service.archive.wp.n2.tibco.com
type wp:formType
properties
content complex
children wp:formIdentifier wp:relative-path wp:base-path
attributes
Name  Type  Use  Default  Fixed  Annotation
version  xs:string  optional      
documentation
Version number of the form artifact.
guid  xs:string  optional      
documentation
GUID of the form artifact.
name  xs:string  required      
documentation
Name of the form artifact.
annotation
documentation

Form
indicates
the
presentation
resource
that
needs
to
be
displayed
for
this
particular
work
type
request
source <xs:element name="form" type="wp:formType">
  <xs:annotation>
    <xs:documentation>
Form
indicates
the
presentation
resource
that
needs
to
be
displayed
for
this
particular
work
type
request
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/work-type/page-flow
diagram wp_diagrams/wp_p111.png
namespace http://service.archive.wp.n2.tibco.com
type wp:pageFlowType
properties
content complex
nillable false
children wp:page-activity
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:string  required      
documentation
ID of this pageflow.
name  xs:string  optional      
documentation
Name of this pageflow.
url  xs:string  required      
documentation
URL of this pageflow.
moduleName  xs:string  required      
documentation
Module name of this pageflow.
moduleVersion  xs:string  required      
documentation
Module version number of this pageflow.
source <xs:element name="page-flow" type="wp:pageFlowType" nillable="false"/>

element Service-Archive-Descriptor/channels/channel/work-type/extension-config
diagram wp_diagrams/wp_p112.png
namespace http://service.archive.wp.n2.tibco.com
type wp:channelExtentionType
properties
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
filename  xs:string  required      
documentation
The requested filename
location  xs:string  required      
documentation
The requested location
source <xs:element name="extension-config" type="wp:channelExtentionType"/>

element Service-Archive-Descriptor/channels/channel/work-type/page-flow-ref
diagram wp_diagrams/wp_p113.png
namespace http://service.archive.wp.n2.tibco.com
type wp:pageFlowRefType
properties
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
refId  xs:string  required      
source <xs:element name="page-flow-ref" type="wp:pageFlowRefType"/>

element Service-Archive-Descriptor/channels/channel/domain
diagram wp_diagrams/wp_p114.png
namespace http://service.archive.wp.n2.tibco.com
type xs:string
properties
minOcc 0
maxOcc 1
content simple
source <xs:element name="domain" type="xs:string" minOccurs="0"/>

element Service-Archive-Descriptor/channels/channel/extended-properties
diagram wp_diagrams/wp_p115.png
namespace http://service.archive.wp.n2.tibco.com
type wp:extendedPropertiesType
properties
minOcc 0
maxOcc 1
content complex
nillable true
children wp:property
annotation
documentation
It is a provision to add custom properties to the work model type which can be interpreted by the Work Presenation Deployment Analyser.
source <xs:element name="extended-properties" type="wp:extendedPropertiesType" nillable="true" minOccurs="0">
  <xs:annotation>
    <xs:documentation>It is a provision to add custom properties to the work model type which can be interpreted by the Work Presenation Deployment Analyser.
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/extension-config
diagram wp_diagrams/wp_p116.png
namespace http://service.archive.wp.n2.tibco.com
type wp:channelExtentionType
properties
minOcc 0
maxOcc 1
content complex
nillable true
attributes
Name  Type  Use  Default  Fixed  Annotation
filename  xs:string  required      
documentation
The requested filename
location  xs:string  required      
documentation
The requested location
annotation
documentation
Defines extended channel information, for example, Email Channel, or for a channel not yet implemented in WP.
source <xs:element name="extension-config" type="wp:channelExtentionType" nillable="true" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Defines extended channel information, for example, Email Channel, or for a channel not yet implemented in WP.
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/business-service
diagram wp_diagrams/wp_p117.png
namespace http://service.archive.wp.n2.tibco.com
type wp:businessServiceType
properties
minOcc 0
maxOcc unbounded
content complex
children wp:page-activity
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:string  required      
documentation
ID of this pageflow.
name  xs:string  optional      
documentation
Name of this pageflow.
url  xs:string  required      
documentation
URL of this pageflow.
moduleName  xs:string  required      
documentation
Module name of this pageflow.
moduleVersion  xs:string  required      
documentation
Module version number of this pageflow.
annotation
documentation
Defines pageflow business service form related resources.
source <xs:element name="business-service" type="wp:businessServiceType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Defines pageflow business service form related resources.
</xs:documentation>
  </xs:annotation>
</xs:element>

element Service-Archive-Descriptor/channels/channel/page-flow
diagram wp_diagrams/wp_p118.png
namespace http://service.archive.wp.n2.tibco.com
type wp:pageFlowType
properties
minOcc 0
maxOcc unbounded
content complex
children wp:page-activity
attributes
Name  Type  Use  Default  Fixed  Annotation
id  xs:string  required      
documentation
ID of this pageflow.
name  xs:string  optional      
documentation
Name of this pageflow.
url  xs:string  required      
documentation
URL of this pageflow.
moduleName  xs:string  required      
documentation
Module name of this pageflow.
moduleVersion  xs:string  required      
documentation
Module version number of this pageflow.
source <xs:element name="page-flow" type="wp:pageFlowType" minOccurs="0" maxOccurs="unbounded"/>

element Service-Archive-Descriptor/version
diagram wp_diagrams/wp_p119.png
namespace http://service.archive.wp.n2.tibco.com
properties
minOcc 0
maxOcc 1
source <xs:element name="version" minOccurs="0"/>


XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy