Journal Entry '....requested to approve task' for Change using Change Models

[NMiel]

My company is working on moving to Change Models.  When we use Change Models we get an approval history change entry for every user of a group and one for the group itself. 

• Example: 
  • John Doe requested to approve task
  • Group approval for ServiceNow Administrators is requested.

Our current process, which uses Workflow, only documents the group approval request, and we would like the same using Change Models.

I found the following Business Rules but am unable to make them work to prevent the journal entry for the user requested to approve task entry.

• Business Rules:
  • Approval Events (Task)
  • Approval Events (Non-Task)

Any help or direction would be appreciated. Thank-you.

[Tony Chatfield1]

Hi, the individual approval journal\audit data has no impact on your approval process so I see no real need to disable and would consider the requirement an unnecessary customization. Also the OOB approval process is based on these individual approval records, meaning that they are core to approvals functionality, and I would think altering this would require major customization. When you state 'I found the following Business Rules but am unable to make them work to prevent the journal entry' what exactly did you do\change? and what were the results?

[NMiel]

Hi Tony,

Thank you for your reply.  Our current process for Change, which uses Workflow, only documents the group approval in the Notes of the change, not an approval requested for every member of the group.  When we switched to Change models, it is now documenting the approval request for every member of the group in the Notes section of the Change.  This creates a lot of unnecessary noise in the change.  I did not do anything to the Business Rules above, other than test with them inactive, which did not impact the approval requests noted on the Change.  I tested this in my developer instance, which has no customizations, and received the same result.

Below are screenshots of what I'm seeing:

Using Workflow:

Using Change Models with Flow:

[Tony Chatfield1]

Curious indeed, I can see the same behavior in a PDI, but was unable to quickly identify where it sources from.

Will try and find time to review.