The user needs a UI to enter and submit requests for account changes. The user should be presented with a grid similar to the table in the diagram that results in a Set<AccountTransition> objects to be passed to the AccountChangeService.post method. The user needs to be able to create, edit, and delete AccountTransition objects from this UI.

• Add a new menu item named Account Change under the Utilities menu

• Add a new view containing a UI similar to that shown in the attached image

  • UI should have a grid listing all account transitions/changes to be performed

    • Grid should have a delete button, fromAccount, toAccount for each transition

  • UI should have an Apply button above the table that submits the account transitions to the service

  • UI should have a drop-down for selecting the fiscal year to which these changes will be applied. The drop-down should only list open fiscal years. This field should be required and defaulted to the current fiscal year. Add a validator to make sure this is required.

  • UI should have a Create button above the grid that adds a new row to the grid

  • Selecting accounts should be done using the existing AccountComboBox

• The UI also needs to have a shortcut for the user to create a new account. Ideally, we would like a detail viewer for creating an ExpenditureAccount or RevenueAccount to popup on the screen via a button in the UI. Make an attempt to implement this and see if it is doable in a reasonable amount of time. If there are significant problems with this, we will just require the user to go create the new account in a different browser tab for this initial pass. If it is doable, prompt the user with a popup to select whether they want to create an expenditure account or a revenue account after clicking the create button to determine which detail viewer needs to be shown.

• Also address issues found in USASRCR-2065:

  • Change repository methods to return object instead of id's

  • Change asserts in repository methods to use Spring's Assert.isTrue method

  • Fix instanceof check in AccountChangeServiceImpl to be isAssignableFrom

  • Remove eventManager.withoutEvents from AccountChangeServiceImpl

  • Make accountChangeServiceImpl transactional

• Note: we don't want to tie up the UI

Per 12/5 & 12/19 meetings - changes

• create accountChangeRequest

  • similar to AccountTransition but also add a status with values: new, pending, in progress, completed, failed

• need to be able to delete requests from the grid, but accountTransitions are not deleteable