ShowTable of Contents
OpenSocial Widgets need to be created and trusted before they will render in the Notes and iNotes clients. Trust is also needed before Embedded Experiences will render, whether the Embedded Experience is rendering an OpenSocial gadget or a simple URL.
Creating OpenSocial Widgets
To learn how to create OpenSocial Widgets in the Notes client, see Creating OpenSocial widgets
Approving a Widget in the Widget Catalog
To learn more about the initial approval process, see Approving a widget created from an OpenSocial gadget
Viewing Approval Status in the Widget Catalog
The 9.0 version of the Widget Catalog template includes a new "All Widgets by Approval" view that can be used by an administrator to quickly see the approval status of his or her Widgets.
Widget Approval Process Diagram
Upon approval, the “PushToCredStore” agent writes data to the credential store. Notes client local replicas of the Widget Catalog need to be updated to get the new widget approvals and ancillary data.
More information on Administering OpenSocial Widgets
For more information on administering OpenSocial Widgets in general, see Widgets created from an OpenSocial gadget
and its sub-topics.