Dev

[frozen-occult]

Description

Describe the changes made and why they were made. (Ignore if these details are present on the associated Apache Fineract JIRA ticket.)

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made.
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.
• If merging this PR resolves a JIRA issue, I will mark that issue as resolved and set "Fix Version/s" appropriately.
• I followed the AI Policy.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[adamsaghy]

Please make sure you are following our PR title and commit message conventions:

You need a FINERACT JIRA ticket to cover the changes
Use that JIRA id in the PR title and commit message as prefix. Like: "FINERACT-1234: Short description of the change"

[vidakovic]

You implemented this with the legacy command processing... this just duplicates efforts later, because if this here lands in develop then someone else has to pick it up again and fix it for the new command processing. Have a look at FINERACT-2169.

[vidakovic]

Also: multiple authors... and you as the one who created this PR is not verified. Please configure your account with a GPG certificate.

[Aman-Mittal]

Seems like Author is not responding.Closing this PR. Please Reopen with proper ticket if this is for upstream contribution.