|
The current Client transfer functionality asks the initiating user to provide the target branch, the receiving user will decide on the target group/loanofficer.
We would like to be able to optionally already provide destinationGroupId and staffId in the first step, to allow a real maker/checker workflow where a head-office will approve the transfer.
To make the code more flexible another bit of functionality that would be useful is to allow the above stated transfer, to also work within the same branch, so branch remains the same, but group or staffId changes. This allows us to make one workflow for all transfer related activities that can be maker/checker-ed.
|
