As an ONAP Drools Policy Designer, I want to ensure that the usecases.drl can support the 5G OOF SON use case in that it handles incoming Control Loop Events so that events do not get removed from Drools working memory if a guard or lock policy returns "deny" so that when one CL is done then other CL will pick up the event and process it.
Currently, the other use cases in ONAP "flood" the drools working memory continuously with events when a CL Event condition is triggered. The Drools usecases.drl simply processes each event and if the resource is locked or guarded, it simply errors out the event and then removes it from memory. For 5G OOF SON, this is not the case only one event will be sent so it cannot be removed from memory. The requirement is that the CL event must remain in memory until ready to be executed.