Campaign Management Tool Advanced Topics

I am working to enable some security for the inbound interaction for Adobe Campaign Classic Offer. We are working to get the inbound call via SOAP for call center channel. I have setup the offer space will name "callCtr" under Recipient Environment. The goal is to ensure the caller passes an username and password while making the SOAP call. Also I want to enable the authentication for specific offer spaces only. The SOAP request for Propose method has the <urn:sessiontoken> node. But for offer service that is not used. So I planned to use the node in the same way as Message Center enables the authentication. So the caller needs to pass the  value as username/password inside the sessionToken element. Here are the changes I did and note I made changes to the nms:interaction.js file. Be sure to backup the original file before you try and Adobe may not support if you make changes. So be ready to fly on your own!!! Step 1: Create an option variable to store the name o...

While working on a requirement on Adobe Campaign Classic, I got a requirement to make the offer code mandatory and unique. Initially it seemed to be an easy requirement as I can just create a unique key on the offer code field. But later realized that, every offer has another version of the same stored in the same schema nms:offer for the live environment. Adobe automatically creates the internal name as ogininalName_liveRcp while deploying the offer to the live environment (don't know how that is done yet, may be a post for future :)). But for other fields, it is copied as is and so is the offer code too. So unique key is not option. Then thought, if I add another field in the nms:offer schema for the environment and make the key with offer code + the environment. But same deployment problem, how do I set the env variable as part of deployment? So decided to go with the toughest but cleanest solution, SOAP call from input form. Here are the steps for the same. You can follow a...