josehernandezfintecheandomx opened a new pull request, #2569:
URL: https://github.com/apache/fineract/pull/2569

   ## Description
   
   Instead of only supporting the Delinquency Classification as a separate job, 
we need to make sure that it can be configured as a Business Step as part of 
the COB. 
   
   There might be use-cases where in a Loan COB, another business step wants to 
build upon the delinquency information but serializing the Delinquency 
Classification job and the Loan COB steps is quite challenging so it’s best if 
the Delinquency Classification logic can be included as part of the Loan COB.
   
   [FINERACT-1721](https://issues.apache.org/jira/browse/FINERACT-1721).
   
   ## Checklist
   
   Please make sure these boxes are checked before submitting your pull request 
- thanks!
   
   - [ ] Write the commit message as per 
https://github.com/apache/fineract/#pull-requests
   
   - [ ] 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 coding conventions at 
https://cwiki.apache.org/confluence/display/FINERACT/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
   
   - [ ] Submission is not a "code dump".  (Large changes can be made "in 
repository" via a branch.  Ask on the developer mailing list for guidance, if 
required.)
   
   FYI our guidelines for code reviews are at 
https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to