The following example shows how to invoke the emxIndentedTable.jsp with postProcessJPO: ${COMMON_DIR}/emxIndentedTable.jsp?mode=Edit&table=<indentedtable_name> &postProcessJPO=<JPO Name>:<Method Name> If both a postProcessURL and postProcessJPO are specified, the postProcessURL is processed first followed by the postProcessJPO The post process JPO specifies the programMap as an argument for the post processing. The programMap contains the following HashMaps:
The above maps are packed using the packArgs method supported by JPO and passed on to the post process JPO being invoked. The post process JPO can unpack this input parameter and it can be used by the post process for custom coding. See Pre Process JPO for an Editable Structure Browser for code samples that retrieve request parameters and the table data. The post process JPO returns a HashMap or returns nothing. The HashMap contains the keys defined in this table:
If the Message key contains any value, it displays to the user as an alert. If the value of the Action key is CONTINUE, then the system commits the entire transaction of the edit process, post process JSP, and post process. If the value of the Action key is STOP the entire transaction, including the edit process, aborts. If the post Process JPO does not need to communicate to the structured browser, it can return nothing (void) or an empty HashMap. In this case, the process proceeds with the default behavior of Continue and No message. |