The Exists action performs two tasks: The first checks whether an element has already been filed to the connected repository. The second task reads the GUID of the archived element and save it to the work area of the element.

The first task in the Exist action can be performed with the GUID in the element field "EloXcArchivedExt", which requires a previous application of CheckinDef, or in Exchange archiving, can also be performed with the element field "PidTagSearchKey". The latter is only possible if "PidTagSearchKey" was transferred to an index field in the keywording at the time of archiving.

If the element is found with either of these tasks, the GUID of the SORD is automatically transferred to the work area of the element and can be processed with CallExternalDef, for example. Previously determined GUIDs in the work area are overwritten.

Click the Advanced button in the Options area to open the advanced configuration settings.

Name: Enter a name for the Exists action.

Keyword: Specify the group name of the index field.

MatchGuid: Select this option if you want to perform an additional check to determine if an entry exists in the repository.