Close popover
Jerome Recker (Jerome@quavo)
Lead System Architect
Jerome@quavo Member since 2015 27 posts
Posted: December 5, 2017
Last activity: January 9, 2018

Agent Processed Data Pages

This is in response to the post that I found at

I am running into a similar issue, and disagree that this is "expected behavior". My scenario is as follows:

  • A very common DCR data page is defined at MyCo-Data-ClassRef. This defines all classes that extend from MyCo-Data-ClassRef.
  • At the implementation layer, the loading data transform changes the data page to instead be of class MyCo-Impl-Data-ClassRef. It does so by updating .pxObjClass. This works completely if a normal user references the data page.
  • If an SLA triggers a rule that references the data page, the MyCo-Data-ClassRef version runs, even though according to the application, it should be running the other version of the rule.

To me, it seems like thread/requestor level data pages, whether editable or read only, should always be flushed when an agent fires. Any given run of an agent could potentially run under a different application's scope, and it is not the job of the rules triggered by the agent to know that they need to flush these data pages, or to know that they were ultimately triggered by an agent. This should be handled by the agent.

***Edited by Moderator Marissa to update categories***

Data Integration
Moderation Team has archived post