[midPoint] Trigger on task's attributes

Yakov Revyakin yrevyakin at gmail.com
Fri Nov 10 15:26:14 CET 2023


Yes, you are right. I meant policyRule - my mistake.
Thank you for your explanation.

On Fri, 10 Nov 2023 at 12:22, Pavol Mederly via midPoint <
midpoint at lists.evolveum.com> wrote:

> Hello Yakov,
>
> I assume you are talking about policy rules here. These are primarily
> meant for the management of objects like users and abstract roles. This
> corresponds to the fact they are evaluated within the Projector
> component in model-impl module.
>
> The task management is far far below that layer - in task-quartz-impl
> module. These rules are ignored there.
>
> This is quite by design, at least for now.
>
> Best regards,
>
> --
> Pavol Mederly
> Software developer
> evolveum.com
>
> On 10/11/2023 10:59, Yakov Revyakin via midPoint wrote:
> > Hi all,
> > Honestly I believed that if the task archetype creates a trigger on
> > modification of, for example, executionState task attribute, then if
> > the task gets suspended due to an error the task will create a trigger
> > on this event. I can see that a trigger is created only if the
> > attribute was changed manually.
> > Can someone explain what is wrong in the approach?
> > Thanks,
> >
> >
> > _______________________________________________
> > midPoint mailing list
> > midPoint at lists.evolveum.com
> > https://lists.evolveum.com/mailman/listinfo/midpoint
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20231110/ab9496a1/attachment.htm>


More information about the midPoint mailing list