Table of Contents
Picturepark San Salvatore Release
Scheduling Business Rules, creating unique identifiers, and preparations for more to come this year.
Table of Contents
,The Picturepark Content Platform is released in its newest version.
- Version: San Salvatore Release (10.9)
- Date: 6-Mar-2021
- Platform: {name}.picturepark.com
-
Main changes:
- Scheduled Business Rules
- Number sequences for creating unique IDs.
- Preparations for upcoming releases.

Monte San Salvatore is a popular sightseeing destination near Lugano, the largest city in Ticino, in the Italian-speaking part of Switzerland. With its peak measuring 912 meters above sea level, this is more of a hill than a mountain, which might well have been the reason Picturepark staff selected San Salvatore: it’s a fitting name for a release that contains a good amount of “under the hood” preparations for a major upcoming release later this year.
Release Details
These are the final release notes.
Scheduled Business Rules
Send reminders or notifications, publish or archive content, and automate much more at predefined dates and times using scheduled Business Rules.

See what you can do with Scheduled Business Rules
Business Rules are a powerful and flexible way to automate the management of your content and metadata in Picturepark. With this release, we introduce schedules for Business Rules that enable you to trigger Business Rules at predefined date and time intervals. Previously, Business Rules could only be triggered by user activities such as a user importing or updating content.
Scheduled Business Rules open a new array of automation possibilities, for example:
- Informing teams, such as Sales, every Monday about new product literature.
- Hiding content that is nearing license expiry dates, and proactively informing the content owner.
- Publishing content to select stakeholders based on predefined schedules and other criteria.
- Archiving content by a predefined end-of-life date, e.g., your products.
- Tagging content “New” when it isn’t older than a few days, or as “For review” when it’s years old.
- Reminding content suppliers to complete their tagging if it wasn't done properly after import.
- Sorting out content that needs a check, e.g., when faces are detected without consent data.
To create a scheduled Business rule that, e.g., “locks” content on the day of expiry and informs the owner of the content, you need to do the following:
- Create or reuse a Business rule that changes the content permission by adding a permission set that restricts access to content to certain users. Use “Schedule” as a trigger point.
- Create or reuse a Notification based on an existing or new email template, informing the owner that the content has expired and was consequently locked, so he might want to check it manually.
- Now, create a Schedule by defining the execution time intervals, a search string to query all content items that are expiring (based on a corresponding expiry date field), and assigning the Business Rule (from step one) to execute each time the interval occurs.
- Test the Schedule by triggering it manually and applying it to a test Content Item only (e.g., by filtering for that item for testing purposes).
The above Schedule could also be used to trigger other Business Rules at the same interval. For instance, if the schedule is set to run every day at 7 AM CET and you also wish to release certain content by then, you can do so by assigning another Business Rule to the same Schedule.
Additional options and best practices for creating Schedules, Business Rules, and Notifications are available in the updated Administration Manual. Especially noteworthy are:
- The minimum accepted interval time is 15 minutes. The powerful cron job syntax is used for scheduling, e.g., to run jobs recurrently every hour, every Friday, the first day of the month, and more.
- Schedules are executed at an approximate time. If you set a schedule to 07.00 AM CET, it will be executed exactly at that time, but the Content Items might be offset depending on the defined search query, the number of Content Items to be processed, and the system's overall load.
- If processing of the items takes a long time and overlaps with the next interval, then the execution of that next interval will be skipped. For instance, if you are using 15-minute intervals and the processing takes 20 minutes, then the next execution will happen 30 minutes after the one that took longer. Filters should be used to narrow down Content Items to prevent overload and long processing times.
Sequential Numbers for Business Rules
Create customized identifiers for easier reference of your content, based on metadata classification and sequential numbers for Business Rules.

Note: The following content is available in English only.
How You Can Use Sequential Numbers
Unique IDs enable users and integrated systems to quickly identify a Content Item. Picturepark uses GUIDs, which are globally unique but therefore rather lengthy. For quick reference, a shorter number will usually be enough, which is why this release introduces new sequential numbers that can be created and applied using a Business Rule action. Applications include:
- Easier content referencing for users and machine processing.
- Counting new content and ranking it in the order it was added to Picturepark.
- Automatically generating new product or content codes, when creating a new item.
For creating a new sequential number that, for example, counts up content and makes it identifiable as “Picturepark” content, the following steps are required:
- Create a new sequential number by defining the start number and format (for example, “PP-” for Picturepark, used as a prefix).
- Create or modify a Business Rule by adding the corresponding action to retrieve a new sequential number and then assign that number to a metadata field of a Layer.
Best practices for creating sequential numbers and Business Rules are available in the updated Administration Manual. Several small bug fixes were applied to improve usability. Especially noteworthy is that, for now, sequential numbers can only be assigned to Content Items (not, for example, to List Items).
Various Other Changes & Improvements
For All Users
- Several small bug-fixes were applied for improving the usability.
For Admins
- Business Rules can now be triggered by multiple trigger points, such as when content is created or updated, the assigned file is replaced, or triggered by a schedule (see Scheduled Business Rules above). This greatly reduces the number of Business rules that need to be created separately.
- Caches are now built in parallel, which speeds up their creation, especially in large-scale systems where many List Items are frequently changed. Previously, this resulted in delays when, e.g., auto-tagging content using product or other identifiers, as Microsoft will end support for it
- Search suggestions, display of filters, and search in filters can now be enabled or disabled for fields in the Content Browser and List Item filters. This allows Admins to better control in which fields search suggestions are shown, which fields will be displayed in the Content Browser and List Item filters and which filters will have a search.
- A warning is shown when deleting a user role that is used in a permissions set requiring Admins to confirm the deletion explicitly.
Changes to API & SDKs
Please note that the following API changes and SDKs are tentative and may change until the release date.
With the upcoming Picturepark Release “San Salvatore” (10.9), we will also introduce some API Changes. Please find details here.
Please check whether those changes will affect your integration and adapt your Source Code accordingly. If you use our SDKs or samples like the Content Portal, we recommend updating to the latest version:
- Picturepark.SDK.DotNet
- Picturepark.SDK.TypeScript
- Picturepark.SDK.Samples (including Content Portal)
If you want to test your changes in advance, we can provide a test account that runs already on the new version, for free or a charge, depending on your subscription plan.
Changes to System Requirements
From April 2021 onward, we will no longer support the Microsoft Edge browser (version 18, non-Chromium version), as Microsoft will end support by the end of March 2021. See additional information on Edge support by Microsoft: Consult our documentation to see which Web Browsers are supported for the Picturepark Content Platform.
Bug Fixes
Aside from various improvements to the system's overall stability, bug fixes have been applied to the backend, along with updates to the versions of the components we use. The following bugs have been fixed with this release:
- Fixed a bug that resulted in video and audio files only being played back once until the page was refreshed.
- Fixed a bug that resulted in text overflow in the sidebar of the user management when the text was too long for the shown fields.
- Fixed a bug that prevented Monaco editors from loading when editing a Content Item with a video or audio file preview.
- Fixed a bug that occurred when scrolling multi-line text fields.
- Fixed a bug where multiline text was cut in the trace log for Business Rules, preventing information from being seen.
- Fixed a bug that meant the contents of nested tagbox fields were not exported via the Excel Roundtripping App.
- Fixed a bug that prevented importing data via the Excel Roundtripping App if only the target Layer had non-indexed tagbox fields configured.