Table of Contents

Search

  1. Preface
  2. Overview, Downloading, and Installing
  3. Administration API
  4. Identity Service API
  5. Screenflow Programming and SDK
  6. ActiveVOS WSHT API
  7. Embedding Request Forms in Standalone Web Pages
  8. XML-JSON for Process Central

7. APIs, SDKs, and Services

7. APIs, SDKs, and Services

Process Central Includes

Process Central Includes

When Requests (and Task) forms are displayed in Process Central, they only use the contents of the
<body>
in the HTML form. The HTML elements in the
<head>
are not used. This means any references to
<meta>
,
<script>
,
<link>
, and
<style>
elements are not included in Central's main page.
<head> <!-- Include 3rd party script to show tree control plugin. This example requires the jQuery treeview script and the css. --> <link type="text/css" href="js/treeview/jquery.treeview.css" rel="stylesheet" /> <script type="text/javascript" src="js/treeview/jquery.treeview.js"/> <!-- Include your custom or common scripts that is shared with other forms --> <script type="text/javascript" src="js/some_util.js"/> <!-- Inline CSS --> <style type="text/css"> p {margin-left: 2em;} </style> <!-- Inline common script --> <script type="text/javascript"> // execute your code. e.g. jQuery $(document).ready( function() { // do something }); </script> </head> <body> </body>
If the HTML form is as shown above, Process Central discards the contents of the
<head>
, which means your custom script and CSS including third party scripts and CSS (for example, jQuery tree-view) are not loaded and executed. This is because the page that is displaying Central only deals with form content (body). In order to inject (or contribute) custom scripts and style into the main page that is displayed by Process Central, the custom scripts and CSS must be specified by using an include within the
.avcconfig
file. With Central Includes, all custom scripts, link, styles, and meta elements contributed by one or more forms are aggregated and dynamically included in
<head>
of the main display page of Central.
The Central Includes for the above sample HTML is shown below in the
<centralIncludes>
element (in an
.avcconfig
file).
<!-- Central Includes in the .avcconfig file --> <tns:centralIncludes> <!-- Contents of the xhtml head go here as-is, with xhtml namespace. The path to resources must be absolute href or relative to this .avcconfig file. E.g. js/treeview/jquery.treeview.css --> <!-- Third party library (jQuery treeview for example) --> <link xmlns="http://www.w3.org/1999/xhtml" t type="text/css" href="js/treeview/jquery.treeview.css" rel="stylesheet" /> <script xmlns="http://www.w3.org/1999/xhtml type="text/javascript" src="js/treeview/jquery.treeview.js"/> <!-- Custom scripts --> <script xmlns="http://www.w3.org/1999/xhtml" type="text/javascript" src="js/some_util.js"/> <!-- Inline CSS --> <style xmlns="http://www.w3.org/1999/xhtml" type="text/css"> p {margin-left: 2em;} </style> <!-- Inline common script --> <script xmlns="http://www.w3.org/1999/xhtml" type="text/javascript"> // execute your code. e.g. jQuery $(document).ready( function() { // do something }); </script> </tns:centralIncludes>
Note
: The XHTML elements
<meta>
,
<script>
,
<link>
, and
<style>
declared in the
<centralIncludes>
must be in the XHTML namespace (
http://www.w3.org/1999/xhtml
). When deploying the
.avcconfig
file, all resources referenced in the Central Includes (for example, JavaScript files, CSS files) must also be deployed to the server.