How can we avoid generating/dispatching redundant issues?

[Former Member]

Hello colleagues,

How can we avoid generating/dispatching redundant issues?

For ex. Scenario:

1) Weekly assessment of process control (automated monitoring)

2) Deficiency identified for business object A in week 1.

3) Issue generated and assigned to responsible party.

4) Remediation delayed -> Issue still open after one week.

5) Same deficiency identified for business object A in week 2 again.

-> How to avoid flooding people with redundant issues?

Is it possible to do something about?

Thank you,

Best Regards,

Anton

[rajeshwari_akkamgari · Accepted solution]

Hello Anton,

Generally, for one Business rule-one issue will be generated. If certain exceptions are found in Week-1, those will always be there when rule is scheduled for Quarter-1 or Yearly.

It should not result the exact same results for Week-2, if the changes are varying from

week-1 to week-2.

I don’t think this as a duplication of data, as user may have a different approach to remediate these issues based on timeframe.

Regards,

Rajeshwari