Some interesting discussions have resulted in feedback from some business partners around the concepts of Composite Application Editor (CAE) and wiring components. Since CAE is now in the Notes runtime - which can optionally be disabled - it is only natural to think general users will use CAE to create their own business contextual applications. Or not... Some partners have gone so far to say their business users will never use CAE and only a power user would. What is interesting is the Expeditor platform brings the ability to have several layers of component interaction. I hope to clarify the different ones in this posting. The reason is, there are even more ways business users, power users, admins, and developers can get components to speak to each other.
The developer traditionally is responsble for hardcoding communication between components. This means it most likely can not be changed at the run time however there could be thing put into the UI that allow the end user to change behavior - more later.
Power users or administrators can use tools like CAE or Portal to wire components together and create new applications from existing components with no programming.
The business user or "Samantha" can also use runtime tools like CAE to create new composite apps or re-wire existing ones to change behavior. There is also another choice and that is the concept of Click to Action. You can search the internet for what Click to Action is - but in short - it is a slick user interface that allows Samantha to "wire", "link" or change behavior of the application just by pointing and clicking within the application itself. This means, she did not go into another screen or open an application editor to change behavior - she just clicked a menu or selected an option in the UI to have a component publish its data to something else. What is really cool about this concept is the fact the state can be saved per application screen - down the individual rectangle level so Samantha does not have to set this wire up the next time she is in that screen - in short, it remembers the selection and just acts the next time.
So what kind of shop do you have? Do you have a shop where only developers would wire components? Do you have a shop where administrators or power users would wire components or create composite applications? Do you have a shop that would allow business users to use tools like CAE to create their own contextual composite applications? Or do you have a shop where Samantha would strictly be limited to only UI wiring like Click to Action concepts?
To Wire or not to Wire, and then whom?