Navigation to Editability: System Management>Lending>Editability

Editability allows the Administrator to select which (typically restricted) fields, collections and actions are editable Pre-Decision, Post-Decision, Post-Disbursement or Post-Withdraw. The Editability Administrator page contains a database table that allows a user with the appropriate permissions to individually select which fields, collections and actions may be performed on a global level.

Administrators are able to add or restrict the Editability of these fields through rules. If a rule is driven by data that changes post-decision/disbursement or if Editability is altered through the Administrator side, Editability does not change until the user logs out or the app pools recycle.

Five factors determine the Editability of a field: User Permissions, Editability selection, Editability Rules, UI Editability and System Defined Editability.

Editabilty settings are managed on the Field Editability System Management Page located in System Management>Lending>Editability. 

Framework Administrators are able to update the field Editability, however a cache refresh must occur prior to the Editability changes to take effect. There are seven events which trigger a Cache Refresh:

•       Make Decision

•       Remove Decision

•       Disburse

•       Withdraw

•       Remove Withdraw

•       Logout/Login

•       Change Product

 

If any of these events do not occur, the Editability changes will not take effect. For this reason, it is advised that Editability is updated during off hours.

Fields Tab

The Fields tab lists every field that is either system-defined or custom. On the Fields tab, an Administrator can view all of the fields, Allow Pre-Decision editability, Allow Post-Decision editability, Allow Post-Disbursement editability and Allow Post Withdrawing editability.

The Fields Tab contains the following Permissions: Allow Post-Decision, Allow Post-Disbursement and Allow Post Withdraw.

Permission	Description
Allow Pre-Decision	Allows a user to edit a field during the loan origination process (prior to rendering a decision).
Allow Post-Decision	Allows a user to edit a field after a decision.
Allow Post-Disbursement	Allows a user to edit a field after disbursement.
Allow Post-Withdraw	Allows a user to edit a field after the application has been withdrawn.

Custom Field Editability

When custom fields are added to the Framework, the “script” will configure the default editability, however, an Administrator is able to update the Editability rights immediately.

Collections Members Tab

The Collection Members tab contains groupings of related application objects such as Applicants, Collaterals and Payees. An Administrator is able to check whether a collection can be added/deleted Pre-Decision, Post-Decision, Post-Disbursement or Post Withdraw. For example, if an Administrator selects that “Application.Applicants” can be added Post-Decision, then a user with the proper permissions is able to add an Applicant even after the loan is decisioned. 

The Collections tab contains the following Permissions: Add Pre-Decision, Delete Pre-Decision, Add Post-Decision, Delete Post-Decision, Add Post-Disbursement, Delete Post-Disbursement, Add Post Withdraw and Delete Post Withdraw.

Permission	Description
Add Pre-Decision	Allows a user to add a collection during the loan origination process (prior to rendering a decision).
Delete Pre-Decision	Allows a user to delete a collection during the loan origination process (prior to rendering a decision).
Add Post-Decision	Allows a user to add a field after a decision.
Delete Post-Decision	Allows a user to delete a field after a decision.
Add Post-Disbursement	Allows a user to add a field after the application has been disbursed.
Delete Post-Disbursement	Allows a user to delete a field after the application has been disbursed.
Add Post Withdraw	Allows a user to add a field after the application has been withdrawn.
Delete Post Withdraw	Allows a user to delete a field after the application has been withdrawn.

Actions Tab

The Actions tab displays a list of actions that may be performed Pre-Decision, Post-Decision, Post-Disbursement and Post Withdraw. For example, an Administrator may allow certain users to “Get Valuation” Post-Decision. A user is then able to perform this action after the loan has been decisioned.

The Actions tab contains the following Permissions: Allow Pre-Decision, Allow Post-Decision, Allow Post-Disbursement and Allow Post Withdraw.

Permission	Description
Allow Pre-Decision	Allows a user to perform an action during the loan origination process (prior to rendering a decision).
Allow Post-Decision	Allows a user to perform an action after the loan has been decisioned.
Allow Post-Disbursement	Allows a user to perform an action after the loan has been disbursed.
Allow Post Withdraw	Allows a user to perform an action after the loan has been withdrawn.

Editability Rules

Rules Management allows an Administrator to refine Editability by authoring rules in the Editability category. A user may have the permissions granted in both User Permissions and Editability rights but still have Editability actions revoked through rules.

When writing Editability rules, rule authors are able to refine editability to users and security groups.

For more information on Editability Rules, refer to the Rules section in the Administrator Guide.

UI Editability

Certain Framework Fields, such as Length at Address, are calculated fields that users are unable to manually edit within the field.

System Defined Editability

Certain actions can take place only when the application is in a particular state. For example, a user cannot update from core when an application is disbursed. These types of restrictions fall into System Defined Editability.

Additionally, certain Framework Screens may restrict access to edit a particular field. This is evaluated on a page by page basis. If a screen restricts Edibility then it revokes all user permissions, Editability and rules.