The Selerix Data Model is used throughout the BenSelect architecture.  As such, accessors to that data use the same nomenclature.  That means that the class property names used in the .NET library are the same as the fields in completed form.  The Transmittal XML and the Application XML bear the field names as the Selerix Census template, and so forth.  In fact, the same objects used by web services are also used in BenSelect scripting to customize system behaviors, product rates, report output and so forth.  This means that once you learn one aspect of the system you have effectively learned them all.

 

With that said, some exceptions exist.  Most of the time, enrollees are referred to as either an Employee or a Dependent.  Examples where this rule holds true include:

• The Application object in the .NET library and the corresponding serialized XML
• Report customization scripts
• Enrollment customization scripts
• The serialized XML used by completed forms
• The Selerix Census Template

However, the data Transmittal helper class in the .NET library as well as the corresponding serialized XML used by exclusively by Selerix web services and SAML SSO integrations refer to enrollees as applicants, while Transmittal properties such as FirstName and LastName largely remain the same.