how to restrict incident creation from calendar invites for DL

[RudhraKAM]

As of now we are creating an Incidents via Inbound action , but when there is a calendar invite , still it is creating Incident , How to restrict that ?

I am not able to restrict subject , as it can be any 

[pratyusha11]

{
  "qa_attestation": "production_system=true^state=3^typeINnormal,expedited,standard,emergency^close_code!=no_work_performed^closed_atONLast month@javascript:gs.beginningOfLastMonth()@javascript:gs.endOfLastMonth()",
  "infrastructure_attestation": {
    "change_query": "production_system=true^state=3^typeINnormal,expedited,standard,emergency^close_code!=no_work_performed^closed_atONLast month@javascript:gs.beginningOfLastMonth()@javascript:gs.endOfLastMonth()",
    "task_query": "state=3^change_task_type=testing^u_sub_typeINinfrastructure,infrastructure_no_test_plan^change_request.production_system=true"
  }
}

[pratyusha11]

var filterPropString = gs.getProperty('wf.chg.attestation.filter.conditions');
var filterPropParsed = filterPropString ? JSON.parse(filterPropString) : null;
var queryChg = (filterPropParsed && filterPropParsed.qa_attestation) ? filterPropParsed.qa_attestation : '';

var filterPropString = gs.getProperty('wf.chg.attestation.filter.conditions');
var filterPropParsed = filterPropString ? JSON.parse(filterPropString) : null;
var queryChg = (filterPropParsed && filterPropParsed.qa_attestation) ? filterPropParsed.qa_attestation : '';

[pratyusha11]

var filterPropString = gs.getProperty('wf.chg.attestation.filter.conditions');
var filterPropParsed = filterPropString ? JSON.parse(filterPropString) : null;
var queryChg = (filterPropParsed && filterPropParsed.qa_attestation) ? filterPropParsed.qa_attestation : '';

[Dharma Liyanage]

@RudhraKAM 

How is this inbound email being triggered? Is it related to the RSVP setting in the iCalendar invite?

One possible approach would be to modify the calendar template to use RSVP=FALSE, for example:

ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=FALSE:MAILTO:${to}

We could also update the inbound action logic to specifically identify emails related to the Change table by incorporating the Change Number in the email subject line. This would allow the Incident inbound action to ignore or skip these messages appropriately.

Example:  CAB Meeting - CHG0030123

Usually the inbound email action identifies the target record using:

• watermark
• subject line
• In-Reply-To headers
• record number in subject/body