KB Version:

Page Navigation

Learning Levels

Most Read

Web Services Changelog

8.5

Stale Content Filtering

With the addition of the "Include in Stale Content report" property in the UI for excluding folders from the Stale Content Report, an includeInStaleContent property has also been added to the folder complexType in web services.

Metadata Field Help Text

Metadata help text fields are now available for read/edit via web services to match the UI.  Fields authorFieldHelpText, descriptionFieldHelpText, displayNameFieldHelpText, endDateFieldHelpText, expirationFolderFieldHelpText, keywordsFieldHelpText, reviewDateFieldHelpText, startDateFieldHelpText, summaryFieldHelpText, teaserFieldHelpText, and titleFieldHelpText have been added to the metadataSet complexType and field helpText has been added to the dynamicMetadataFieldDefinition complexType to facilitate reading/editing help text.

Scheduled Asset Review

Configuring scheduled asset reviews is now available via web services.  The reviewOnSchedule and reviewEvery properties have been added to the folder-contained-asset complexType which can be used to enable and configure the scheduling of reviews on home area assets.

8.3

WYSIWYG Configurations

Customizable WYSIWYG Configurations, added in Cascade 8.3, can be manipulated via web services operations like most other assets in the system.  The available fields are displayed below:

listEditorConfigurations operation has also been added which allows script writers to access all Wysiwyg Editor Configurations contained in a particular Site.

With the addition of WYSIWYG configurations, all WYSIWYG related properties on Groups and Sites have been removed.  Sites and Content Types have new properties defaultEditorConfigurationId/defaultEditorConfigurationPath and editorConfigurationId/editorConfigurationPath respectively, which allow editor configurations to be assigned to those asset types via web services.

New abilities accessEditorConfigurations and bypassWysiwygEditorRestrictions have been added to the sites-abilities complexType and the accessDefaultEditorConfiguration ability has been added to global-abilities to match new abilities available in the UI related to WYSIWYG configurations.

Global Area Cleanup and Other Misc Updates

In an effort to clean up remnants of the Global Area, most of the old Global Area abilities on Roles that are no longer applicable have been removed from the global-abilities complexType.

The defaultGroup property has also been removed from User objects as it has been removed from the system entirely.

The accessAudits ability has been added to the global-abilities complexType to match the UI.

8.1

Search Updates

The Web Services search API has been updated to mirror the new Advanced Search UI added in Cascade 8.0.  

It's now possible to filter search results by specific types, specific fields, and/or a specific site.  Search terms behave identically to how they behave in the UI.  Multi-word phrases can be searched for by surrounding the terms in double-qoutes.  Unquoted terms will be matched individually.  For example, "mouse rat" will exactly match the phrase "mouse rat", but mouse rat will match mouse or rat or both.

Note that single term searches in 8.1 will also include partial word matches.  So, searching for house will match milhouse and houseboat.  This did not happen in 8.0.x.

The "searchInformation" complexType has been changed to the following which more closely matches the new Advanced Search UI:

Notice the elements to specify a site by either id or name, the element to specify the types of assets to match, and the element to specify the fields to match.

The searchTypes element can be populated with any of the values that already exist in the entityTypeString simpleType.

The searchFields element can be populated with any values present in the newly added searchFieldString simpleType displayed below.

8.0

Asset Factory Descriptions

With the addition of the "description" field for Asset Factories and Asset Factory Containers in the UI, the WSDL has been updated to allow configuring that field via web services.

Goodbye Global!

With the removal of the Global Area from the system, all existing complexTypes containing a siteName and siteId now require that at least one of those fields be populated.  This includes all home area assets and site management components.  Note that this is not enforced in the WSDL but is enforced by the server whenever an edit or create operation is performed.

Ability Updates

The existing "accessAdminArea" global ability has been renamed to "accessManageSiteArea" and a new ability with the old name, "accessAdminArea", has been added which governs access to the new System Administration area and not the Manage Site area as the renamed ability does.

The New Site wizard and Site Migration wizard tools have been removed from the system and their corresponding global abilities in the WSDL, "newSiteWizard" and "siteMigration", have also been removed.

The Recycle Bin Checker and Path Repair database tools have also been removed from the system and their global abilities, "recycleBinChecker" and "pathRepairTool", have likewise been removed from the WSDL.

Search Updates

Search via the UI has been revamped; however, the WSDL has not yet been updated to be compatible with the new search functionality.  Searching via web services will be unpredictable at best and will outright fail at worst.  Stay tuned for search updates in a future release!

7.14.3

Fixed setting visiblity and requiredness of Expiration Folder on Metadata Sets

We fixed a bug that was preventing users from setting the expirationFolderFieldVisibility and expirationFolderFieldRequired properties on Metadata Sets.

7.14

Read System Preferences

In 7.14, it is possible to read system preferences. The result of the operation is a list of preferences--objects containing a preference key and its respective value. All possible preferences are returned though not all may have a set value.  System preferences are read using the "readPreferences" action.

Edit System Preference

Also new in 7.14, is the ability to edit a system preference. A preference object--a preference key and its value-- is supplied as a parameter to the "editPreference" action. It may be useful to run the "readPreferences" operation to obtain a list of possible preference keys to supply.

7.12.3

In 7.12.3, it is possible to enable external link checking on publish. This setting is available at a site level through "externalLinkCheckOnPublish" property:

7.12.2

Scheduled Destinations

In 7.12.2, it is possible to specify destinations on assets that can be published on a schedule.  These fields can also be set via web services.

Two new elements are now available on target, publish-set and site complextTypes. 

The "scheduledPublishDestinationMode" element specifies whether or not the scheduled asset will publish to all enabled destinations ("all-destinations") or only the destinations selected by the user ("selected-destinations") when published on a schedule.

The "scheduledPublishDestinations" element is of type "destination-list" and is used to supply a list of destinations to publish to when the "scheduledPublishDestinationMode" is set to "selected-destinations" and is required in that case.

The "contentTypePageConfigurationDestinations" complexType has been renamed to "destination-list" so that it can be used for both Content Type Destination mappings and scheduled publishing Destinations.

7.12.1

New page serialization types

CSI-806 in Cascade Server 7.12.1 added 3 new seraialization types -- JSON, JS, and CSS -- for outputs in configuration sets. These have been added to the Web Services layer for reading/updating Configuration Sets. Existing scripts will continue to funtion.

7.12

Updated Role properties

CSI-721 added the "databaseExport" Global ability and "sendStaleAssetNotifications" Global and Site ability that previously existed in the Role web interface.

The new Broken Link Report also added "brokenLinkReportMarkFixed" and "brokenLinkReportAccess" to both Global and Site roles.

Property "linkCheckerEnabled" in Sites

The property linkCheckerEnabled has been added to the site complex type that corresponds to the Scheduled Link Checker checkbox in the Site Management area of the Cascade UI.

Also, the unpublishOnExpiration was added to the site type to be consistent the options available within the interface

7.8

Linkable Asset Chooser

With the addition of the Linkable Asset Chooser, Data Definition fields being processed via web services can now use a new value, "page,file,symlink", for the assetType element of the structured-data-node complexType.  

When dealing with a stuctured-data-node using type "page,file,symlink", only one of the pageId/pagePath, fileId/filePath, symlinkId/symlinkPath fields should be populated.

7.4

Content Type Editing

Content Types are now configurable for in-context editing. As a result, you can now specify which fields should be in-context editable for a Content Type when editing through Web Services using the inlineEditableFields property.

The types for that property are defined as follows:

Stale Asset Notifications

A new ability has been added to both the Cascade UI and web services which determines whether or not a user can send stale asset notifications.  It is available as either a site ability or a global ability.

Global Abilities

Site Abilities

7.2

Publishing Changes

The unpublish property of publish operation is not required by WSDL; but prior to Cascade Server 7.2, an error would be returned if the property value was not provided making that property effectively required. In 7.2 this property is truly optional. Authenticating User needs to have read access to given asset in order to be able to perform this operation.

ListSubscribers Operation

A new operation has been added to Cascade Server web services that allows retrieving subscribers for a particular asset.  These are the same assets that appear when viewing the Subscribers tab in the web UI.  Subscribers are returned as a list of identifiers.

ListSites Operation

Another operation added in Cascade Server 7.2, listSites, allows retrieving identifiers of all Sites that the authenticating User can view. This corresponds to viewing the list of the Site assets in the Site Management area of the web UI, which can differ from the list of Sites the current User can switch to using the Site switching drop-down at the top of the web UI.

Folder Workflow Settings

Two operations have been added related to Workflow settings assigned at the Folder level: readWorkflowSettings and editWorkflowSettings. They correspond to viewing and updating the information in the Workflows tab of a Folder in the web UI. They allow reading and modifying assigned Workflow Definitions, reading and modifying Inherit Workflows and Require Workflow options and retrieving identifiers of inherited Workflow Definitions. When editing, it is possible to apply given settings to child folders the same way it is possible to do so in the web UI.

