Using Custom Fields

General

LoanPro lets you create custom fields in order to keep track of things that the system doesn’t track by default.  You can  add custom fields in four specific areas of a loan: Loan Setup,  Loan SettingsCollateral, and  Insurance.  You may also create custom fields in other areas including investor,  customerpayment, and  source company. This article will cover the different ways that these custom fields can be used throughout the software.

Custom Forms

Because custom forms are a way for companies to track information that is not native to LoanPro, they are very commonly used on  custom forms

To add a custom field to a custom form, navigate to Settings > Loan > Custom Forms > Form Management and select    next to the form on which you would like to display the custom field.

Once you are in the form editor select on the right-hand side of the screen and then search Custom Fields. Now select the section containing the custom field that you would like to add to the form (e.g. Collateral, Setup, Settings, etc.). Once you have selected the section, you will see a list of custom fields contained in that section. If you are editing an HTML form, make sure your cursor is positioned on the form where you would like the custom field variable to show and then select the hyperlink for the field you would like to add from the Expected Values list.

Notice that after selecting the hyperlink, the correct variable will be added to the form with the correct custom field ID. However, the word “PROPERTY” will need to be replaced by “value” as shown above.

Select Save to finish editing the form.

Note: If you are adding the custom field to a DOC file type custom form, you will need to add the correctly formatted variable (i.e., [[v('settings-custom-fields.30.value')]]) to the word document that is being used to generate the custom form. Then re-upload the word document to LoanPro inside of the correct custom form.

If the updated form is now generated inside of a loan, the value that has been entered in the selected custom field for the specific loan will be displayed where the variable has been added on the form.

Notifications

Because loan specific variables are generated using the Context Engine, the process of adding custom field variables to an email is extremely similar to the previously explained process of adding them to a custom form.

To add a custom field to an Event Based Notification, navigate to Settings > Company > Notifications > Event Based Notifications and select    next to the notification on which you would like to display the custom field.

You may add a custom field to the content of the Email, System, Mail House, or Web Hook notifications. SMS templates and variables will need to be configured with Solutions by Text.

Steps for adding a custom field to Email, System and Mail House notifications: 

1. Scroll down and place your cursor in the content box where you would like the custom field to appear  

2. Select Help Variables 

3. Search "custom fields" 

4. Select the section in which the desired custom field is found 

5. Select the custom field from the Expected Values hyperlinks 

6. Inside of the custom field variable in the content box, change "PROPERTY" to "value" 

7. Select Save

Follow this same process to add a custom field to a trigger based or manually sent notification.

Rules/Triggers

LoanPro gives you the ability to complete certain actions or processes on an account automatically based off of certain criteria being met. You may create this criteria using  rules. Using a custom field in a rule is very similar to using any other variable that is native to the system. However, a very specific formatting is required.

For example, if you click the Expected Values hyperlink for a custom field with an ID number of 31 found in Loan Settings, you would see that (-> settings-custom-fields (get :31) :PROPERTY) has been added to the rule. All of the formatting is correct, except just like in the custom forms and notifications, you will need to change "PROPERTY" to say "value".

Example rules with custom fields:

True/False output for currency or number type fields: (> (Double/valueOf(-> settings-custom-fields (get :31) :value)) 0) - This rule would evaluate whether or not a currency type custom field with ID 31 has a value greater than $0.

True/False output for select type field (= (-> settings-custom-fields (get :19) :value) "This value") "This value" - This rule would evaluate whether or not a select type custom field with ID 19 has a specific value selected. "This value" would need to be replaced by the ID of the select value that you would like to run the rule off of.


How did we do?


Powered by HelpDocs (opens in a new tab)