[
https://issues.apache.org/jira/browse/SYNCOPE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635402#comment-16635402
]
ASF subversion and git services commented on SYNCOPE-1369:
----------------------------------------------------------
Commit 6f6d91569d94112023f74b42898354d190d7d180 in syncope's branch
refs/heads/2_1_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=6f6d915 ]
[SYNCOPE-1369] User requests forms now support dropdowns - via Flowable
customization
> 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)
