[JBoss JIRA] (SRAMP-142) governance console to pick up tasks
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-142?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-142:
--------------------------------
Fix Version/s: 0.3.0 JBPM6 Integration
> governance console to pick up tasks
> -----------------------------------
>
> Key: SRAMP-142
> URL: https://issues.jboss.org/browse/SRAMP-142
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Governance
> Reporter: Kurt Stam
> Assignee: Kurt Stam
> Fix For: 0.2.0 Security, 0.3.0 JBPM6 Integration
>
>
> I'd like to put in a link to the exact task in the notification email. I can link to the jbpm-console, but it'd be a lot nicer if we can embed the taskforms in a governance ui.
> Note that we typically use groupIds (dev, qa, etc), and that people in this group need to claim this task first, before they can work on it.
> Something like, Scott being in qa, and looking for the tasks he is participating in, and then claiming task 53:
> http://localhost:8080/gwt-console-server/rs/tasks/scott/participation
> {"tasks":[{"id":53,"processInstanceId":"87","processId":"overlord.demo.SimpleReleaseProcess","name":"overlord.demo.CheckDeployment","assignee":"","isBlocking":true,"isSignalling":false,"outcomes":[],"currentState":"OPEN","participantUsers":[],"participantGroups":[],"url":"http://localhost:8080/gwt-console-server/rs/form/task/53/render","priority":0}]}
> POST http://localhost:8080/gwt-console-server/rs/task/53/assign/scott
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-142) governance console to pick up tasks
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-142?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-142:
--------------------------------
Fix Version/s: (was: 0.2.0 Security)
> governance console to pick up tasks
> -----------------------------------
>
> Key: SRAMP-142
> URL: https://issues.jboss.org/browse/SRAMP-142
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Governance
> Reporter: Kurt Stam
> Assignee: Kurt Stam
> Fix For: 0.3.0 JBPM6 Integration
>
>
> I'd like to put in a link to the exact task in the notification email. I can link to the jbpm-console, but it'd be a lot nicer if we can embed the taskforms in a governance ui.
> Note that we typically use groupIds (dev, qa, etc), and that people in this group need to claim this task first, before they can work on it.
> Something like, Scott being in qa, and looking for the tasks he is participating in, and then claiming task 53:
> http://localhost:8080/gwt-console-server/rs/tasks/scott/participation
> {"tasks":[{"id":53,"processInstanceId":"87","processId":"overlord.demo.SimpleReleaseProcess","name":"overlord.demo.CheckDeployment","assignee":"","isBlocking":true,"isSignalling":false,"outcomes":[],"currentState":"OPEN","participantUsers":[],"participantGroups":[],"url":"http://localhost:8080/gwt-console-server/rs/form/task/53/render","priority":0}]}
> POST http://localhost:8080/gwt-console-server/rs/task/53/assign/scott
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-117) Add caching of ontologies to JCR persistence layer
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-117?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-117:
--------------------------------
Fix Version/s: 0.4.0 API Management
(was: 0.2.0 Security)
> Add caching of ontologies to JCR persistence layer
> --------------------------------------------------
>
> Key: SRAMP-117
> URL: https://issues.jboss.org/browse/SRAMP-117
> Project: S-RAMP
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Persistence
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.4.0 API Management
>
>
> The getOntologies method should return a cached version of the ontologies rather than reading the JCR nodes each time. The cache should be invalidated when ontology nodes are changed. This can be done by hooking into the JCR eventing feature. The eventing feature of JCR may or may not be supported by the JCR impl - so only cache if eventing is available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months