Release Notes for Studio Server 10 – Home

The Release Notes for Studio Server 10 contain information about the new features, changes, fixed issues, known issues, and upgrade instructions for each release of Studio Server 10.

The versions are sorted by version number in descending order. Use the Navigation block to the right of the page to quickly navigate to the information of a released version, or filter the article by version to only show that version.

Filter by version:

Studio Server 10.20.0

Studio Server version 10.20.0 build 404

Release date: 17 November 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

Stored user settings can now be reset for Studio users who cannot log in anymore because of corrupted settings. Users of Smart Connection, Studio, and Studio for InDesign and InCopy can store settings for search filters, panels, column settings, and more. In some cases, these settings can get corrupted which prevents Studio users from logging in to Studio.

This can now be resolved by resetting these settings to their default state by clicking Reset Stored Settings on the User Maintenance page of the user in Studio Server.

For details, see Managing user accounts in Studio Server. Note that this also resets the settings for the users of Studio for InDesign and InCopy, and users of Smart Connection.

When logging server activity, the full stack of calling functions can now also logged. When an alert is logged, by default only the error message itself is logged. Now, the full stack of calling functions can also be logged, thereby providing much more information about the cause of the error.

This can be done by configuring the following option:

Option: LOG_STACK_ON_ALERT
File: configserver.php file (recommended: config_overrule.php file)
Possible value:
null. Default value. Stacks are included in the log file on alerts when the applied log level is set to DEBUG.
true. Stacks are included in the log file on alerts, regardless of the applied log level.
false. Stacks are never included in the log file.
Default value: null
Example:

define( 'LOG_STACK_ON_ALERT', null );

For full details, see Logging server activity in Studio Server 10.14 or higher – Configuration.

Server methods have been removed or marked as deprecated as part of improving Studio Server performance. To improve performance, the following BizClasses methods have been removed or marked as deprecated:

Method

Details

\WW_DbClasses_Wfl_Query_QueryObjectComposer::
filterOnAuthorization()

Removed.

This method was deprecated since Studio Server 10.16.0.

\WW_DbClasses_Wfl_Query_QueryObjectComposer::
filterOnAuthorizationAndBrandsId()

Deprecated.

This method will be removed in a future version.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.20 - new
Managing user accounts in Studio Server - updated
Logging in to Studio - updated
Logging server activity in Studio Server 10.14 or higher – Configuration - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12242 MySQL - Database Upgrade script fails for database names with a dash.

WSS-12987 Make it possible to reset user preferences to resolve issues with corrupted user settings.

WSS-13070 Performance: Improve execution time of filtered searches without losing performance on searches that are not filtered.

WSS-13105 Add a configuration option for logging stacks.

Installation

Choose one of the following installation paths:

Studio Server 10.19.0 build 401 Quick Patch

Studio Server version 10.19.0 build 401

Release date: 1 November 2022

Downloads

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-13153 Performance: Improve execution time of filtered searches without losing performance on searches that are not filtered.

Note: This performance degradation was observed when upgrading to Studio Server 10.16 or later. The level of degradation depended on several factors and could cause severe performance issues in some environments.

Installation

Choose one of the following installation paths:

Studio Server 10.19.0

Studio Server version 10.19.0 build 399

Release date: 20 October 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

The maximum number of characters of the 'Description' property of a file has been raised to 10,000. The maximum number of characters that can be stored in the 'Description' property of a file has been raised from 2,040 to 10,000 characters. This brings it in line with the number or characters that the same property in Assets Server can hold.

Assets Server integration: The 'Page' property now stores the 'page order' value of the page on which a file is placed instead of the 'page number' value. When placing a file from the Production Zone in Assets Server onto a layout, the 'page order' value is now stored in the Page property. In previous versions, the 'page number' value was stored.

Notes for upgraded systems with an Assets Server integration:

Shadow objects that were created before the upgrade to Studio Server 10.19.0 retain their current value (the page number). These shadow objects are only updated with the page order value when the layout on which they are placed is re-opened and re-saved.

Objects that were archived before the upgrade to Studio Server 10.19.0 retain their current value (the page number). Objects that are archived after the upgrade to Studio Server 10.19.0 will have the page order value stored.

Archiving to Assets Server: During archiving, the 'Page range' property is now populated for all articles, images, spreadsheets, and adverts that are placed on a layout. When archiving a layout and its placed objects, all articles, images, spreadsheets, and adverts that are placed on a layout now have the 'Page range' property populated. In previous versions, this property was only populated for the layout and its PDF or EPS files. The value used is the 'Page (order)' value of the page on which the object is placed.

Note for upgraded systems with an Assets Server integration: The page range value for objects that were archived before the upgrade to Studio Server 10.19.0 remains empty. Only objects that are archived using Studio Server 10.19.0 or higher will have this property populated.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.19 - new
Metadata mapping between Studio Server and Assets Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-11752 When placing an article component on a layout on which it is already placed, no warning is given when the layout only contains one Edition.

WSS-11955 Preview optimizations: Reduce the requestInfo call for a login request in the IDPreview.jsx file.

WSS-12954 Unable to deactivate an SSO-user.

WSS-12984 Performance: Too many SQL statements are called to retrieve Workflow Statuses.

WSS-12986 Performance: Too many SQL statements are called for save layout operations to resolve duplicate placements.

WSS-13011 Performance: Too many SQL statements are called for save layout operation to determine placed relations to be deleted.

WSS-13044 Extend the 'Description' field of a file to 10,000 characters.

Installation

Choose one of the following installation paths:

Studio Server 10.18.0

Studio Server version 10.18.0 build 398

Release date: 8 September 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

Centralized logging: The fields structure now only supports the ECS standard. With the introduction of centralized logging in Studio Server 10.14.0, the structure for the ECS fields was unfortunately not respecting the ECS standard and therefore implemented incorrectly.

As a result, the field names were logged in a flat concatenated structure instead of a hierarchical structure as defined by the ECS standard.

Support for the new ECS field structure was then added to Studio Server 10.14.1, together with the LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS option which made it possible to temporarily use the old/incorrect structure and to update the 3rd-party logging monitoring system to the new structure at a later point.

Now, only the new ECS field structure is supported. The LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS option has therefore been removed.

When upgrading from a previous version in which this option is still set in the config_overrule.php file or configserver.php file, the 'PHP' Health Check test will give a warning. In case the 3rd-party logging monitoring system is not adjusted to the new field structure, note that the monitoring system will not work; the logs will not appear as expected.

Updated database definition for improved performance. When upgrading from a previous version of Studio Server, the database definition is updated. This change is required to improve the performance of Studio Server. The 'Database' test on the Health Check page will show a notification that the update has been implemented; no action is required.

Server methods/functions: Improvement in performance by removing and/or replacing Inefficient BizClasses methods. To improve performance, the following BizClasses methods have been removed and where possible replaced by methods that are more efficient and require less database access:

