Skip to main content

View Configuration

Once a view is ready, it can be published. Publishing takes the configuration for the view and search connections and combines them into a single JSON object for TSearch to process. These are stored separately in the database. TSearch will only ever use the published version of a view. When a view configuration is retrieved, Simflofy will check if there are any permissions on the view. If so, it will remove widgets from the configuration that the requesting user is not allowed to use.


When you make changes to your view, search connection, or widgets you must Publish those changes before you will see them in TSearch

How TSearch Constructs a View

Once you navigate to a view, TSearch loads the index.html page for the template you've chosen. So, the simflofy view index can be found in the "views/simflofy" folder.

This index page is expected to act as scaffolding for jQuery to append onto. The base html for the widgets that are required for functionality should already exist. Many widgets have modals associated with them.

When the javascript for the base widget initializes (more on that in Widgets) it should target these components and add the needed logic and components to them. TSearch has a number of methods to make this process easier. More on that later.

Sections of the Templates

See the TSearch Utility sections for methods to easily add features to these sections.

Simflofy Template

A left-handed sidebar for the template: $(‘#left_sidebar’)
Sidebar widgets should be appended here.

The body section of the page: $(“#body”)
Only the Result widget should interact directly with the body. It appends $(‘#docs”) as a wrapper for the document rows. Most widgets build on top of the Results widgets.

An unordered list <ul> in the navbar for appending menu widgets:

Records Management (RM) Templates

An unordered list <ul> in the navbar for appending menu widgets:

Control the tabs in the RM Template:
$(‘#rmtabs’) and $(‘#rmnavtab’)
Simflofy uses Boostrap’s tabs library. #rmnavtabs represent the clickable tabs, while $rmtabs represents the tab content: