Double update occurs and business rules can trigger twice for Inbound Actions when using both the 'Field Actions' and the 'Script' to assign values to the newly created record - Known Error

Double update occurs and business rules can trigger twice for Inbound Actions when using both the 'Field Actions' and the 'Script' to assign values to the newly created record Description When using an 'Insert' inbound action and it sets fields using the 'Field Actions' and the 'Script', it will create two commits to the database for the record. The First is the creation and all target fields are empty. The Second is an Update, which includes all the data from the inbound action Field Action and Script.

This is causing issues for customers who also want an email to be sent out upon the creation of the record. Since the values all get set on the 'Update' and not the 'Create', the notification will fail its conditions and not fire.

Because the notification engine calls current.insert only once that is after applying script and field actions, and if an insert is called in a script such as business rule, that will result in 2 insert calls on same object, which causes business rules to trigger twice as it is same object. Steps to Reproduce

Make sure inbound mail is set up on an instance to receive mail. Setup an inbound action to the incident table with both Field Actions and Scripts set to apply data to the New target record. Please see attached: InboundAction_Actions.png or you can load in 'ExtraUpdate_InboundAction.xml' Send in an email to trigger the inbound action to open an incident. Go to the History of the incident and you will see the following: A Create of the incident where all fields are empty. An Update of the same record, setting all the values from the inbound action. It will create two commits to the database for the record As a result, affected business rules are likely to be triggerred twice Workaround To achieve a single insert, remove the current.insert() from the script. After the field actions are evaluated the record will be inserted. That will also avoid duplicate execution of business rules.

OR

On the inbound action, do not combine both 'Field Actions' and 'Scripts' to set field values on the inserted record. Move the Field actions into the Script so all the code is in the Script.