Viewing and Importing Participants

Enterprise Archive creates an entry in the Participant page whenever the participant details are imported or ingested. Clicking the listed participant in the Participant page displays these details.

The history of a user or a participant is tracked in the following cases:

  • When a Enterprise Archive User becomes a participant—This happens when details of an existing user are ingested or imported on the same identity ID. In this case, history indicates all changes from USER to SYSTEM.

  • When a participant becomes a Enterprise Archive user—This happens when an ingested or imported participant information already exists, and a user with the same identity ID is created. In this case, history indicates all changes from SYSTEM to USER.

  • When a Enterprise Archive user's attributes are updated using the Enterprise Archive UI, the Source field in the History tab displays the following updates:

    • SYSTEM to USER, if the user was previously an ingested or an imported participant and later converted to a Enterprise Archive User.

    • Source value will remain as “USER”, if the user was previously a Enterprise Archive user and then the attributes (such as First Name, Last Name and so on) have been edited.

      Note

      In this case, only the latest values of the user object are displayed.

  • When a Enterprise Archive user's attributes are updated by the import or ingestion process, the Source field in the History tab displays the following updates:

    • SYSTEM to SYSTEM, if the user was previously an ingested or imported participant and now the participant information has been updated.

    • USER to SYSTEM, if the user was created through the Enterprise Archive UI and then converted as Participant through ingestion or import.

      Note

      User attributes can be edited or updated several times with different values by either ingesting or importing user attributes with same identity ID as key.

Participant/Participant Group behavior on Distribution Lists

When messages come in that have a Distribution List (DL) included in the To or Cc fields, the DL name gets created in Enterprise Archive as a Participant. However, if the DL name is only on the Bcc field the Participant does not get created.

  • DLs coming in from Exchange get expanded and each member written in Enterprise Archive as a participant, as well as the DL itself gets written as a participant AND participant group. However, the DL as a participant and the DL as a Participant Group do not contain any members. The DL will just be an empty participant and participant group.

  • DLs coming in from migrations or third-party are handled separately and depends on the nature of the XML coming from the third-party app on how things are handled.

Auto-Mapping Participants

Enterprise Archive is enhanced to auto-map participants added through ingestion (most recent) to participants added using CSV import.

Enterprise Archive auto-maps the participant using the Network + EndPoint ID initially. When Enterprise Archive is unable fetch Network detail, only the Endpoint ID is considered to auto-map the participant.

In case the application is unable to fetch both Network and Endpoint ID, an unmapped participant (new participant) is created.

Note

Messages are mapped only when the endpoint is in the format name@domain.com, adhering to standard email address conventions. Formats such as X.400 and X.500 are not currently supported, resulting in messages with these formats being archived but remaining unmapped.

Unmapped Participant Naming

  • For Tier 1: Unmapped participant IDs in the Tier 1 flow are generated using the following syntax: EndPoint ID+__auto.

  • For Age Based Promotion: In the ABP flow, unmapped participant IDs are generated using the following syntax: unmapped__+EndPoint ID.

For example, in the Tier 1 flow, if the network EndPoint ID is 12345, the generated participant ID will be 12345__auto. Similarly, in the Age-Based Promotion flow, if the network EndPoint ID is 67890, the generated participant ID will be unmapped__67890.

This section provides information on viewing and importing participants in Enterprise Archive: