I am very excited to be involved in what is probably the project with the largest scope/size that of which I have had involvement. I have been doing small websites for HumanArc since my hire. The next project is a large-scale application that touches many different departments. It was in the initial phases of this project that I first heard of UIPAB.
All I can tell you so far is that UIPAB is an acronym for User Interface Process Application Block. There are Enterprise level Microsoft Architecture Solutions being defined in project X. UIPAB is coming on the heels of CSLA. Component-based Scalable Logical Architecture is a software framework for standard ways to create robust object oriented programs using business objects (as summed up on Wikipedia.
My first lightbulb came from the line 'It is designed to abstract the control flow and state management out of the user interface layer into a user interface process layer'. I understand state because I understand the statelessness of web applications, as well as the overhead of trying to maintain state in the stateless web. If generic code can manage the process of defining state in windows and web applications I am all for it.
Of course, as time goes on and project requirements change, I may or may not be implementing UIPAB. There may not be a requirement for it because of CSLA.
More to come...