Current.Update() in a OOTB Before type Business Rule of Major Issue Management application

[Juan Miguel]

Hello devs, 

I encountered an Current.Update() in a Out of the Box Before type Bussiness rule (named MIM Candidate to Case) of the Major Issue Management application: 

Is this code correct? I was told that Current.Update() in a Before BR can cause errors. 

Regards

[Ankur Bawiskar · Accepted solution]

@Juan Miguel 

yes it's an OOTB business rule and has current.update() in before business rule.

This is not best practice which ServiceNow tells but you will find a lot of components which are OOTB which don't follow these best practices.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar · Accepted solution]

@Juan Miguel 

yes it's an OOTB business rule and has current.update() in before business rule.

This is not best practice which ServiceNow tells but you will find a lot of components which are OOTB which don't follow these best practices.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Juan Miguel 

Thank you for marking my response as helpful.

Please raise a case with ServiceNow

As per new community feature you can mark multiple responses as correct.

If my response helped please mark it correct as well so that it benefits future readers.

[Sandeep Rajput · Accepted solution]

@Juan Miguel This is super weird and not inline with the best practices. You should raise a case with ServiceNow support and bring this to their notice as this will cause multiple updates on the record.

[Juan Miguel]

Thanks Sandeep, I will write them.

[Anurag Tripathi]

You are right, it is not needed, and this looks like a mistake by SserviceNow.

You can comment or delete it out but that would mark this script as updated by customer.