Contacts can be captured in the CRM App using one of the plugins mentioned, causing a corresponding dialog to always appear. Depending on the plugin, this dialog offers extended functionality in addition to capturing contacts.
Capturing a contact in the app
Incomplete records can be updated, regardless of the form in which a contact reaches the capture app (OCR, QR or local contact from the device).
Contacts captured in the business card app or in the context of a fair or visit report can be supplied with offline and online data from the server via the same selector (magnifying glass). Incomplete records are updated in the database from complete attributes in the enterprise system, depending on the data conditions.
The selectors in the recording apps that combine offline data with server records, when opened, show the records set by the server at the initial start of the mask if the server is accessible. Otherwise, it will continue to show the local records.
If the magnifying glass (selector) is pressed for a contact in the recording app, a search can be performed on the offline record using a search string to match or qualify the recorded contact. If no corresponding offline data is found, tap "Reload/Search" (magnifying glass) again for the data to be searched on the server (requires the backend 1.5.100 to provide an initial server context).
By selecting and accepting a contact from the search, the combined attributes from the server (marked in color) appear above the fields in the recording app.
By manually replacing attributes directly in a field (by tapping) or using the toggle (Old/New) for all fields at once, the attributes are merged, regardless of whether it’s offline or online data.
If there is no time to qualify the contacts, or they still need to be verified, the captured contacts should be marked using the Postprocessing necessary switch in the capture dialogs.
Note: The default state of the switch in the mobile app can be set in the back office settings of the app. The value is stored in the PSA_BCR_PST_PRC_DFV server variable.
The contact data will be imported into the enterprise system and entered into the CPPW postprocessing list, where it will have an open postprocessing status.
There is no routing into the CPPW. The convenience of contact postprocessing is not automatically available. Contact data captured using the business card and visit report app is immediately used to create a contact in the enterprise system, and mark it as a duplicate if necessary. Its status is imported.
Participants (persons) entered and marked via the Fair app can be qualified further in the Fair lead import of the Enterprise system. No persons will be found or offered automatically for contact postprocessing.
Note: In any case, the contacts are colored (red) and marked by the "imported" status. Any required postprocessing or duplicate handling is then possible directly for the person in the web client using
Contacts marked for postprocessing from the fair app (switch =ON) can only be entered in a separate intermediate table in the fair lead import in the web client when the Contact postprocessing select function at the fair report is used.
The contact data is not imported but temporarily stored in the intermediate table of the Fair lead import as well as in the intermediate table of the CPPW.
In this case, contact postprocessing is handled in the Enterprise System via a function call from the Fair lead import. On completion, the data qualified in the CPPW is written to the intermediate table of the Fair lead import.
Attention: Only on "Import" of the fair report or appointment (Import appointment function), the data supplied and postprocessed from the Fair lead import is saved as a contact! Note, however, that the function saves the contacts even if their postprocessing status in CPPW is still unchecked, i.e., the traffic light status is red or yellow.