Common Support Questions

General

This article is intended to help with common troubleshooting related to custom forms, computation fields, custom fields, and rules applied. For further information not found in this article, check here: Template Logic

Custom Forms

How to Evaluate a Rule Formula in a Custom Form

  • [[evalFormula('(- status-scheduled-payments 1)')]]

How to Evaluate a Rule Formula in a Custom Form AND Format the Number Output

  • [[formatNumber([[evalFormula('(- status-scheduled-payments 1)')]],'2','.',',')]]

How to use Computation Fields in Custom Forms

  • [[v('computation-fields.5.calculated-value')]]

If you would like to include Secondary Borrower information on a custom form, you must use this statement or similar for the output to be correct

  • [[IF customer.secondary.full-name ]][[v('customer.secondary.full-name')]][[ELSE]][[END]]

More Formatting Options 

  • Phone Number

[[formatPhoneNumber ('settings-custom-fields.1.value')]]

  • Company Date Format

[[companyFormatDateTime('current-date',’F’)]]

  • Currency

[[formatNumber('setup-total-amountt')]]

  • Zip Code

[[formatZipcode(‘tenant-zipcode’)]]

  • Currency as Words

[[formatNumberAsText('setup-payment')]]

  • Check Format (Text plus 50/100)

[[formatNumberAsCheck('setup-payment')]]

Select Type Custom Fields Output Values

The way 'Select' type custom fields work is when you choose to display one on a form it will output the ID of the selection rather than the actual text. This is the case for every section EXCEPT Customer Custom Fields.

So, in short, if you need to use select type custom fields in a custom form, you will need to use [[evalFormula to 'trick' it into printing the actual text unless you are using Customer Custom Fields, in which case you can just use the variable.

Example: [[evalFormula('(if (= (-> settings-custom-fields :35 :value) "1") "Not Obtained" (if (= (-> settings-custom-fields :35 :value) "2") "Experian" (if (= (-> settings-custom-fields :35 :value) "3") "Transunion" (if (= (-> settings-custom-fields :35 :value) "4") "Equifax" " "))))')]]

Additionally, here's a list of how the formatting of each custom field actually works:

  • Setup: (-> setup-custom-fields :9 :value)
  • Settings: (-> settings-custom-fields :8 :value)
  • Collateral: (-> collateral-custom-fields :10 :value)
  • Insurance: (-> insurance-custom-fields :12 :value)
  • Customer: (-> customer :primary :customer-custom-fields :14 :value)
  • Employer: (-> customer :primary :employer-custom-fields :15 :value)

Computation Fields

How to turn a string into a number using Double/valueOf (most commonly used for evaluating on Custom Fields)

  • (+ (Double/valueOf(-> settings-custom-fields :9 :value)) 100)

How to Format a Date in a Formula

  • (u/format-date (u/date-+ setup-contract-date 3) "MM/dd/yyyy")

Payment Schedule Creation

The following example shows how to create a payment schedule inside a word document:

To achieve this, you will input the [[BEGIN scheduled-payments]] in between the two tables shown in the screenshot, then change the [[BEGIN...]] and [[END]] font size to 1 pixel.

Shown above is a screenshot of what the table will look like when it is generated on a custom form, email, etc. It lists the history of payments made on an account from oldest to newest.

Listed below is the HTML for the table above.

Example HTML:

<table>
<tbody>
<!–[[BEGIN payments]]–>
<tr>
<td>$[[formatNumber(payment-amount, '2', '.', ',')]]</td>
<td>[[formatDateTime(payment-date, 'm/d/Y', '')]]</td>
</tr>
<!–[[END]]–>
</tbody>
</table>

Alternate Example:

Example HTML:

<table style="width: 40%; border-collapse: collapse;">
<tbody>
<tr>
<th style="padding 3px; border: 1px solid;">Payment Date</th>
<th style="padding 3px; border: 1px solid;">Payment Amount</th>
</tr>

<tr>
<td style="padding-left: 5px; padding 3px; border: 1px solid;">[[payment-date]]</td>
<td style="padding-left: 5px; padding 3px; border: 1px solid;">$[[payment-amount]]</td>
</tr>

</tbody>
</table>

The table can be formatted as needed.

Payment Information Formatting Option Examples

  • Next Scheduled Payment ie. 1st, 15th

[[FormatDateTime('next-scheduled-payment-date','jS')]]

  • First Payment Date ie. 1st, 15th

[[FormatDateTime('setup-first-payment-date','jS')]]

  • First Payment Date ie. January, February, March

[[FormatDateTime('setup-first-payment-date','F')]]

  • First Payment Date ie. 2015, 2016, 2017

[[FormatDateTime('setup-first-payment-date','Y')]]

  • First Payment Date ie. 2015, 2016, 2017

[[FormatDateTime('setup-first-payment-date','y')]]

  • Final Payment Amount (commonly used when the final payment amount of a loan is different than the rest)

[[ BEGIN scheduled-payments ]][[ IF $_last  ]][[ $amount ]][[ END ]][[ END ]]

Rules Applied

Below is a list of commonly used clojure segments used in Rules Applied.

In many cases, the formatting found in these examples can be applied to different variables.

(= (-> portfolio (get :10) :active) 1) - Portfolio is Active

(not= (-> portfolio (get :10) :active) 1) - Portfolio is Not Active

(-> checklist :10 :value (= 1)) - Checklist item is checked

(-> checklist :10 :value (= 0)) - Checklist item is unchecked

(= (u/date-compare (u/today :format :date) (-> checklist :10 :last-updated)) 0) - Checklist item was checked on current date

(= (-> settings-custom-fields (get :10) :value) "1")) - Settings Custom Field Equals a certain value

(not= (-> settings-custom-fields (get :10) :value) "1")) - Settings Custom Field does not equal a certain value

(> (u/date-compare (u/today :format :date) (-> settings-custom-fields :10 :value)) 0) - Comparing Today with a settings custom field date

(or (= (-> settings-custom-fields (get :10) :value) "") (nil? (-> settings-custom-fields (get :10) :value))) - a settings custom field is blank or null (meaning there’s nothing in it, or nothing ever has been in it)

(or (= settings-account-closed-date "") (nil? settings-account-closed-date )) - Account closed date is blank or null (meaning there’s nothing in it, or nothing ever has been in it) 

(= setup-active 1) - Loan is activated

(= setup-active 0) - Loan is not activated

(= (-> customer :primary :primary-state) "CA")) - Primary Customer State equals a value ‘CA’

(= (-> settings-credit-status) "loan.creditstatus.97") - Credit Status equals a value ‘97’

(= (-> setup-payment-frequency) "loan.frequency.biWeekly") - Loan Frequency equals a value ‘biWeekly’

(not (empty? bankruptcy-case-number)) - Case Number contains a value

(not= bankruptcy-case-number “”) - Case Number contains a value


How did we do?


Powered by HelpDocs (opens in a new tab)