Deprecated method	New method
WW_BizClasses_Wfl_Publication::getSectionInfos()	None.
WW_BizClasses_Wfl_Publication::getAuthorizedStates()	WW_BizClasses_Wfl_Publication::getAuthorizedStatesByBrandsId()
\WW_BizClasses_Wfl_Publication::getStateInfos()	WW_BizClasses_Wfl_Publication::getStateInfosForBrandsId()
\WW_BizClasses_Wfl_Publication::getCategoryInfos	WW_BizClasses_Wfl_Publication::getCategoryInfosByUserRights()
\authorizationmodule::getRightsCached()	None.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.18 - new

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12687 Performance: Opening the 'Inbox' and the 'Checked-out files' pages in Studio is very slow.

WSS-12702 Performance: Drop-down lists in the Create dialog take a long time to populate.

WSS-12887 Security: Update the guzzlehttp/guzzle package.

WSS-12982 Performance: 32 SQL statements are called for Create and Save operations to validate the Status and Category.

WSS-12992 An object can be created in a Workflow Status that is configured for a different object type in the same Brand.

WSS-12997 Migration script is failing because some fields in old databases are using Full User Name instead of the Short User Name.

WSS-13016 Performance: improve the LogOn Service - getPublicationInfos process.

Installation

Choose one of the following installation paths:

Studio Server 10.17.0

Studio Server version 10.17.0 build 396

Release date: 11 August 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

Support for Solr 7 has been dropped. Support for Solr 7.7 has been dropped in Studio Server 10.17; this version of Solr has reached its end of life some time ago. Supported versions of Solr for Studio Server 10.17 are 8.8 and 8.11. Solr indexes any file in the system for quick access whenever a search is performed.

Validation added for users with duplicate e-mail addresses. In Studio Server, users are identified by using the values of their name, full name, and e-mail address. When multiple users exist in the system with the same e-mail address, the user settings can become corrupted (especially when used in combination with Single Sign-On or LDAP). The e-mail address of each user in the system should therefore be unique. To prevent user accounts from becoming corrupted because of duplicate e-mail addresses, the following is now done:
When adding an email-address that is already used by another user to a new or existing user, a message is shown to indicate this.
The 'Authentication' test on the Health Check page now provides a warning when multiple users with the same e-mail address are detected.

RabbitMQ repair operations are now mentioned in the Health Check test. When a repair operation for RabbitMQ was required in previous versions of Studio Server (such as when creating a missing RabbitMQ virtual host), the operation was performed but no notification was given. Now, when such an action is performed, a notification is given as part of the 'Messaging (RabbitMQ)' test.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.17 - new
Managing user accounts in Studio Server - updated
Integrating LDAP in Studio Server - updated
Implementing single sign-on in Studio Server using Amazon Cognito - updated
Implementing single sign-on in Studio Server using Okta - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12888 Health Check: Multi-byte test fails to connect to RabbitMQ when running it the first time.

WSS-12289 LDAP Users with same email-address get corrupted.

Installation

Choose one of the following installation paths:

Studio Server 10.16.0

Studio Server version 10.16.0 build 394

Release date: 19 July 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been added in this release of Studio Server:

Support for Solr 8.11. Studio Server 10.16.0 now also supports Solr 8.11. Solr indexes any file in the system for quick access whenever a search is performed.

Changes

The following changes have been made in this release of Studio Server:

Assets Server integration: deleted users are recreated when restoring a file. When restoring an archived file from Assets Server to Studio Server, any users associated with the file that were removed from Studio Server are recreated as deactivated users. This is because users that are part of the workflow (for example as the user who created, modified, or deleted the file) have to exist as a user in the system. Deactivated users are hidden by default on the Overview of Users Maintenance page, but can be shown again by clicking 'Show Deactivated Users' at the bottom of the page.

Assets Server integration: Database change related to removed users when restoring files on Studio Server 10.15. Since Studio Server 10.15, users or user groups that are still part of the workflow (for example as the user who created, modified, or deleted the file) cannot be deleted anymore. When upgrading from Studio Server versions older than Studio Server 10.15, objects could exist that had a user associated with it that no longer existed in the system. The upgrade process of Studio Server 10.15 therefore restored all removed users that were still part of the workflow. However, when restoring an archived file from Assets Server to Studio Server 10.15, such a process was not in place and therefore still resulted in a file with an associated user that did not exist in the system.

When upgrading from Studio Server 10.15 to 10.16, a check is done for removed users and corrected when found. This check is performed by the 'Database Connection' Health Check test which will direct you to the Database Setup page on which the update can be run.

Note: The update needs to be run on each Studio Server 10.15 system that is upgraded, even when no files have been restored or Assets Server is not integrated.

During this process, all removed users and user groups that are still part of the workflow are recreated as deactivated users (note that user groups are also recreated as users). As mentioned above, deactivated users are hidden by default on the Overview of Users Maintenance page, but can be shown again by clicking 'Show Deactivated Users' at the bottom of the page.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Known issues

The following issues exist for this release of Studio Server:

Upgrading from Studio Server version 10.13 or lower fails. When upgrading from Studio Server version 10.13 or lower, the upgrade fails with the following error:

Database upgrade failed

The log files will show the following error:

ERROR    mysql           MySQL: 1054:Unknown column 'loglevel' in 'field list'
WARN     BizException    Message: Error: Failed to insert the user in the database.

These errors are caused by an upgrade script that recreates non-existing users; it expects specific database fields which are not yet present at that time.

To resolve this, do one of the following:

First upgrade to Studio Server 10.14.x and then to version 10.16.0.

Update the following script:

<your server>/server/dbscripts/dbupgrades/RecreateMissingWorkflowUsers.class.php

by changing the beforeUpdateModel method to return false. The method can be found on line number 58; the end result looks as follows:

public function beforeUpdateModel(): bool
{
	return false;
}

Archiving from Studio Server to Assets Server: When archiving a Digital article, the following fields are populated but cannot yet be shown in the Metadata panel in Assets:
Character count
Line count
Paragraph count

This requires an update in Assets Server and will be available in a future release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-12802 Slow search performance when the user has no Brand or type selected.

Installation

Choose one of the following installation paths:

Studio Server 10.15.0

Studio Server version 10.15.0 build 391

Release date: 21 June 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been added in this release of Studio Server:

Support for RabbitMQ 3.9. Studio Server 10.15.0 now also supports RabbitMQ 3.9.

(With RabbitMQ integrated in Studio Server, message notifications — such as when a user updates the properties of a file — can be pushed to client views of all users who are connected to Studio Server. This ensures that users immediately see the changes that other users make.)

Deactivated users can now be hidden. Should the list of users on the Overview of Users Maintenance page contain deactivated users, these deactivated users can now be hidden or shown using the 'Hide Deactivated Users' and 'Show Deactivated Users' options at the bottom of the page.

Note: Deactivated users are hidden by default.

Additional metadata fields are now populated when archiving from Studio Server to Assets Server. When archiving files from Studio Server to Assets Server, various metadata fields are populated with information that describes how and where the file was used in Studio Server. Many fields were already populated, but the following Assets Server fields are now included as well:
copyright
credit
edition
issueIdentifier
issueName
numberOfCharacters
numberOfLines
numberOfParagraphs
pageRange
publicationChannel
publicationName
section
wordCount

If and when a field is populated depends on the archive schema that is used (digital, Dossier, or print schema) and the type of file. For more information, see Metadata mapping between Studio Server and Assets Server.

Changes

The following changes have been made in this release of Studio Server:

Codes used in the ticket tracking system have been changed from 'EN' to 'WSS'. Historically, tickets for tracking bugs and improvements for the server started with 'EN-' (short for 'Enterprise'). With the renaming of the product to Studio Server some time ago, 'EN-' has now been changed to 'WSS-' (short for WoodWing Studio Server).

All tickets related to Studio Server will therefore now start with 'WSS-'. In addition, all existing tickets that started with 'EN-' have also been changed to 'WSS-'. For this, new tickets had to be created. This also means that the original number has changed (for example: 'EN-12345' could now be 'WSS-67890').

Note: Apart from the change in the codes, the rest of the ticket handling process has not changed. If you have submitted an 'EN' ticket which has now been renamed to 'WSS' and renumbered, you will of course still receive notifications for that ticket.

Users and user groups that are still associated with an object can no longer be deleted. When a user or user group is still associated with a workflow object in Studio Server, it can no longer be deleted. These associations are:
Users who are listed as the person who has created, modified, or deleted an object.
Users who have locked an object.
Users or user groups who have objects routed to them.

When trying to delete such a user or user group, a message is now shown. To resolve the issue, the user should be deactivated, or the objects should be removed from being routed to the user group.

For more information, see:

Database change related to removed users that are still part of the workflow. Studio Server 10.15 and higher prevents deleting users or user groups that are still part of the workflow (see above). For existing systems that have been upgraded, objects can exist that have a user or user group associated with it that no longer exists in the system. To prevent issues that this can cause in the system and as a first step to future optimizations, the database needs to be updated.

This is done as part of the upgrade process by running the Health Check tests. The 'Database Connection' test will now fail and direct you to the Database Setup page on which the update can be run.

Removal of obsolete Solr facet settings from the code. In Content Station, Solr facets were used for grouping search results. With the discontinuation of Content Station some time ago, the Solr facet settings listed below that were still present in the code have now been removed.

Note: The ‘Solr Search Server’ Health Check will give a warning if any of these settings are still used.

SOLR_ARTICLE_FACETS
SOLR_AUDIO_FACETS
SOLR_DOSSIERITEMS_FACETS
SOLR_GENERAL_FACETS
SOLR_IMAGE_FACETS
SOLR_INTEGER_RANGE
SOLR_LAYOUT_FACETS
SOLR_LENGTHCHARS_RANGE
SOLR_LENGTHLINES_RANGE
SOLR_LENGTHWORDS_RANGE
SOLR_RATING_RANGE
SOLR_SPREADSHEET_FACETS
SOLR_VIDEO_FACETS

Upgrade of JavaScript libraries. The following JavaScript libraries have been upgraded to make use of the security and performance improvements that these versions provide:

Library	Upgraded to version
jQuery	3.60
jQuery-UI	1.13.1
jsTree	3.3.12

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.15 - new
Managing user accounts in Studio Server - updated
Managing user groups in Studio Server - updated
Metadata mapping between Studio Server and Assets Server - updated

Known issues

The following issues exist for this release of Studio Server:

Upgrading from Studio Server version 10.13 or lower fails. When upgrading from Studio Server version 10.13 or lower, the upgrade fails with the following error:

Database upgrade failed

The log files will show the following error:

ERROR    mysql           MySQL: 1054:Unknown column 'loglevel' in 'field list'
WARN     BizException    Message: Error: Failed to insert the user in the database.

These errors are caused by an upgrade script that recreates non-existing users; it expects specific database fields which are not yet present at that time.

To resolve this, do one of the following:

First upgrade to Studio Server 10.14.x and then to version 10.15.0.

Update the following script:

<your server>/server/dbscripts/dbupgrades/RecreateMissingWorkflowUsers.class.php

by changing the beforeUpdateModel method to return false. The method can be found on line number 58; the end result looks as follows:

public function beforeUpdateModel(): bool
{
	return false;
}

Archiving from Studio Server to Assets Server: When archiving a Digital article, the following fields are populated but cannot yet be shown in the Metadata panel in Assets:
Character count
Line count
Paragraph count

This requires an update in Assets Server and will be available in a future release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

WSS-11549 Upgrade jQueryUI 1.12.1 to 1.13.1.

WSS-11550 Upgrade to jQuery 3.5.1 / jsTree 3.3.10.

WSS-11931 InDesign Server jobs fail when a user that has last modified the layout has been deleted.

WSS-12311 When copying a Brand and leaving the Brand name empty, nothing happens when clicking Copy to create the Brand.

WSS-12674 After a database upgrade and with DEBUG enabled, users are unable to log in (Uncaught throwable "TypeError").

WSS-12686 Having a large number of Brands configured impacts authorization checks made by workflow services.

WSS-12700 Studio Server integration: Some fields under the 'Publication' section are not populated for the archived objects in Assets.

WSS-12701 Unexpected search results when sorting columns when files include layouts that are flagged.

WSS-12768 Security: Prevent using the FILTER_VALIDATE_FLOAT filter

WSS-12804 LDAP users are unable to log in after a server upgrade (Uncaught throwable "TypeError").

Installation

Choose one of the following installation paths:

Studio Server 10.14.1

Studio Server version 10.14.1 build 380

Release date: 21 April 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

Assets Server integration: metadata fields 'Page range' and 'Publication date' are now also stored when archiving a layout. When archiving files from Studio Server to Assets Server, values from various metadata fields are stored. When a layout is archived, the values from the following metadata fields are now also stored:
Page range
Publication date

Note: The page range of the Studio Server value is converted to single page numbers in Assets Server.

Example:

Studio Server: 1–5
Assets Server: 1,2,3,4,5

Centralized logging: Option added for configuring the used ECS field structure. With the introduction of centralized logging in Studio Server 10.14.0, the structure for the ECS fields was unfortunately not respecting the ECS standard and therefore implemented incorrectly.

As a result, the field names were logged in a flat concatenated structure instead of a hierarchical structure as defined by the ECS standard.

Example:

Incorrect: { "client.ip": "123.123.123.123" }

Correct: { "client": { "ip": "123.123.123.123" } }

Because implementing the correct structure would break existing installations, the LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS option has been introduced. It is used for matching the configuration of your 3rd-party logging monitoring system:

It should be enabled when the old/incorrect structure of the ECS field is used.
It should be disabled when the new/correct structure of the ECS field is used.

Possible values:

true - Default value. The old/incorrect structure of the ECS field is used.
false - Recommended value. The new/correct structure of the ECS field is used.

Example:

if( !defined('LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS') ) {
define( 'LOG_CENTRALIZED_CONCATENATED_ECS_FIELDS', true );
}

Notes:

Future versions of Studio Server will only support the new/correct structure. When your system uses the old/incorrect structure, this structure will therefore need to be changed in your 3rd-party logging monitoring system at some point.

When running the Health Check PHP test, it will notify when the old structure is being used and will advise to change it to the new structure.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Metadata mapping between Studio Server and Assets Server - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-93684 When the order number of Issues is set to zero, the sorting order is set alphabetically in Studio Server but not in the client applications.

EN-93997 solrconfig.xml file: The comment for setting the 'mm' value contains an incorrect example.

EN-94114 Health Check: PHP errors in the Server Plug-ins test when a plug-in does not provide connectors.

EN-94159 User names appear multiple times in the Username list when configuring a Studio Server Job.

EN-94178 Logging: Replacing an image in Studio is incorrectly logged as a Warning.

EN-94216 Upgrading: Database error because of a duplicate alter table statement.

EN-94402 The ionCube Loader Wizard fails for PHP 7.4.

EN-94414 Studio panel in Studio for InDesign and InCopy is not updated when replacing an article or image in Studio.

EN-94446 Searching: Sorting On 'Dimensions' in Studio results in an empty view and an error in the log file.

EN-94455 LDAP/AD: Admin user needs to be included in Brand authorizations to get access to the Admin Maintenance pages.

EN-94475 LDAP/AD: User with a comma in the name cannot log on.

EN-94495 Archiving: Using a Custom property as the place holder for including the year and month in a folder name in the Archive Zone is no longer working.

EN-94561 MadeToPrint: The Route To field for a file is not set, even though automatic routing is enabled.

EN-94563 Assets: Custom metadata is cleared in Assets after synchronization by Studio.

EN-94584 Studio: Using a forward slash ('/') in a tag results in two tags instead of one.

EN-94614 New message event ObjectFlagCleared causes an exception in the Studio plug-ins.

EN-94653 After copying a layout, a warning 'Trying to get property 'Format' of non-object' is added to the log files.

EN-94675 Mandatory Dossier field can be bypassed when creating a new article in Studio.

EN-94796 Search: Using an empty 'Route To' option in the search filter returns zero results.

EN-94774 MadeToPrint: Allow customization to cater for multiple Status IDs and manipulate the Edition ID.

EN-94881 Assets Server integration: Publication Date and Page Range metadata fields are not stored when archiving a layout.

EN-94887 Solr: QueryObjects for a publication and type will list all workflow states of the system in the Solr request.

EN-94971 MadeToPrint: No subsequent job is triggered when a processed job sets a status and a job exists for that status.

EN-95028 Studio Print editor: 'Access denied' error and no layout preview is shown when the user does not have Write access to a layout and an image is placed on the layout and added to Studio.

EN-95040 LDAP: The 'EXCLUDE_USERNAME' option incorrectly excludes users.

EN-95055 Maintenance pages: Full user name not shown at the bottom of the menu when accessing the User Maintenance page.

EN-95184 Security: Hide sensitive HTTP header content in the phpinfo.htm file.

EN-95186 Maintenance pages: The value for OPENID_CLIENT_SECRET is not obfuscated.

EN-95214 Logging: Improve Studio Server logging to make it more compatible with Cloudwatch.

EN-95239 Security: login credentials are leaked via the phpinfo.htm file.

EN-95323 Security: An error message is not sanitized before displaying, thereby making it sensitive for an XSS-attack.

EN-95404 Upgrade guzzlehttp/psr7 to version 1.8.5 to avoid vulnerabilities found in the package.

Installation

Choose one of the following installation paths:

Studio Server 10.14.0

Studio Server version 10.14.0 build 373

Release date: 13 January 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following features have been added in this release of Studio Server:

Compatibility with Adobe 2022. Studio Server 10.14.0 or higher is compatible with Adobe 2022.

Note: This requires Studio for InDesign, InDesign Server and InCopy for Adobe 2022 (planned release Q1 of 2022).

Improvements to server logging. To improve the functionality of logging server activity, the following has been added:

Log files can now be output or streamed to a central location. When multiple instances of Studio Server are used, errors, warnings and information about the use of deprecated features can now be logged in a central location outside of Studio Server. This makes it easier and more efficient to detect problems from multiple servers from just one location.

Controlling the logging detail for an individual user via the User Maintenance page. When server logging is used for investigating technical issues that a user experiences, the level of detail to log can now be controlled via the User Maintenance page for that user. This is done by setting any of the DEBUGLEVEL options (ERROR, WARN, INFO, or DEBUG) in the new Log Level field.

This has the following advantages:

It prevents having to configure the log level in the configserver.php file to which few people have access.
The generated log files are smaller in size and contain only data based on the actions performed by the user. The data is thereby more relevant and easier to analyze.

New loglevel field in the smart_users table. To support the new Log Level field on the User Maintenance page, a new field named 'loglevel' has been added to the smart_users table. User logging is set to NONE by default, including when upgrading to Studio Server 10.14.0.

LogLevel has been added to the Admin WSDL. Integrators using the admin web services can define the log level for a user in the SmartConnectionAdmin.wsdl file. A 'LogLevel' option has been added to the 'User'. Affected web services such as Create/Modify/Get/Copy-users will now have a 'LogLevel' item: Users[]->LogLevel.

<xsd:simpleType name="LogLevel">
    <xsd:restriction base="string">
        <xsd:enumeration value="NONE"/>
        <xsd:enumeration value="ERROR"/>
        <xsd:enumeration value="WARN"/>
        <xsd:enumeration value="DEPRECATED"/>
        <xsd:enumeration value="INFO"/>
        <xsd:enumeration value="DEBUG"/>
    </xsd:restriction>
</xsd:simpleType>

More information about server logging is available in the following articles:

Note: It is particularly recommended to read the article explaining the concept to get a good understanding of the way the configuration is interpreted by the system.

Changes

The following changes have been made in this release of Studio Server:

Changes to server logging. The following changes have been made:

Logging deprecated features. Features that have been marked as deprecated can now be specifically tracked by either setting the DEBUGLEVEL option or the ‘Log Level’ field on the User Maintenance page to DEPRECATED or higher. In previous versions this could only be done by using the highest log level DEBUG. The DEPRECATED option can be used to see if a user or implementation still makes use of such a feature and to then take appropriate steps to move the used process to a supported feature.

DEBUGLEVEL option 'NONE' does not always mean that logging is disabled. Setting the DEBUGLEVEL to NONE does not always mean that logging is disabled. This is because the log level can now also be adjusted or set on the User Maintenance page. Disabling logging is now solely done by clearing the value of the OUTPUTDIRECTORY option.

Support dropped for outputting log files to disk in JSON format. Outputting log files in JSON format is now only done when logging to a central location. The JSON format cannot be configured anymore as a format for storing log files on disk.

Note: When upgrading from an instance of Studio Server in which the LOGFILE_FORMAT is set to ‘json’, upgrade steps are required. For more information, see Upgrading an existing installation of Studio Server.

New value 'null' for the options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES. The options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES can now also be set to value 'null'. When doing so, the system then only logs SQL statements, internal services and RabbitMQ services respectively when the log level that is used by the system is DEBUG.

