I'll try to explain the Script Include to you. There is a piece I'm not 100% on how it works. This is from my OOB PDI on Tokyo.

tl;dr: If all the tracked fixes are no longer active, generate the event.

1. When a change_request record is updated, the BR tells the SI to run the checkRelatedFixes function in it's script.
2. (Not 100% sure on how this part actually works) When it initializes, it creates an fix tasks map using the property "problem.fix.records". According to documentation, this is what the property is for:
   • List of related task records (comma-separated) to track as fixes for this Problem. Used to notify the Coordinator when all the related fix records are Completed or Canceled.
3. That function checks if the current record's sys_class_name (table) is sn_cim_register
   1. If it is:
      1. It checks all sn_cim_inbound_m2m records for problem records for the change_request.
      2. Then, loops through those and checks if the table for any of the fix tasks are sn_cim_register or not
         1. If yes, check if any of the sn_cim_inbound_m2m records are active
         2. If not, check if any of the records are active in their respective tables
   2. If not:
      1. Checks if the table for any of the fix tasks are sn_cim_register or not
         1. If yes, check if any of the sn_cim_inbount_m2m records are active
         2. If not, check if any of the records are active in their respective tables

I hope this helps a bit.