<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
xml:lang="EN" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="acq-new-features">\r
<info>\r
- <title>New in Evergreen Version 2.8</title>\r
+ <title>New in Evergreen Version 2.10</title>\r
<legalnotice>\r
<para><emphasis role="bold">Adapted with permission from original material by the <link\r
xlink:title="http://docs.evergreen-ils.org/2.8/_evergreen_2_8_release_notes.html"\r
\r
\r
<section xml:id="new-features-0">\r
-<title>Acquisitions Admin Menu Move</title>\r
-<para>The acquisitions administration menu is now under the main <guilabel>Admin</guilabel> menu rather than under <guilabel>Server Administration</guilabel>.\r
-This is a more logical place for this menu to be and makes it faster to access.</para>\r
+<title>PO Line item "paid" label</title>\r
+<para>A new "paid" label appears along the bottom of each line item in the PO display when every non-canceled copy on the line item has been invoiced.</para>\r
\r
<informalfigure>\r
<para><mediaobject>\r
<imageobject>\r
- <imagedata scalefit="0" fileref="media/acq-menu.png"/>\r
+ <imagedata scalefit="0" fileref="media/acq-paid.png"/>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
\r
\r
<section xml:id="new-features-1">\r
-<title>Sticky Org Unit Selector</title>\r
- <para>The <guilabel>Context Org Unit</guilabel> selector on the <guilabel>Funds</guilabel> interface\r
- will now remember and default to the most recently selected org unit. </para>\r
+<title>Disencumber funds on invoice close</title>\r
+ <para>Fund debits linked to an invoice are now marked as paid (encumbrance=false) when the invoice is closed instead of at invoice create time. This is particularly useful for EDI invoices which may be created well in advance of receipt and payment. </para>\r
\r
- <informalfigure>\r
- <para><mediaobject>\r
- <imageobject>\r
- <imagedata scalefit="0" fileref="media/sticky-org-funds.png"/>\r
- </imageobject>\r
- </mediaobject></para>\r
- </informalfigure>\r
</section>\r
\r
<section xml:id="new-features-2">\r
-<title>Differentiate between cancelled and "delayed" lineitems</title>\r
-<para>It is now more clear to users when a lineitem has been fully cancelled or if it has been\r
- cancelled temporarily "delayed".</para>\r
- <itemizedlist>\r
- <listitem>\r
- <para>All cancel reasons are now prefixed by <guilabel>Canceled</guilabel> or \r
- <guilabel>Delayed</guilabel>.</para>\r
- <informalfigure>\r
- <para><mediaobject>\r
- <imageobject>\r
- <imagedata scalefit="0" fileref="media/cancel-delay-1.png"/>\r
- </imageobject>\r
- </mediaobject></para>\r
- </informalfigure></listitem>\r
+<title>Improved reporting of progress during purchase order activation</title>\r
+<para>The progress dialog that is displayed when activating a purchase order now displays more information, particularly during the asset creation phase. It is now also updated in a more linear fashion; making it less likely for it to appear that the activation has stalled.</para>\r
+ \r
\r
- <listitem><para>The prefix also displays with the cancel reason on the line item.</para>\r
<informalfigure>\r
<para><mediaobject>\r
<imageobject>\r
- <imagedata scalefit="0" fileref="media/cancel-delay-2.png"/>\r
+ <imagedata scalefit="0" fileref="media/progressbar.png"/>\r
</imageobject>\r
</mediaobject></para>\r
- </informalfigure></listitem>\r
- \r
- </itemizedlist>\r
+ </informalfigure>\r
\r
</section>\r
\r
<section xml:id="new-features-3">\r
-<title>Support Cancellation and Receiving of Delayed Lineitems</title>\r
- <para> </para>\r
+<title>"Blanket Orders"</title>\r
\r
- <para>Line items marked as delayed can be canceled again in the using a <guilabel>Canceled</guilabel>\r
- cancel reason if the item become truly canceled as opposed to delayed. Once an item is marked as truly canceled\r
- it cannot be canceled again.</para>\r
+<para>"Blanket" orders allow staff to invoice an encumbered amount multiple times, paying off the charge over a period of time. </para>\r
+<para>The work flow supported by this development assumes staff does not need to track the individual contents of the order, only the amounts encumbered and invoiced in bulk.</para>\r
\r
</section>\r
\r
-<section xml:id="new-features-4">\r
-<title>Duplicate Order Detection Improvements</title>\r
- <para>A new column on the line item displays the number of copies already attached to the \r
- bibliographic record belonging to the ordering agency or a lower organizational unit. </para>\r
- <para>This count does not include the copies attached to the line item itself nor does it include \r
- copies that have the status of <guilabel>Lost</guilabel>, <guilabel>Lost and Paid</guilabel>,\r
- <guilabel>Missing</guilabel>, <guilabel>Damaged</guilabel>, or <guilabel>Discard/Weed</guilabel>.</para>\r
- \r
- <informalfigure>\r
- <para><mediaobject>\r
- <imageobject>\r
- <imagedata scalefit="0" fileref="media/item-count.png"/>\r
- </imageobject>\r
- </mediaobject></para>\r
- </informalfigure>\r
-</section>\r
-\r
-<section xml:id="new-features-5">\r
-<title>Specify Purchase Order Name During Creation</title>\r
- <para>When creating a purchase order there is now a field called <guilabel>Name</guilabel> where staff\r
- can specify the name of the purchase order. This field is optional.</para>\r
- \r
- <informalfigure>\r
- <para><mediaobject>\r
- <imageobject>\r
- <imagedata scalefit="0" fileref="media/po-name-creation-1.png"/>\r
- </imageobject>\r
- </mediaobject></para>\r
- </informalfigure>\r
- \r
- <para>Duplicate purchase order name is in effect on the new <guilabel>Name</guilabel> field and \r
- will indicate if the same purchase order name is used more than once for a purchase order for a \r
- specific provider. The existing purchase order can be viewed by clicking \r
- <guibutton>View PO</guibutton> and will open in a new tab.</para>\r
- \r
- <informalfigure>\r
- <para><mediaobject>\r
- <imageobject>\r
- <imagedata scalefit="0" fileref="media/po-name-creation-2.png"/>\r
- </imageobject>\r
- </mediaobject></para>\r
- </informalfigure>\r
-</section>\r
\r
</chapter>\r