This blog will take you through the Inbound Triggers – triggers sent from other applications to Campaign. Inbound Triggers

Inbound triggers are triggers sent from other applications to Campaign.  The other applications send information to the unica_actrg executable that resides in the bin directory (<CAMPAIGN_HOME>/bin).  The application calls unica_actrg and passes parameters:

Usage of unica_actrg
​Possible
parameters can be seen by typing ‘unica_actrg’ from the command line:
Unica_actrg [-p <port.] [-s ] [-v] [ |  |
-n ] , , …
Where items enclosed in [] brackets are optional.
 
The | sign indicates an ‘OR’ – campaign code can be used, or campaign name or flowchart name.
 
-v is used to indicate the version of the Campaign Trigger Utility.
 
Examples:
1)     All flowcharts waiting for ‘Go’
This would send a message to continue execution of all flowcharts (the * is a wildcard) waiting for the command ‘go’.
 
Tip:  In Unix, if there are spaces in the campaign name or flowchart name this will cause an error.  To avoid this put quotes around the asterisk.
<CAMPAIGN_HOME>/bin/unica_actrg ‘*’ Go
 
2)     All flowcharts waiting for ‘Go’ specifying the port.
 
<CAMPAIGN_HOME>/bin/unica_actrg –p 5664 ‘*’ Go
 
This would call the Campaign on port 5664 (if multiple versions of Campaign are installed on the same server you may need to specify the port) and send a message to continue execution of all flowcharts (the * is a wildcard) waiting for the command ‘Go’.
 
3)     A specific flowchart waiting for the command ‘Go’
<CAMPAIGN_HOME>/bin/unica_actrg TestFlowchart Go
 
This would send a message to continue execution of the flowchart ‘TestFlowchart’ waiting for the command ‘Go’.

Campaign A Triggers Execution of Campaign B
In this example Campaign A will send an outbound trigger that will then be the inbound trigger that Campaign B is waiting for.
1) Campaign B is waiting for an inbound trigger before executing.  In Campaign, B add a Schedule Process. In the ‘Schedule box’ choose Custom Run.  Select ‘Run on Trigger’ and add a trigger name, e.g. ‘Go’.
 
2) From the Session menu, start Campaign B.  You should see three green dots on the Schedule process. Save and Exit Campaign B.
 
3) Campaign A will send a message to unica_actrg to kick off Campaign B.  To set this up an outbound trigger needs to be created.
 
4) In Campaign A go to the Tools menu and select ‘Stored Triggers’.  
 
5) Click ‘New Item’.
 
6) Give the trigger a name, e.g. ‘Run_Flowchart_B’
 
7) In the ‘Command box’ type the command for the trigger.
        e.g. /opt/Campaign/bin/unica_actrg -n FlowchartB Go
8)     From a Mail List or ‘Schedule process call the trigger.  Example, in the Contact process, click on the ‘Contact List’ tab.
9)     Check ‘Send Trigger’
10)   Select the outbound trigger that was just created, Run_Flowchart_B
11) Start Campaign A.  When the file has been created (or table written/appended to) the trigger will execute and will launch Campaign B.

Picture

  Sumitra Chachar
  Product Manager
  HCL Products and Platforms

Marketing Platform, Campaign, Interact, Marketing Operations, Contact Optimization, and Opportunity Detect are trademarks of IBM Corporation, in at least one jurisdiction, and are used under license. 
Comment wrap
Further Reading
Reading and Using Campaign Log files
Log files are useful for troubleshooting and performance improvements within Campaign. Once we had a slow running flowchart at a client, and by reviewing the log file we identified that the actual issue was caused by the network traffic to the database. This helped us to fix the issue and optimize the performance of the flowchart. ​ One of the more advanced features of Campaign is that it has its own log generation tool from within the application. This means that they are accessible for end-users without having to consult IT Administrators. This blog will provide information about using flowchart log files for analysis and performance improvements. ​The flowchart log provides information about: Potential performance issues with a flowchart run; Identifying flowchart run errors; Capture details of the configuration settings and table catalogs; Capture the actual SQL passed to the database server. Reading the Log The flowchart logs are available from the options menu: Options à view log When searching for a specific error, it is best to clear the log first, set the required logging options and then run the flowchart again and look at the log file. By following this procedure, only the last run of the flowchart containing the error is shown. This makes it easier to diagnose the error. Logging Options and Levels The log file can provide much more detail than you typically would need. Therefore, it may be useful to set the logging level using the Logging options function in the menu. Debug logging options may be useful when contacting Technical Support. Otherwise, this option may definitely produce too much detail. The debugging level usually also decreases the execution speed of the flowchart. So after identifying the root causes, turn it off again. The lowest level of logging is to include only errors, these can...
Automation, Secure DevOps | October 15, 2020
Securing Remote Employees From Cyber Threats
In this twin year 2020, we have faced a global crisis which compelled many organizations to adapt to the changes to ensure their business continuity. Work from office to work from home is one of the major shifts that businesses have incorporated. We now have the largest remote workforce in human history, and many companies are struggling to secure them from potential cyber threats. This leads to the requirement of educating your employees to save them from potential risks and build a strong security shield for your remote workforce while they are working on VPN, Wi-Fi or personal network and using their devices. According to Google, in April, there were more than 18 million daily malware and phishing email cases related to COVID-19 in just one week. The stats are enough to prove that we are in a much bigger zone of cyber-attacks than ever and how essential it is to look after on the cybersecurity for both organizations and employees. There are two aspects where we can work on and ensure secure remote workforce. Educating your employees and establishing teleworking policy so, that everyone adheres to the standard approach of working from home and be vigilant about cyber-threats.  Secondly, as an organization, you can secure your remote endpoints and web applications by integrating respective tools for the same. 1.1 Educating employees Conduct an internal survey among your employees to gauge their knowledge about cyber-threats, based on the survey results, execute a small internal campaign. This may include types of cybersecurity attacks, do's and don’ts, measures, and a dedicated help email ID within the organization where they can report any malicious activity or quickly connect with the concerned team for the solutions. Regular email updates regarding how to detect and stay away with phishing emails, malware, Ransomware and Watering hole...
Automation, Secure DevOps | June 30, 2020
Introducing the DevOps Power Pack
The DevOps Power Pack contains our core DevOps product offerings; a great way to explore the portfolio and accelerate your DevOps journey.
a/icon/common/search Created with Sketch.