Certificate Management Incident Priority level and Frequency Change

[Ben36]

We would like to (if possible) change priority levels from p1's to p3's for any incidents created by certificate tasks.

We would also like to alter when incidents for just certificate tasks are created in the first place. Ideally, we would have the incidents created days before a certificate task is due in order to ensure people are completing them on time, so we don't have any certificates expire.

Is there a way to customize either or both of these and, if so, where is it located? I've looked all over the place in our environment.

[Ben36]

I figured out one of the above things. If you go to business rules under Discovery, you can create one that caller is Certificate Administrator, check the insert and update box, and actions are impact to 3 - standard and urgency to 3 - normal, then submit.

[Martin_e]

we have the same requirement; we would like to create an incident n days before the certificate expires. The scheduled Job "Certification Notification" checks daily for Expiring & Expired Unique Certificates and triggers sub Flow "CertificateNotifier" for each record found.

I think we have to create a copy of subflow CertificateNotifier and implement our customizations there.

Wonder if anyone has a better solution without replacing out-of-thebox stuff.

[Marcio Olivieri]

Did you find a solution? We also would like to create an incident n days before the certificate expires...

[Martin_e]

Hi Marcio, as mentioned in my previous post, we created a copy of the subflow to implement our customizations. Incidents are now created n days before expiration.