, 2013 11:00 AM
To: dev@syncope.apache.org
Subject: Re: Activiti approval fails on deny
On 29/03/2013 14:01, Walker, David R. (JMD) wrote:
> Here is the bpmn we're using. Corrected for roles meant that the roles in
> the default bpmn were not created at installation so I created n
flow adapter [4] for
the workflow engine that an organization like yours might have already
in place.
Regards.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, March 29, 2013 4:07 AM
To: dev@syncope.apache.org
Subject: Re: Activiti approval fails on
for our organization.
Regards, Dave.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Friday, March 29, 2013 4:07 AM
To: dev@syncope.apache.org
Subject: Re: Activiti approval fails on deny
Hi David,
you will find my replies embedded below.
Regards.
Hi David,
you will find my replies embedded below.
Regards.
On 28/03/2013 21:23, Walker, David R. (JMD) wrote:
When using the default workflow (corrected for roles)
I guess you are running 1.1.0-SNAPSHOT: correct? What does "corrected
for roles" mean? Can you provide your userWorkflow.bpmn20
When using the default workflow (corrected for roles) the approval task will
accept a response of "No" but the user is provisioned to the denied resource
anyway. What is the correct approach to denying access to one resource but
granting access to others?
Scenario:
1. Admin creates a new
