Backwards compatibility and API changes in Content Manager introduced in Tridion Sites 9.5
The API has changed somewhat in this release, which may affect your customizations.
General changes
- Server time versus UTC time converted to client time
- Before this release, all timestamps returned by the Content Manager APIs were server times. That is, if your server was physically located in, say Hong Kong, the time would be returned as local time in Hong Kong Standard Time, that is, UTC + 8 hours.
- User names for impersonated users must now be fully qualified
-
Certain Content Manager APIs allow you to impersonate other users for various purposes, such as to give a user a higher level of access than the user would have ordinarily. In some instances, you can configure a specific Windows user who will be impersonated, such as the one External Content Library (ECL) allows you to configure with the
PrivilegedUserNameproperty. In previous releases, you could define the user with a simple, unqualified username, such as of "administrator" and Content Manager would recognize this as the local Windows administrator. As of release 9.5, you must use a fully qualified username, such as "global\administrator". The fully qualified username can specify a domain, such as "global\administrator", or can be a local server account. In this case, you need to include the machine name rather than a domain, for example, "MYCMSSERVER\Administrator".
New methods and properties
ConvertSchemaFieldsToXsdForSchemaPurpose- Interface:
ICoreService201701 IncludeCurrentPublication- Namespace: Tridion.ContentManager.Publishing.ResolveInstruction
PublishInChildPublications- Namespace: Tridion.ContentManager.Publishing.ResolveInstruction
IsIndexable- Namespace: Tridion.ContentManager.CoreService.Client.SchemaData
IsPublishable- Namespace: Tridion.ContentManager.CoreService.Client.SchemaData
Locale- Namespace: Tridion.ContentManager.CoreService.Client.PublicationData
Locale- Namespace: Tridion.ContentManager.CoreService.Client.RepositoryLocalObjectData
ClaimType- Namespace: Tridion.ContentManager.CoreService.Client.IdentityProviderGroupMappingData
Value- Namespace: Tridion.ContentManager.CoreService.Client.IdentityProviderGroupMappingData
IsDataPipelineBased- Namespace: Tridion.ContentManager.CoreService.Client.ResolvedItemData
IsIndexable- Namespace: Tridion.ContentManager.CoreService.Client.ItemFieldDefinitionData
IsPublishable- Namespace: Tridion.ContentManager.CoreService.Client.ItemFieldDefinitionData
IsDataPipelineBased- Namespace: Tridion.ContentManager.Publishing.Resolving.ResolvedItem
Locale- Namespace: Tridion.ContentManager.ContentManagement.RepositoryLocalObject
IsPublishable- Namespace: Tridion.ContentManager.ContentManagement.Schema
IsIndexable- Namespace: Tridion.ContentManager.ContentManagement.Schema
IsPublishable- Namespace: Tridion.ContentManager.ContentManagement.Fields.ItemFieldDefinition
IsIndexable- Namespace: Tridion.ContentManager.ContentManagement.Fields.ItemFieldDefinition
Locale- Namespace: Tridion.ContentManager.CommunicationManagement.Publication
Deprecated method
ConvertSchemaFieldsToXsd- Interface:
ICoreService201701
Handling of dates and times
As of SDL Tridion Sites 9.5, the WCF Core Service and the TOM.NET API return date/time system values in UTC only, as opposed to earlier versions of the product where most of date/time values were returned in the timezone of the Content Manager server. That includes all system date/time values that data items may contain, such as for example FullVersionInfo.CheckOutDate, ActivityData.StartDate and PublishTransactionData.StateChangeDateTime. Accordingly, any value provided by the API user as input, such as PublishInstruction.DeployAt, are also expected to be in UTC.
Note that the SDL Tridion Sites 9.5 APIs do not convert or adjust the values of date/time fields in data or metadata; they continue to be returned "as is."