Please contact support@picturepark.com if you have questions or would like to discuss possible business rules for your Picturepark. If available please send over your documented workflows and business processes (BPMN) so we can validate the setup in the Picturepark Content Platform.
|
|
|
|
|
Business Rule Use Cases
|
Best PracticeEvery business process inside an organization should be sketched out - for internal documentation and training of new employees.
All of those processes involving content like imagery, videos, text and pure data require a business process engine. Picturepark offers a business process engine with a set of business rules which allow automation and more sophisticated integrations. Specific business rules like approval workflows or life cycles can be developed to run in Picturepark only or communicate with external systems via API using service providers. Business rules in Picturepark combined with service providers allow you to convert your content platform into a content hub, that connects your required business systems and send data where it is needed or required. |
Debugging Tips
|
Fieldtype HintsCheck the fields and their individual formats and return values. A date-time field condition must have the expected value expressed in YYYY-MM-DD and date time as 2019-09-12T17:03:34.5293947Z for example For Multi Fieldsets or Relationship fields you can add to the condition that the value you are looking for is in the first fieldset by adding the [0] to specify the first fieldset. If you want to search through the second fieldset use [1] e.g: { If you would like the condition to be checked against any of the fieldsets in that field you can use: { Fields (tagbox, fieldsets, relationship) can be erased with “value”:null, This requires the field to be configured with the setting replace to true (“replace”:true). |
Business Rule Limitations
|