Every business process inside an organization should be sketched out - for internal documentation and training of new employees. How is new content for the website created? How is the product information data updated? Where is the shop data coming from? How to deal with end-of-life-products? 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 to convert your content platform into a content hub, that connects your required business systems and send data where it is needed or required.
The current setup is in JSON only. An interface for configuration will follow soon. The business rules always run in the context of the service user which is the Super Admin. Therefore only Super Admins have access to Business Rules in the Settings Menu. Otherwise users can configure actions as business rules they are not allowed to perform.
In the meantime please contact firstname.lastname@example.org if you have questions or would like to discuss possible business rules for your Picturepark.
If available please send over your workflows and business processes (BPMN) to validate the setup.
Adding or removing permission sets: Removing all or specific permission sets assigned to a content item when a layer is added to the content item. For example, if a user were to add a layer for archiving purposes to a content item, this could then trigger the content to become inaccessible for select user groups.
Assigning to or removing tags or layers from fields based on entries in other fields. This is helpful if, for example, a photographer uploads files and sets certain tags which then in turn add a tag such as “To be approved”. Or, a “multimedia” layer for capturing video-specific information could be added automatically on the upload of video or audio files, already populated with default values such as copyright mentions. This feature only supports static values at the moment, no dynamic values are resolved via the lookup of referenced items; which is scheduled for a later release.
Sending messages to an integration if particular conditions are met. For example, once the above bespoke photographer has completed his upload, an integrated system can become notified about new content that requires approval, e.g tasking a user user with approval via a third party system.
Possible Use Cases
Updates to product images trigger a business process that assigns a "PIM review"-layer which will get an update of product information from the PIM system and a service procider can then send the image to the PIM.
Legal department must recall content after a complaint and assigns a "Stop Now"-Layer. The business rule engine can directly restrict access to content and trigger a potential microservice that removes the content from all online sources.
Content suppliers assign a layer to content where copyright information is missing. This layer holds a trigger called "Get Copyright Details" which can be used to trigger a service provider that would then go and fetch copyright details like source and original title and usage restrictions from the corresponding websites. The business rule can always run for content with this layer or the content creator can trigger the copyright update when the content is used in campaigns to save credits on stock platforms.
Content creators can assign a layer to content they plan to use in campaigns. This layer starts a business process that executes a reverse image search to check if the image is currently in use in competitor campaigns. This information is stored in the research information. The content creator can trigger the image check only for the preferred imagery.
The service provider for image tagging (AI-powered Clarifai) will assign a layer on import that will hold all automatic tags. Those tags require human review and cleanup. After manual cleanup and removal of wrong tag assignments a trigger field will start a business rule that copies the reviewed and correct tags into the real metadata layers that are used in the search.
Production process where a storyboard layer contains all information about the next Instagram stories where a trigger button can then start a business process that informs the story creator inside the story creation tool using a service provider from where it is then uploaded back to Picturepark linked to the storyboard information.
Content uploaded to Picturepark is automatically tagged with the correct location tag based on GPS information in the extracted metadata.
After a new product document is uploaded and defined as approved the business process sets the layer for publication. A service provider informs a third party system that the Marketing team shall create corresponding marketing material out of it.
Field Value Change
Match Regex (the input can be checked e.g. for email address or product codes)
Content Schema Available (check if the content schema is matching a specific schema e.g. trigger a rule for audio files only)
Add, Delete, Reorder
Assign Content Permission Set
Unassign Content Permission Set
Business rules always run in the context of the service user (so FULL privileges), an indication that a business rule might have changed a content can be found in the activity panel where the updating user would be the service user.
If your business rule isn't working first check the platform kibana logs.
You always have to assign a layer before adding text to it, or you provide the to-be-assigned-data in the default values for the layer.
Are there any reserved characters in default value fields that you need to escape?
Required fields need to be added to business rule - if not the business rule process will fail and Kibana logs an error
Check that you don't have a duplicate action twice in the same rule, i.e assigning the same tagbox to the same field.
Make sure you are using the correct json for translated vs not translated fields.
Are your refids in the business rule correct?