...
Disclaimer
The page extensions linked to below in this knowledge base are provided as examples only, ‘as is’ and are tested and working on new installations of EngageIP. These are to be used or customized at your own risk. Page Extensions may cause in-browser errors or may not function correctly if:
The adminportal interface has been customized
Other page extensions are in place and interfering
The browser is not fully supported based on the scripting used , i.e. JavaScript
Lists or column preferences in reports or lists are changed, sorted, or paginated. Please be sure to fully test any page extension added to your system
Adding a Page Extension
Page Extensions allow you to inject a piece of JavaScript code into any page rendered through EngageIP’s view engine. The code can interact with the client DOM directly, intercept other executing code or invoke custom code blocks that you have added to the system. Here are the steps to add a page extension:
Log into EngageIP as an adminstrator
Navigate to the Setup tab
Under the Extensibility heading select Page Extensions
Note: Prior to EngageIP version 8.5.17.0 the Page Extensions link was listed under the Configuration heading on the Setup tab
On the Page Extension listing, click Add
What the Fields Mean
Here is a sample listing of Page Extensions added to one system:
...
There are really only two fields here that we care about: Name and Page.
The Name is simply used to help you remember what the script does. It is a good practice to name this script in a way that makes it easy to locate the source file where you maintain your scripts under source control. In this example, a prefix (“Application” or “Ticket”) is used to help sort the page extensions and each entry could represent a separate script file under source control.
...
Content Under this Section
| Page Tree | ||||||
|---|---|---|---|---|---|---|
|