Skip to main content
This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.
LinkedIn
Copied!

Table of Contents

Configuring email signature parsing for contacts in Pega Sales Automation

Pega Sales Automation™ uses natural language processing (NLP) on a contact's email signature to create default contact values. For example, NLP can extract the first and last name, title, and phone number from a contact in Outlook add-in based on the email signature and add these values to a Pega Sales Automation contact.

After you configure the integration between Microsoft Outlook and Pega Sales Automation, configure signature parsing to use NLP to fill out contact information.

After you configure signature parsing, when users add contacts to either Pega Sales Automation or Microsoft Outlook, the following fields populate based on the signature of the email that is already in the system: first and last name, title, mobile phone number, and work email.

Configuring signature parsing for Pega Sales Automation 8.4

You must have administrator access to perform these steps.
  1. Log in to Pega Sales Automation as a system administrator.
  2. In the header of Dev Studio, click your application name > Channels and interfaces.
  3. Create an Email channel.

    For more information, see Configuring Intelligent Virtual Assistant for Pega Sales Automation.

  4. Open the new Email channel.
    1. On the Behavior tab, in the Text analyzer section, select the Record training data check box. 
    2. Click Save.
    3. Click Open text analyzer rule.
    4. In the Text extraction section, verify that the pySystemEntities and SASystemEntities models are listed.
    5. If these models are not listed, add them by clicking Add text analyzer.
    6. Click Save.

Configuring signature parsing after upgrading to Pega Sales Automation 8.4

You must have administrator access to perform these steps.
  1. Log in to Pega Sales Automation as a system administrator.
  2. In the header of Dev Studio, click your application name > Channels and interfaces.
  3. Open an existing email channel that you want to associate with signature parsing.
  4. On the Behavior tab, under the Text analyzer section, select the Use advanced configuration check box.
  5. In the Text analyzer section, click the Switch to edit more icon on the right side of the iNLP text analyzer.
    1. In the Text Analyzer type field, select iNLP.
    2. Select the Enable model training check box.
    3. Click Submit.
  6. In the Text extraction section, delete the existing pyNER model by clicking the trash icon on the right side of this extraction model.
  7. Add the pySystemEntities and SASystemEntities models by clicking Add extraction model.
  8. Click Save.

Further customizing the shipped entity models

You can further customize the pySystemEntities and SASystemEntities entities models to fit your business needs.

This task is performed by developers.
  1. In the navigation pane of Dev Studio, click Records > Decision > Decision Table.
  2. Search for and open the pyAllowedNLPShippableRulesets decision table.
  3. Save the pyAllowedNLPShippableRulesets decision table into your implementation layer.
  4. In the table, perform the following steps:
    1. Add your rulesets under the Rulesets column.
    2. Set the return value to true.
    3. Click Save.
      "Shippable"

      Configuring the pyAllowedNLPShippableRulesets decision table

  5. In the navigation pane of Dev Studio, click Records > Decision > Decision Data.
    1. Search for and open the SASystemEntities model.
    2. Download the training data in every language by clicking Download.
      "Download"

      Downloading the training data files

  6. In the navigation pane of Dev Studio, click Records > Technical > Binary File.
    1. Create a binary file for each model for each language that you want to use, by clicking Create > Technical > Binary File.
    2. In the Label field, add NLPDefault.
    3. In the App Name (Directory) field, add information in the following format: <Rule purpose>_<language>, for example, pyNER_English.
    4. In the File Type (extension) field, enter zip.
    5. Save the file in the implementation ruleset.
  7. Open the binary file and upload the training data .zip file for each language by clicking Upload file.
The extraction of entities depends on the training data that you feed to the model. The pySystemEntities model is a Pega Platform model, whereas the SASystemEntities model is a Sales Automation model.
Suggest Edit
Did you find this content helpful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us