This function is only available to users with the System Administrator role
RESTRICTED
Custom sub-tabs
In ASSURE, every application or worksheet, and some other records, are presented as a collection of tabs, and each tab may have one or more sub-tabs. System administrators can add custom sub-tabs to any application, worksheet or tabbed record (such as HMO Details records). These custom sub-tabs are specific to your authority.
Each sub-tab must have a unique name within the worksheet.
Each sub-tab can include either a static or a repeatable collection of fields.
Any field can be made mandatory, and whether it is mandatory may depend on the value of another field.
ASSURE keeps a record of changes to the worksheet's sub-tab configuration and presents the sub-tabs that were current when the worksheet was created. This means that new worksheets always have the current configuration, but earlier worksheets look the way they did when they were created.
Name-Address Collector fields are available only for ASSURE Public Protection.
A Name-Address Collector field is used to collect the name and address of a person who is in some way relevant to the worksheet. If the worksheet has a Relevant Persons tab, this person will automatically be visible there.
The field is defined by its label, and the relevance of the person (from the Contact Type code type). In the sub-tab, the ✚Add Detail link will open a Person Details dialog in which the user can identify the person, their contact details, and the period of their association.
M3PP User Defined fields are available only for ASSURE Public Protection.
An M3PP User Defined field is defined by its label and one of the 70 user-defined LA Code types (LA Code 01 to LA Code 70). In the sub-tab, the active codes in the code type are presented as a drop-down list. Only one value can be chosen.
Multiple field sets
On a multiple sub-tab the set of fields is repeatable. The user can add, edit, and remove any number of field sets. Each set is captured by a dialog that has the same name as the sub-tab.
When the custom sub-tab is used, it will include a table that summarises the captured field sets. Any field can be defined as a column header for this table, as long as there is at least one. Ideally, the fields chosen as column headers should be capable of uniquely identifying each field set.
Dependent mandatory fields
A dependent mandatory field is one that can be made mandatory depending on the value of a parent field. The dependent field can be of any type, but the parent field must be one of the following types:
Checkbox
Drop-down List
Radio Button
M3PP User Defined (only for Public Protection)
Multiple dependent fields may refer to the same parent field. A dependent field may itself be the parent field for another dependent field.
Merge fields for custom sub-tabs
Both the field labels and their populated values are available as merge fields for document production, but there are some differences depending on the type of template.
Note that TABNAME, SUBTABNAME and FIELDLABEL are in upper case and any space characters have been removed. The PKID number is not important unless the sub-tab includes two fields with the same label.
To use these merge fields in a template, the correct Sub Tab Application Type must be specified in the Letter Template Details screen.
For a sub-tab with a multiple layout, the sub-tab fields can be inserted as either:
A repeating section, within a pair of <%rs_DOCUMENT> and <%es_DOCUMENT> tags.
Rows of a repeating table, within a pair of <%rr_DOCUMENT> and <%er_DOCUMENT> tags.
Refer to the ASSURENCS Template Guide for details.
For MS Word/TMT templates (also known as DP templates):
Field labels are available in the SUBTABDATA_DESC child schema in the form:
SubTabName__FieldLabel__DESC.
Field values are available in the SUBTABDATA child schema in the form:
SubTabName__FieldLabel.
Note that double underlines __ are used as separators in the merge field names, not single underlines.
For a sub-tab with a multiple layout, these fields must be referenced within a pair of {MERGEFIELD TableStart:CHILD_SCHEMA_NAME} and {MERGEFIELD TableEnd:CHILD_SCHEMA_NAME} delimiters.
To use these merge fields in a template fragment, the correct Application type must be specified in the Template Fragment Details dialog.
Note
The SUBTABDATA_DESC and SUBTABDATA child schemas include fields from any sub-tabs that have previously been defined for this application type but which are now hidden, as well as the current sub-tabs.
NEC Software Solutions welcomes your feedback on our documentation.
If you have any comments about the current ASSURE Help, or want something to be added in a future revision, please contact the NEC Software Solutions HelpHub.
If your comment relates to this particular Help topic, remember to include the following information:
Product
Help revision
Help topic
File name
ASSUREVersion 25.2.0.0
Revision 0Draft A
Custom sub-tabs
admin_gen_subtabs_con.htm
Your comments help us to improve our product information. Thank you.