[jira] [Commented] (SYNCOPE-1369) User requests

["Francesco Chicchiriccò (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SYNCOPE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625823#comment-16625823 ] 

Francesco Chicchiriccò commented on SYNCOPE-1369:
-------------------------------------------------

While working with this issue, I have found the brand new [Flowable Form Engine|https://www.flowable.org/docs/userguide-form/] which looks quite an exact match for user requests detached from user workflow.

I think now that the best solution would be:
 # leave the Flowable's features as current, but refactor the code as an extension which includes the Modeler
 # define the new {{UserRequest}} entity and related to match the features available with Flowable Form Engine
 # adjust REST services, Admin Console and Enduser UI to cope with the new User Request entity

> User requests
> -------------
>
>                 Key: SYNCOPE-1369
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1369
>             Project: Syncope
>          Issue Type: New Feature
>          Components: common, console, core, documentation, enduser
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.1.2, 3.0.0
>
>
> With user requests, users can initiate whichever request among the ones defined, for example "assign me a mobile phone" or "give me those groups on AD", for them or on behalf of others; once initiated, such requests can then follow their own path, which might include one or more approval steps.
> There is also no limitation on the number of concurrent requests that an user can initiate. 
> Unfortunately, our current implementation is not able to properly implement the user requests as briefly outlined above; among other things, the impossibility to handle more than an approval process at a time, per user.
> Hence, and a major refactoring is needed:
> # remove approvals features from the current Flowable user workflow adapter 
> # define a new UserRequest entity, which includes at least
>     ## some triggering conditions
>     ## a Flowable workflow definition, possibly containing approval form(s)
> # adjust REST services, Admin Console and Enduser UI to cope with the new User Request entity



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)