When you create a workflow using Create Workflow under Available Actions, the generated HTML is similar to the example below:
{% extends "base.html" %} {% block css %} <link rel="stylesheet" href="css/example_page.css?version={{ g.version | urlencode }}"> {% endblock %} {% block title %} {{ text['title'] }} {% endblock %} {% block heading %} {{ text['title'] }} {% endblock %} {% block custom %} <p>{{ text['info'] }}</p> <!--Your page's HTML goes here.--> {% from "form_helper.html" import render_form %} {{ render_form(form, action=url_for('exampleexample_example_page_form'), id="example_page_form") }} {% endblock %} {% block scripts %} <script src="js/example_page.js?version={{ g.version | urlencode }}"></script> {% endblock %}
Note: This template extends the base.html template provided by
BlueCat. This means that the existing libraries will be kept up to date and any new
JavaScript library will be automatically included. This library will work for you
unless you rely on a specific version of a certain library or add to your workflow
any additional libraries. If you have any customizations and to avoid any library
collisions in the future, BlueCat recommends to create your own HTML template. The
same applies for any custom CSS changes. The only CSS customizations supported by
BlueCat Gateway and guaranteed to remain compatible are if you
create a custom UI theme and set it in config.py as the
ui_theme parameter.