Delegate individual letter reminders to the deputy

The employee assignment can be pre-populated on activities side in the document creation wizard for the single letter area (quotes, contracts or document-capable entities). Pre-population offers the following advantages:

• Pre-population of the "Delegated to" an "Delegated from" employee and others

• Custom employee pre-population per protocol and reminder activity

• The following values can be suggested for pre-population

  • Employee token, e.g.: 'KM'

  • Variable 'USER'
    Token of the currently logged in user

  • Variable 'USER_DEPUTY'
    Shortcut of the deputy if the user has logged in as a deputy.
    If a user logs in under his account, the variable 'USER_DEPUTY' returns the shortcut of the currently logged in user (analogous to the variable 'USER')
    Examples:
    If user A logs in as a deputy of user B, the variable 'USER_DEPUTY' contains the shortcut of user B.
    If user A logs in without deputy control, variable 'USER_DEPUTY' contains user A's shortcut.

  • Employee variables from the mapping of the document template
    In the mapping of the document template, the administrator can define employee variables for the employee assignment. That means that not only fixed employee tokens can be used, but also employees from the selection results sub section, e.g. the KAM (key account manager) of the business partner.
    The mapping of the document templates offers at most the following employee variable names:
    

    SERIALEmployeeOffice, SERIALEmployeeSales, SERIALEmployeeKey, SERIALEmployeeQuote, SERIALEmployeeExtra1
    SERIALEmployeeExtra2
    Prerequisite for the use of one of these employee variables is that these exist in the mapping of the document template. The employee variable will otherwise be deemed invalid and the entry will be discarded.

  • Where one employee token is used multiple times (e.g. as delegated-to and delegated-from) or where the employee token is resolved multiple times due to the use of variables, the employee entry will still only appear one time in the employee assignment. The attributes delegated-to and delegated-from remain intact.

  • Invalid entries (invalid employee token, employee variables, etc.) are ignored.

  • The previous pre-population will be maintained if no individual pre-population for the employee assignment exists. This is shown as follows:

    • Delegated to: SERIALEmployeeQuote (for a quote document), otherwise never set

    • Delegated by: Token of the currently logged in user

• The pre-population of the employee assignment occurs per document type, i.e. for all quotes (no pre-population per template!)

• The configuration is carried out via PropertyMapper entries, which have to be executed once directly on the database via SQL (analogous to the previous procedure for single letter document generation).
  The property mapper entry consists of the activity page type, the employee type, and the document type. That means:

  • ID.Propertymapper = Typ_der_Aktivitätenseite$Mitarbeitertyp

  • Property.Propertymapper = Document type

  • PropertyValue.Propertymapper = Employee token or variable or list

Concrete examples