Navigation between Main Page and Edit Page(vice-versa) in OVP Application

[former_member196273]

In an OVP application, multiple pages of different types can be created and navigation can happen by raising CONTENT CHANGE event and calling the appropriate PAGE ID of the target page. FPM also make allows us to integrate a default edit page and default detailed page to a main page and by raising just an standard event these pages can be called. This post helps to show navigation from main page to default edit page and vice versa.

The main page displays a form UIBB of the flight table SPFLI fields. The feeder class details

Create an OVP application configuration.

The page is now a MIAN page. Provide page title. Add a form uibb and create a form uibb configuration with the above feeder class.

Add few fields. Make some fields as input field. Save and test the application.

Test the application and here we have the MAIN page with flight information. As the demo tries to show the navigation between main page and edit page ,lets make these fields as read only field in the main page and will show these as edit fields in EDIT page.

Put the below code in the GET_DATA method of the feeder class to make the input fields as read only fields in the main page.

Test the application again. now the input fields becomes read only on the main page. Now we have to create a button to navigate to the edit page and also have to create an edit page and link to the main page.

Go to the toolbar schema.

Add a toolbar element.

Add a button.

provide the button text and make sure the event id should be as ‘FPM_CALL_DEFAULT_EDIT_PAGE’ Save the configuration.

Test the application and now we have a button as Edit page on the Main Page to call the Edit page. Click the button.

We receive the error as the edit page is not yet created and also not yet assigned to the Main page.

Now we are creating the edit page with the same form uibb configuration as on the main page. So create an edit page .

Provide edit page title and choose a form component.

provide the same form uibb configuration as in the main page.

Now select the main page and in the default edit page provide the edit page id and save the configuration.

Test the application again. Click on the Edit Page button to call the edit page.

So here we have the edit page displayed . So here the standard FPM handles the content area change process. Now we have to make the fields as editable on the edit page. So as we are suing the same form uibb configuration in the edit page.

In the feeder class GET_DATA, for the event : FPM_CALL_DEFAULT_EDIT_PAGE add the below code to make the fields as input enabled.

Test the application.

So the fields appear as input enabled in EDIT page. Now here we have to put a button to go back to the main page.

Create a button on the edit page form uibb toolbar.

Provide the event id of the button as ‘FPM_BACK_TO_MAIN’ Save the configuration.

Test the application.

Click on the Main page button on the edit page and automatically it will go back to the main page.

So here we are on the main page.