Hi Francesco,
Your answer is absolutely clear, thanks
Regards
Lionel
- Le 25 Oct 23, à 16:28, Francesco Chicchiriccò ilgro...@apache.org a écrit
:
> So let me summarize what is happening.
>
> This step:
>
> - update the user so that the approval is needed
>
> is actually performed by
So let me summarize what is happening.
This step:
- update the user so that the approval is needed
is actually performed by calling
PATCH /users/self/
or
PATCH /users/
depending on whether the caller is the user themselveers or an administrator.
Both invocations reach up to
Hi Francesco,
Thanks for your answer.
You should be able to reproduce this with the UserWorkflow defined in the fit
part of Syncope (which I used as a base for my customized workflow definition)
and with the LogicActions implementation attached to the email:
- declare the ExampleLogicAction in
Hi Lionel,
can you provide a simple project that reproduces this issue?
It should be enough to create a new Maven project from latest stable version
(3.0.5 at this time), change the workflow definition to match your case and
finally provide the steps to reproduce in embedded mode.
Regards.
To be more specific about the issue, I must tell that I have a flowable
UserWorkflow with approval on user update operations (on certain circumstances).
It seems that when the update needs approval, the afterUpdate() is called
before approval with an empty List.
When the update does not need
Dear all,
I have a customized LogicAction with afterUpdate() implementation, but this
method receives an empty List when called.
Nevertheless, the propagation works fine, and I get the correct REST response
with propagationStatuses and beforeObg/afterObj.
Am I missing something?
Regards
