Comment

Yes, you can set that up in the business rules. There are several different options to solve. Immediately I think about leveraging the incident status as part of the rule, ie. if status = new or whatever status you have when incident is created THEN fire the action of the rule you set up. You can also research the IF condition: Incident.updated or Incident.Response Sent.

Alternatively if you need actions to happen to the Incident before it is Saved, you could potentially leverage Incident workspace rules, but again I leverage these mainly if I need an action to happen before I save the record.

In addition to Tasha's suggestions, it's important to understand how the rules engine is executed (more on that here). Since all applicable rules are executed against a record during each commit, you'll need to find a way to identify your "new" incidents in such a way that BR conditions would apply. Using rule states to isolate new from "in-flight" incidents is another way you might consider tackling this.

Also you can use States (1 - Initial - For Create/New incidents, 2 - In Progress - Update incidents , 3 - Close - Final stage of incidents ) to transition from Creation to Update actions so you can keep away rules from execution in the state