11.4.0

Metadata

RelationUiSettings

Renamed enum RelationView

• has been renamed to ItemFieldViewMode

See PictureparkSwagger.json

Metadata

FieldBase.Fixed

Unused property has been removed

• Value of field was always false

See PictureparkSwagger.json

OutputFormat

Interpretation of OutputFormat.ViewForAll

Permission check now only relies on value of concrete OutputFormat

• Previously, a format was effectively ViewForAll if it or any of its ancestors were ViewForAll

• This made it impossible to restrict a format derived from one with ViewForAll

• It also allowed for a given format to have different effective ViewForAll depending on the content type

See Contracts.Generated.cs

Notifications

EmailNotificationsSettings
GET /notifications/emailNotifications/settings
PUT /notifications/emailNotifications/settings

Multiple sources support

With introduction of commenting email notifications will come from multiple sources. Therefore a new attribute Sources was added that contains an object where

• keys represent the sources (source name)

• values contain EmailNotificationsSourceSettings contract with information that was previously directly in the contract itself

See Contracts.Generated.cs

Notifications

GET emailNotifications/types

Now returns an object

To accommodate multiple email notification sources, the endpoint now returns an object where

• keys represent the sources (source name)

• values contain the list of available types for the specific source

See API spec change

BusinessRule

EnqueueCreateEmbedAction

Business rule EnqueueCreateEmbedAction action added

• EnqueueCreateEmbedAction allows to enqueue the creation of an embed for the current content.

• An OutputFormatID is required. The created embed will contain only the output for the format specified. If, at rule's execution time, the output format is not found, the action is skipped.

• Optional parameters for the output conversion can be set (ConversionString,LockDeliveryOptions).

• Embed's name is optional. If not filled, a name will be generated in the form 'Embed_{RuleID}'. Variable supported.

• Embed's description is optional. Variable supported.

• ExpirationDate of the created embed is optional and it should be a variable or a string representing a datetime in ISO format with or without milliseconds 'yyyy-MM-ddTHH:mm:ss(.fffffff)K'.

• It is possible to set a variable, specified in StoreIn where the url of the future embed is stored.

See PictureparkSwagger.json

BusinessRule

FieldValueCondition

Business rule FieldValueCondition condition added

• FieldValueCondition allows to check the current value of a content's field and optionally compare it with an expected value.

• If no ExpectedValue is set, the condition matches if there is any value in the content's field identified by the FieldPath property. If there is no value in the content's field, the condition will not match.

See PictureparkSwagger.json

Metadata

FieldDynamicView

New field type added

• Stores information to search for related items in the system

• No per-item data is stored in Picturepark

• Data of related items cannot be used for indexing

See PictureparkSwagger.json

Metadata

ShowRelatedContentOnDownload (DynamicViewFieldUiSettings, RelationUiSettings)

New display setting

• Instructs Picturepark admin UI to offer related items for download

See PictureparkSwagger.json

Metadata

GET /v1/Schemas/many/sortFieldsBySchemaType?schemaTypes=...

New endpoint to provide available fields for sorting

• Accepts types Content, Layer and List

See PictureparkSwagger.json

OutputFormat

PUT /v1/outputFormats/{id}/permission, PUT /v1/outputFormats/many/permission

New endpoints to change OutputFormat.ViewForAll

• ViewForAll can now be changed for all formats (static & dynamic)

• Enpoint for single & many update

See PictureparkSwagger.json

Content / Commenting

Multiple new endpoints and contracts

Comments can be added/edited/removed on contents

The following new endpoints were added:

• GET /content/{contentId}/comments/{id} to access a comment

• POST /content/{contentId}/comments to add a comment

• PUT /content/{contentId}/comments/{id} to edit a comment

• DELETE /content/{contentId}/comments/{id} to delete a comment

• POST /content/{contentId}/comments/search to search comments

The Comment contract contains the following:

• Id – comment ID

• ContentId – which content the comment is made on

• Message – what is the comment's message

• ParentId – if the comment is a reply, this will be the ID of the original comment

• Audit – audit information who and when created or modified the comment

Other respective contracts were also added, please see the SDK link to the right or the API documentation.

See CommentTests.cs or Contract