Create outbound rules

The following screen shot shows an example outbound rule configuration for a Case Exchange integration.

 

The following table provides example outbound rules that work in the out-of-box Service Manager system. You may modify these rules according to the workflow in your system.

Note When you create a Rule Set for Incident exchange, set the Table name field to probsummary.

Condition (RAD expression)

Event

assignment in $L.file="<assignment group>" and problem.status in $L.file isin {"Pending Customer", "Pending Vendor"} and sysmoduser in $L.file~="<smis_scheduler_name>" and jscall("CaseExchangeExternalReferencesDAO.getExternalID",number in $L.file)=""

Create

(not same(problem.status in $L.file, problem.status in $L.file.save) or $apm.activity isin {"Communication with customer","Communication with vendor"}) and not ( problem.status in $L.file isin {"Rejected","Resolved","Closed"}) and sysmoduser in $L.file~="<smis_scheduler_name>" and jscall("CaseExchangeExternalReferencesDAO.isExternalActive","probsummary",number in $L.file)=true

Update

not same(problem.status in $L.file, problem.status in $L.file.save) and problem.status in $L.file isin {"Resolved","Closed"} and resolution.code in $L.file~="Request Rejected" and sysmoduser in $L.file~="<smis_scheduler_name>" and jscall("CaseExchangeExternalReferencesDAO.isExternalActive","probsummary",number in $L.file)=true

Resolve

not same(problem.status in $L.file, problem.status in $L.file.save) and problem.status in $L.file isin {"Rejected","Resolved","Closed"} and resolution.code in $L.file="Request Rejected" and sysmoduser in $L.file~="<smis_scheduler_name>" and jscall("CaseExchangeExternalReferencesDAO.isExternalActive","probsummary",number in $L.file)=true

Reject

(sysmoduser in $L.file="<smis_scheduler_name>")

Acknowledge

For more information about the getExternalID and isExternalActive functions, see Functions used in rule conditions.

For more information about how to create Rule Sets, see the following topics: