Module Launch Scenarios

Modules can be launched in different ways:

clicking on a module in the business system’s module bar

clicking on an action entry in the business system’s session list.

clicking on a module icon on the windows desktop or another location

by initiation from another module.

by another module that want to use your module as an IMCServer.

clicking in the Session list and select 'Print' – The module is then launched with a Print Action or Print Action Group command.

The module instantiates the ModuleAPI (refer to the ‘Instantiating the Module’ section).

The Module can determine why it was opened by reading LaunchInfo.

The module connects itself to Noah via the ModuleAPI.

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. 

The user has completed the session, the user closes the Module

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:

• if a module reads or uses data created by another module on the same date, it must not attempt to alter or over-write the original data, but must save the data as its own new action
• if a module reads or uses data already created on the same date, it should alter and over-write the original data
• if the user decides to create a new action based on a previous action from a previous session, the new action must be saved in the current day’s session

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