Readme for CBISA Online™ Version 3.3.0
  • Reporter enhancements
  • Bring forward department rates
  • "Targeted for" relocated to Activity/General screen
  • Close a fiscal year
  • "Save Failed:  Ambiguous Fiscal Year" error explanation
  • New reports

    Reporter Enhancements
    The Reporter permission level has been enhanced to allow Reporters to "publish" a record when they have completed the data entry.  "Publishing" a record will signify to the Coordinator that the record is ready to be imported.  Reporters may also copy a data record while it is still pending.  To access the new functionality, select the function button "More" from the control panel and then highlight the desired action.

    Bring Forward Department Rates
    System Administrators and Coordinators now have the ability to "bring forward" average salary rates from the previous year to automatically populate the active years rates.  The "bring forward" selection button will show when a department is edited and has an average hourly rate equal to 0.00 (zero).  You may update one or more departments at a time.  To select multiple departments, simply hold down the control key on your keyboard and select the applicable departments, then click on "Edit" (or use "control shift" to select a block of records).  When you choose to "bring forward" the rates, all selected department rates will simultaneously update.   

    "Targeted For" Relocated to Activity/General Screen
    The field "Targeted for" has been relocated from the Activity/Target Audience screen to the Activity/General screen.  The selection of "Broader Community" or "Living in Poverty" is now mandatory when adding a new record.  When saving a new Activity/General screen, if "Targeted for" remains at "select one", you will receive an error message prompting you to select the targeted population. 

    Close a Fiscal Year
    A System Administrator may now "close" a fiscal year.  A "closed" year, annotated by an asterisk in the active year dropdown, will be "read only" for all users (except Reporters who will no longer have any access to closed year).  Closing a fiscal year is a permanent function and may not be reversed.  However, a System Administrator or a finance user may temporarily "re-open" a closed year for the purpose making any necessary adjustments.  For important additional information, please review the attached documentation, "Fiscal Year Closing" and "Fast Facts about Closing a Year".

    Please Note:  The "bring forward" functionality is not available in "re-opened" years.  Also, rates must exist on the department rate table prior to closing the year for the "bring forward" function to properly apply previous years rates.

    "Save Failed:  Ambiguous Fiscal Year" Error Explanation
    CBISA™ active fiscal years are set with a calendar year as the default.  Therefore, if your active fiscal year starting and ending dates are not equal to a calendar year, you will have overlapping months from one year to the next.  When you save a dated record for the first time in version 3.3.0, you will receive the following message until you align your fiscal year dates- "Save Failed": Ambiguous Fiscal Year.  To correct the misaligned fiscal dates, follow the steps below.
     
    1.  Change the active fiscal year from the dropdown in the upper right hand corner to the previous year (i.e., if you were entering data in 2009 when you received the error, activate 2008).
    2.  Access the reporting unit financial default screen (Options/Org Defaults/Reporting Unit/Financial)
    3.  Update the beginning and ending fiscal dates for the activated year. Save your changes and close out of Org Defaults
    4.  Reactivate your current active fiscal year, and re-enter the information on the dated record.
     
    As an example, your fiscal year runs from July to June.  You are entering information into CBISA™ for the first time in active year 2009.  You have correctly set your 2009 fiscal year dates to 7/1/2008 (beginning) to 6/30/2009 (ending).  You try to save an occurrence record with a date of 5/31/2009 and you receive the "Save Failed": Ambiguous Fiscal Year error.  To properly align the fiscal years and remove the overlapping 2008 dates, you first set the active year to 2008, then edit the reporting unit financial screen to show the correct fiscal dates 7/1/2007 (beginning) to 6/30/2008 (ending) thus removing the overlapping date range.  You are now able to save the occurrence with the date of 5/31/2009 (after correctly activating 2009) without error.  


    New Reports
    Control Listings: Occurrences-Selected Users; Occurrences-Restricted Grant Revenue; and Occurrences-Indirect Cost


    See Also
    Readme3.1.22
    Readme3.1.15
    Readme3.1.12
    Readme3.1.6
    Readme 3.1.2
    Readme 3.0