Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Lotus Domino > Widget approval process
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Integration with XPage Embedded Experiences

XPages can be leveraged as embedded experiences in Notes and iNotes. This article outlines the considerations one should make to enable this functionality.

Gadget data flow

OpenSocial Component functionality in Notes and iNotes relies on several different pieces of data, including proxy rules, OAuth consumer information, and gadget capability information. This article outlines how this data is used and how its use can be customized.

Collecting support data

In the event that verification of the OpenSocial Component fails an administrator will need to collect support data. This article outlines how an administrator can collect support data for Notes, iNotes, and Domino.

Verification

Once the OpenSocial Component is installed and configured, administrators need to verify that their environment is working properly. This article outlines how an administrator can do such verification.

Troubleshooting

In the event that verification of the OpenSocial Component fails an administrator may need to troubleshoot his or her environment. This article outlines how an administrator can do such troubleshooting.
Community articleWidget approval process
Added by ~Vera Umponetexings | Edited by ~Laura Nimvelutherakol on September 15, 2016 | Version 17
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
This article outlines how Widgets are created and approved to establish trust during OpenSocial Widget and Embedded Experience rendering.
Tags: 9.0, 9.0.1, opensocial, widget
ShowTable of Contents
HideTable of Contents
  • 1 Overview
  • 2 Creating OpenSocial Widgets
  • 3 Approving a Widget in the Widget Catalog
    • 3.1 Importing a Widget into the Widget Catalog
  • 4 Viewing Approval Status in the Widget Catalog
  • 5 Widget Approval Process Diagram
  • 6 More information on Administering OpenSocial Widgets

< Previous | Cookbook Contents | Next >


Overview


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.

For more information on Widgets in the Notes client, see Widgets and Live Text 9.0 or Widgets and Live Text 9.0.1external link.

Creating OpenSocial Widgets


To learn how to create OpenSocial Widgets in the Notes client, see Creating OpenSocial widgets 9.0 or Creating OpenSocial widgets 9.0.1external link.

Approving a Widget in the Widget Catalog


To learn more about the initial approval process, see Approving a widget created from an OpenSocial gadget 9.0 or Approving a widget created from an OpenSocial gadget 9.0.1external link

Importing a Widget into the Widget Catalog


The standard approval process requires the Widget Catalog administrator to fill out OAuth and proxy information when a Widget is approved. This process can be simplified by using the "Import" functionality, in which configuration files containing pre-configured OAuth and proxy data are imported. For more information, see the "Import" section of Widget catalog options and access 9.0external link or Widget catalog options and access 9.0.1external link.


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.

IMPORTANT: Data in the Widget Catalog and the Credential Store is only read periodically (every hour, by default). Thus, the data needed to render a newly approved Widget may not be immediately available. For more information see Gadget Data Flow
IMPORTANT: The Mail Server must be listed as a "Trusted Server" in the "Security" tab of the server document for the Domino Server with Shindig for the PushToCredStore agent to successfully write data to the credential store. See Widget Catalog server must be trusted by the Domino Server with Shindigexternal link for more information.



More information on Administering OpenSocial Widgets


For more information on administering OpenSocial Widgets in general, see Widgets created from an OpenSocial gadget 9.0 or Widgets created from an OpenSocial gadget 9.0.1external link and its sub-topics.

< Previous | Cookbook Contents | Next >


  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (17)Sep 15, 2016, 8:11:04 PM~Laura Nimvelutherakol  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility