Implement your own form renderer for KIE Server

As it was described in this article, KIE Server now provides form renderers for process and task forms built in jBPM Console (aka workbench). Out of the box there are two renderers provided

  • based on PatterFly to provide same look and feel as entire jBPM tooling – it’s the default renderer
  • based on Bootstrap to provide a simple alternative that utilises well established framework for building web and mobile UIs
This obviously won’t cover all possible needs of users and thus the renderers are actually pluggable. In this article we build a custom one from scratch to illustrate what it takes to have your own.

Create project with dependencies

First of all, a new maven project needs to be created. It should be most basic project with packaging jar. Then let’s add required dependencies to pom.xml

<project xmlns="" xmlns:xsi="" xsi:schemaLocation="">
<name>Custom Form Renderer</name>



Create configuration folders

Create folders in the project that will configure the renderer – all should be done src/main/resources

  • form-templates-providers – folder that will contain templates, css and java script files used to render the form
  • META-INF/services/ – an empty file that will be used as discovery mechanism to find and register the renderer – it will be edited a bit later to provide actual implementation details

Create form renderer implementation

In src/main/java create a class (e.g. org.kie.server.samples.CustomFormRenderer) that will extend and implement the required methods 
  • getName – provide the name of the template that shall be used as reference when rendering
  • loadTemplates – main implementation that loads different types of templates to be used by renderer
  • default constructor
IMPORTANT: this new class must be configured as the implementation of the renderer so add its fully qualified class name into 
There are several types of templates that renderer must provide (and load on startup)
  • master – main template that builds the HTML page
  • header – header template that creates header of the form
  • form-group – form input fields template
  • case-layout – layout for case forms
  • process-layout – layout for process forms
  • task-layout – layout for user task forms
  • table – table to be build for multi subforms
The easiest way is to base your customisation on top of the out of the box templates (either patternfly or bootstrap). In this example I will use bootstrap templates that can be found here.
Copy all resources from the linked directory into 
and then implement the loadTemplates method of the CustomFormRenderer class
package org.kie.server.samples;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class CustomFormRenderer extends AbstractFormRenderer {

private static final Logger logger = LoggerFactory.getLogger(CustomFormRenderer.class);

public CustomFormRenderer() {
super(null, null);

public CustomFormRenderer(String serverPath, String resources) {
super(serverPath, resources);

public String getName() {
return "custom";

protected void loadTemplates() {
loadTemplate(MASTER_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/master-template.html"));
loadTemplate(PROCESS_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/process-layout-template.html"));
loadTemplate(TASK_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/task-layout-template.html"));
loadTemplate(FORM_GROUP_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/input-form-group-template.html"));
loadTemplate(HEADER_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/header-template.html"));
loadTemplate(CASE_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/case-layout-template.html"));
loadTemplate(TABLE_LAYOUT_TEMPLATE, this.getClass().getResourceAsStream("/form-templates-providers/custom/table-template.html"));"Custom Form renderer templates loaded successfully.");


Customise your templates

Since the templates where copied from another renderer we need to customise it, let’s start with master template. Open it and replace ${serverPath}/bootstrap with ${serverPath}/custom  
This will ensure that our customised files will be loaded.
Make any additional changes to the master template as needed. I will just add custom text next to header.
Master template is the place where you can add additional scripts or stylesheets. There is main js file called kieserver-ui.js that provide all the logic required to manage and submit forms. It also includes validation, so in case you need extensions to that logic consider to create new file with your changes and replace the location of it to point to your new file.
Make additional customisation to other templates as needed.

Build and deploy renderer to KIE Server

Implementation is completed so now it’s time to build the project and deploy to KIE Server.
  • Build the project with maven – mvn clean package
  • Deploy the project to KIE Server by coping the jar file to kie-server.war/WEB-INF/lib
Start the server and take advantage of your custom renderer by using following URL that works for one of the sample projects – Evaluation (make sure to deploy it before using the renderer).
As you can see new renderer is fully operational and customised to your needs.

That’s it, you have now your custom form renderer. The sample described in this article can be found in GitHub.

Let’s embed forms … rendered by KIE Server

jBPM comes with rather sophisticated form modeller that allows to graphically build forms for processes and tasks. These forms can then be used to interact with process engine to start new instances or complete user tasks.

One of the biggest advantages of using forms built in workbench is that they share the same life cycle as your business assets (processes and user tasks). By that they are versioned exactly the same way – so if you have another version of a process that requires more information to start you simply create new version of the project and make changes to both process definition and form. Once deployed you can start different versions of the process using dedicated forms.

Although to be able to take advantage of these forms users have to be logged into workbench as the only way to render the content is … through workbench itself. These days are now over … KIE Server provides pluggable renderers for forms created in workbench. That means you can solely interact with kie server to perform all the needed operations. So what does this brings:

  • renders process forms – used to start new instances
  • renders case forms – used to start new case instances – includes both data and role assignments
  • renders user task forms – used to interact with user tasks – includes life cycle operations
Worth noting is that rendered forms are fully operational, meaning they come with buttons to perform all the operations that are based on the context – e.g. if user task is in in progress state there are buttons to stop, release, save and complete.
Here are few screenshots on how the forms look like, these are taken from the sample projects that come out of the box with jBPM distribution
Evaluation start process form
Mortgage start process form
IT Orders start case form
As it was mentioned, form renderers are pluggable and out of the box there are two implementations
  • based on PatternFly – this is the default renderer that keeps the look and feel consistent with workbench
  • based on Bootstrap
Renderers can be switched per each form rendering request by simply appending query parameter
?renderer=patternfly or ?renderer=boostrap if not given patternfly is the default one.
Here are few examples of the REST endpoints that illustrate how to get these forms rendered



Note that containers are given as alias so that brings in additional benefits when working with forms and multiple project versions.

And at the end few short screen casts showing this feature in action

Evaluation process

Mortgage process

IT Orders case

Multi Sub Form – dealing with list of items in forms

More technical information will be provided in the next article as this one is just a quick preview of what’s coming. Hope you like it and don’t forget to provide feedback!