Dynamic Data Management: Global DDM Settings
Dynamic Data Management User Guide
Top Use Cases for Dynamic Data Management
Encompass 18.4 Dynamic Data Management Demo
This feature is not available in Encompass Broker Edition.
This setting was introduced in Encompass 18.4 (See the Release Notes).
Global DDM Settings includes default and user-defined settings to trigger the user defined DDM Fee rules and Field rules. Triggering DDM rules would mean the application of active fee rules and field rules to a loan file. When the fee rules and field rules are applied to a loan file, Encompass will consider only the scenarios that are active under each active rule at the time of DDM rule execution.
- By default, DDM rules will apply on a Loan Save or Loan Create event. User will not be able to modify this option.
- In addition to loan save, you may choose to trigger DDM rules on a ‘Field Change’ event, specifically when a user modifies a field. You can use the Add icon in the Fields table to manage your list of impacted fields. Once you add a field, you will have reference to the number of active and inactive scenarios under which this field is being referenced.
We strongly recommend reviewing the fields you provide here. The higher the number of fields, the greater the impact on performance for the user. If the user can wait until the next loan save for the field updates to occur, then there is no need to add those fields here. However, if there are critical fields such as Subject Property State (field ID 14) or Loan Program (1401) that you want updated sooner than the next loan save or other trigger event, then add those fields here.
Global DDM Settings also enable you to define a default global condition on when DDM rules should stop auto-populating the data in a loan file. This default stop condition correlates to the advanced code you set up as part of the condition you configured for a fee rule or field rule. You may modify this default condition when you define the rule – the rule will be applied based on the stop condition that exists at the rule level.
For more information, see the Dynamic Data Management User Guide.