To configure a document transfer rule using communication definition metadata

Parent Previous Next

The procedure to configure a document transfer rule using communication definition metadata is as follows:

  1. Navigate to Quick Menu > System > Configuration > Integration Management. The Integration Management window is displayed.
  2. Expand a document store subheading from within the nested EDM System classification structure and select an associated integration service from the alphabetical list (or enter its name into the Search Integrations field). By default the list is filtered to show Current integration services. An alternative filter can be applied using the Select view drop-down field: Expired, Future or All combinations 1.
  3. Click on Communication Configuration. The Communication Configuration tab is activated.
  4. Click on New Communication Metadata. The CRM Communication Metadata Value window is displayed.
  5. Using the Cx entity type drop-down field, select the specific focus area relevant to the communication origin e.g. ASB Case.
  6. Using the Cx data tag drop-down field, select the data merge field to be used as the unique identifier for all generated communications matching the chosen entity type 2.
  7. Using the EDM folder drop-down field, select the target location within the document store i.e. the destination folder within the EDM system where all resulting communications will be stored.
  8. Using the EDM property drop-down field, select the unique identifier value within the EDM system corresponding to the chosen Cx data tag.
  9. Choose an Effective from date for this document transfer rule i.e. the date on which it came into effect 3.
  10. Choose an Effective to date if the document transfer rule is to be reviewed on a specific date or to capture a change of circumstances; a blank field means the rule will be continually valid.
  11. Click on Save. The new document transfer rule is displayed in the Metadata Mapping for Communication Definitions summary table.


Note

1 The Search Integrations field will match against any element of the EDM service description.

2 Only communication data tags linked to the chosen entity type will be available for selection.

3 The Effective from date defaults to the current system date and cannot be left blank.


See related topics...

Alfresco EDM integration management overview

Alfresco EDM integration management quick start guide

To create a new Alfresco EDM integration service