Alfresco Job Run History Nodes
The purpose of this task is to get the Alfresco Node Reference from the Current Job Run History, in order to update an existing document from a previous Job run in Alfresco, rather than creating a new one.
It’s used in Incremental or jobs where the Alfresco connector is being used. This task uses the Source Repository ID from the Repository the document is pulled from, in order to find the document in the Job Run History.
Configuration
Set up: There are no configuration options for this task. It uses the Document’s Source Repository ID in order to find the node Reference in Alfresco. Exception/Requirements: Since the Source Repository ID is used, any source repositories that use a Path Based Source ID will not work if the path of the document changes.
Alfresco Property Mapping Nodes
This task is for getting existing node references in an Alfresco instance, in order to update them, rather than create a new one if the existing file has moved from its original ingestion location. It’s used in jobs where the Alfresco Output connector is used. Typically, in incremental or sync jobs, where changes to a file from a source system need to make it to the node it previously integrated to.
Configuration
How to set up: Provide the query JSON object, which is then sent to Alfresco which will return the matching Alfresco Node Reference, which we’ll use to update the document.
Exceptions / requirements: If the query is too vague, and matches more than one node/document, then none of the documents will be updated. The query has to uniquely find a single node/document in Alfresco.