We're currently working with dx apis v1 in order to advances case types using different channels.
While working on that, we discovered that none of the pre-processing actions is ran for each call/assignment.
It looks like a limitation of dx api, but we didn't find any article mentioning it.
This post is only mentioning some limitation in the post processing, but nothing about the pre processing https://docs.pega.com/pega-digital-experience-dx-api-overview/87/dx-api-compliance-guidelines.
Any of you is aware about this limitation or can give us some feedback?
***Edited by Moderator Marissa to update Capability tags***
I use DX API v1, and in my experience pre-processing data transform in flow actions are executed.
I suppose that your specific situation is a flow, with an assignment and a connector with a flow action that invoke a preprocessing.
My advice is try to trace the API invoked, in order to understand if the data transform is actually invoked.
If so, check if the value of the result of the data transform in pre.processing is actually committed on Pega.
Have a nice day.