Search
/
|
|
|

Classes in app_code

EfficiencySpring contains several standard classes in app_code which are used throughout the platform.

Class Description
EfficiencyCommonC.EfficiencySpringPage This class is inherited by every .aspx file within the EfficiencySpring platform. It inherits the System.Web.UI.Page class, with its local Page_Init function called on every page load. This class has an extensive list of page level variables and functions, all of which have corresponding XML documentation within the class files.
 
EfficiencyCommonC.DesignManager

This class is used to load, process, and output EfficiencySpring's visual design. It contains the code that loads and renders the design from the database, as well as functions for displaying dynamic portions of the design, such as menus and sidebar panes.

EfficiencyCommonC.ContentPage This class inherits the EfficiencyCommon.ContentManager.ContentPage class and is instantiated whenever EfficiencySpring renders a content page. Customizations to how content is rendered can be made to the GetContentToDisplay function.
 
EfficiencyCommonC.Instance This class inherits the EfficiencyCommon.ProcessManager.Instance class and is instantiated whenever EfficiencySpring loads an instance of a Process Manager process. Customizations can be added to the wrapper functions of this class.
 
EfficiencyCommonC.InstanceStep This class inherits the EfficiencyCommon.ProcessManager.InstanceStep class, providing developers the ability to customize how step outcome paths are filtered as well as how text for emails is assembled. One of the two constructors for the EfficiencyCommonC.Instance class accepts an instance of this class as its fourth parameter; if passed in, all steps instantiated within that process instance will utilized the passed in version of InstanceStep as the basis for all of the internal step objects the process instance creates.
 
EfficiencyCommonC.Record This class inherits the EfficiencyCommon.DataManager.Record class, providing developers the ability to customize things that happen before and after record loading, creation, edits, deletions, and server-side validation within Data Manager. Within the app_code\data_manager folder, multiple examples of how the Record class has been customized for EfficiencySpring's administrative tools can be found.
 
EfficiencyCommonC.RecordSearch This class inherits the EfficiencyCommon.DataManager.RecordSearch class, providing developers the ability to customize the search SQL that the class generates, before that SQL is passed back the results, export, and reporting code.
 
EfficiencyCommonC.StructureElement This class inherits the DataManager.StructureElement class, providing developers the ability to customize multiple aspects of a structure element's data loading, output, and validation. An instance of this class can be passed into the EfficiencySection.LoadElements() function, which will cause all of the internal StructureElement objects created by that section to use the inherited customized StructureElement class as a template.
 

 


Printable Version