AnsweredAssumed Answered

Why doesn't a new Event Rule Action work on physical source?

Question asked by Brett_Zipkin on Sep 5, 2017
Latest reply on Sep 7, 2017 by Louis_van_Amelsfort

I'm trying to add a new Event Rule that will trigger on the usm_request_status table.  For now I'm making the criteria ultra simple but will refine it once it's working.  According to the documentation, you can only add new events based on physical sources and those sources are the database tables. 


So here's my Event Type:

Event Type Name: Event Test - LC3
Event Source: Physical
Audit Trail Level: Include Multiple Attributes
Transaction Name: USM_REQUEST_STATUS
Transaction Type: Added
Event Type Parameters: $request_id$, $request_status_id$, $status$, $status_old$, $subscription_detail_id$, $user_id$, $all$


It currently has one rule:

Name: When Status for Request Item is set to Cancelled
Status: Enabled
Description: Check when the Request Item (Service Option level) status is set to Cancelled through Service Catalog
Event Filter: status = 4


And I have a PAM action that is tied to it that fires and passes in the details of the database row.


Name: Brett's PAM Cancelling Process
Type:CA Process Automation
Status: Enabled
Timeout: 0

Configuration Name: Default
Start Request Form: /Service Catalog/SRF/Catalog - Cancel SDM Ticket



I can see new entries being added to the table but the event doesn't fire.  If I add the same PAM process to the OOTB Request/Subscription Item Change event it fires fine so I know it's not the process or how I set up the action.


In the end the goal is to only fire the PAM process when a Service Option is cancelled by an ID that is not a specific service account once it's reached the fulfillment range.  So I know I'll be adding conditions around the userid and status_old and if I'm pulling it from the the status table as expected, subscription_detail_id not null.


Why doesn't my new rule work?