...
In following steps, five summary pages need to be implemented with the image below illustrates the run definition summary page. Furthermore, another four summary pages should be created, one for the process run drill down, including another two for the successful and failed entries accordingly and lastly one summary page for the previous versions, as we can see. 
| Expand | ||
|---|---|---|
| ||
|
In this case, a UI class have to implement as well extending the CRMUIProcessRunDefinitionBean. Also, module id and process id, must be defined in the UI as they declared in the module.xml file. To implement the basic functionality, we will need to create the following methods: createButton, loadForm, editButton, saveButton, submitButton, deleteButton and amendButton.
...
On the last step, the CRMProcessRunBean mentioned in the module.xml as additional process need to be implemented whilst the method executeMessageProcess which executes the process runs via threats mechanism like in Implement a multithreaded process section. Firstly, process run method saves the action inputs. then Then each process run request processed from a thread and if everything procedure works correctly, the next process run prepared prepares to been processed and the current one saved as completed. On the other hand, if something goes wrong, the current process run is saved as failed and moves to process the next request. This procedure continues until all the process run requests pass from the multi-threading mechanism. As a result, all the successful and failed process runs are illustrated in the summary page image above.
...