Configuring the HUD ARM Module
The user-facing HUD configuration steps are:
1 - Inactivate any previous HUD forms or processes you have in place
2 - Create a new HUD ARM form
3 - Create a new HUD ARM process
4 - Add the new HUD ARM process to a menu on the case profile
Creating the new HUD form
Add the field: HUD Form 9902 Eligible to this form
Add the block: HUD ARM Data & Matter Overrides to your new HUD form
Understanding the HUD ARM Block
This block does more than let the user choose to Override what information is sent in the HUD data report. The block also lets the user, on the same block, add or edit case data, when the field is a HUD-specific field that can be placed on other forms. The block also serves as a case level check to be sure that you aren't accidentally using custom, non-HUD fields to collect data that needs to be entered into HUD's format for electronic submission.
Although some of these fields can be placed on forms outside this block, it is not configurable, and is carefully designed to exactly match HUD's rigid data definitions.
Add Override - will transmit the user's input in HUD transmissions, depending on the analysis LegalServer will perform in applying HUD's multi-level override rules
Edit Case Data - will appear when there is *already* data in the field, usually captured at intake or on another form
Add Data to Case - will appear when the field exactly matches HUD's requirements but has no data in it
Optional Branch Logic
You may want to put the entire HUD ARM Data block behind Branch Logic so that if the user does not select Yes, this case is HUD Form 9902 Eligible, the user doesn't see the HUD ARM Data block.