• When an embed is updated, the specified order of the contents in the update request is kept. Before the new contents were always added after the already existing contents, ignoring the order in the request.

• All business rules contained in the business rule configuration have now backend validation of Names and Description properties, while before the validation was only enforced by the UI. Update of the business rule configuration won't be possible if any businees rule does not pass following validation:
  • Names property is required, Names and Description properties have language validation: if a translation other than for the customer default language is provided, than also the customer default language translation must have a value.

• Before 11.2.0 it was possible to use a MetadataValuesSchemaRemoveCommand command on a Content schema. This should have been prevented as the result was to flush the metadata dictionary of the Content schema.
• In 11.2.0 the operation is rejected

• OutputFormat has new property XmpWritebackOptions.
  MappingOnly (default): corresponds to previous behaviour (i.e. only data produced by XmpMappings is applied to file).
  MergeWithOriginal uses Xmp metadata of the originally uploaded file and overwrites only values which are specified in an XmpMapping. Other values are left intact (where possible).
  OutputFormatSetXmpWritebackStateRequest was updated accordingly.

See

PictureparkSwagger.json

• BusinessRuleTransformationGroup and all contracts inherited from BusinessRuleAction, BusinessRuleCondition, BusinessRuleTransformation have new Names and Description properties as TranslatedStringDictionary.
• The new peoperties are only used for display purposes in the UI.

See

PictureparkSwagger.json

• Schema extended to include MetadataProtection property. Can prevent creating new items (Content Schemas) or assigning schema to items (Layers), editing metadata in schema or deleting/unassigning items in schema
• Options cannot be changed for Structs.

See

PictureparkSwagger.json

• UserInUserRolesCondition contract added to allow to configure the new UserInUserRoles business rule condition.

See

PictureparkSwagger.json

• LookupReturnedItems property added to LookupCacheTransformation contract. Possible values:
  • Found: return the value of the found item in the lookup cache, null if not found (existing logic, default).
  • NotFound: return the input key value of the not found item, null if found.
  • All: return the value of the found item in the lookup cache or the input key value of the not found item.

See

PictureparkSwagger.json

The fp argument to the crop instruction was enhanced:

• If the Content has FocalPoints (with coordinates) in ImageAnalytics Layer, fp:identifierOfFocalPoint can be used to specify the position of the cropping rectangle.
  Crop size can be automatically derived (crop:auto,fp:fpIdentifier) if the focal point has 2 or more coordinates.
  If the crop size is specified in the URL and a focal point identifier is specified (crop:200x200,fp:fpIdentifier), the focal points centroid is used to position the cropping rectangle.

See

ContentTests.cs

• Polymorphism was moved to size and position properties.
  The existing crop actions (CropAction, GravityBasedCropAction, RelativeCropAction) remain for compatibility reasons (also added the new properties).
  New CropSizeRelative allows for relative dimension of cropping rectangle.
  Introduced explicit CropGravity.Center value.

See

PictureparkSwagger.json

• RenderingState attribute was added to reflect the rendering state of the shared output.

• New properties allow to check if all the layers specified in the AddedLayerIds property are being added during the current operation and if all the layers specified in the RemovedLayerIds property are being removed during the current operation.
• If values are set, all values for both conditions must match.
• If no values are set, behavior of the condition remains unchanged.

See

PictureparkSwagger.json

• The new condition allows to perform a simple "string contains" check that can be case sensitive or not.
• The check is performed against a specified value.
• In case of a successful match, a custom value / object can be optionally stored in a variable.

See

PictureparkSwagger.json