There are 2 types of pages: detail and action. A detail page simply displays a set of read-only fields and their values for an existing Model instance. It features an
Actions button (as seen in the basic example) that opens a list of possible actions that can be executed on the current Model instance. When the user clicks on one of these actions, or if an instance of
ModelFormContainer is opened without a
sysId set, an action page is created. An action page is configured by an action screen in the MPT/SPT (as seen in the basic example), and has a list of editable fields, as dictated by the action's write mask in the MPT/SPT.
There is also this notion of a "default page", which is what every action page transitions to after the user has executed it or decided to cancel. As was already mentioned, there are 2 types of pages: detail and action. Therefore there are 2 possible types of default pages. You already saw a detail default page in the basic example, which outlined a simple Create -> Detail flow; a detail default page can be specified with the
detailViewName property on the
ModelFormContainer class. To specify an action default page, you should pass in a