The general user types are administrator, power user or application developer, and end user.

Note: Widgets and Live Text user documentation is supplied with IBM® Notes® 9.0.1 Social Edition Help.

• Administrator

  The administrator is responsible for creating the catalog application and assigning Widgets and Live Text access. Administrators control which users are designated as power users and end users. They also perform the following tasks:

  • Create and edit the catalog on a central server.
  • Control user access to the catalog using Domino® desktop policy settings and ACLs.
  • Control what Widgets and Live Text functionality is available to specific users.
  • Create and manage widgets in the catalog.
  • Create and designate widget categories to control which widgets are available to specific users.
  • Deploy features and plug-ins to client users using specially created widgets that call an Eclipse or NSF-based update site.
  • Manage clients by provisioning client plug-in and policy updates using a centrally managed widget catalog. For example, the administrator can control which plug-ins, and which plug-in versions, are deployed on any given client system at any given time.
  • Enable initial display of the My Widgets sidebar panel and toolbar for specific users.
• Power® user and application developer

  The power user or application developer is responsible for creating and managing, such as widgets designed to act on Live Text recognizers. For example, a power user could create a widget that links a zip code with a national weather Web site. By clicking on a Live Text zip code, the end user could automatically engage that widget and discover the current weather conditions in that zip code. The power user will typically perform the following tasks:

  Note: Power users also have all the capabilities listed for the end user and may also have some or all of the capabilities listed for the administrator.

  • Use a wizard to configure new Notes-based or Web-based widgets.
  • Create and manage widgets in the catalog.
  • Create and designate widget categories to control which widgets are available to specific users.
  • Publish widgets to the catalog to make available to other users.
  • Control which users have access to specific widgets based on use of widget categories.
  • Configure new and edit existing widgets components and actions, content types, and recognizers.
  • Create new actions, content types, and recognizers for new or existing widgets.
  • Display and act on Live Text in the active document.
  • Browse the catalog to obtain new widgets, content types, or recognizers.
  • Wire content types and recognizers for different types of content (for example, use a Web site to map a zip code or track an airline flight number).
  • Set preferences such as catalog server and application name.
  • Import and export widgets.
  • E-mail a widget to another user.
  • Remove a widget from the My Widgets sidebar panel.
  • Create a recognizer using a Java™ regular expression.
  • Update the My Widgets sidebar panel with widgets from the catalog.
• End user

  The end user uses existing and available widgets to act on Live Text in their documents based on policy and preferences settings. The end user will typically perform the following tasks:

  Note: End users may also have some of the capabilities described for the power user.

  • Act on Live Text in the current document using widgets that have been made available to them.
  • Change the display of Live Text or optionally toggle that display on and off using Live Text preferences.
  • Create a dashboard if multiple actions are available for a Live Text instance.
  • Add a widget to the My Widgets sidebar panel.
  • Add a widget when received in an XML file attachment.
  • Set Widget preferences such as catalog server and application name.

Related tasks
Deploying client plug-ins with widgets and the widget catalog

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Feedback on Help or Usability?

Help on Help