Campaign Management(CRM #70000080)

Learn about configurations for Campaign management.

Graph

A campaign graph has been implemented into the tree to quickly navigate inside the campaign. The graph node shows the ‘CORE_CM_CampaignGraph’ form.



Rights & Triggers

  • Rights for Info Area Campaign (CM)

    The info area is defined in the main right as visible. New, update or delete of companies is not denied.



    It is also defined that records with tenant 9000 are not allowed to be updated or deleted as they are part of the template and should be “upgradeable”.





  • Trigger for Campaign (CM) Info Area

    CORE_CM_DV Trigger

    This trigger is used to set the current rep as the responsible rep for the Campaign (CM) when the record is created. The action used is “Edit/update” (not default values) – as otherwise it would not work when records are created from a template.



    The trigger can be overwritten in a child right:



  • Rights for Marketing Activity (AK) Info Area

    The info area is defined as visible in the main right but the actions new, update or delete are disabled for this infoarea.



    It is also defined that records with tenant 9000 are not allowed to be updated or deleted as they are part of the template and should be “upgradeable”.





  • Trigger for the Marketing Activity (AK) Info Area

    Trigger CORE_AK_DV

    This trigger is used to set the current rep as the responsible rep for the Marketing Activity (AK) when the record is created. The action used is “Edit/update” (not default values) as otherwise it would not work when records are created from a template.



    The trigger can be overwritten in a child right:



  • Rights for the Execution (Marketing Activity) (AD) Info Area

    It is also defined that records that belong to marketing activities (AK) with tenant 9000 are not allowed to be updated or deleted as they are part of the template and should be “upgradeable”.





  • Trigger for Execution (Marketing Activity) (AD) Info Area


    CORE_AD_DV Trigger

    This trigger is used to set the default values when an Execution (Marketing Activity) (AD) is created that is NOT based on a template.



    The trigger can be overwritten in a child right:



    AD_UPD_SetExecutionRep Trigger

    This trigger is used to set the u7Server user of the current tenant for the record. The action used is “Edit/update” (not default values) – as otherwise it would not work when records are created from a template.

    The u7Server creates (among other tasks) messages and they are produced in a specified language (this language is set in the registry entry for the u7Server with the “–l” flag).

    In a project: If a new tenant is created for an installation, then this trigger has to be adapted:



CORE_AD_UPD_ExecuteMarketingActivity Trigger

  • Trigger for Target Group (Marketing Activity) (AG) Info Area CORE_AG_UPD_SetInactive Trigger

    This trigger is used to set the “Inactive” flag in an AG record. Thus the user does not have to touch each single record and set the flag, but he has to select several records and use the button. The trigger is called via the “CORE_AG_SetInactive” button.



  • Rights for Response (Marketing Activity) (AN) Info Area

    The info area is defined as visible in the main right but the actions new, update or delete are disabled for this infoarea.



    It is also defined that records that belong to marketing activities (AK) with tenant 9000 are not allowed to be updated or deleted as they are part of the template and should be “upgradeable”.





  • Rights for Response (Marketing Activity) (AO) Info Area

    The info area is defined as visible in the main right but the actions new, update or delete are disabled for this infoarea.



  • Rights for the Statistics (Marketing Activity) (AX) and Rep (Marketing Activity) (AI) Info Area

    The info area is defined as visible in the main right but the actions new, update or delete are disabled for this infoarea.



Label Formats

German (Base)



English (UK) (BASE)



English (US) (BASE)



These labels are used based on the label value in the FI or KP record and therefore forms the content of the pre-defined CORE_German_Invitation.doc and CORE_English_Invitation.doc documents.

Campaign Templates

The following campaign templates are defined:

  • Documents

    CORE_ProductInformation_E-Mail.html (StNo: 10000 INo: 186)

    The document is designed to send the e-mail in the recipient’s language. Due to the fact that the “Activity_E-Mail” marketing activity format has set the “Language transformation” flag to true:



    …the value of the “Language” field is transferred according to the document and an IF-ELSE statement delivers the correct text to the e-mail sent.

    E-Mail Template

    Recipient with “German” Language

    Recipient with “English” Language or any other language

    <%$IF KPLanguage = 'Deutsch'%>

    Betreff: Produktinformation

    <%$ELSE%>

    Subject: Product Information

    <%$FI%>




    If you want to add another language you would have to extend the IF-ELSE statement in the following way:

    <%$IF KPLanguage = 'Deutsch'%> Betreff: Produktinformation <%$IF KPLanguage = 'Français'%> Object: Validation <%$ELSE%> Subject: Product Information <%$FI%>

    The value in the IF-ELSE statement must be in the language of the user’s catalog value.



  • Default Values

    The following default value formats are defined



  • Catalogs
    • Fixed Catalogs

      5 Status (Aktivität (MA))



      6 Ergebnis (Aktivität (MA))



      Code 4:

      TE_German: Möchte keinen Kontakt mehr

      TE_English: Does Not Want Contact Any More

      9 Wichtigkeit (Aktivitat (MA))

      40 Ausführungsstatus (Marketing-Aktivität (AK))



      44 Status (Marketing-Aktivität (AK))



      46 Prozess (Protokoll (Marketing-Aktivität) (AO))



      Einheit Reaktionszeit/SLA (Angebot (PR))



      Durchführungsart (Durchführung (Marketing-Aktivität) (AD))



      Note: The grey text should be locked, i.e. not visible.

      TE_German

      Sprachunabhängig / TE-English

      Einmalig: Zielgruppe durch Abfrage erstellen

      One-off: Create target group based on query

      Einmalig: Selektion nicht durchführen

      One-off: Do not execute selection

      Einmalig: Zielgruppe aufgrund von Reaktion/ Neuzugang erstellen

      One-off: Create target group based on response / new entry

      Wiederholt: Zielgruppe jedes Mal neu durch Abfrage erstellen

      Repeated: Create target group based on query every time new

      Wiederholt: Selektion einmal durchführen

      Repeated: Create target group based on selection once

      Wiederholt: Selektion nie durchführen

      Repeated: Never execute selection

      Wiederholt: Zielgruppe aufgrund von Reaktion / Neuzugang erstellen

      Repeated: Create target group based on responses

      Wiederholt: In Paketen durchführen

      Repeated: Send in packets

      Wiederholt: Zielgruppe jedes Mal durch Abfrageergebnisse erweitern

      Repeated: Extend target group based on query results

      55 Status (To-Do (TD))

      60 Basis (Durchführung (Marketing-Aktivität) (AD)



    • Variable Kataloge

      372 Kamp.-Typ. (Marketing-Aktivität)



      20 Marketing-Aktivität



      161 Variante (Marketing-Akt.)



      52 Reaktion (Marketing-Aktivität)