1. User Guide
  2. Business Rules Administration
  3. Cashflow Assumptions
  4. Behavior Patterns

Behavior Patterns

PBSM (Profitability and Balance Sheet Management) Cloud Service’s User Defined Behavior Patterns allow you to define Principal Amortization Schedules for Non-Maturity Products in your portfolio. You can utilize a Behavior Pattern to generate Cash Flows by entering the Amortization Type Code as “Behavior Pattern” along with the actual Behavior Pattern Code for the relevant Instrument Records.

Behavior Pattern Summary

This page is the gateway to all Behavior Patterns and related functionality. You can navigate to other pages relating to Behavior Patterns from this point.

Figure 4-33 Behavior Pattern Summary


Behavior Pattern Summary

Search Behavior Pattern

Prerequisites: Predefined Behavior Pattern

To search for a Behavior Pattern:

Click Search after entering the search criteria. The search results are displayed in a table containing all the Behavior Patterns that meet the search criteria.

The Behavior Pattern Summary displays the following information:

  • Code: Numeric code of the Behavior Pattern
  • Name: The Behavior Pattern's name.
  • Behavior Type: The type of Behavior Pattern.
  • Last Modified By: The user who last modified the Behavior Pattern.
  • Last Modified Date: The Date and Time when the Behavior Pattern was last modified.
  • Action: Click this icon to view a list of actions that you can perform on the Behavior Pattern.
    • View: You can view an existing Behavior Patterns.
    • Edit: Based on the user privilege assigned, you can edit existing Behavior Patterns. To edit a rule, you must have Read/Write privilege.
    • Save As: You can reuse a Behavior Pattern by saving it under a new name thus saving time and effort in entering data multiple times; it also leads to reduced data entry errors.
    • Delete: You can delete Behavior Patterns that you no longer require. A Behavior Pattern that has a dependency cannot be deleted.
    • Dependency Check: You can perform a dependency check to know where a particular Behavior Pattern has been used. Before deleting a rule, it is always a good practice to do a dependency check to ensure you are not deleting Behavior Patterns that have dependencies. A report of all rules that utilize the selected Behavior Pattern is generated.

      Note:

      This is functionality will intended for a future release.

In addition to above actions, you can perform below actions using icons located at top right side of the summary:

  • Add: Click the Add icon on the page header to build a new Behavior Pattern.
  • Multiple Delete: Enables you to select and delete one or multiple rules in the tables simultaneously.
  • Download: Export contents of summary to a CSV file
  • Refresh: Click refresh icon to reload the summary.
  • Help: Click help icon to access online guide to use Behavior Pattern.

Also See: