Incident, Application, and Event

[gdm1411]

Ok, I've bought into the scoped application paradigm.   However, it's giving me fits.

I want to make a rest call to an external system after an incident record is inserted/updated.   My approach is to generate an event, and then have a script action listen for the event.   If I understand it correctly, this is one approach to minimizing the delay when a record is inserted/updated.

So, the script action is in my scoped application (call it 'yyy').

Logic tells me to create my event in the scoped application.   Woops - can't see the incident table.

So, I create the event in the global scope.

I then create a business rule (in my scoped app) to fire the event on the incident record (conditions are after insert/update).

Woops - within my scoped business rule, using the global event name fails.   I get

'Access to event 'yyy.incident' from scope 'yyy' has been refused. The event is not defined.'

How do you 'get around' this?   I'm using the Helsinki version.

Thanks.

GregM

[Pradeep Sharma · Accepted solution]

Hello Greg,

Can you create an event in the same scope and try once. Leave the table field to blank.

[gdm1411]

Well, I'm dumb and you're a genius.   I just assumed you had to select a table so that 'current' in the event handler would be the corresponding table. Not so.

Just for fun, what's the point of selecting the table in the event registry?