I tried to run a distribution test for customers that eligible for the Inbound channel. The results show distribution test only generates actions for the outbound channels.
When I debug through the strategy, I checked on this strategy CreateEligibleChannels there is a filter for inbound Channel to check the payload direction. So that I need to add Primary.ContainerPayload.Direction and Primary.ContainerPayload.Channel in data transform to testing the inbound actions through startegy. But when we are running distribution test where to set these direction value and why only outbound channel that gettting generated?
I believe this is more a question of data preparation than a distribution test simulation. When you say “I tried to run a distribution test for customers that eligible for the Inbound channel”, can you please elaborate how did you set-up the test data to run a simulation?
If you used customer data directly from the customer table in the database or used a data set that is not representative of your inbound customer data, this behavior is expected. Ideally, on the inbound channel, the customer data is expected to contain the ContainerPayload page with contextual information and this is what that particular filter also relies on.
By the way, Pega has a data migration feature out-of-the-box that can help you capture inbound customer data in production and migrate the same over to your simulation environment. Please check the following link.
Yes, we are using customer data directly from the customer table in the database. Actually, we will use data in BOE database. The data is already the same as production data. But, I have a question on how to include the payload structure in our data?
You can create a data flow with an abstract destination and your customer database as the source. And in this data flow you can add convert shape (or data transforms) between the source and destination to add ContainerPayload to your customer data. You should then be able to use this data flow as the audience for your simulation.
However, please note that this might NOT be an accurate representation of your customer data in the production because you will probably need to set static values for channel, direction etc. Our recommendation is for you to sample your inbound customer data in production and bring it over to the simulation environment using a data migration pipeline for a more accurate representation of the inbound customer data. For more information on how to do this, please check out the link I shared earlier.
for this, Our recommendation is for you to sample your inbound customer data in production and bring it over to the simulation environment using a data migration pipeline for a more accurate representation of the inbound customer data.
Q: How the data should be brought? The container payload should be present in that, right? how this conversion is to be done for bulk and how to make sure the container payload is available in the data being migrated?
The data migration feature gives you the ability to sample the customer data in the inbound channel. This means, a small percentage of the inbound data will be collected into a customer sampling data set. When this data is collected in the sampling data set, it will also have the ContainerPayload. The sampling data set is a Cassandra data set and it can be used as the simulation audience once you migrate the data to your simulation environment. Therefore, if you use the data migration pipeline, there is no need for any additional bulk conversion to add the container payload information to the customer data.
We also have a module on Pega Academy dedicated to this feature. We encourage you to leverage it to understand the data migration feature better.
