Hi, I don't think this is particularly unusual...
While department B wants additional features and won't use some of the existing, I am assuming that the features they share, and indeed the business rules behind them all are common. In that case, write an application that does everything for everybody, then set up a security matrix that hides/disables the functionality from those users/groups/departments that don't want it (or shouldn't be using it for security reasons). I seem to remember there was a thread on this list recently discussing various security models using groups, roles and authorities. If you're using an architechture like fusebox, you can easily restrict an action or a circuit to a particular group or user. Ian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188848 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
