configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. 4 Request Map A request in the control servlet might contain the following information: • Define response could either be another request or a view map. So in this example, the findInvoices request is mapped to a findInvoices view. View Map A view map maps a view name to a certain view-type and a certain a FreeMarker template. • screenxls: An Excel spreadsheet. In the findInvoices example, the view-map type is a normal screen which is mapped to the screen: component://accounting/widget/InvoiceScreens

configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. 4 Request Map A request in the control servlet might contain the following information: • Define response could either be another request or a view map. So in this example, the findInvoices request is mapped to a findInvoices view. View Map A view map maps a view name to a certain view-type and a certain a FreeMarker template. • screenxls: An Excel spreadsheet. In the findInvoices example, the view-map type is a normal screen which is mapped to the screen: component://accounting/widget/InvoiceScreens

configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. 3 Request Map A request in the control servlet might contain the following information: • Define response could either be another request or a view map. So in this example, the findInvoices request is mapped to a findInvoices view. View Map A view map maps a view name to a certain view-type and a certain a FreeMarker template. • screenxls: An Excel spreadsheet. In the findInvoices example, the view-map type is a normal screen which is mapped to the screen: component://accounting/widget/InvoiceScreens

configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. 3 Request Map A request in the control servlet might contain the following information: • Define response could either be another request or a view map. So in this example, the findInvoices request is mapped to a findInvoices view. View Map A view map maps a view name to a certain view-type and a certain a FreeMarker template. • screenxls: An Excel spreadsheet. In the findInvoices example, the view-map type is a normal screen which is mapped to the screen: component://accounting/widget/InvoiceScreens

configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. Request Map A request in the control servlet might contain the following information: • Define response could either be another request or a view map. So in this example, the findInvoices request is mapped to a findInvoices view. View Map A view map maps a view name to a certain view-type and a certain a FreeMarker template. • screenxls: An Excel spreadsheet. In the findInvoices example, the view-map type is a normal screen which is mapped to the screen: component://accounting/widget/InvoiceScreens

data. 1. Select the 'FinAccount Type Id' from the drop down list 99 2. Select the ' GL Account' to map it to from the drop down list 3. Press the 'Add' button 4. The new mapping will be displayed in the made such as 'Customer Deposit' then it will translate to a GL Account Type Id which in turn will map to an actual GL Account) • GL Account Class Id: This appears to be a classification system and hierarchy used to map various transaction type codes to a specific general ledger account Accounting transactions are made up of a Debit Entry and a Credit Entry. The GL Account defaults screens help map which accounts

1. Select the 'FinAccount Type Id' from the drop down list 110 2. Select the ' GL Account' to map it to from the drop down list 3. Press the 'Add' button 4. The new mapping will be displayed in the made such as 'Customer Deposit' then it will translate to a GL Account Type Id which in turn will map to an actual GL Account) • GL Account Class Id: This appears to be a classification system and hierarchy used to map various transaction type codes to a specific general ledger account Accounting transactions are made up of a Debit Entry and a Credit Entry. The GL Account defaults screens help map which accounts

1. Select the 'FinAccount Type Id' from the drop down list 110 2. Select the ' GL Account' to map it to from the drop down list 3. Press the 'Add' button 4. The new mapping will be displayed in the made such as 'Customer Deposit' then it will translate to a GL Account Type Id which in turn will map to an actual GL Account) • GL Account Class Id: This appears to be a classification system and hierarchy used to map various transaction type codes to a specific general ledger account Accounting transactions are made up of a Debit Entry and a Credit Entry. The GL Account defaults screens help map which accounts

configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. Request Map A request in the control servlet might contain the following information: • Define response could either be another request or a view map. So in this example, the findInvoices request is mapped to a findInvoices view. View Map A view map maps a view name to a certain view-type and a certain a FreeMarker template. • screenxls: An Excel spreadsheet. In the findInvoices example, the view-map type is a normal screen which is mapped to the screen: component://accounting/widget/InvoiceScreens