Mauricio Salatino [https://community.jboss.org/people/salaboy21] modified the 
document:

"BPM Console Proposed Components"

To view the document, visit: https://community.jboss.org/docs/DOC-18742

--------------------------------------------------------------
This document a set of decoupled documents to provide the functionality that is 
already provided by the bpm-console
The main focus is to keep all the components as decoupled as possible using a 
central bus of communication to share information between them.

* 
 #Process_Components Process Components


** 
 #1_Process_Definitions_List 1) Process Definitions List


** 
 #2_Process_Definition_Details 2) Process Definition Details


** 
 #3_Process_Instances_List 3) Process Instances List


** 
 #4_Process_Instance_Details 4) Process Instance Details


* 
 #Global_Requirements Global Requirements




h1. Process Components
This section describe all the component related to Business Processes. This is 
how the jbpm-console looks right now:
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19004/Screen+Shot+2012-07-14+at+11.22.57+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19004/450-254/Screen+Shot+2012-07-14+at+11.22.57+AM.png
 
This functionality will be decoupled in the following components
h2. 1) Process Definitions List
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19005/Screen+Shot+2012-07-14+at+11.27.19+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19005/261-578/Screen+Shot+2012-07-14+at+11.27.19+AM.png
 
Requirements for this component:
* Query Process Definitions* Use the Rest Implementation
* Provide a pluggable way to hook any runtime (basically using an interface)
* Add filter option by process definition name
* Pagination
* Filter by type of definition
* Refresh
* Double clicking in one of the rows of the list must open the Process 
Definition Details component

We should have a local implementation to not depend on the jbpm-console 
server.. 

@TODO: analyze how the current rest implementation is returning the process 
definitions. We should list all the process definitions from the VFS, does it 
have ways of filtering things?
If it does, let's create a local implementation of this service inside the 
process definitions list widget to avoid using an external component and speed 
testing.


h2. 2) Process Definition Details
I'm not sure if this was included in the jbpm-console. We should provide a 
detailed view about the process which should allow us to see the process 
diagram and the BPMN XML text.
It should also contain a link to edit the process using the process designer 
which should be provided as a separate component. 

@Toni: can we get reuse the code for displaying the diagram of the process here 
from the old console? or is it in someway using something that we will not have 
available here?



h2. 3) Process Instances List
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19006/Screen+Shot+2012-07-14+at+11.27.30+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19006/450-240/Screen+Shot+2012-07-14+at+11.27.30+AM.png
 
Requirments for this component: 
* Filters (by process definition, started date, state, etc)
* Pagination
* Refresh
* Perspectives (show and hide colums, but we should be able to show all of them 
from the begining)
* build a local implementations and see if we can use the Rest Services for 
this. A local service which give us the information required for this shouldn't 
be difficult to create.
We must avoid for the first version the buttons to create,delete and signal the 
process instances. That should not be responsability of the process instances 
list component, see Process Instance Details Component 

h2. 4) Process Instance Details
The process instance detail component should be in charge of showing us the 
current status of a process instance along with the process information and the 
controls to interact with that specific instance.
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19007/Screen+Shot+2012-07-14+at+11.27.40+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19007/450-77/Screen+Shot+2012-07-14+at+11.27.40+AM.png
 
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19008/Screen+Shot+2012-07-14+at+11.45.12+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19008/450-142/Screen+Shot+2012-07-14+at+11.45.12+AM.png
 
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19009/Screen+Shot+2012-07-14+at+11.45.20+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19009/450-46/Screen+Shot+2012-07-14+at+11.45.20+AM.png
 
 
https://community.jboss.org/servlet/JiveServlet/showImage/102-18742-3-19010/Screen+Shot+2012-07-14+at+11.51.27+AM.png
  
https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18742-3-19010/215-35/Screen+Shot+2012-07-14+at+11.51.27+AM.png
 
@TODO add all the actions and parameters for each action. 


h1. Global Requirements
For the BPM components perspective we will not deal with authentication or 
authorizations, that must be provided by the application that is using the 
components. But there are some basic things
that our components will be waiting in order to decide how to render themselves.

There should be an Administrator Role and also we can create an Owner role that 
can be mapped to different groups or users. 
All the components should recieve and use the role provided by the containing 
applicaiton.
--------------------------------------------------------------

Comment by going to Community
[https://community.jboss.org/docs/DOC-18742]

Create a new document in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2034]
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to