Campaign Management Tool Advanced Topics

 I had many scenarios where I ran a costly query to select some good no of records and then process them further. But when it comes to processing I had to restrict the number of records to be processed in one go. And once the subset is processed, then select from the table again and then process the subset. Something like below where the end activity calls the signal when the complement from Split has more than 0 records to start the whole process again. But the problem is every time you have to run the costly select process to process a fraction of the records. As a result the overall throughput is decreased heavily. As an alternate I used a looping through the selected records avoiding selection every time I need to process the subset. Here the JS Activity after select is dummy one but required. I added a log in it with count. Test activity is also needed to ensure we have the exit path from the loop. In the above example the select query fetched 8680 records and then split restricte

The SQL Generated by Campaign created the string column with 255 chars like sFieldName VARCHAR2(255 CHAR) or similar depending on the the SQL type. So even if you need to store a field that requires bigger length, it  fails. The below trick I applied into a Campaign Standard implementation, but the code example is using Campaign Classic as I currently don't have access to the standard instance. In my case I had to create a calculated value which requires more than 255 char in length and it was complaining due to the length of the field. My ACC DB is Oracle and here is the error I got. ORA-210000 Oracle error: ORA-12899: value too large for column "AC_APPUSER"."WKF12862341_31_1"."SEXPR1676832221" (actual: 276, maximum: 255) Resolution: AC Standard Code: Read Option Variable: Add a field in Enrichment or Select Activity Additional Data using the expression $(options:<Name of the Option Variable>). Example: $(options:MyAPIKey)