You've seen that UI actions can launch actions and invoke other targets, like client-side and server-side JavaScript, but what if you need to accept user input prior to executing the backend code? In the previous chapter you created a custom Action Handler, which used a JSF-managed bean and a JSP page to accept action parameters. A dialog is a lot like an Action Handler. It uses a JSF-managed bean and a JSP page, but it is not specific to actions. You can use UI actions to invoke a dialog anywhere in the web client.
Let's walk through an example to see how this works.
So far you've addressed several requirements from departments throughout SomeCo, but what about making your own life a little better? Running server-side JavaScript against folders and content is something you and SomeCo's Alfresco administrators will do on a regular basis. But executing scripts on folders and content using the out of the box web client...