Skip to main content
LinkedIn
Copied!

Table of Contents

Disabling the Decision Data Store as action state storage on Pega Cloud

New deployments of Pega Customer Decision Hub on Pega Cloud Services are configured to use the Decision Data Store (DDS) to store action state. The DDS data sets manage large and active data from different sources and make it available for real-time and batch processing.

When the DDS is used to store action data, the following features are disabled:
  • Volume Constraints
  • Wait volume overlays
  • Campaign run restarts
  • Direct output to template
  • Prospects

If you want to use these features, you need to disable the DDS as action state storage, and then configure the campaigns and scheduled runs to write data to database tables.

Perform this task during a maintenance window.
  1. Disable the DDS service as action state storage:

    1. In the navigation pane of App Studio, click Settings Application settings Customer Decision Hub .

    2. Clear the Use Decision Data Store for Action state storage check box, and then click Save.

  2. Go to Pega Customer Decision Hub portal to switch existing Campaigns and Next-Best-Action Designer Scheduled runs to write to database tables:

    In progress Campaigns and Scheduled runs continue to run and store Action data in the Decision Data Store.
    Choices Actions
    For each existing Scheduled Run (both Primary and Secondary schedules included)
    1. If the Scheduled Run is running, suspend it by going to: Next-Best-Action Designer Channels .

    2. Click More Suspend .

    3. Edit the Recurrence section and set a valid recurrence schedule.

    4. Launch the Scheduled run by clicking More Run .

      New runs for this Schedule will now store Action state data in database tables.
    For each existing Multi-channel Campaign
    1. If the Campaign is running, suspend it by going to Campaigns menu in the left navigation pane and clicking on Campaigns

    2. Choose the individual campaign you want to suspend, and click More Suspend .

    3. Click the Edit button, and then update the Engagement section to a valid recurrence schedule if needed.

    4. Save the Campaign.

      You must edit and re-saved the Campaign even if there is no change required to the schedule.
    5. Launch the Multi-channel Campaign by clicking the Run button.

      New runs for this work object will now store Action state data in database tables.
    For each existing Outbound Campaign
    1. If the Campaign is scheduled for the future, suspend the Campaign by going to Campaigns menu in the left navigation pane and clicking on Campaigns

    2. Choose the individual campaign you want to suspend, and click the Suspend button.

    3. Click the Edit button, and then Save the Campaign.

      You must edit and re-saved the Campaign even if there is no change required to the schedule.
    4. Schedule the Outbound Campaign by clicking Actions Run .

      The Campaign Run for this work object will now store Action state data in database tables.
  3. Stop the DF_ProcessWaitingActions real-time data flow to free up resources.

    Perform this step only when all runs have been completed and there are no waiting Actions that are written to the Decision data store. Performing this step sooner could result in runs not completing properly and waiting Actions not expiring as expected.
    1. In the header of Dev Studio, in the search box, search for the class name Pega-DM-DDF-Work.

    2. Click Pega-DM-DDF-Work.

    3. Filter the ID column by DF_ProcessWaitingActions.

    4. Open the remaining instance with the ID DF_ProcessWaitingActions and then click Stop.

Did you find this content helpful?

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