Guest

Preview Tool

Cisco Bug: CSCum32709 - 2 Email events w/ same Subject but different Message trigger 1st event

Last Modified

Jan 26, 2017

Products (14)

  • Cisco Workload Automation
  • Cisco Tidal Enterprise Adapter for Oracle Database
  • Cisco Tidal Enterprise Adapter for Web Services
  • Cisco Tidal Enterprise Adapter for Oracle E-Business Suite
  • Cisco Tidal Enterprise Adapter for SAP
  • Cisco Tidal Enterprise Adapter for Cognos
  • Cisco Tidal Enterprise Adapter for Informatica
  • Cisco Tidal Agent for Windows
  • Cisco Tidal Enterprise Adapter for JMS
  • Cisco Tidal Enterprise Adapter for SAP BusinessObjects
View all products in Bug Search Tool Login Required

Known Affected Releases

5.3.1

Description (partial)

Symptom:
Have 2 email events with the same Subject string but different Message strings.  Events trigger on 1st Subject string.

Conditions:
Reproduction steps for 5.3.1:
1. Create email adapter connection 
2. Create Job A, a simple sleep job with no calendar. 
3. Create 1st email event using Email connection created in step 1.  For Scan for Text, use APR for Subject and No for Case Sensitive.  Use PD for Message and No for Case Sensitive. On Schedule tab, use Daily calendar.  For Associated Action, use job action to launch Job A.
4.  Test email event  by sending email with appropriate subject and message field characters.  This will work fine. 
5. Create Job B, a simple sleep job with no calendar.
6. Create 2nd email event using Email connection created in step 1. For Scan for Text, use APR for Subject and No for Case Sensitive.  Use QA for Message and No for Case Sensitive. On Schedule tab, use Daily calendar.  For Associated Action, use job action to launch Job B.
7. Test 2nd  email event by sending emails with appropriate Subject and Message field characters.  This will launch Job A.  It should launch Job B. The 1st email event is triggering.
7.  Now send email for 1st email event with a subject line of APR and NO message text. Job event will trigger and launch Job A.  This should not happen as the 2nd criteria is not met.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.