Some cleanup needs to be done on the provided footer beans within the UIF. See the following thread:

From: Jerry Neal jkneal@indiana.edu
Sent: Friday, February 24, 2012 4:27 PM
To: 'Niesen, Claus H [ITUIS]'
Cc: 'Brian Smith'
Subject: RE: footers

Claus,

The Uif-PageFormFooter (maybe 'Uif-FormPageFooter' would be better) would just contain the Save, Close, and Cancel. There is actually a bean for this now ('Uif-FormFooter') so I am suggesting are renamed. Then we have Uif-DocumentPageFooter that extends footer base and has the current list in Uif-PageFooter. Brian might have some further suggestions on naming.

Thanks,
Jerry

From: Niesen, Claus H [ITUIS] cniesen@iastate.edu
Sent: Friday, February 24, 2012 5:18 PM
To: Jerry Neal
Cc: Brian Smith
Subject: RE: footers

Hello Jerry,

Yes, that was the result of my work. What you suggested makes sense. I just need a clarification on the Uif-PageFormFooter, are you suggesting that that should hold all these buttons or that you want to provide that definition (which contains only the save and close buttons) as an extra that people could use if desired?

Claus

From: Jerry Neal jkneal@indiana.edu
Sent: Friday, February 24, 2012 4:04 PM
To: Claus Niesen
Cc: Brian Smith
Subject: footers

Hi Claus,

I am seeing something that I am wondering is a result of the work you did to move the document buttons from the view footer to page footer. We have a Uif-PageFooter definition of:

<bean id="Uif-PageFooter" parent="Uif-FooterBase">
<property name="items">
<list>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="performRouteReport" p:actionLabel="route report"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="sendAdHocRequests" p:actionLabel="send adhoc"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="route" p:actionLabel="submit" p:clientSideValidate="true"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="save" p:actionLabel="save" p:clientSideValidate="true"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="reload" p:actionLabel="reload"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="blanketApprove" p:actionLabel="blanket approve" p:clientSideValidate="true"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="approve" p:actionLabel="approve" p:clientSideValidate="true"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="disapprove" p:actionLabel="disapprove"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="fyi" p:actionLabel="fyi"
p:render="@

"/>
<bean parent="Uif-PrimaryActionButton" p:methodToCall="acknowledge" p:actionLabel="acknowledge"
p:render="@

"/>
<bean parent="Uif-SecondaryActionButton" p:methodToCall="close" p:actionLabel="close"
p:render="@

"/>
<bean parent="Uif-ActionLink" p:methodToCall="cancel" p:actionLabel="cancel"
p:render="@

"/>
<bean parent="Uif-ActionLink" p:methodToCall="copy" p:actionLabel="copy"
p:render="@

"/>
</list>
</property>
</bean>

Which is configured for the default page (Uif-Page). Most of these buttons are not applicable for standard pages. So I think we need a 'Uif-DocumentPage' that has these buttons. The standard Uif-PageFooter probably should have nothing by default. Then we can provide the 'Uif-PageFormFooter' or something that has the save and close.

Also, this Uif-PageFooter bean should be in the UifHeaderFooterDefinitions.xml file.

Does this make sense? If so I will create a Jira for 2.2.

Thanks,
Jerry