Description
When a loan product with the borrowcycle feature enabled is created without filling the required details, the product is successfully created. However, issues arise when this loan product is later assigned to a client. The problem occurs in the conditional logic that follows:
- Issue: The conditional check on the loancycle counter assumes it will always have a numerical value. However, in cases where the borrowcycle is enabled but no specific details are provided, the loancycle counter is set to null.
- Impact: This results in a NullPointerException during the execution of the conditional check, disrupting the normal flow of the application.
Proposed Solution: To address this issue and ensure a smooth application flow, the conditional logic should be enhanced to account for scenarios where the loancycle counter is null. This may involve updating the conditional checks or setting a default value for loancycle when it is not explicitly provided during loan product creation.