...
In the automated workflow, you need to do a bit more to get it working. In the image below, I’ve shown the steps that one needs to instantiate a business workflow.
...
Step 1: Trigger
This part is the same as with all other automation workflows. Simply put, this is the action that triggered this automation workflow.
...
This part is optional, but needed if you e.g. want to control who should be able to instantiate the business workflow. As written in the business workflow section in the top, transitions from the created note must not contain an “execution“ constrant constant - meaning that everyone could potentially initialize the business workflow. (Please note that, you should always aim for designing the system to not even allow such users to trigger the automation workflow trigger)
In the image show, there’s a check on the upload computer. This is made to ensure that profile images, logos, and splashscreen (introscreen) images/videos aren’t triggering the workflow. When you upload normally, the “upload computer name“ you set in the MM’s config manager via the DC will make this pass. If you instead upload a new profile image, a new splash screen image/video, or logos it will append “ profile“, “ splashscreen“, and “ logo“.
Step 3: Extract itemGuid
As the last step (5) requires an entity guid, which is created from concatenating a string with an itemGuid, we need to extract the itemGuid. This is done with “Item ID to Item GUID”.
...