Using Status Lines


When viewing the Ares HTML pages through Notepad, Microsoft Visual Studio or an HTML editor like Dreamweaver or Frontpage, you will notice tags that are represented by the text <#somevalue>. These tags are instructions to the ares.dll file, which controls the web pages during the user's session.

One such tag is the STATUS tag. In Ares, the STATUS tag is controlled by the Status Line customization keys, housed in the Customization Manager. An example of a STATUS tag is the line Choose an option from the choices below, shown on the Instructor and Student Main Menu page (the web pages IHome.html and UHome.html).

The STATUS tag

All STATUS tags within the DLL are customizable and not hard-coded. The STATUS tag as seen in the HTML page looks like this: <#STATUS>. The STATUS tag generally displays at the top of the associated menu to show relevant status messages for that page of the web interface.

While it is common to put the STATUS tag at the top of the web form, you can place it wherever it may be best visible. The tag has no additional specifications, as the text of the status itself is customized within the Customization Manager under Web | Status Lines.

Multiple Status Tags

In some cases, there may be more than one STATUS tag separated by line breaks. For example, if a user attempts to submit a request and there are several required fields missing values, each error message would have its own line. So while there would only be one STATUS tag in the HTML, the resulting text may be several lines long in a few instances.

Configuring Status Lines

Status Lines correlate to the specified STATUS tag in the HTML web pages and are customized in the Configuration Manager under Web Status Lines. They are plain text entries though font colors can be specified as well. To change the text of a Status Line, simply click on the line you wish to edit, make your changes and click the Save button.


If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation: