Web Client changes
Web Client improvements for this version.
Properties dialogs
Overview
The object's properties for all object levels (logical, version and language levels) are now displayed in the same dialog instead of in one dialog for each object level. When the dialog is summoned from the Properties button at a given object level, the properties' form scrolls down to the appropriate level. This major change affects the object creation procedure and the properties display behavior in the Web Client. It also affects the way you customize the object properties dialog during implementation.
Object creation
- You no longer follow a three-steps procedure to create an object, you now fill in a single list of fields.
- All three levels of the object are always created when an object is created.
During the creation process, you now need to select the object template first (it was previously an action carried out during the third and last step of the object creation). After you have selected the template, the object creation dialog will appear with some of the fields pre-filled according to the chosen template.
When you create an object, the language of the object is automatically the default language of the user who creates the object. That setting can no longer be changed. If you want the object to be in a different language, you need to create an additional language for this object after creation. The same applies to resolution for images.
When you create new versions/branches or new languages for an object, the single dialog with all properties is also used.
When you create a new version, the parent level (logical level in this case) fields in the creation dialog can be edited, as those properties are in display mode. The same goes for the language level: when you create one, the two parent levels are in display mode in the dialog.
For the publication object, only two levels are present at creation: logical and version. You must create specific output formats for the publication after the publication creation has completed.
Properties edition and display
For properties edition and display, you can access an object's properties from three different locations in the user interface depending on the level of the object you want to see: logical, version or language/resolution/output format.
In previous versions of CM, the displayed information was different depending on the location. Now all properties have been regrouped in a single dialog and that single dialog is accessed from any of the three locations. Depending on where you access it from, the view will scroll down to the appropriate group of fields.
If you display properties at the logical level (from the top menu bar), the Web Client will automatically display properties for the last version of this object, and for the default user language for this version. You need to select a specific version/branch, or a specific language/resolution, and use the appropriate level property button, if you want to display the properties for those object's levels.
Whenever you try to display properties for an object that has no version or an object version that has no language (created with earlier versions of Content Manager), an error message will be displayed instructing you to create the required version and language. You can view the properties only after you have created those. Note that all the rules for creation apply when you carry out the required action (for example, creating a new version will make the default user language pre-selected).
Dialog customization
The procedure for customizing properties dialogs in the Web Client is now identical to the procedure used for customizing them in Publication Manager. Both use the MetadataConfig.xml file.
The MetadataConfig.xml file now contains the ClientName condition that lets you specify the fields that you want to show in Publication Manager and not in the Web Client or vice versa. This condition can be set for any Tridion Docs tool that uses the metadata fields. The details can be found in the configuration section of the Content Manager documentation.
Web Client preview resolves content references (@conrefs)
The content preview in the Web Client now also shows content references (@conref). The preview uses the latest available version of the libraries. This resolution is on by default: ignoreObjectFragments=false.
The resolution of navigation titles (navtitles) and link text in the Web Client preview is also available in this version, but is off by default as this may affect performance significantly: ignoreNavigationTitles=true and ignoreLinkTexts=true.
Language inheritance during language creation
The default language of the content passed on to a new language when this new language is created for an object, have changed.
In Content Managerversion 13, when you created a new language of an object in the Web Client, the language of the content put in the new language would always be the default language of the user. It then had to be entirely translated.
Now we first search for a previous content in the created language in previous versions of the object, and use it if we find any. We search latest versions first.
- If there is a Japanese language for the version 2, this content is used for the created language. If not...
- If there is a Japanese language for the version 1, this content is used for the created language. If not...
- The English content is used for the created language.
Other improvements
The ability to select a resolution from a list when creating a new image object in the Web Client is available again, in the new metadata form.
The preview is now correctly displaying right to left languages.
When the upload action (using the Upload button) returns an error, the error message is now more specific and adapted to the actual issue than the former Oops, something went wrong.