You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2025/01/17 08:23:00 UTC

[jira] [Resolved] (SYNCOPE-1854) propagation not triggered after user updated while in status "updateApproved"

     [ https://issues.apache.org/jira/browse/SYNCOPE-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò resolved SYNCOPE-1854.
---------------------------------------------
    Resolution: Fixed

> propagation not triggered after user updated while in status "updateApproved"
> -----------------------------------------------------------------------------
>
>                 Key: SYNCOPE-1854
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1854
>             Project: Syncope
>          Issue Type: Improvement
>          Components: extensions
>    Affects Versions: 3.0.10
>            Reporter: Lionel Schwarz
>            Assignee: Francesco Chicchiriccò
>            Priority: Minor
>              Labels: flowable
>             Fix For: 3.0.11, 4.0.0
>
>
> In my BPMN workflow, I have implemented the ability to update certain attributes on a user which is already in status "updateApproved" (after the update the user will then stay in status "updateApprove").
> Example:
> A user requests a change for its "home institute". This change requires the validation of the boss: the status is "updateApproved", waiting for the boss approval. During this period of time (before the boss approves), the user wants to modify its first name (this change does not requires the boss validation).
> My BPMN implementation allows the user to do this modification. Unfortunately, in this case, this modification is not propagated to external resources.
> I had to make this [patch|https://github.com/apache/syncope/pull/955] to make it work.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)