Change in behavior of the value 'true' for the options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES. Setting the options LOGSQL, LOG_INTERNAL_SERVICES, and LOG_RABBITMQ_SERVICES to 'true' now means that the system only logs SQL statements, internal services and RabbitMQ services respectively when the log level that is used by the system is INFO or DEBUG.

Changes to the ent_log_errors.htm file in the server log folder. This file is created when a log message of level ERROR, WARN, or DEPRECATED is logged while the applied log level is DEBUG or INFO. This makes it possible to:
Manually check if the log message contain errors or warnings.
Let the Health Check automatically detect if one of its tests indirectly causes warnings or errors even though the test itself may be OK.

When centralized logging is enabled, this file is only present when the log level that is used by the system is INFO or DEBUG.

When server logging is enabled, no 'Running in DEBUG mode' message is shown anymore on the Log In screen.

More information about server logging is available in the following articles:

Note: It is particularly recommended to read the article explaining the concept to get a good understanding of the way the configuration is interpreted by the system.

Support for SVG images. Images in SVG format are now supported by default by including it in the EXTENSIONMAP settings of the configserver.php file. This format therefore does not have to be added manually anymore, for example when wanting to make use of features such as adding images in SVG format to a Digital article in Studio.

The following requirements and limitations exist:

The use of SVG images is supported in InDesign 2020 or higher and Studio 11.100 or higher.
The embedded text is not searchable.
Previews and thumbnails are in JPEG format.

Removal of UPDATE_GEOM_SAVE option. When an article is placed on a layout and a change is made to that article or layout, users of InDesign and InCopy need to be informed of that change to verify if it affects their work. In previous versions of the server and the plug-ins for InDesign and InCopy, this was controlled through the UPDATE_GEOM_SAVE option in the configserver.php file. With the improvements made in the plug-ins for Adobe 2020 and higher, this functionality has changed and the UPDATE_GEOM_SAVE option is not used anymore. It has therefore been removed, together with the following public methods:
BizRelation::isPlacedArticleRelation()
BizObjectLock::isLockedByDifferentUser()

Removal of the WW_Utils_IpAddressRange class. As a result of making improvements to the code, the WW_Utils_IpAddressRange class has been replaced by the WW_Utils_IpAddressRangeChecker class.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.14 - new (all other relevant compatibility matrix articles have been updated as well)
File formats supported by Studio Server - updated
Logging server activity in Studio Server 10.14 or higher – Concept - new
Logging server activity in Studio Server 10.14 or higher – Configuration - new
Logging server activity in Studio Server 10.14 or higher – Viewing log files - new
Managing user accounts in Studio Server - updated
Upgrading an existing installation of Studio Server - updated
Upgrading Enterprise Server to Studio Server 10.10 or higher - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

No issues have been fixed in this release of Studio Server.

Installation

Choose one of the following installation paths:

Studio Server 10.13.1

Studio Server version 10.13.1 build 363

Release date: 8 September 2021

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been added in this release of Studio Server.

Changes

The following changes have been made in this release of Studio Server:

Archiving files to Assets Server: The following changes have been made:
It is now possible to keep files in Studio Server after they have been archived to Assets Server. Deleting the files from Studio Server used to be an implicit step that was part of the archive operation, but has now become a configurable option that can enabled or disabled.

For this, a new option named 'After archiving' is added to the configuration options of each archive schema. It contains 2 settings to choose from:

Delete files. When selected, the archived files are deleted from Studio Server. Note that files are purged; they cannot be found in the Trash Can and cannot be restored.
Send files to next Status. When selected, the layout, Digital article, or Dossier is sent to the next Workflow Status. (Only applicable when the Delete files option is not selected, else it has no effect.)

It is now possible to send files to the next Workflow Status. When a layout, Digital article, or Dossier is kept in Studio Server after archiving, it is sent to the next Workflow Status.

It is now possible to automate tasks on files in Studio Server after archiving. Combining the two options above, files can be kept in Studio Server and sent to the next Status. This makes it possible for integrators to automate tasks on these files such as modifying them in a way which results in versions that are not suited for archiving, converting print layouts to digital articles, and so on.

The period at which the archiving should start can now be defined in hours instead of days for better control of the archiving process. For this, the option 'Archive after (days)' has been renamed to 'Archive after (hours)'.

The option 'Archive after (hours)' now also applies when Trigger 'Status Based' is chosen. This makes it possible for this method of archiving to keep the files in the system for a short while to perform specific actions on them and to prevent that they are archived instantly.

The archiving process can now be started before the trigger is reached by setting a negative value in hours.

When archiving layouts, Collections are now created to represent the Dossier structure. Layouts are typically part of multiple Dossiers: one for each Story consisting of the layout, an article that is placed on the layout, some images that are placed on the layout, and additional reference files. To represent this structure in the archive, Collections are now created in the archive folder: one for each Dossier that contains the layout as well as the article and any other files that are placed on the layout.

Compatibility with Elvis Server increased to version 6.44 or higher. Because of the added functionality of creating Collections when archiving layouts, the compatibility with Elvis Server has been increased to version 6.44 or higher.

For more information about archiving, see Archiving files from Studio Server 10.13.1 or higher to Assets Server.

Note: When upgrading previous versions of Studio Server, archive settings are automatically updated to the new options and set to the default value (which reflects the configuration of the version that is upgraded from).

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Archiving files from Studio Server 10.13.1 or higher to Assets Server - new
Compatibility of Studio Server 10.13 - updated
Compatibility of Elvis 6 - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-94157 No hierarchical view is shown in the Studio panel of Studio for InDesign after making a change in the planning interface.

EN-94169 MadeToPrint: No MadeToPrint job is created when multiple layouts are set to a status that should trigger a job (manually or via Send to Next Status).

EN-94305 Unable to activate a license for Studio Server.

EN-94310 Studio: When sorting on an unsupported column in the Search results of a user defined Named Query, a database error is shown and Studio becomes unusable.

EN-94321 Allow character set utf8mb3 next to utf8 in the Health Check to support MySQL 8.0.24+.

EN-94338 Error 'Undefined index: id' is logged when deleting a Workflow Status.

EN-94340 Error 'Undefined variable' is logged when exporting an image.

EN-94346 Breadcrumb link is missing on Service Logs - Details page.

EN-94347 Security: Vulnerability found in "phpseclib" library used by "php-amqplib" library.

EN-94348 Security: Vulnerability found in "phpseclib" library used by "php-amqplib" library.

EN-94367 Assets Server integration: When updating the status for multiple files in Studio, the status for the files in Assets Server is not updated.

EN-94393 Assets Server integration: When updating the status for a file in Studio via the context menu, the status for the file in Assets Server is not updated.

EN-94413 Image position on the layout changes after cropping or moving it in the Studio Print editor.

EN-94451 Asset Server integration: Images imported from Assets Server get corrupted when config_elvis.php file contains an incorrect header.

EN-94481 Improve query performance by adding additional indices to the smart_objects table.

