Business Rule Settings

May affect your subscription plan limit.






The remove icon deletes the Business Rule and all settings after you confirm your desire to delete.


The JSON is the exact representation of the UI settings. The whole business rule code overview may be helpful for validation of your Business Rule or duplicating an existing Business Rule with adjusted settings.




The display name for the Business Rule per UI language. The language property "x-default" is the fallback language and used the default language setting of the customer.



The Id of the Business Rule cannot be changed once it has been initially set. There are no special requirements except for uniqueness amongst rules. We recommend leaving the ID as rewritten from Picturepark based on your input for Name.



On creation, the Business Rule is enabled by default, if you are preparing a Business Rule to ensure it is disabled until you want it to execute. Picturepark executes enabled Business Rules directly for the items that fulfill the condition.



The description of the Business Rule which helps other administrators to understand the exact behavior of the Business Rule. Describe goal and setup here e.g.

Looks for a Product Code in the Filename (needs to be at the beginning and 14 char, needs to start with either F-, G- or V-). If you find a product code, then assign the product as a tag.

Trigger Point


The user action (action) on a specific item (documentType) in Picturepark that triggers the Business Rule, affecting a defined index.

Execution Scope


The scope where the Business Rule should be executed, which means the underlying index:

  • The MainDoc, means the document in ElasticSearch that carries all information about an item e.g. types, permission, actions, like the CV of the item.

  • The SearchDoc, means the document in ElasticSearch that carries information of an item which is optimized for the usage in the Picturepark search. This includes information set to "include in search". The SearchDoc is optimized in several ways, including saving nested and hierarchical information in a flat structure.

Document Type


The affected type of document in Picturepark, currently limited to:

  • Content: The DocumentType Content means Content Items visible in the Content Browser, this includes File Items and Virtual Items.

Picturepark documentTypes are "Content", "ListItem", "Schema", "User", "ContentPermissionSet", "Owner".



The specific actions happening in Picturepark, which are currently:

  • Create: The action Create means the creation of a Content Item through upload (File Item) or creation (Virtual Item) in the Content Browser.

  • Update: The action Update means the modification of a Content Item through metadata or content edits in single edit, batch edit or through Excel or API. This action does not cover file replacements!

  • Replace File: The action Replace File means the replacement of a file item using the replace file functionality in the toolbar of the Content Item or via API. This action does not cover virtual content updates!




Add one condition for items, so the Business Rule considers them and performs the actions. This one condition can also be a group of AND/OR connected individual conditions.

This will create a kind of collection of items and their values.

images/s/ejklpa/8401/8e8f74c7e2fea2df662fe8d0f5d79ff6ab016336/_/images/icons/emoticons/information.svg Select AND/OR first, to define multiple conditions.




Add one or multiple Transformation Groups. Transformation Groups are conversions of values.

Example: You have a tagbox "products" on a Content Item, linked to the List "Product" which has the following additional attributes (which are again nested):

  • _refId: 8465xxxos

  • product name: CP2020

  • product family:

    • product family name: platform

  • product market

    • product market name: Switzerland

A Transformation Group uses e.g., the fieldpath as input: layer.tagbox-products and converts the whole structure into individual values:

  • output1 = tag._refId

  • output2 =tag.productname

  • output3 =tag.productfamilyname

  • output4 =tag.productfamilymarketname

Those can then be further transformed (in the following Transformation Group) or used in action:

  • Use output4 and look it up in the region list.

  • Action: If you find a match, assign it.




Perform the actions on the collection of items that fulfilled the condition.