[
https://issues.apache.org/jira/browse/OFBIZ-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207551#comment-16207551
]
Deepak Dixit commented on OFBIZ-9826:
-------------------------------------
This has been committed at ofbiz framework trunk at r#1812394
I was stuck on use case where same service in being called with different
parameter.
Eg.
{code}
<eca service="createPartyRelationship" event="invoke">
<set field-name="partyId" env-name="partyIdFrom"/>
<action service="ensurePartyRole" mode="sync"/>
</eca>
<eca service="createPartyRelationship" event="invoke">
<set field-name="partyId" env-name="partyIdTo"/>
<action service="ensurePartyRole" mode="sync"/>
</eca>
{code}
In this case Seca rule is same, condition is same and action is same but we are
passing different in parameter, in first rule partyId will be partyIdFrom and
in second case it will be partyIdTo.
But good news is we don't have this kind of rule,
if we have this kind of rule we can use condition to make sure partyIdFrom/To
(or any param that we are setting in set field) is not empty to make them
unique.
> Add ability to disable seca rule
> ---------------------------------
>
> Key: OFBIZ-9826
> URL: https://issues.apache.org/jira/browse/OFBIZ-9826
> Project: OFBiz
> Issue Type: Improvement
> Reporter: Deepak Dixit
> Assignee: Deepak Dixit
> Attachments: OFBIZ-9826.patch
>
>
> We have enabled flag in ServiceEcaRule class, if its set false then seca rule
> will not be execute.
> But there is not way to disable seca.
> We can add enabled flag in SECA definition to disable the existing seca rule.
> Here is the proposal:
> - Add new attribute on seca tag named enabled
> - Default value will be true for this.
> - If user want to disable existing OOTB seca rule, then user can define same
> rule in custom component and set the enabled=false
> - Need some changes in code to honor the enabled attribute while loading seca
> rule.
> Also as per current flow if same seca rule is define more then once, system
> will execute all the rule, ideally it should not execute same rule (same
> rule, condition and action) if its defined more than one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
