Title: Message Title
|
|
|
|
|
Sander van der Heyden: So the transfer is not proposed by a head/Higher office User who has data scope to both the destination and target branch for the Transfer.
The earlier approach we had taken was that a user of one branch does not have data scope to another branch (would not be able to view both staff and the groups of the destination group) Optionally changing the data scope is not a biggie....just wanted to explicitly mention the same.... )
|
|
|
|
|
|
|
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.
...
|
|
|
|
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
