Basically we will reuse RA aspx pages for PFA Adding pages, we will just convert the styles to make them have the same look and feel.
Follow this wiki page when doing these styles conversion:
Wiki Page: ASPX Pages Conversion
For the c# code behind the aspx pages, we need to do some code change for RO5, like removing the 'isRoMode' flag and FindCustomer() function which have been removed from the BasePage.
In RA, when the current entity use PFA template with the PFA Addin loans and schedule enabled, the Proposed Loans and Expand Chart of Accounts will be displayed under the Customer Setting menu item.
In RO5, to show the PFA Adding page, we need to add a tab called 'PFA' in Financial Analysis page, which we need to update menu definition in ROME.
Menu Structure: Financial Analysis==> PFA
And we also need to create a new business rule to control whether this tab display or not. Only when current entities use PFA template, then this tab will displayed. For other financial template, this tab is invisible. The business rule detail is as below:
if (!string.IsNullOrEmpty(item.Financial.FinancialTemplate) && item.Financial.FinancialTemplate.Equals("PFA"))
return True();
else
return False();
In RO5, we are going to create a new aspx page called 'PFA.aspx' for this PFA tab, when clicks PFA tab, this page will be displayed, showing a DropDownList component in the page.
If the PFA Addin Loans or PFA Addin Schedule is enabled, PFA Loans or PFA Schedule will be displayed in the dropdown list when clicks the dropdown component to select the item for further action. Otherwise, the dropdown list will show nothing.
Also, the 'PFA.aspx' page will include a Frame which under the DropDownList component, to show the actual aspx page for PFA loans page or PFA schedule page when the DropDownList selection changed. This frame is invisible when the page is first initialed or no selection in the DropDownList.
