Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Context: Household

NameDescription
actionName of last action in household history
carbalTotal A/R Ending Balance for Current Month (Does include Repayment balance)
ha_cityHousing Authority City
ha_cszHousing Authority City State Zip
ha_emailHousing Authority Email
ha_faxHousing Authority Fax
ha_nameHousing Authority Name
ha_phoneHousing Authority Phone
ha_stateHousing Authority State
ha_str1Housing Authority Street 1
ha_str2Housing Authority Street 2
hh_careofHead of Household mailing Care/Of
hh_cszHead of Household mailing city, state, zip
hh_dobHead of Household Date of Birth
hh_emailHead of Household email
hh_fmlname or lsfmlnameHead of Household full name: First M. Last
hh_fnameHead of Household First Name
hh_lfmnameHead of Household full name: Last, First M.
hh_mnameHead of Household middle name
hh_prphoneHead of Household Primary Phone #
hh_ssnHead of Household SSN
hh_straptHead of Household mailing with with apt no
hh_surname or lssurnameHead of Household surname, including title.
insdtschedDate of Scheduled Inspection
lastCreditPostedOnLast Payment Date
newContractTenant's current Contract Rent
newHapTenant's current HAP
newtenTenant's Monthly Charge/Rent
nextardtDate of next annual recertification
ofc_cityOther HA Office City
ofc_cszOther HA Office City State Zip
ofc_emailOther HA Office Email
ofc_faxOther HA Office Fax
ofc_nameOther HA Office Name
ofc_phoneOther HA Office Phone
ofc_stateOther HA Office State
ofc_str1Other HA Office Street 1
ofc_str2Other HA Office Street 2Street 2
oldContractPrevious contract rent amount
oldHapPrevious Hap amount
oldtenPrevious tenant rent amount
outputdateCurrent Date

{ DATE  \@ "dddd, MMMM d, yyyy"  \* MERGEFORMAT }

Use this (with the quotation marks included) to put in a date without a time
If copying into existing mergefield then delete pre-existing mergefield code between brackets, leave one space adjacent to each bracket and copy and paste in from the "D" from "DATE" all the way to the "T" on "MERGEFORMAT" → This will display as "Thursday, January 30, 2020"

Remove the 'dddd' portion to remove the name of the day from the generated output.


TIP: Easiest way to achieve desired date format is to highlight an outputdate mergefield, then right click, select "Edit Field...", under "Field Names" select "Date", then select your desired date format.


