Work Packet Template
NoteBeginning with NLS 5.24, the setup and creation of new Work Packets are no longer supported. Upgraded databases with existing configurations of Work Packet Templates are not affected and will continue to work.
Much of the information required to enter a Work Packet may be common among all the Work Packets of a certain type. To save time, and minimize the chance of errors during data entry, NLS allows you to configure Work Packet Templates. These templates contain much of the information that would usually be entered on a Work Packet, and they allow an operator to bypass the entry of that information by simply selecting the appropriate Work Packet template during the Work Packet entry process.
Work Packet Templates are configured in Setup > Task Setup > Work Packet Template.
The buttons along the top of the Work Packet Template Setup screen are:
|Add||Click to set up a new Work Packet Template. The template is then configured through the tabs: Main, UDF, and Script.|
|Delete||Deletes the selected Work Packet Template. A Work Packet template may only be deleted if there are no existing Work Packets in the database that was built using that Template.|
|Modify||Click to modify the code and the description.|
|Move Up||Moves the focus up one template on the list.|
|Move Down||Moves the focus down one template on the list.|
|Trustee||Allows you to set security on a user level for the Work Packet Templates.|
NLS 4.9.3 and later
Right click on a work packet template and select Export to file to save the work packet to an XML file or select Import from file and choose an XML file from which to import.
The Main tab of the Work Packet Template setup contains information on what type of Work Packet may be set up with that template, as well as default settings for the Work Packet that may be changed or overridden when the Work Packet is created.
|All Types||This template may be used to generate any type of task within NLS.|
|Message Task||This template may be used to generate a task that sends a message to another NLS user.|
|Contact Task||This template may be used to generate tasks that are linked to Contact accounts.|
|Loan Task||This template may be used to generate tasks that are linked to Loan accounts.|
|Collateral Task||This template may be used to generate tasks that are linked to Collateral items.|
|Late Loan Task||This template may be used to generate tasks that are generated automatically by a late loan event.|
|Default Owner||The user selected in this field will be the owner of any task created with this template, unless the owner is changed at the time the task is created.|
|Subject||The text entered in this field is placed as the default Subject Text on all Tasks created with this template.|
|Notes||The text entered in this field is placed by default in the Notes Text field on all Tasks created with this template.|
Each Work Packet Template has its own set of 30 User-Defined Fields, which are configured on a Template by Template basis. The UDF setup (field types and labels) is determined by the Template, but the actual field data is entered on each individual Work packet.
For information on how to set up User-Defined Fields, see User Defined Field Setup.
VB scripts (Visual Basic) may be used to manipulate User Defined Fields on Contacts and Loans, and may also be used for controlling the execution of tasks and Work Packets in the Task Manager.
A VB script that is configured on a Work Packet Template will automatically be on any Work Packet that is created under that template. The execution of that script code is governed by the instruction associated with the script, as follows:
|Before Save||The script is executed upon creation of a new task or modification of an old task, prior to saving that task to the database.|
|Before Activate||The script is executed whenever the task is accessed from the Task Manager main window or from a Contact, Loan, or Collateral item that it is attached to.|
|Before Create||The script is executed when the task is saved, but only if it is a new task. The script is not executed upon the modification of an existing task.|
|On Delete||The script is executed when a task is deleted from the loan system.|
|After Save||The script is executed upon creation of a new task or modification of an old task, after the task is saved to the database.|
|After Create||The script is executed upon creation of a new task, after the task is saved to the database. The script is not executed after modification of an existing task.|