Title: Message Title
|
|
|
|
|
|
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. Ideally the inter-branch and inside-branch transfers would have different approve permissions, to make sure branch manager can approve inside-branch and head-office / other branch approves inter-branch
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