EN-94487 Error 'Missing function parameter (S1000)' appears in Studio when previewing a layout and layout and placed article are in multiple Dossiers.

EN-94492 Upgrading: Incorrect statement for 'masterticketid' field in some SQL files in the dbscripts folder.

EN-94493 Upgrading: Incorrect statement for 'masterticketid' field in some SQL files in the dbscripts folder.

EN-94502 Archiving - Studio Server metadata properties are not or only partly set when archiving files to Assets.

EN-94571 Deleted files are still shown in a Dossier.

EN-94617 Studio panel blanks and error 'Invalid column name 'fulname' is logged when sorting on 'Modified By' column.

Installation

Choose one of the following installation paths:

Studio Server 10.13.0 build 352 Quick Patch

Studio Server version 10.13.0 build 352

Release date: 21 July 2021

Downloads

Fixed issues

Installation

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-94463 MadeToPrint: No MadeToPrint jobs created when sendToNext or multiSetObjectProperties are changed for multiple layouts.

EN-94521 'Missing function parameter (s1000)' message is shown when previewing a layout if layout and article are in multiple Dossiers.

Installation

Choose one of the following installation paths:

Studio Server 10.13.0

Studio Server version 10.13.0 build 351

Release date: 3 June 2021

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following has been added in this release of Studio Server:

Support for Webhooks. A Webhook listens for specific triggers and then performs a predetermined action. Webhooks can now be used for adding customizations to Studio Server.

Examples:

When an article reaches the Ready status, a ZIP file of the content of the entire Dossier of the article is made, uploaded to an S3 bucket and the URL for downloading the file is made available by adding it to a row in a Google Sheet.

Same as the previous example, but now done when a layout reaches the Ready status to make all of its pages in PDF format available for download.

Important: This feature is currently experimental, incomplete and subject to change. Nevertheless, we invite you to experiment with it. Based on your feedback we can refine and shape this feature into the right direction.

Background information

In previous versions of the server, adding customizations was solely done through the use of custom Server plug-ins. Such plug-ins sit directly on top of the Studio Server technology stack (PHP version, Studio Server version, and so on) and as a result can make server upgrades problematic because manual attention may be required by the integrators to make them compatible with the upgraded technology stack.

By introducing the Webhooks concept, we enable our partners and integrators to use modern integration platforms such as Workato.

Webhook calls made by Studio Server travel over HTTP to the integration platform which makes the customizations built for Studio sit on top of the technology stack of that integration platform rather than the one of Studio Server. Studio Server can then also be upgraded without the need to migrate the customizations because these are now hosted by the integration platform.

Note: The Webhooks concept does not make the custom server plug-ins concept obsolete because there are many pros and cons between using each concept. Many customizations are currently made with custom server plug-ins that are simply unachievable by using Webhooks because of various technical reasons. Webhooks should therefore be positioned as a good alternative, when technically feasible.

What is implemented?

Some basic workflow services of Studio Server are now pushing event data into the Event Bus. Also, the following has been added:

A Server plug-in named Webhooks.
A configuration file: config/config_webhooks.php.
Options (prefixed with EVENT_BUS_ ) in the config/configserver.php file.
A message queue named Event Bus to RabbitMQ (added by Studio Server).
A message queue for each Webhook registration to RabbitMQ (added by Studio Server).
An event processor for the Event Bus queue (to be executed with a scheduler).
An event processor for the Webhooks queues (to be executed with a scheduler).

More information

For more information, see the Webhooks page in the Web Services Guide.

Changes

The following changes have been made in this release of Studio Server:

Compatibility Matrix. Compared to Studio Server 10.12, the following changes have been made to the compatibility between Studio Server and other systems:

Technology/feature

Remarks

Adobe

Dropped:

Support for Adobe CC 2017.

Solr

Added:

Support for Solr 8.8.

Dropped:

Support for Solr 7.6.

Support for creating catalogs removed (Datasource integration). Support for creating catalogs that was marked as deprecated in Studio Server 10.12.0 has now been fully removed.

The integration was offered through the following web service interfaces:

Data Source (workflow Data Source). Used for integrating any external storage carrying structured catalog data.
Data Source admin. Administered the data such as creating, getting, and saving queries used in the Data Source interface.

These interfaces have now been removed. As a result, the services under these interfaces cannot be called anymore, even when they have their own integrations / plug-ins.

Next to the components and functionality that were removed in Studio Server 10.12, the items below have now also been removed.

The following Web Services have been removed:

The Admin Data Source interface (StudioServer/server/interfaces/PlutusAdmin.wsdl)
The Data Source interface (StudioServer/server/interfaces/PlutusDatasource.wsdl)

No services related to the Data Source can be called anymore.

The following files have been removed:

StudioServer/server/bizclasses/BizAdmDatasource.class.php
StudioServer/server/bizclasses/BizDatasource.class.php
StudioServer/server/bizclasses/BizDatasourceUtils.php
StudioServer/server/dbclasses/DBDatasource.class.php

The following Studio business connector has been removed:

DataSource_EnterpriseConnector

This means that in the custom server plug-in, in the <pluginName>/PluginInfo.php file, the following entry cannot be called anymore in the getConnectorInterfaces() function:

final public function getConnectorInterfaces() 
{ 
     return array( 'DataSource_EnterpriseConnector'  );
}

The following web service connectors have been removed:

Because the Admin DataSource and Workflow DataSource interfaces have been removed, the web services connected to them are also no longer supported.

This means that in the custom server plug-in, in the <pluginName>/PluginInfo.php file, the Ads*_EnterpriseConnector and Dat*_EnterpriseConnector entries cannot be called in the getConnectorInterfaces() function anymore.

Examples:

Ads*_EnterpriseConnector:

final public function getConnectorInterfaces() 
{ 
     return array( 'AdsGetSettings_EnterpriseConnector'  );
}

Dat*_EnterpriseConnector:

final public function getConnectorInterfaces() 
{ 
     return array( 'DatGetRecords_EnterpriseConnector'  );
}

The following database tables have been removed:

smart_datasources
smart_dsobjupdates
smart_dspublications
smart_dsqueries
smart_dsqueryfamilies
smart_dsqueryfields
smart_dsqueryplacements
smart_dssettings
smart_dsupdates

The following Maintenance page has been removed:

Integrations > Data sources

Axaio MadeToPrint integration: manipulating Edition IDs. The signature of one of the Enterprise Connector methods of the MadeToPrint integration has been changed to make it possible for customization scripts to manipulate the Edition ID.

It involves the following method:

\AxaioMadeToPrintDispatcher_EnterpriseConnector::queueLayoutObjectFilterEditions()

Its signature has been changed from:

