After all templates have been completed and merged, a final review is required for consistency and to take advantage of iterative changes made while in process. Namely:

• Ensure all templates follow a similar pattern in terms of parameter names and what needs to be exposed
• Implement a single approach for both rhpam70-authoring and rhpam70-trial-ephemeral in terms of allowing KIE server access to both the Maven repo of business-central and hence the new kjar, as well as potential dependencies. The solution would be based on one of two PRs, both not merged at the time of writing: https://github.com/jboss-openshift/cct_module/pull/228 and https://github.com/jboss-container-images/jboss-kie-modules/pull/24
• Set proper labels to allow filtering all artifacts created by the template in each invocation (app-name + template) as well as all artifacts of a given type (only KIE servers of rhpam70-kieserver-postgresql, or only its Postgres artifacts).
• Look into collapsing multiple services with one port in each (https://github.com/jboss-container-images/rhpam-7-openshift-image/blob/rhpam70-dev/templates/rhpam70-authoring.yaml#L228-L269) to one service with multiple ports in it (https://github.com/jboss-openshift/application-templates/blob/master/datavirt/datavirt63-basic-s2i.json#L162-L196)
• Double-check issues JBPM-6691 and JBPM-6692.
• Remove any provided value for secret name as a template parameter and make it required (see comments)
• Where using EAP cluster, leverage the newer DNS ping approach.
• Add RH SSO configuration points to all templates that include businesscentral or businesscentral-monitoring per BAPL-897.
• Add MAVEN_EAP_USERNAME / MAVEN_EAP_PASSWORD to businesscentral section of appropriate templates after RHPAM-891.
• Make sure that templates have required annotations to properly show up in the service catalog, when loaded.