[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389021#comment-15389021 ]
ASF GitHub Bot commented on SYNCOPE-880: ---------------------------------------- Github user ilgrosso commented on a diff in the pull request: https://github.com/apache/syncope/pull/26#discussion_r71833076 --- Diff: core/workflow-activiti/src/main/resources/userWorkflow.bpmn20.xml --- @@ -82,12 +82,47 @@ under the License. <serviceTask id="delete" name="Delete" activiti:expression="#{delete.execute(execution.processInstanceId)}"/> <sequenceFlow id="flow99" sourceRef="delete" targetRef="theEnd"/> + <!-- Recertification tasks --> + <userTask id="RecertificationRequest" name="Recertification Request" activiti:candidateGroups="managingDirector" activiti:formKey="recertify"> --- End diff -- You cannot refer to the `managingDirector` group in the production workflow, as production content does not contain such group. Please remove `activiti:candidateGroups` from this element. > Identity Recertification > ------------------------ > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: console, core > Reporter: Nicola Scendoni > Priority: Minor > > Identify Re-certification is required for many national and international > standards like SOX, GxP, etc. > The idea is to implement one scheduled task that filter users basing on some > attributes (example: last recertification date, role,...) and move then on > one state "to be certified" and assign one task to some group that has the > responsibility to recertified the user, or delete it from the system. > Some report should report evidence about when the users have been recertified > and who was the certifier. > > This feature would be also the starting point to create account, role and > groups re-certifications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)