Choosing which Destinations to publish to/unpublish from

As of Cascade Server 7.2 it is possible to provide which specific Destinations a given asset should be published to or unpublished from using the publish operation. Providing a blank list will publish to all Destinations that the authenticating User can publish to. Prior to 7.2 the asset was being published to all enabled Destinations, even the ones the authenticating User could not publish to.

The property maintainAbsoluteLinks has been added to page complex type that corresponds to Maintain absolute links when publishing checkbox in the web UI. This property was missing prior to 7.2 and editing a Page using web services with that checkbox already checked was resulting in it getting unchecked.

Scheduled Publishing Improvements

It's now possible to specify which users/groups should receive publish reports for scheduled publishes.  The following elements have been added to the destination, publishSet, site, and target complex types:

Likewise for these complex types, a new element is available which allows scripts to specify if publish reports should only be sent when there's an error in the publish.

Dynamic Metadata Changes

In 7.2 it's no longer necessary to provide XML for dynamic metadata field definitions both through the Cascade UI as well as through the web services API.  New elements have been added to represent dynamic metadata fields and their values when creating/editing Metadata Sets.  

The configurationXML field has been removed from the dynamicMetadataFieldDefinition complex type in favor of a collection of dynamic-metadata-field-definition-values.

Using these new elements, scripts can specify each individual value for a dynamic metadata field and whether or not that value should be selected by default.

New Field Type

Additionally, a new dynamic field type has been added to match the Cascade User Interface.  The value multiselect can now be submitted for the fieldType element on the dynamicMetadataFieldDefinition complex type.  Multiselect fields used to be represented using the dropdown field type where the attribute multiple="true" would be submitted in the field definition XML.  This is no longer the case.

7.0

Twitter Feed Block Changes

A new block complex type has been added to represent Twitter Feed Blocks.

Another new complex type has been added to represent the different possible query types of the Twitter Feed Block.

A "block_TWITTER_FEED" entry has likewise been added to the "entityTypeString" enumeration.

Site Copy Changes

A new action complex type has been added to represent Site Copies. An identical complex type was added to the "workflow-configuration" complex type.

Another complex type has been added to represent the site Copy result.

A new element was added to the "operation" complex type to represent site copies.

Publish Changes

A new "Unpublish" option has been added to the "Publish" type.  This is similar to the checkbox on the GUI publish screen: setting it to true means that an unpublish will be performed instead of a publish.

An identical "Unpublish" option has been added to the "Publish" type for "workflow-configuration".

Search Changes

Several new elements were added to the "searchInformation" complexType that represent options to include the new Admin area assets that were added to the search index.

Global Abilities Changes

A new element was added to the globalAbilities complex type to represent the ability to use the Database Export Tool.

6.10.8

Missing Abilities

A number of Role abilities available in the Cascade UI were not available via web services.  These abilities have been added to the WSDL.

Global Role Abilities

Site Role Abilities

Index Block Settings

The structure of Index Block properties in web services now corresponds more closely to the structure represented in the web UI. There is a new renderingBehavior property that contains the 4 choices that correspond to the web UI choices:

  • Render normally, starting at the indexed folder
  • Start at the current page and include its folder hierarchy
  • Start at the current page with folder hierarchy, and also include siblings
  • Start at the current page with folder hierarchy, siblings, and also render forward

Similarly, there is now a pageXML property that contains the 3 choices that correspond to the web UI choices:

  • Do not render page XML inline
  • Render page XML inline
  • Render page XML inline only for current page

As a result, the following properties have been removed:

  • includePageContent
  • includeCurrentPageXML
  • renderCurrentPageAndHierarchy
  • includeChildrenInHierarchy

6.10.2

Asset Factory assetType

Previously, when creating a Format Asset Factory the correct value for the "assetType" field was "xSLTFormat."  As of 6.10.2, "format" is the correct value.

6.10

Facebook Connector Changes

A new connector super-type has been added that acts as the parent type for the new Facebook Connector and for the existing Twitter Connector.  It's called a "statusUpdateConnector" and is declared as the following:

Another new connector complex type has been added to represent Facebook Connectors.

A "facebookconnector" entry has likewise been added to the "entityTypeString" enumeration.

Destination Web URLs

A new field has been added to the "destination" complex type called "webUrl" which is equivalent to the field now available in the UI.

6.8.3

Addition of Created By/Created On Fields

