You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/09/17 10:07:34 UTC

[jira] [Resolved] (SYNCOPE-550) Provide cleaner user workflow definition for production

     [ https://issues.apache.org/jira/browse/SYNCOPE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò resolved SYNCOPE-550.
--------------------------------------------
    Resolution: Fixed

> Provide cleaner user workflow definition for production
> -------------------------------------------------------
>
>                 Key: SYNCOPE-550
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-550
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.2.0, 1.3.0
>
>
> Currently the same {{userWorkflow.bpmn20.xml}} used for integration tests is also packaged - and then enabled by default - in any Syncope distribution.
> While such definition contains various elements, showing most of the potential that can be exploited by empowering Activiti - form-based approval, scripting and so on - it also features some test-related configurations which are pretty useless and confusing when starting with a clean implementation.
> It is definitely worthwhile to separate the two things and leave the test {{userWorkflow.bpmn20.xml}} when test data are loaded - debug / embedded Maven profiles, standalone distribution - while providing a simpler and cleaner {{userWorkflow.bpmn20.xml}} for all the rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)