CREATE & UPDATE events fired when issues is created in Workfront

[tibormolnar]

Hi All,

I'm calling for Black Belt Fusion experts, hoping for help with resolving this mystery.

I have a custom form (with loads of fields) on the Issue object in WF. I have a Fusion Scenario that I need to run when one of these fields (FIELD2) is updated on an existing issue, or a new issue is created with this field populated.

The filters defined for the webhook look like this:

Record type: Issue
State: New state
Filters:
	DE:FIELD1 EQUAL Yes
    AND DE:FIELD2 Changed 
AND connection updates included
Record Origin: New and Updated Records

 When I CREATE a new issue that matches the filters, 2 events are fired: one "CREATE" and one "UPDATE" event. So my scenario runs twice and I can't figure out why.

The Fusion scenario does not update FIELD2, so the 2nd event is not triggered by Fusion itself.

I checked the data in the output bundle of the "Watch event" Fusion module in both runs and found the following:

- The "newState" data is exactly the same in the CREATE event and in the UPDATE event (and it includes the custom field data).

- There are 2 differences between "oldState" and "newState" in the UPDATE event:

  - oldState doesn't include the custom form fields (only newState does).

  - in oldState the fields rootGroupID and groupID are null, in newState they have a value.

I don't understand why I have 2 events, I would only expect 1 CREATE event, since that's when FIELD2 is set.

I appreciate any advice.

Tibor

[Sven-iX]

I remember beating my head against the wall with this. Really annoying to have to filter out because on rootGroupID...

Do you need to know it was a CREATE event? 

[tibormolnar]

Hi Sven,

I need the scenario to run (once) when FIELD2 is updated on an existing issue, or a new issue is created with this field populated. In other words: I need the scenario not to run twice when a new issue is created.

So, I guess, as a first step I'd like to understand exactly why this is happening. Did you manage to figure it out?

Why is there an UPDATE event (too) when I create an Issue? What is rootGroupID?

Thanks for sharing your knowledge!

[Sven-iX]

I didn't manage to solve it. No idea why that's happening. I ended up using filters too. 
You could also try 2 scenarios with a single event handler (one for new, on for updated only) and then use HTTP module to send the newState/oldState to a worker scenario. 

Sorry i can't be of more help!

[tibormolnar]

Right, let's assume I'll use filters.

How can I tell a genuine UPDATE event (i.e. that is fired when the issue is actually updated) from a pseudo UPDATE event that is fired nanoseconds after the CREATE event?

[Sven-iX]

Use what you wrote above - rootGroupID and the custom field? 

[Lawson02]

I've had this issue before and the only way I've would to fix it is to add an exists statement, but this assumes you only care when it exists and you don't need to know when its blank. Assuming the 2 statements is correct you could even try changing record origin to Updated records only.

DE:FIELD2 Exists

AND DE:FIELD2 Changed