DFS 9.3.0 - Keeping the Silo Updated

In DAM For Sitecore 9.3 we have shifted technology from pulling updates to pushing updates. In the previous versions of the module we had a hook which ran every minute. The purpose of this background process was to listen for changes in the DAM and then subsequently make sure that the changes was synchronized into the silo. This feature has been deprecated.
Now we have changed this to an event driven architecture. The Digizuite DAM will send out notifications to Sitecore whenever something has changed to an asset or some metadata and Sitecore will then automatically update the content.

In order for Digizuite DAM to notify your Sitecore instance, you have to register what we call an integration endpoint. 

The synchronized silo, will automatically be kept up to date by the system. This page attempts to give some insights to this:

In the ../App_Config/Include/damforsitecore/DFS.Connect.config configuration file, there is a "hook", which is a timer that by default runs every minute. The purpose of this background process is to listen for changes in the DAM and then subsequently make sure that the changes are synchronized into the silo. You may change the interval between when the timer looks for changes in the DAM.

You may also stop the timer completely if you wish. This is done by commenting out the configuration entirely (practically removing it). If you choose to disable the timer, then you have to manually synchronize the DFS Silo every time a change is done in the DC to have the silo up to date.

This is how the timer (hook) looks in the configuration file:

<hooks>
	<hook type="DFS.Connect.Hooks.DetectDamChangesLoader, DFS.Connect">
		<param name="agent" type="DFS.Connect.DetectDamChangesAgent, DFS.Connect">
			<param name="repository" ref="DFS.Connect/assetSiloRepository" />
		</param>
			<param name="interval">00:01:00</param>
	</hook>
</hooks>