Web users don’t have access to Notes menu choices when they work in Domino databases. Therefore, you should create menu equivalents for them.

Create actions with @command formulas and make them available as buttons in the action bar. Keep in mind that Domino cannot translate commands based on a selected document in a view because there is no notion of a "selected" document on the Web. For actions such as "Create Response Document," you must add a form action to the Main Topic form for opening a Response document.

To Web-enable all buttons in a database as well as certain @commands, select the database property "Web access: Use JavaScript when generating pages." Without this property set, Domino recognizes only the first button in a document and treats it by default as a Submit button that closes and saves the document.

Be aware that Domino displays all buttons, actions, and hotspots -- even those that contain @commands and @functions that aren’t supported for Web applications.

Complete these steps to create a button to open a new Main Topic in the current database:

1. Open the view where you want to add the button for Web users.

2. Choose Create - Action - Action.

3. Complete the Action Properties box. On the Action Info tab, do the following:

• Enter the name "Create Main Topic."
• Select "Include action in button bar."
• Select "Notes graphic" and select a graphic for the button.

5. In the Run pull-down list, select Client and then Formula.

6. Enter this formula:

@Command([Compose];"Main Topic")

Examples of other commonly used menu items:

• Create a document

  @Command([Compose]; "formname")

  @Command([Compose];"":"database"; "formname")

• Open a view

  @Command([OpenView]; "viewname")

  @Command([OpenView];"":"database"; "viewname")

  @Command([OpenView];"By Date")

• Delete an open document

  @Command([Clear])

• Close an open document or view

  @Command([CloseWindow])

You want to simplify the process of distributing proposed concert schedules to a review board.

1. In the Concert Schedule form, create a field of type Names that will specify all the reviewers.

2. In the Concert Schedule form, choose Create - Action - Action and specify the following in the Action Properties box:

• Name -- Enter "Distribute for Review."
• Display -- Select "Include action in button bar"; deselect "Include action in Action menu."
• Button Graphic -- Select Notes graphic and pick a graphic from the pull-down list.

4. In the Run pull-down list, select Client and then "Simple action(s)."

5. Select the Add Action and Send Document actions.

6. Save the form.

Approving and denying requests

You want to improve a Requisition form to make it easy for managers to approve or deny requests that are mailed to them. You create two form actions: "Approve Request" and "Deny Request."

The "Approve Request" action uses this formula to change the document’s status to Approved and routes the document to the next approver:

FIELD Status:="Approved";
@MailSend(NextApprover;"";"";"For your review";"Click Approve Request to approve this requisition or click Deny Request to return the request to " + Initiator;"Initiator":"Body";[sign]);

The "Deny Request" action changes the document’s status to Denied and routes a notification to the initiator.

FIELD Status:="Denied";
@MailSend(Initiator;"";"";"Re: Your request";"Your request was unable to be approved. Contact " + PreviousApprover + "for more information.");

See Also

Adding automation to applications
Actions