ppu/accountNumberppuCode or acctnum
pgmnameProgram Name
prjname (Doesn't work)Project Name
<<{substring(ppuCode , 0 , 6)}>>Project Code
totarbalTotal A/R Ending Balance for Current Month (Does include Repayment balance)
typeschedType of Inspection Scheduled
u_aptnoUnit Apartment Number
u_bathsUnit's # of Bathrooms
u_bdrmsUnit Size (# of Bedrooms)
u_cityUnit City
u_cszUnit City State Zip
u_stateUnit State
u_str1Unit Street Address Line 1
u_straptUnit Street Address Line 1 plus Apt Number
u_yrbuiltYear Built
u_unitNumberUnit Number
user_emailHA employee/user email
user_fnameHA employee/user first name
user_lnameHA employee/user last name
user_nameHA employee/user name
user_signatureN/A
user_titleHA employee/user title
work_order_tableIterate over all work order's tied to a household
members_tablehousehold members table
waiting_list_tableAll waiting lists that this household is assigned to

balDueCurrentMonth

Balance for the last 0-30 days
balDue30To60Balance for the last 30-60 days
balDue60To90Balance for the last 60-90 days
balDue90To120Balance for the last 90-120 days
balDueOver120Balance over 120+ days old
balDueOver90Balance over 90+ days old.

...

Waiting List Table (Household Context)

(<<rr_waiting_list_table>><<er_waiting_list_table>>)

NameMerge Field
Waiting List Namewl_name
Waiting List Application Datewl_dton

...

Household Action (Household Action Context)

The initial need for this new merge field coordinator and the merge fields it provides is to support Tax Credits including TIC forms/templates and the TTP template.

NameMerge Field
annualcheckbox on top of the TIC form, shows if this is an annual recertification
effdteffective date of the action initiating the TTP or TIC form
fixedRentReasonreason for household's fixed rent
hh_moveindthousehold move in date
imputedAssetIncomeimputed asset income calculated at the time the action took place
inclimitcurrent income limit of household per family size
inclimitx140current income limit of household multiplied by 140% (1.4)
initcheckbox on top of the TIC form, shows if this tenant income certification is for an initial move in
isFixedRateRentdoes the household have a fixed rate rent
maximumChargemaximum rent charge allowed
minimumChargeminimum rent charge allowed
mi_famcntcount of family members at the time of the move in
mi_inctotal income of the househole at the time of move in
speccheckbox on top of the TIC form, shows if this is a certification for a reason other than move in or annual recertification
otherdescnote field used if spec field above it set
passbookRate

imputed asset rate, currently set at 0.06% as defined by HUD

ppuCodePPU Code / account number
totalAssetIncometotal annual income from assets
totalCashValuetotal cash value of assets
totalExpenseAnnualtotal annual expenses
totalIncomeAnnualAdjustedtotal annual income, adjusted
totalIncomeOthertotal value of other income
totalIncomePensions

total value of pensions

totalIncomeWagestotal value of wages
totalIncomeWelfare total value of welfare
ttpFinalRentfinal rent charge
ttpFixedRenthousehold's fixed rent amount
ttpPercenttotal tenant payment percent
utilityAllowanceunit's utility allowance for household
u_unitNumberunit number

Tenant Ledger Context

Mergefields:

"_id"

"accountRecords"

"actionId"

"closingBalances"

"closingDate"

"conveyanceDate"

"deactivatedOn"

"formattedUnitTenantStatus"

"headFirstName"

"headLastName"

"household"

"householdActions"

"moveInDate"

"moveOutDate"

"openingDate"

"ppuCode"

"program"

"programName"

"programType"

"project"

"projectName"

"projectSegmentCode"

"tenantLedgerName"

"unit"

"unitAddress"

"unitCSZ"

"unitNumber"

"unitPPUCode"

"unitSegmentCode"

"unitStreetAddress"

"unitTenantStatus"

"transactions"

"__v"

"numAccountRecords"

"sortField"

Tables:

"accountRecords"

"householdActions"

"transactions".

accountRecords
"name"

"accountDefinitionId"

"accountId"

"actionId"

"chartOfAccountsId"

"deactivatedOn"

"displayName"

"isAR"

"isPrimary"

"isBadDebt"

"isDeposit"

"isPrincipal"

"programId"

"projectId"

"unitId"

"openingBalance"

"closingBalance"

"transactionIds"



Deposit Report Context

Deposit Transactions Table
«rr_depositTransactions»/«er_depositTransactions»
«sequenceNumber»
«householdName»
«categoryName»
«subCategoryName»
«amount»

«postedOn»

«accountName»

«ppuCode»

Deposit Groups Table
«rr_depositGroups»/«er_depositGroups»
«groupName»
«groupTotal»

«subGroups»

SubGroups Table
«rr_subGroups»/«er_subGroups»
«subGroupName»
«subGroupTotal»

Non-Table Mergefields
«depositSequence»
«depositCreatedOn»

«depositPostedOn»

«depositTotal»

...


Docmosis Documentation

*Don't utilize any quotes on the outside of expressions or mergefields, they're written here to emphasize it's a piece of code or an input/output. Some expressions/mergfields may utilize single or double quotes within themselves, these are okay to use and are part of the code.

Using Expressions

Sometimes an expression will work with the already existing mergefield name - you'll simply place the name of the mergefield in the expression.

Other times you may need to establish a variable for the expression to recognize it and be able to use it. In that case, to establish a variable you will place a dollar sign in front of a newly created word.

For example, we have an already existing mergefield named "applicationDate" but we need to apply an expression to it to modify it. We will establish a new variable named "application" by writing this in the top of the document (top of the document is the best place as it needs to be read by the system first before being able to be used further below in the document). That looks like this: "$application=applicationDate"  (Once again, please don't use the double quotes when you actually do this, they're there to emphasize it's code or a named variable.) This line of code will automatically be hidden by Word as long as Docmosis accepts it as an established (functioning), new variable. You will then use an expression below this line of code to augment the date from the mergefield named "applicationDate" by writing "<<{dateFormat(application, ‘MM/dd/yyyy’)}>>" now that we've established that "applicationDate" mergefield has been turned into a variable called "application".

Establishing an expression that is a sum of two already existing mergefields:

In this case, using currentAmountDue and newten on a billing statement to add the new projected rent (updated from an interim) with the current amount billed looks like the following...
<<$totalCurrentAmountDue={currentAmountDue+newten}>>
<<{numFormat($totalCurrentAmountDue,'$#,##0.00')}>>


Below are some useful expressions for Doorways templates:

Formatting a Monetary Value:

myVal = variable name or pre-existing mergefield.

<<myVal{renderer=number(‘$#,##0.00’)}>>

This will change an input such as "1127.4" into "$1,127.40".

If you're having an issue with a monetary amount not rounding to the 2nd decimal place, use this expression: «carbal» $<<{round(carbal,2)}>>  make sure to right click the carbal mergefield, click on Font, and press the hidden button, otherwise you will see the amount displayed twice (the expression requires that the mergefield be in the document in order to work so that's why we keep it there but hide it). 

...