Laserfiche WebLink
CF -11632 Cayenta updated the Remaining Balance Report to include two new fields. The <br />Purchase Order Requestor ID and the Purchase Order Date Required fields are <br />now columns displayed in the report. <br />Selected PO Line Report Ennancemenr <br />JIRA# CAYENTA FEATURE DESCRIPTION <br />CF -1 1752 Performance improvements were made for the Selected PO Line Report, when <br />I running the reportfor a large date range over multiple years. <br />SYSTEM <br />Admin Scripting Enhancement <br />JIRA # CAYENTA FEATURE DESCRIPTION <br />CF -12402 The Admin Scripting option in Cayenta Financials will now allow you to paste <br />records with the right -click of the mouse. It also allows you to use keyboard <br />shortcuts Ctrl + C (Copy) and Ctrl + V (Paste). <br />API Enhancement <br />JIRA # CAYENTA FEATURE DESCRIPTION <br />F-1 1166 The Cayenta Financials API is updated with new meaningful specific error <br />messages, replacing the generic error message in previous versions. <br />Journal Entry, Purchasing Requisition and Purchase Order Entry Enhancement <br />JIRA # CAYENTA FEATURE DESCRIPTION <br />CF -12811 We have added a look up to the Departmental Security Code (DSC) field in <br />j Journal Entry, Purchasing Requisition and Purchase Order Entry forms. The lookup <br />will display the DSC code the user has access to and allow them to select the <br />appropriate code. <br />SMTP Office 365 Support <br />JIRA # CAYENTA FEATURE DESCRIPTION <br />F-1 1756 Cayenta Financials is enhanced to support smtp.office.365.com protocol in Multi - <br />Level Approval in the financial application. <br />Requirements include: <br />I The user email address should be a valid email address on the <br />office365.com account <br />• The user is required to sign into the Cayenta application with their Office <br />i 365 credentials. <br />CF -12867 A further update to Office 365 integration was completed in the Cayenta <br />Financials application. The smtp.office365.com protocol is enhanced to use a <br />generic user instead of the logged in user. This change requires you to update the <br />