The created by and created on fields for Home Area Assets can now be accessed via web services. Their element declarations are found below.

6.8

Simpler editing of read assets

When reading an asset, Cascade returns both ids and paths (or names for assets that do not have paths) of both the read asset and any referenced assets. Prior to 6.8, a user had to manually null out one of these two values in addition to their other modifications before submitting the page for edit. As of Cascade 6.8, all asset relationship elements which include id and path elements can now contain both values when submitted for edit. If both fields are present, the id will be used in favor of the path to locate the asset or any referenced asset.

Java Example

Here's Java code to update the Page's title prior to 6.8:

Here's the same operation in 6.8:

Google Analytics Connector

In Cascade 6.8, a new type of Connector has been introduced: Google Analytics Connector.

Creation and editing of that Connector is identical to the other ones with a small difference:  connectorContentTypeLinks are not requred. This is because Google Analytics Connector does not use Connector Content Type Links. However, when creating or editing a Twitter Connector or a WordPress Connector, they still need to be provided.

Asset scheduled publishing - new properties

Sites, Publish Sets, Destinations and Targets have updated scheduled publishing properties. The type of scheduled publishing (every day, each selected day of a week, every n hours, Cron expression) is dependent on which one of the following fields is not null:

  • publishIntervalHours - for every n hours publish, provide the amount of hours for the interval
  • publishDaysOfWeek - uses the complexType daysOfWeek. Provide one or more values from the enumeration daysOfWeek indicating which days the asset should be published.
  • cronExpression - for Cron expression publish, provide the cron expression in a string form, timeToPublish field is ignored in this case

Content Type Page Configuration-Destinations

As of 6.8, Content Types in Sites can have Destinations assigned for each Configuration coming from the Content Type's Configuration Set. These can be assigned through web services using contentTypePageConfigurations element.

Each contentTypePageConfigurations element contains a list of contentTypePageConfiguration elements.

Each contentTypePageConfiguration element should correspond to each Configuration Set's Configuration and is referenced by pageConfigurationId and pageConfigurationName elements. Only one of these elements is necessary. If the contentTypePageConfiguration element is not provided for a particular Configuration, Cascade Server will assign the default value to it - "All Destinations".

Also, contentTypePageConfiguration elements contain a required publishMode simple type. The available publish modes correspond to the ones provided in the user interface:

  • all-destinations - "All Destinations" option
  • selected-destinations - "Selected Destinations" option
  • do-not-publish - "Do not publish" option

If the publishMode is selected-destinations, a list of destination identifiers is required.

6.7.5

Workflow Configuration End Date

Workflow end dates can now be set when issuing create, edit, copy, move, or delete requests with a workflow configuration.  Below is the new element that has been added to the workflow-configuration complex type.

Workflow Start Date and End Date

The Workflow object returned through "readWorkflowInformation" operation now contains two additional properties: startDate and endDate. Below are the new elements that have been added to the workflow complex type.

Database Transports

The data type of the transportSiteId element of the databaseTransport complex type has been changed from positiveInteger to nonNegativeInteger to allow use of transport site id '0'.  This ensures parity between the valid site id values that can be submitted through the UI and through web services operations.

Workflow Step Configuration

The "move" element has been removed from the workflowAction complex type as it is no longer used in workflow.

6.7.3

Applicable Groups for Workflow Definitions, Asset Factories, Asset Factory Containers, and Destinations

As of 6.7.3, the "applicableGroups" property is not required and non-nillable for Workflow DefinitionsAsset Factories, Asset Factory Containers, and Destinations and should contain a semicolon delimited list of group names.

Previously, "applicable groups" assigned were being read as a comma-separated list of group names. However, they were being stored as semicolon-separated so if you attempted to edit using commas it would actually clear out the "applicable groups" property when the asset was viewed in the application.

New Sub-types for Transports

The entityTypeString simple type has been updated so that it contains more specific Transport types, which is consistent with other asset types that have sub-types (e.g. Blocks can be block_INDEX, block_XML, etc.).  The new entityTypeStrings are displayed below.

6.7

Recycle Bin

With the addition of the Recycle Bin, it was necessary to add new elements in various places where recycle entities are being referenced.  These new elements will indicate whether or not an assignment made on an asset is referring to a recycled asset.  This element was added mainly so that users can tell when a relationship refers to a recycled entity.  Setting these elements to true will NOT recycle an asset that has not been recycled yet.  These elements are ignored when creating/editing assets.

Here are a few examples:

Template's Format

Group's Starting Page

Page Region's Block

Purge Interval

