...
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.
Later on, data entry page must be implement giving the ability to the user create, view, modify, delete or apply other operations on a process run record. Below, we can see the detail page of the process run definition and specifically the process runs tab, showing the successful whilst failed runs.
Expand | ||
---|---|---|
| ||
|
In addition, an XMLUtilBean need to be implemented, in order to save action inputs, criteria and schedule settings in the xml. Also this, messageRunDefinitionXMLUtilBean extends ProcessRunDefinitionXMLUtilBean.
...