There are actually a plethora of good reasons to keep the PBL architecture around. You bring up a great point with IM but, things like dynamically changing PBL's at run time, using PBL order to help with Unit Testing, Adding a temporary PBL to the developers App list for testing changes before actually accepting the object changes, etc.
There are no replies made for this question yet. However, you are not allowed to reply to this question.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.
There are actually a plethora of good reasons to keep the PBL architecture around. You bring up a great point with IM but, things like dynamically changing PBL's at run time, using PBL order to help with Unit Testing, Adding a temporary PBL to the developers App list for testing changes before actually accepting the object changes, etc.
Regards ... Chris