APPLICATION DESIGN
1. Open a form, subform, page, view, or folder.
2. Choose Create - Action - Action. The Actions Properties box appears.
If you choose Menu separator, a menu separator appears and there is no action. You can also use menu separators between subactions of an action drop-down list.
5. (Optional) On the Advanced tab, specify how Notes workflow proceeds after the user activates the action.
6. In the Info List of the Programmer’s pane, click Objects and select the action you just created.
7. To program the action to run one of the client or one of the Web program code types, choose either Client or Web at the Run pull-down list.
To create an action with subaction
Creating actions with one of more subactions lets you create a hierarchical list of actions. You can also drag and drop actions to create hierarchies. To create an action with subactions:
2. Choose Create - Action - Action with Sub Action. A main action with an indented sub-action appears in the Action pane. The Actions Properties box also appears.
3. Define the main action and the sub-action.
When you create system actions, you are creating a predefined list of common view and form actions.
1. Open the form or view.
2. Choose Create - Action - System actions. The list of actions created appears in the Action pane. These system actions include:
To copy: select the action in the Action pane and choose Edit - Copy and Edit - Paste.
To delete: select the action in the Action pane and choose Edit - Delete.
To change properties: select the action in the Objects list and choose Design - Action Properties.
To change automation: select the action in the Objects list and edit the programming tasks in the right pane.
Actions menu
The Actions menu is a context-sensitive list of any actions and agents available for a particular part of an application, as well as some menu commands included with the Notes software. From an open view, Notes users see only those actions associated with the view, plus any manually run agents. From an open document, Notes users see the actions associated with the form used to create the document, plus any manually run agents. Web users don’t see the Actions menu.
Calling an agent
You can use a form or view action to run an agent. Use the @Command([RunAgent]), @Command([ToolsRunMacro]), or the OpenAgent URL command to call an agent.
See Also