The Recycle Bin comes equipped with a automatic purge feature which will remove items from the Recycle Bin (and from the system completely) after a specified amount of time.  This configuration property is applicable for each Site and has therefore been added to the 'site' complex type so that it can be modified via web services.

Values which are valid for this property are displayed below.  The unit of measure is 'days'.

 

XHTML/Data Definition Blocks

In 6.7, XHTML Blocks have been upgraded to XHTML/Data Definition Blocks and therefore required some changes in the WSDL.  First, you will notice that the name of the complex type for these Blocks has been changed to "xhtmlDataDefinitionBlock" from "xhtmlBlock".  This complex type also now contains a new element, "structuredData", which is used to specify a Data Definition and the structured data itself (exactly like Page editing).  Either the "xhtml" element or the "structuredData" element should be filled out, but not both.

Here is the new entity type string declaration for XHTML/Data Definition Blocks:

In addition to the changes mentioned above, the term "structured data definition" has been replaced by "data definition" across the board (not just in the WSDL but also in the Cascade UI).  Elements referring to Data Definition no longer contain the prefix "structured".  Below are a few examples.

Entity type strings for Data Definition and Data Definition Container

The "dataDefinition" and "dataDefinitionContainer" complex types, formerly known as "structuredDataDefinition" and "structuredDataDefinitionContainer".

Move Operation

Moving/renaming assets is now its own operation within the Cascade UI.  This change has also been made in the Web Services layer.  There now exists a "move" operation that must be used in order to move or rename an asset.  The elements of the move operation are vary similar to a copy operation.  Relevant complex types are displayed below.

The "move" operation and parameters:

New Audit Types

A few new audit types have been added that correspond to new features mentioned above.  These audits types are:

Ability Updates

A number of abilities have been added and updated as a part of 6.7.  They are listed below and separated into Global and Site abilities.

Global Abilities

Site Abilities

Additional Changes

A few miscellaneous items have been updated to maintain parity between properties available for editing in the Cascade UI and via Web Services.

The first is the default Site property on the "user" complex type.  As in the Ui, this is used to specify a Site into which a User is placed upon logging into Cascade.

The remaining fields are contained in the "file" complex type.  They are "rewriteLinks" and "maintainAbsoluteLinks" which dictate how links are managed inside File assets.

6.4

Connectors

Available in 6.4 is the ability to manipulate Connectors and their containers via web services.  Three new values have been added to the entityTypeString simple type to use when reading a Connector or a Connector's container.  Three new elements have also been added to the asset complex type which enables creation and editing of Connectors and Connector Containers.

Creating and editing Connectors is accomplished by using a number of new complex types.  The three main complex types are displayed below.  Notice there is a connector complex type which is extended by the wordpressConnector and twitterConnector complex types.

Each Connector must have at least one Content Type assignment.  Content Type assignments are declared by using the connectorContentTypeLinks element available on the connector complex type.  The connectorContentTypeLinks element is of type connector-content-type-link-list which is another complex type which can contain any number of connector-content-type-link's.  Each connector-content-type-link represents a single Content Type assignment for a particular Connector.

For some Connectors, Connector Content Type assignments have additional parameters specific for each Content Type assignment which can be manipulated using the connectorContentTypeLinkParams element available on each assignment.  Each parameter simply has a name and a value.

Connectors can also have additional parameters that are not specific to a particular Content Type link.  These parameters are supplied via the connectorParameters element available in the connector complex type.  The connectorParameters element is of type connector-parameter-list and contains any number of connector-parameter objects.

Manipulating Connector Containers is accomplished using the connectorContainer complex type which behaves the same as most other system area container types.  The main difference is that all Connector Containers must belong to a Site.

The root Connector container id for a particular Site can be acquired by reading the Site and accessing the rootConnectorContainerId element now available on the site complex type. 

Abilities

Access to the Connectors area within a Site can be granted via web services using a new Site level ability which has been added to the WSDL.  It has been added to the site-abilities complex type and is shown below.

A new global ability has been added to Cascade which governs a user's access to Broadcast Messaging.  This ability can now be enabled via web services using the element below which has been added to the global-abilities complex type.

6.2

Specifying Cross-Site Relationships

Now available in Cascade 6.2 is the ability to populate cross-site asset relationships via Web Services.  For example, the Metadata Set field present on many Home Area assets can now be specified by path using the cross-site relationship format displayed below.  Note that populating these relationships by id does not require a special format.

