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. Clear direction helps everyone understand what steps to take, reduces the risk of disruptions, and keeps campaign management efficient. By following the outlined processes, teams can keep workflows reliable and adaptable, leading to stronger campaign results.

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 quite complex and requires careful planning and execution. It is essential for you 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 is critical for ensuring a seamless and efficient transition. This knowledge not only helps in minimizing disruptions during the migration but also aids in maximizing the benefits of the new platform features. Proper guidance and support throughout this process can significantly enhance your experience and lead to successful implementation.

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. This overview is essential for understanding the different approaches taken by RPI in handling updates, ensuring that you are well-informed about the processes involved in maintaining and modifying object configurations effectively. By examining the nuances of each object type and the corresponding campaign scenarios, stakeholders can better appreciate the intricacies of RPI's configuration management strategies. This knowledge is crucial for optimizing the performance and functionality of the systems in use.

* When updates are made to a selection rule used for a filter within a channel’s configuration, the latest version of the selection rule will not be referenced until the channel configuration is saved again.

Definitions

• Always refresh:
  It is essential to ensure that any modifications made to the object are instantly reflected in both ongoing and newly initiated workflows, as well as in interactive activities, so RPI automatically refreshes these objects. This feature guarantees that users have access to the most current data and functionality, enhancing the overall efficiency and effectiveness of their tasks. By maintaining real-time updates, users can trust that the information they are working with is accurate and up-to-date, allowing for better decision-making and streamlined processes.

• 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, it is important to note that 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. Users can focus on analyzing the updated results without the concern of modifying the foundational criteria, thus fostering a more reliable and user-friendly environment for managing workflows.

When offer approvals are enabled, an active (non-sandbox) recurring workflow keeps using the last approved version. A newly saved edit moves the file’s approval state to a “not approved (previous version approved)” state. The draft is ignored until it is approved, with the following exceptions:

• Sandbox/Test executions bypass this and can use the latest draft.

• If there is no previously-approved version (first-ever version unapproved), behavior depends on channel validation; typically, the send may be blocked or use the only version if logic does not enforce an approved prior version.

So in normal production recurrence, the last approved content is used, not the unapproved edits.

Best practice recommendations

1. Plan object updates carefully:
   Before making any modifications to objects that are currently in use within active campaigns, it is crucial to take the time to consult the relevant table. This step is essential 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, it is important to thoroughly identify all objects that will require updates. Additionally, assess whether any workflows need to be rebuilt or restarted as part of this process. A comprehensive evaluation will ensure a smoother transition and help avoid potential issues that could arise from overlooking necessary updates.

3. Document exceptions:
   In the event that you encounter object types or scenarios that are not covered in the provided table, it is important to document the observed behavior meticulously. This documentation should then be shared with the RPI documentation team to facilitate the inclusion of these exceptions in future updates. By doing so, you contribute to the collective knowledge base and help improve the resources available for others.

4. Coordinate with stakeholders:
   Effective communication is key when planning changes that may impact campaign performance. It is essential to coordinate with all relevant stakeholders, including campaign managers and technical teams. By communicating the planned changes and their potential impact, you can help avoid unexpected behaviors in campaigns, ensuring that everyone is on the same page and prepared for the adjustments.

5. Test before production:
   Where feasible, it is highly advisable to conduct tests of object updates in a non-production environment. This practice allows you 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.