Policy 23/6 - 7/7, Policy 12/7-26/7, Policy 28/7-17/9
In APEX (Cli editors, core model), no 2 outputs can be created for the same state. The following is rejected (two outputs for next state S2 differing in event only:
policy state output create name=P1 stateName=S1 outputName=S1Out eventName=eo_a nextState=S2
policy state output create name=P1 stateName=S1 outputName=S1Out eventName=eo_b nextState=S2
Now, if the state is the last state of the policy, i.e. NULL, this restriction should not apply, since the policy is handing over control to APEX for good, and APEX creates an output event and sends it to the producers.
I don't know if there are deeper implications changing this, inside the implementation. But it would be very helpful to allow multiple outputs for "nextState=NULL".
I marked this as bug, not sure if it is a story.
- is duplicated by
POLICY-3122 Provide capability in apex-pdp executor to send notification messages to DMaaP/Kafka
- mentioned in
|122107,8||Changes to support multiple outputs from a state||master||policy/apex-pdp||Status: MERGED||+2||+1|
|122387,7||Cleanup input & outputFields from Task definition||master||policy/apex-pdp||Status: MERGED||+2||+1|