Aesthetic changes can be made for single users or groups of users by directing each user/group to different custom .aspx pages. However, we suggest using Application Themes instead to encapsulate groups of changes, which can be selected dynamically in the API.
To visually integrate Exago, make a copy of the ExagoHome.aspx file and modify the elements surrounding the Exago control or override the CSS of the user interface itself.
Note
Do not make changes directly to ExagoHome.aspx as they will be overwritten during upgrades. Instead use the example below to create a custom .aspx page.
The example below is the minimum code necessary to embed the Exago control.
<%@ Page Language="C#" EnableViewState="false" EnableEventValidation="false" %> <%@ Register src="WebReportsCtrl.ascx" tagname="WebReportsCtrl" tagprefix="wr" %> <!DOCTYPE html> <html> <head runat="server"> <title>Exago</title> </head> <body> <form runat="server"> <wr:WebReportsCtrl ID="WebReportsCtrl" runat="server" /> </form> </body> </html>
Several properties can be set on the Exago Control to modify various settings and behaviors of Exago. The following properties can be set.
ConfigFile="NorthwindConfig.xml"
).
Note
If entering Exago through the Api this parameter is ignored.
LanguageFile="es-mx, getting-started-custom"
).ForceIECompatMode="true"
).XUaCompat="true"
).
Note
IE8 is no longer supported by Exago, as of v2016.1.
All of the CSS and images used by Exago can be modified within the aspx page if desired. However we recommend using an Application Theme instead.
Any icon in Exago can be changed on a per-company or per-user basis:
<element id="ExportTypeMenuHtml" image= "ConfigImagesCustomHTMLExecutIconLarge.png"></element>
For icons that have hover effects there is a special naming convention.
To change custom icons with hover effects:
To find the Ids of icons in Exago: