Issue with update business rule firing immediately after the insert business rule

onAfter business rules - firing on incident table.
I didn't want the after rule firing on an insert operation...and the issue seemed intermittent - was not occuring in dev, occured in test...

Adding the following condition to the update business rule seemed to do the trick and it no longer fired on insert.


previous.state!=0

Comments

Popular posts from this blog

Running transform maps asynchronously

Post a command to the ECC queue for the mid server to initiate a powershell file copy

GlideRecord setValue