Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Migrating data table values to field values

Updated on September 20, 2021

In Pega Sales Automation for Insurance 8.6, rules using the D_TaskCategories and D_ManageLossReasons data pages are changed to use field values to display Type on the Task screen, and Loss Reason on the Opportunity close screen.

Pega Customer Relationship Management for Insurance 8.6 Post-update Tasks for Pega Cloud services Environments
Modify the overridden rules in your implementation layer that are using the D_TaskCategories and D_ManageLossReasons data pages to display their values in the UI by performing the following steps:
  1. Log in to Dev Studio as an administrator for your implementation layer.
  2. In the navigation pane of Dev Studio, click Records TechnicalActivities.
  3. Search for and open the CreateFieldValuesFromDataTable activity.
  4. Edit this activity by entering the following values:
    1. In the FieldName field, enter TaskType.
    2. In the FVAppliesToClass field, enter PegaCRM-Work-Task.
    3. In the DataTableDP field, enter D_TaskCategories.
    4. In the PropertyToCompare field, enter Name.
  5. Click Save.
  6. Run the activity by clicking Actions Run.
  7. Search for and open the CreateFieldValuesFromDataTable activity.
  8. Edit this activity by entering the following values:
    1. In the FieldName field, enter LossReason.
    2. In the FVAppliesToClass field, enter PegaCRM-.
    3. In the DataTableDP field, enter D_ManageLossReasons.
    4. In the PropertyToCompare field, enter Name.
  9. Click Save.
  10. Run the activity by clicking Actions Run.
  • Previous topic Checking your Pega Sales Automation access roles for the required privileges
  • Next topic Configuring Federated Case Management case types for web mashup

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us