RPI object caching behavior best practices

Purpose

This guide explains how to manage changes to the objects used in RPI campaigns and what those changes mean for active workflows. It covers specific scenarios when updates take effect right away in ongoing workflows, and when a workflow needs to be restarted or recreated for the changes to apply. Understanding these guidelines is key to keeping things running smoothly, whether in steady-state operations or during bigger transitions like migrating from RPI v6 to v7.

Key use cases

1. Ongoing campaign management:
   When engaged in steady-state campaigns, you may need to update various elements of your campaigns. This can include refining selection and audience criteria to better target your desired demographics, refreshing content to keep it relevant and engaging, and adjusting channels to optimize outreach and effectiveness. Additionally, other campaign elements may require modifications to ensure that the overall strategy remains aligned with your goals and market trends. Continuous assessment and adaptation are key to maintaining the success and relevance of these ongoing campaigns.

2. Platform migration:
   When transitioning from RPI v6 to v7, the migration process can be complex and requires careful planning and execution. You’ll need to update your ECPs (External Communication Protocols), channel configurations, and database schema names, among other technical specifications. Understanding which changes require a complete rebuild of workflows ensures a seamless and efficient transition. This knowledge helps to minimize disruptions during the migration and maximizes the benefits of the new platform features.

Object configuration update behavior

The following table provides a comprehensive summary of how RPI manages updates to object configurations across various object types and campaign scenarios.

Definitions

• Always refresh:
  RPI automatically refreshes these objects to ensure that modifications made to the object are instantly reflected in both ongoing and newly initiated workflows. This guarantees that users have access to the most current data and functionality.

• Values and results update, cannot change input selection:
  While the values and results pertaining to the object, such as those found in cell lists, are continuously updated to reflect the latest changes, the input selection criteria for running workflows remain fixed and cannot be altered. This design choice ensures stability in the workflow execution, preventing any unintended disruptions that might arise from changing input parameters mid-process.

Best practice recommendations

1. Plan object updates carefully:
   Before making any modifications to objects that are currently in use within active campaigns, consult the relevant table to determine whether the changes you intend to implement will be reflected immediately or if a workflow restart will be necessary. Understanding the implications of your updates will help in minimizing disruptions to ongoing campaigns.

2. For migration projects:
   When undertaking migration projects, such as transitioning from RPI v6 to v7, identify all objects that will require updates. Additionally, assess whether any workflows need to be rebuilt or restarted as part of this process to ensure a smoother transition and help avoid potential issues that could arise from overlooking necessary updates.

3. Document exceptions:
   If you encounter object types or scenarios that are not covered in the provided table, document the observed behavior and then share with the RPI documentation team to facilitate the inclusion of these exceptions in future updates.

4. Coordinate with stakeholders:
   When planning changes that may impact campaign performance, coordinate with all relevant stakeholders, including campaign managers and technical teams to help avoid unexpected behaviors in campaigns.

5. Test before production:
   Where feasible, conduct tests of object updates in a non-production environment to confirm that the expected caching and refresh behavior occurs as intended. Testing in a controlled setting can help identify any issues before they affect the production environment, ultimately safeguarding the integrity and performance of your campaigns.