Trigger
The Trigger field you can use to trigger a business rule with the benefit that it stores the information about the user who clicked the field and when (date and time), whereas a checkbox "start business rule" would not have any information about user and time.
Trigger Overview
Icon | ![]() |
Behavior | |
Usage | Instead of working with checkboxes, the trigger field can execute a business rule and carries information about the user who triggered and the time and date of the triggering. |
Button text | EN: [Field Name EN] |
Examples |
|
Trigger Value Handling
Picturepark Setup Example | Layer: Auto-tagging (ID: AutoTagging) |
Fieldpath | autoTagging.assignMatches.triggeredOn |
Advanced search for field / field value | _exists_:autoTagging.assignMatches.triggeredOn
|
Use in Display Pattern | |
Use in the business rule as path & field id | Path: Field: |
Returned field value | .triggeredOn returns date time, which must be formatted |
Trigger Field Settings
Nothing specific about the Trigger field settings.
Name | The label of the Trigger field, which should give a clear indication of what the user triggers. The trigger button will have this name too. ![]() Trigger Field Name as Button Text |
ID | The field id is the ID of your field, which is used to link to this field. The field id is always lowercase. The id of the field is set on the creation of a new field, using camel casing. You need the field id for the configuration of filters or display pattern. The ID is automatically created from the name you insert:
![]() You can open the Display Pattern Editor to see the JSON of a Content Item. |
Include in filters | The field setting “Include in filters” allows the field to be added as a filter for content (see Channels Configuration) and the field values to be edited in the Batch Editor (indexed fields). Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit, and by testing your common search scenarios - too much values will not automatically result in better search results. |
Include in search | The field setting "Include in Search" determines whether the field's values should be considered in content browser simple search operations. If this option is not enabled, the search does not consider the values of the field in search operations. This can be useful, for example, if the field is used for internal discussions or work directives that you don't want to affect the search results. Picturepark checks those settings against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit. |
Boost value | The field setting "Boost" will boost the values in the search and helps you define the relevance of the content for your users. The boost parameter increases the relative weight of a term (with higher boost values) or decreases the relative weight (with lower boost values), but the increase or decrease is not linear. In other words, a boost of 2 does not result in double the score. You can select between 1, 10, 25, 50, 100, or 500.
Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit. |