What will be affected if I stop the business rule "Incident create Knowledge"?

[GaominZ]

We are thinking to make a new workflow to make it easier to create knowledge artices from incident tickets.
To do so we need to stop the business rule "Incident create Knowledge". Is there any risk with doing so?

The system message shows that this business rule is highly possible being changed in future upgrade. 

[Dr Atul G- LNG]

Hi @GaominZ 

The only thing is, you are stepping away from the out-of-the-box approach. If SN adds more features in this BR, you may not be able to utilize them. Is there any reason to skip the OOTB option and build your own?

[Utkarsh9]

This is an out-of-the-box (OOB) ServiceNow feature, so please reconsider the rationale for creating a new custom flow. Additionally, deactivating the OOB Business Rule will impact the linkage between Incident and Knowledge Management, including the associated related lists. If you proceed with a custom flow, these dependencies must be explicitly handled and recreated within the new flow.

[Tanushree Maiti]

Hi @GaominZ 

Staying close to Out-of-the-Box (OOTB) is a core ServiceNow best practice designed to ensure upgrade stability, reduce technical debt, and simplify maintenance.

Implementing custom rules or modifying OOTB components forces the instance into a deviation state, creating a "skipped" record in upgrades that requires manual merging and troubleshooting.

If you deactivate the mentioned BR -

• You are stopping the automatic creation of Knowledge articles when an incident is resolved.
• The "Knowledge" checkbox on the incident form will no longer automatically create a draft knowledge article when the incident state is set to Closed or Resolved.
• Agents must manually use the Create Knowledge UI Action (button) to create articles, ensuring higher quality knowledge creation, if you do not automate it.