Hi,
we are currently evaluating syncope as a replacement for our proprietary IAM system. We think that modelling internal processes with BPMN would allow better communication of our processes. Therefore we are looking into using the flowable functionality. After testing some things out it seems that the configuration of a flow is instantiated when it is started and then never changed for the lifetime of this workflow instance. For the user process tis would mean that we will not be able to change the user management flow after initial importing of an user. Our User management process is not changing rapidly but there are some changes here and there. Some of these changes are minor and could be implemented by changing the serviceTask implementation classes. Some of them are bigger and we would want to reflect them in the BPMN representation. If I am not mistaken that would mean that we would have to reimport all 30k+ Users and move them into the right state so that they would benefit from the new process in the future. I understand that applying a new version of the workflow to an existing instance would be a challenge. For example the new version could depend on flow variables that are not available in the current state of the current instance. Nevertheless I think this is a main impediment when using the flowable functionality. Do I understand this restriction correctly or is there a way to “migrate” a given user to a new workflow variant? Mit freundlichen Grüßen Clemens (Bergmann) -- Clemens Bergmann [er/ihm; he/him] Gruppe Nutzermanagement und Entwicklung Technische Universität Darmstadt Hochschulrechenzentrum, Alexanderstraße 2, 64283 Darmstadt Tel. +49 6151 16 71184 <http://www.hrz.tu-darmstadt.de/> http://www.hrz.tu-darmstadt.de/
smime.p7s
Description: S/MIME cryptographic signature