queueLayoutObjectFilterEditions( array $layEditions ....

to:

queueLayoutObjectFilterEditions( array &$layEditions ....

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.13 - new
Archiving files from Studio Server 10.13.0 to Assets Server - new
Studio Server database tables - updated
Web Services Guide - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-31825 Configuration: Default value for ATTACHMENTDIRECTORY for Windows is incorrect.

EN-90992 Brand Maintenance page: Blank page is shown when creating a new Brand, leaving Name field empty and clicking Update.

EN-92771 Workflow Maintenance page: Missing function parameter error when enabling 'Skip InDesign Server Automation' for articles and clicking Update.

EN-92781 AutomatedPrintWorkflow script folder contains a __MACOSX folder.

EN-93125 Health Check page: WoodWing Assets Content Source test show 'Elvis' instead of 'Assets' in error message.

EN-93161 Solr: Fall back on database search when Solr is indexing.

EN-93168 Routing e-mail template: custom date type field's are displaying as type datetime with T00:00:00.

EN-93172 InDesign Server: improve the extraction of the Adobe version of a layout.

EN-93258 ExifTool integration: Metadata extraction for EPS and AI files by ExifTool results in warning in server log.

EN-93373 Health Check page: OPCache error in server logging when user opens page (or clicks links on page).

EN-93401 The WSDLs seems no longer compatible with modern .NET clients.

EN-93537 User Maintenance page: When setting the 'Password Expiration in Days’ field, the database field ‘expirepassdate’ should also get updated/re-calculated.

EN-93585 Breadcrumbs: Enable breadcrumb navigation when new entity is added.

EN-93589 Client applications: Brands are not arranged alphabetically if no display order is defined.

EN-93599 Planning interface: Layout created via planning interface has no preview when the pages use a non-arabic numbering system.

EN-93655 Security: SQL Injection in User Inbox.

EN-93656 Security: SQL Injection via the HaveVersion ID Parameter.

EN-93699 Replace article: No error reported by InDesign Server on macOS.

EN-93702 Access Profiles: remove the 'Content Station Pro - Edition' access right.

EN-93718 Add support for archiving Adverts from Studio Server to Assets Server.

EN-93726 Control characters in the Name field of an object are replaced with a space.

EN-93822 Preview performance optimization: delete master spreads while generating previews on InDesign Server.

EN-93858 'Not sufficient access rights' message S1077 shown when user logs in to the server using the full name.

EN-93891 Add support for Status based archiving.

EN-94014 Solr search is not used when searching in a Dossier.

EN-94122 Assets Server: 'Send to next status' property is not updated in Assets Server.

EN-94196 Limit the use of temporary tables to resolve read access rights in case of database searches.

EN-94217 Axaio MadeToPrint: Allow the customization script to manipulate the Edition ID.

EN-94218 Axaio MadeToPrint: Cater for multiple status IDs (instead of one ID) in 'MtpConfig'.

EN-94240 The default HOLIDAYS definition in configserver.php is outdated (2012-2014).

EN-94243 Health Check: Allow character set utf8mb3 next to UTF-8 to support MySQL 8.0.24+.

Installation

Choose one of the following installation paths:

Studio Server 10.12.0

Studio Server version 10.12.0 build 333

Release date: 20 January 2021

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

No features have been introduced in this release of Studio Server.

Changes

The following sections list the changes that have been made in this release of Studio Server.

Compatibility Matrix

Compared to Studio Server 10.11, various changes have been made to the compatibility between Studio Server and other systems as shown in the following table.

Technology/feature	Remarks
Adobe 2021	Studio Server 10.12 is compatible with InDesign 2021, InDesign Server 2021, and InCopy 2021. Note: The use of these applications requires Studio for InDesign and InCopy 2021 (version 16.0.0) which is planned to be released in Q1 2021.
PHP	Studio Server 10.12 requires PHP 7.4.
ionCube Loader	Studio Server 10.12 requires ionCube Loader 10.4.5.
MS SQL Server drivers	Support for SQL Driver 5.6 for PHP has been removed because this driver is not compatible with PHP 7.4.

Support for creating catalogs in InDesign

The following DataSource Web service interface definitions have been marked as deprecated:

Entry point	WSDL
https://localhost/StudioServer/datasourceindex.php	StudioServer/server/interfaces/PlutusDatasource.wsdl
https://localhost/StudioServer/datasourceadminindex.php	StudioServer/server/interfaces/PlutusAdmin.wsdl

Dossier template support for Content Station 9

Support for adding Dossier templates to the Home page of Content Station 9 has been removed. Support for this feature was already deprecated but has now been fully removed from the software.

The following has been removed from the Brand Maintenance page:

The Dossier templates section.

The Dossier Templates section on the Brand Maintenance page

Note: When upgrading from a version of Enterprise Server in which records for this list existed, these records will be automatically removed during the upgrade.

The following PHP classes have been removed:

BizAdmTemplateObject
DBAdmTemplateObject
TemplateObjectAccess
AddTemplateObjectsRequest
AddTemplateObjectsResponse
AddTemplateObjectsService
GetTemplateObjectsRequest
GetTemplateObjectsResponse
GetTemplateObjectsService
RemoveTemplateObjectsRequest
RemoveTemplateObjectsResponse
RemoveTemplateObjectsService

The following Named Query has been removed:

DOSSIER_TEMPLATES_IN_APPLICATIONS. This was implemented in the Server plug-in 'Studio List Dossiers' (also known as 'Content Station List Dossiers').

The following database table has been removed:

smart_publobjects

The following elements and services under the Admin interface (StudioServer/server/interfaces/SmartConnectionAdmin.wsdl) have been removed:

Elements:
TemplateObjectAccess
ArrayOfTemplateObjectAccess
AddTemplateObjectsRequest
AddTemplateObjectsResponse
GetTemplateObjectsRequest
GetTemplateObjectsResponse
RemoveTemplateObjectsRequest
RemoveTemplateObjectsResponse
Services:
AddTemplateObjects
GetTemplateObjects
RemoveTemplateObjects

Publish Forms: Removal of the Publishing Services feature

Publishing Services were used in conjunction with Publish Forms in Content Station 9. Support for Publish Forms was already deprecated but its functionality (the Publishing Services) has now been fully removed.

Note that this means that these services cannot be called anymore, for example from custom integrations or plug-ins.

The following files have been removed:

StudioServer/server/utils/PublishingProgressBar.class.php
StudioServer/server/utils/PublishingFields.class.php
StudioServer/server/utils/ParallelCallbackCache.class.php
StudioServer/server/bizclasses/BizPublishing.class.php
StudioServer/server/bizclasses/BizPubIssue.class.php
StudioServer/server/interfaces/plugins/connectors/PubPublishing_EnterpriseConnector.class.php
StudioServer/server/dbclasses/DBPubPublishedIssues.class.php
StudioServer/server/dbclasses/DBPublishedObjectsHist.class.php
StudioServer/server/dbclasses/DBPublishHistory.class.php

The following functions have been removed:

In StudioServer/server/bizclasses/facades/ServerPlugin.class.php:

WW_BizClasses_Facades_ServerPlugin::runChannelConnector()

In StudioServer/server/bizclasses/BizServerPlugin.class.php:

BizServerPlugin::getPluginFolderForChannelId()
BizServerPlugin::runChannelConnector()
BizServerPlugin::getChannelConnector()

In StudioServer/server/bizclasses/BizAdmPublication.class.php:

BizAdmPublication::getDefaultPubChannel

The following Named Query has been removed:

The build-in Named Query 'PublishManager'. This was used by Content Station 9 in the 'Publish Manager' tab to show an overview of the publish status of each Publish Form ('Ready To be Published', 'New', 'Updated', 'Published').

The following Studio business connector has been removed:

PubPublishing_EnterpriseConnector

As a result, in the <pluginName>/PluginInfo.php file of a custom server plug-in, the following entry cannot be called anymore in the getConnectorInterfaces() function:

final public function getConnectorInterfaces() 
{ 
     return array( 'PubPublishing_EnterpriseConnector'  );
}

The following classes in StudioServer/server/smartevent.php have been removed:

class smartevent_issuereorderpublished
class smartevent_publishissue
class smartevent_updateissue
class smartevent_unpublishissue
class smartevent_setpublishinfoforissue
class smartevent_publishdossier
class smartevent_updatedossier
class smartevent_unpublishdossier
class smartevent_setpublishinfofordossier
class smartevent_issuereorder

The following database tables have been removed:

smart_pubpublishedissues
smart_publishedobjectshist
smart_publishhistory

When upgrading from a previous version of Studio Server or Enterprise Server, these tables will be removed ('dropped') during the database upgrade.

The following database fields have been removed:

smart_states table: 'readyforpublishing'
smart_targets table: 'publisheddate', 'publishedmajorversion', 'publishedminorversion', 'externalid'
smart_channels table: 'publishsystem'

When upgrading from a previous version of Studio Server or Enterprise Server, these database fields will be removed ('dropped') during the database upgrade.

The following Web Service has been removed:

Publishing interface (StudioServer/server/interfaces/EnterprisePublishing.wsdl). This interface was mainly called by Content Station 9.

No services related to the Publishing interface can be called anymore.

The following 'actions' in the Workflow interface (StudioServer/server/interfaces/SCEnterprise.wsdl) have been removed:

In the Workflow interface as part of simple type 'Action', the following entries have been removed:

<simpleType name="Action”>

<enumeration value="PublishDossier"/>  
<enumeration value="UpdateDossier"/>  
<enumeration value="UnPublishDossier"/> 
<enumeration value="SetPublishProperties"/>

The following properties have been marked as discontinued:

Workflow interface (StudioServer/server/interfaces/SCEnterprise.wsdl)

Under 'Target':
'PublishedDate' and 'PublishedVersion' properties (Discontinued)
Under 'PubChannelType':
'sms' type (Discontinued)

Admin interface (StudioServer/server/interfaces/SmartConnectionAdmin.wsdl)

Under 'Status':
'ReadyForPublishing' property (Discontinued)
Under 'PubChannel':
'PublishSystem' property (Discontinued)
Under 'PubChannelType':
'sms' type (Discontinued)

The Studio Server code base no longer handles these properties.

Web Services: Changes to the WflGetPagesService

The WflGetPagesService is used for retrieving page renditions (thumbnails or previews) of layouts in applications such as Journal Designer. The following changes have been made to it:

Improved performance. To speed up the retrieval process, the following has been changed:

A new parameter named 'HaveVersions' has been added to the WflGetPagesRequest. By setting this parameter, only page rendition attachments are returned when, after an initial request, a newer version of the page is available. Previously all page renditions were copied to the Transfer Server folder (by the server) and downloaded by the client, even though no newer version was available.

The following functions have been removed from the DBPage class; these should no longer be called by PHP customizations:
DBPage::listPagesByLayoutPerIssue
DBPage::listPagesByLayoutPerIds

The following parameters have been deprecated since Enterprise Server 8.3.3 and have now been removed from the WflGetPagesRequest; these should no longer be used by web service integrations:
PageOrders
PageSequences
RequestMetaData
RequestFiles

For information about Web Services, see The Web Services SDK of Studio Server.

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.12 - new
Studio Server database tables - updated
The Web Services SDK of Studio Server - updated
Studio Server plug-ins - updated

Known issues

No known issues exist for this release of Studio Server.

Fixed issues

The following issues have been fixed in this release of Studio Server:

EN-16009 Performance/JournalSuite: Improve performance of the planning overview in JournalDesigner.

EN-91829 Brand and Issue Maintenance pages: The field labels 'Reading Order Reversed" and 'Reading Order' are swapped.

EN-91948 User Authorization report: The tooltip for the Back button is not shown.

EN-92052 Publication Channel Maintenance page: When creating or copying a new Brand, the focus is not set to the Name field.

EN-93426 Performance: Add index to smart_objects table on 'publication and 'type'.

Installation

Choose one of the following installation paths:

Studio Server 10.11.5

Studio Server version 10.11.5 build 376

Release date: 16 March 2022

Downloads

The download files for this version of Studio Server can be found in the Release announcement.

New features

The following features have been added in this release of Studio Server:

Compatibility with InDesign Server 2022. Studio Server 10.11.5 or any higher version of version 10.11 is compatible with Adobe InDesign Server 2022.

Changes

The following changes have been made in this release of Studio Server:

Removal of UPDATE_GEOM_SAVE option. When an article is placed on a layout and a change is made to that article or layout, users of InDesign and InCopy need to be informed of that change to verify if it affects their work. In previous versions of the server and the plug-ins for InDesign and InCopy, this was controlled through the UPDATE_GEOM_SAVE option in the configserver.php file. With the improvements made in the plug-ins for Adobe 2020 and higher, this functionality has changed and the UPDATE_GEOM_SAVE option is not used anymore. It has therefore been removed, together with the following public methods:
BizRelation::isPlacedArticleRelation()
BizObjectLock::isLockedByDifferentUser()

MadeToPrint: A subsequent job is now triggered when a processed job sets a status and a job exists for that status. When a processed MadeToPrint job is completed, the file is set to another Workflow Status to move it along in the workflow process.

When another job exists for that new status, this job is now automatically triggered. In previous versions, the job was only triggered when the file was manually re-set to the status.

Example: Here, a file is set to status 'Reviewed' which triggers a job to create a low-resolution PDF file. When the job is completed, the file is set to status 'Production'. This then triggers another job to create a high-resolution PDF file.

Trigger	Status 'before'	Job	Status 'after'
Trigger 1	Reviewed	Create a low-resolution PDF	Production
Trigger 2	Production	Create a high-resolution PDF	Production

Workflow: TicketHash added to the CheckTicket workflow service. The workflow service CheckTicket now provides a TicketHash in its response. This is specified in the SCEnterprise.wsdl file accordingly (in a backwards compatible manner to not break existing client applications that are unaware of this change). This ticket hash can be used by Studio to compare it with the ticket hash that arrives through an event message. When the same, Studio may conclude that the event was caused by the client app itself and thus may be ignored (to avoid applying the same change in the UI twice).

Documentation

The following changes to the documentation have been made in this release of Studio Server:

Compatibility of Studio Server 10.11 - updated
Integrating MadeToPrint in Studio Server - updated