Once Digizuite, MediaManager and Digibatch has been been installed, there are some recommended post configuration that must be conducted.
Publishing
With 5.5.0, Digimonitor has been removed. Digimonitor was the old Automation engine responsible for publishing assets to other channels, thereby making them available other places than only in the backend Digizuite UI. Digimonitor came with a set of Automations, however, the new Automation engine does not. Therefore it is important to configure these publish automations yourself.
Usually publishing automations are split into two sections
When some metadata changes (e.g. tree), publish/unpublish the asset
When assets are uploaded
For technical reasons, both cases needs to be covered. Usually that gives you a workflow with 3 triggers:
LocationStateChanged (I.e. asset is uploaded)
Metadata added
Metadata removed
An example of this, looks like this:
...
In the specific cases, branch 1 & 2 covers the metadata add/remove case and respectively adds/removes the assets from a channel folder.
The last branch listens to the location state changed event and if the metadata field is set, moves it to the folder. One could add the opposite case here as well as it may be needed, specially if many assets are replaced.
There are many ways in which this can be conducted, however, in general the automation triggers on something and calls the Move asset to folder action which is the publishing.
We refer to the documentation on this for a better overview