No, "Domino Web Access" is the new name for what used to be iNotes in the R5 days. And I think the single name/multiple values approach is better, since it is maintainable with code only, and adding new permitted actions can be handles with a config doc -- only one field needs to be maintained on the form, while multiple buttons can be easily created in passthru (or "treat as") with the simple expedient of fetching values from a config doc. Not that I think forcing server-side activity for all actions is a particularly good idea -- I'd rather it be seen as a fully-degraded condition of the page. Accessibility should not come at the expense of anything else.
No, "Domino Web Access" is the new name for what used to be iNotes in the R5 days. And I think the single name/multiple values approach is better, since it is maintainable with code only, and adding new permitted actions can be handles with a config doc -- only one field needs to be maintained on the form, while multiple buttons can be easily created in passthru (or "treat as") with the simple expedient of fetching values from a config doc. Not that I think forcing server-side activity for all actions is a particularly good idea -- I'd rather it be seen as a fully-degraded condition of the page. Accessibility should not come at the expense of anything else.