Hoping nobody minds stealing this thread I'd like to ask how (simple) approvals are enabled in the first place? I've updated to 1.2.7 and both created a user in self-service and assigned a role to an existing one, but neither triggered an approval task for admin (and both tasks completely finished)? Does the default workflow support approvals, or do I need to change that in the first place to trigger approvals anyway?
Best regards, Martin On Thu, Jan 21, 2016 at 2:49 PM, Dhairya <dhairya.s...@gmail.com> wrote: > I've been evaluating Syncope (v1.2.6) for about 3 weeks. I was able to > figure out most of the stuff we need to do (like syncing, provisioning, > basic role approval) but we also have a requirement that user be able to > submit multiple independent approval requests. I did setup basic approval > as indicated on http://blog.tirasa.net/approval-process-syncope.html but > it seems the user can only submit one approval request and once the user is > waiting approval, he is unable to login into his own profile. > > The scenario we have is like this... > > We have several approval roles based on the application you're requesting > access to. > > app-a-approver-role > app-a1-role > app-a1-role > > app-b-approver-role > app-b1-role > app-b2-role > > app-c-approver-role > app-c1-role > app-c2-role > > So if the user selects app-a1-role, app-b1-role, and app-c2-role then we > need to generate three independent approval request to > app-a-approver-role, app-b-approver-role and app-c-approver-role. > > if app-a-approver and app-b-approver approve then the user will be > assigned app-a1-role and app-b1-role and if app-c-approver-role rejects > then the user won't be assigned app-c2-role. > > How do I setup something like this? > > Thanks, > Dhairya Shah > > > -- If 'but' was any useful, it would be a logic operator
