[
https://jira.nuxeo.com/browse/NXP-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=106845#comment-106845
]
Benjamin Jalon commented on NXP-7852:
-------------------------------------
Revert as API modification will be reverted.
https://github.com/nuxeo/nuxeo-social-collaboration/commit/6e6267524949260f143e55c5666ae4c271ba4867
> Implement a document based Task Service
> ----------------------------------------
>
> Key: NXP-7852
> URL: https://jira.nuxeo.com/browse/NXP-7852
> Project: Nuxeo Enterprise Platform
> Issue Type: Task
> Components: Workflow
> Reporter: Thierry Delprat
> Assignee: Laurent Doguin
> Priority: Major
> Fix For: 5.5
>
>
> For now the task are managed only using JBPM.
> This made sense as long as we were using JBPM.
> In the context of the integration of Content Routing as a default workflow
> engine in DM, keeping Tasks in JBPm does not make sense.
> So the target is to build a simple task service based on Documents.
> In order to make migration as transparent as possible we should be sure that :
> - existing automation APIs for creating / listing tasks : will now manage
> Document based tasks
> - existing widgets can display the new Document based tasks without needing
> changes
> The goal for this task is to be able to provide ContentRouting as a 5.5 Addon
> without having to migrate data and without having to keep JBPM.
> => Be sure all Task related feature can work without any change using the
> Document based task system
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
