dspCompose
TEMPLATE COLUMN Information
BackOffice recommends that the text entered in the TEMPLATE COLUMN field on the Template (Org Units) page correspond to a column in the template that stores the Org Unit values.
In the example above, the TEMPLATE COLUMN value MARA-SPART corresponds to a Division value on the template.
When the template is generated, dspCompose™ creates an Org Unit table in the cMass_Data database for the template with the name tt[template name]OrgUnit. This table contains a column named after the value entered in TEMPLATE COLUMN in the example above.
To simplify joins between tables, it is a best practice to enter the name of the column in the template recording in the TEMPLATE COLUMN name on the Template (Org Units) page. If the Template Administrator chooses to write views that tie other tables, such as the data entry tables, to the Org Units table, it is easiest if the column names match.
The Org Unit table also contains the request ID and the Org Units for the request, which are populated when a request based on the template is saved.
NOTE: If the data entry table does not exist when the template is generated, the security view will not be automatically generated. This situation can occur when the template is a custom template with custom data entry pages.
NOTE: If the value entered in the TEMPLATE COLUMN column on the Template (Org Units) page does not exactly match a column in the data entry table, that Org Unit will be excluded from the generated security view. To add the Org Unit, the security view will have to be manually modified to include a join from the TemplateColumn name in the Org Unit table to the appropriate column in the data entry table.
Refer to Incorporate the Security View into Request Processing for more information.
NOTE: There is no automatic linking of Org Units into request processing. Once the Org Unit table is created and a request that uses Org Units is saved, it is up to the Template Administrator, using DSP® development skills to then customize a solution. Refer to Incorporate the Security View into Request Processing for more information.
The Template Administrator could:
-
Join the Org Unit table into the Data Entry View for the request
-
Join the Org Unit table into list boxes to limit valid list box values to only those values associated with the Org Unit
-
Use the table to write validation rules
-
Use the table to write control views to allow users to view but not edit request data
-
Use the table to write default procedures or default views
NOTE: Refer to Work with Org Unit Assignments at the Request Level for more information.
