Il giorno 18/set/2012, alle ore 11.31, Colm O hEigeartaigh ha scritto:
> Hi Fabio,
>
> This is how to reproduce the error:
>
> 1) Start Syncope in embedded mode (1.1.0-SNAPSHOT)
> 2) Go to http://localhost:9082 and note that the TEST table has a user of id
> "testuser1" and status of "false".
> 3) In the Syncope console, make the fullname, surname and userId attributes
> non-mandatory.
> 4) Go to Synchronization Tasks and add a template to the task for the
> resource "resource-testdb" and select the "resource-testdb" resource in the
> template.
> 5) Execute the task.
> 6) Note that "testuser1" is now in the User list with a "suspended" status.
> 7) Edit "testuser1" and click on save. You then get the error I gave
> previously.
Hi Colm,
so it is not an export/import problem.
Actually, it is not neither an issue. The behavior is correct: suspended users
can be reactivated or deleted (looking into the wf) but not updated.
<exclusiveGateway id="suspendedGw"/>
<sequenceFlow id="suspended2Reactivate" sourceRef="suspendedGw"
targetRef="reactivate">
<conditionExpression xsi:type="tFormalExpression">${task ==
'reactivate'}</conditionExpression>
</sequenceFlow>
<sequenceFlow id="suspended2Delete" sourceRef="suspendedGw"
targetRef="delete">
<conditionExpression xsi:type="tFormalExpression">${task ==
'delete'}</conditionExpression>
</sequenceFlow>
If you try to reactivate the user all will work fine.
Best regards,
F.
> Thanks,
>
> Colm.
>
> On Tue, Sep 18, 2012 at 9:00 AM, Fabio Martelli <[email protected]>
> wrote:
>
> Il giorno 17/set/2012, alle ore 12.29, Colm O hEigeartaigh ha scritto:
>
>> Hi all,
>>
>> I'm experimenting with the H2 instance that ships with Syncope's embedded
>> mode. If I create a user with "status" of true in the backend, then it
>> imports fine. If I create a user with "status" of false in the backend it
>> appears with status "suspended" in Syncope. However it does not appear
>> possible to "enable" the user in Syncope. If I click "save" on the suspended
>> user I get the following error:
>>
>> SEVERE: Servlet.service() for servlet [syncope-core-rest] in context with
>> path [/syncope] threw exception [Request processing failed; nested exception
>> is org.apache.syncope.core.workflow.WorkflowException:
>> org.activiti.engine.ActivitiException: No outgoing sequence flow of the
>> exclusive gateway 'suspendedGw' could be selected for continuing the
>> process] with root cause
>> org.activiti.engine.ActivitiException: No outgoing sequence flow of the
>> exclusive gateway 'suspendedGw' could be selected for continuing the process
>> at
>> org.activiti.engine.impl.bpmn.behavior.ExclusiveGatewayActivityBehavior.leave(ExclusiveGatewayActivityBehavior.java:86)
>>
>> Is this a bug?
>
> Hi Colm,
> I cannot reproduce the issue.
>
> I performed the following tests (manually) using the 1.1.0 snapshot in
> embedded mode:
> 1. (through administration console) new user creation; user suspension; db
> export; db import; user reactivation
> 2. (through resource synchronization) suspended user synchronization; db
> export; db import; user reactivation
>
> In both cases I can reactivate the user without any problem.
>
> Have you customized the workflow?
> Which version are you using?
>
> Best regards,
> F.
>
>>
>> Thanks,
>>
>> Colm.
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
