Posted: 14 Jun 2018 4:03 EDT Last activity: 6 Feb 2019 6:51 EST
Why Campaign BatchOut tables have all exposed columns?
In PM 7.22 for every outbound campaign launched Pega internally creates a batchout table which contains all exposed columns for each proposition property. Considering the number of proposition properties we have it leads to table with numerous column and also it puts a oracle max length constraint 4000 chars. In case we want to keep sms content or email content in proposition data it becomes a problem (as in our project business keen to control all this through proposition data instead of treatments, also it reduces the number of rule count) .
So my question is there any good reason for PEGA to keep all exposed column in Batchout instead of blob?
In continuation to the above query, can you also confirm if Pega has some extensions, where we can restrict the specific columns to be passed to BatchOut table? We have more than 2000 property created in SR class and most them are valid and in used. When I ran the Campaign , system try to create BatchOut table with 2000 columns and throw DB error that ORA-01792: maximum number of columns in a table or view is 1000.
If Pega does’t have any extension then can you also suggest what are the possible solutions?