Excerpt | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
a. clicking on a module in the business system’s module bar b. clicking on an action entry in the business system’s session list. c. clicking on a module icon on the windows desktop or another location d. by initiation from another module. e. by another module that want to use your module as an IMCServer. f. clicking in the Session list and select 'Print' – The module is then launched with a Print Action or Print Action Group command. 2. The module instantiates the ModuleAPI (refer to the ‘Instantiating Instantiating the Module’ Module section). 3. The Module can determine why it was opened by reading LaunchInfo. 4. The module connects itself to Noah via the ModuleAPI. 5. If the module has been launched via 1a, 1c,or (1d) from above, it is recommended that the module show the most recent action of the type it supports. If launch method 1b (1d) from above has been used, the action will be opened in the module in which it was created. In both cases, the module should open in either Edit or View mode, depending on the following circumstances:
6. The user has completed the session, the user closes the Module 7. The Module saves the Action data, if any has been created, by adding the action object to the current session. The module must save data as follows:
8. The Module exits. Whenever the user attempts to close the module with unsaved data (for example, with the Close ‘x’ button in the upper-right corner of the window), the module should offer the option of saving this data before closing |
Page Comparison
General
Content
Integrations