When a new Incident is created with Priority P1, the system should check whether there is already an active P1 Incident associated with the same Configuration Item (CI). If such an Incident exists, the new Incident’s priority should be downgraded to P2.
However, this rule should not apply to certain types of Incidents, which are considered exceptions. The solution should be easily maintainable, allowing administrators to update or add new exception scenarios without modifying business logic each time. Suggest possible ways to manage the exception other than using custom table or system property.
