- Alfresco Path: The output folder path in your alfresco repository.
- Binary Output Path: Binary Output Path for Azure or S3. If populated and no Secondary Auth Connection is present, will output to the filesystem.
- Create Content URL Always: Only used for Manage In Place (MIP). Federation Services will generate an Alfresco Content Url based on a number of configuration:
Be aware that these are checked in order
- If the content service connector is set in the Details tab the content url will be connectorId://documentId
- If the document has the metadata field simflofy.contenturl. It will be checked for validity and used.
- If the secondary auth connection is for Amazon S3 the content url will be s3v2://documentId
- If the secondary auth connection is for Azure Blob the content url will be azb://documentId
- If none of these are true, the content url will be store://documentId
Advanced Settings
- Included Un-Mapped properties: Add all properties from the source to the target metadata. If unchecked, only mapped properties will be added
- Do not convert metadata keys to lowercase: Federation Services converts all type and field values to lowercase by default. If this is checked all fields will keep their original case
- Debug mode: Each document’s metadata will be output as json file to a specified location
- Debug Path: Appears when debug mode is active. A path on the filesystem where the debug JSONs will go.
- Alternative Thread Count: If using a secondary auth connections, this will control the number of worker threads. Should never be set to 0, or the job will fail
- Multi-Value Separator: Multi-value fields will be combined into a list using this separator
- Replace Existing Content: If a document already exists at the output location, it will be overwritten
- Use File Hash: If checked, the file keys for documents will be an SHA Hash of their parent path + file name + modified date plus the extension ‘.sim’
-
Process ACLS: Requires the use of the ACL Mapper or ACL
Conversion Task.
- Will transform the product of these tasks into Alfresco’s format for processing
- Inherit ACLS: If processing ACLs, the parent folder’s permissions will be merged into the list of acls.
- Include Aspects with no Field Mappings: Mapped aspects will be applied even if none of the aspect’s fields are present
- Aspect Remove Field Mapping: Takes a JSON string. Remove aspects if the listed fields are not present. The example of the UI:
{"myaspect:two":["field1","field2"],"myaspect:one":["field1","field2"]} Meaning that if field 1 or field 2 is not present, do not add the aspects.
- Date Format: Date field mappings will be formatted this way.
- Date Time Format: Date/Time field mappings will be formatted this way.