Welcome to Release 16.00 > New and Enhanced for 16 > New Administrator Functionality > New Configuration Tools in the Lifecycle Management Suite |
With the 16 release, system administrators are provided many new and enhanced configuration options right at their fingertips!
In release 16.00.06, the Search functionality is tied to user and security group permissions that allow system administrators to determine which users are able to perform a search, and access workspaces in the Lifecycle Management Suite.
To support this, the following updates have been made to the Permissions tab in System Management > Users and System Management > Groups > Security Groups:
![]() |
This permission is only available for the Account Servicing modules. |
![]() |
This permission is only available for the Origination modules. |
Reference the following table for an overview of the behavior that occurs for the Search feature when the above permissions are set to None, View, or Change:
Permission | Behavior |
Workspace |
None = Users are not able to use the Search feature, and the
View = Users are able to use the Search feature; however, only screens and workflows that the user is assigned permission to are available in the Left Navigation Panel, and no changes can be made to any screens and/or workflows in the workspace. Change = Users have full access to the Search feature, and are able to perform all functions for the selected account or person in the workspace. |
Origination Workspace |
None = Users are unable to use the Search feature, and the ![]() View = User can access and use the Search feature; however, the selected application opens as READ ONLY in the workspace, and no changes can be made; only a comment can be added to the application while in this state. Change = User has full access to the Search feature, and is able to perform actions within the selected application in the workspace. |
![]() |
For institutions that use both Account Servicing and Origination: Since there are two separate permissions that control the Search feature for the Account Servicing categories and Origination categories, it is possible that a permission may be set to View or Change for one, but set to None for the other. When this occurs, the user is only able to use the Search feature for the modules to which he or she is granted permission to access. For example, if the Workspace permission is set to View or Change, but the Origination Workspace permission is set to None, the user is able to click
|
Easily view a predefined Lifecycle Management Suite report directly within the workspace!
The new Report panel available to add to a screen in System Management > Origination > Screens enables the ability to automatically generate a report with information directly from the application in context, preventing users from having to manually enter report criteria at runtime.
![]() |
For information on the predefined reports available in the Lifecycle Management Suite, please see the Reports topic in the Lifecycle Management Suite User Guide. |
Decisions added to applications can now be automatically captured, stored and displayed in the Lifecycle Management Suite's Loan Origination module!
A new Decision Suggested event and a new Store Decision History action have been added to Event Processing and when configured by a system administrator, trigger when a decision is recommended to store decision information on an application or counteroffer. A new Store Decision History event/action pair has also been added to Event Processing to store decision history when an application is approved, declined, or a decision is suggested.
When these events and actions are enabled and decisions are recorded, the decision information appears within the new Decision History panel that an administrator can configure to appear within an application type screen. The Decision History panel displays a record of each decision within a grid and detail screen to provide users with a complete historical record of decisions added to applications through Event Processing.
Get ready to automate the decline of Countered Applications!
When an application includes counteroffers that have not been accepted, institutions can now activate a process to automatically decline or withdraw the application after a pre-determined amount of time lapses from when the counteroffer was created. This process is enabled through configuration of the new Auto Decline Counteroffered Applications parameters added to the Declined tab on the Solution.Origination page.
Once activated, the Automatic Decline Process for Countered Applications runs each night at 10pm to identify applications with a status of "Countered" and automatically decline any applications that exceed the time frame configured for the Cutoff days to Decline parameter.
![]() |
For more information, please see the Origination and Counteroffer Configurations topics in the Administrator Guide. |
The Lifecycle Management Suite has been enhanced to provide system administrators with the ability to order values of certain Origination field list configurations within System Management!
Previously, values of all field configurations were listed alphabetically in the drop-down when displayed on an application. Now, administrators have the ability to configure the list order of specific account holder facing fields when editing lookup values in System Management > Field Configurations.
For the complete list of fields that can be ordered, please see the Origination Field Configurations topic within the Administrator Guide.