Show TOC

Navigation: Implementing Multiple Tasks (Intents) with One Physical AppLocate this document in the navigation structure

For apps that are very similar, you can implement one physical app that runs in two modes. An example for such apps would be PurchaseOrder-display and PurchaseOrder-edit

One option to implement this is to ship two Component.js in different subfolders. The two files can use the same resources, for example, views. However, this option duplicates code.

Another option is to inform the app whether it runs in edit mode or display mode during startup. For this, you ship the app with two entry configurations (TargetMapping-LPD_CUST) pairs: One mapping PurchaseOrder-display, the other one mapping PurchaseOrder-edit to the actual application. As the application code is identical, the mode has to be passed when addressing the application, as part of the target mapping or LPD_CUST.

To do this, pass a startup parameter to the application, for example editmode=X, and write cour application accordingly. You can configure the startup parameter in LPD_CUST, or you can use the target mapping configuration (As Default value). By doing this, the startup parameter will not appear in the URL and you avoid confusing the user. Within your app, you can use the startup parameters to enable or disable specific operations or navigate to different (entry) views.

Note

Do not program against a specific action. Conceptually, the intent is distinct from the physical application and may be reconfigured.