This cross-site relationship format is also used in the Cascade UI when selecting assets using asset choosers.  Notice that this format is different from the format used when creating links between assets in the home area via content areas; this helps to distinguish the difference between a content link and an asset relationship.

To reference assets residing in the Global Area, simply use "Global" as the site name; to reference an asset contained in the same site as the asset being edited/created, simply omit the site name and ':' and only supply the path to the asset.

6.0.3

Site Destination Containers

Because Sites do not employ Targets, it was necessary to create a new type of container in 6.0 called a Site Destination Container.  The web services API has been updated in Cascade 6.0.3 to allow users to manipulate these new containers.  Below is the siteDestinationContainer complex type declaration.

As a result of there being two types of containers for Destinations, the parentTargetId and parentTargetPath elements of the destination complex type have been renamed to parentContainerId and parentContainerPath, respectively.

6.0.1

Sites

A number of new fields have been added to sites in 6.0.1 and are listed below.  These fields correspond to relationships that are now available in the UI.

Asset Factories

Asset factory plugins can now be preserved when editing an Asset Factory via web services.  A new field has been added to the assetFactory complex type, called plugins, which will contain any Asset Factory plugins that have been assigned to the Asset Factory via the Cascade GUI.  Along with this field are a number of supporting complex types that represent dependent plugin properties.

6.0

Sites

With the addition of Sites, the web services API has been augmented to allow for the manipulation of assets that live either inside a Site or in the Global Area.  The path element in an asset identifier has been converted into a complex type that must contain a string representing the path of the asset as well as either the site id or site name of the Site to which the asset belongs.  If both the site id and site name fields are left empty, then the asset is assumed to exist in the Global Area.

When editing or creating an asset via web services, it is possible to specify the site to which the asset should belong by populating the site id or site name.  A siteId and siteName element have been added to the folder-contained-asset complex type as well as the containered-asset to allow for this.

Site assets themselves can also be manipulated via web services.  A site complex type has been added and is displayed below along with two supporting complex types: role-assignments and role-assignment.  The two supporting complex types allow for the assigning of Roles and Users to a particular Site similar to how they would be assigned through the UI.

Roles

Role manipulation has also been added to the web services API in Cascade 6.0.  Below is the role complex type which is used to create and edit Roles.  Each Role requires a role type.  Notice the simpleType role-types which declares the two valid values for the roleType element: site or global

Site Roles can only be assigned to Sites; while Global Roles are only assigned to Users and Groups.

The Abilities available to a particular Role will differ depending on the type of Role.  The two sets of abilities overlap but have been split into two distinct complex types: global-abilities and site-abilities.  Notice that the role" complex type requires either a set of global abilities or a set of site abilities.

Page Configurations

A number of new fields have been added to the pageConfiguration complex type in order to support the manipulation of Configuration Sets that reside in a Site.  These fields are displayed below.  When editing a global Configuration Set, these new fields will be ignored because they do not apply.  When editing a Configuration Set that lives in a Site, these fields will be used.

Templates

To allow for Templates to be created or edited in a Site, the target element of the template complex type is no longer required.

5.7

Index Block Updates

  • The complex type indexBlock has a new optional field, indexBlockType, that refers to a simple type index-block-type.  This field can be set to either folder or content-type. The default value is folder:

  • The complex type indexBlock now also has two additional fields allowing the User to provide either a Content Type id or Content Type path:

  • The name of the simple type index-block-sort-order that is being used by sortMethod in the complex type indexBlock has been renamed to index-block-sort-method

  • The complex type indexBlock has a new optional field sortOrder that refers to a simple type index-block-sort-order that can be either ascending or descending. The default value is ascending:

XSLT and Script Format Updates

  • The complex type stylesheet has been renamed to xsltFormat.
  • A new complex type scriptFormat with the following schema has been added:

  • The stylesheetId and stylesheetPath fields of the template, pageConfiguration, and pageRegion complex types have been renamed to formatId and formatPath, respectively.
  • The complex type asset has had two fields, xsltFormat and scriptFormat, added and the stylesheet field has been removed.

  • The stylesheet field has been removed from the asset and asset-read complex types.

Transport and Transport Container Updates

  • A new complex type has been added, transportContainer, which allows Transport Containers to be manipulated via web services.

  • The ftpTransport and fileSystemTransport complex types have been modified so that they extend the containered-asset complex type.  This allows for Transports to be created/edited with a specified container.
  • 4 new values have been added to the entityTypeString simple type: format_XSLT, format_SCRIPT, format, and transportcontainer.  The value stylesheet has been removed.