{"_id":"54737d95007eb108007e03a8","user":"5433099f9a2b451a00ad4531","version":{"_id":"545137a814af501a00b50cfc","project":"545137a814af501a00b50cf9","__v":11,"createdAt":"2014-10-29T18:53:28.525Z","releaseDate":"2014-10-29T18:53:28.525Z","categories":["545137a814af501a00b50cfd","545138eaa66f020800dbab4a","546b9072b47b5d1400109edf","546b9082b47b5d1400109ee0","546b9088b47b5d1400109ee1","546b909462515a14007ebc43","546b90a0b47b5d1400109ee2","546ced235884600e007a92f6","5481008eea7fd40b00cd7c2b","573b9d83ee2b3b220042291f","57be1efa15efc70e006a5f99"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"parentDoc":null,"project":"545137a814af501a00b50cf9","category":{"_id":"546b9082b47b5d1400109ee0","pages":["54737d5f1a20c70800e1895f","54737d801a20c70800e18961","54737d95007eb108007e03a8","547381da007eb108007e03c7","547382311a20c70800e1897a","55761ac11ce9e6370050137b"],"project":"545137a814af501a00b50cf9","version":"545137a814af501a00b50cfc","__v":6,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-11-18T18:31:30.383Z","from_sync":false,"order":8,"slug":"yammer-embed","title":"Yammer Embed"},"__v":12,"updates":["5540eb9831827a0d007ab234","5703abeab0778e0e00ee1bf5"],"next":{"pages":[],"description":""},"createdAt":"2014-11-24T18:48:53.957Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","try":true,"basic_auth":false,"auth":"never","params":[],"url":""},"isReference":false,"order":2,"body":"URLs pasted into Yammer messages create OG objects represented as Pages. These pages display all the OG metadata Yammer knows about that URL. When an OG object feed is placed on a page in your application, it will grab the URL and OG metadata from the page. The first user to authenticate will create the OG object for that page in Yammer (or find the existing OG object if one already exists). It will then load the feed for that object. Note that this embed feed is not restricted to a specific network and users from different networks can view this feed (although they will only see the feed for their own network). However, open graph objects are restricted to their related networks.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"OG feeds can effectively become a commenting system for internal blogs or any line of business application.\"\n}\n[/block]\nTo display an OG Object Feed, add the following embed code to your HTML page.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"yam.connect.embedFeed({\\n container: \\\"#embedded-feed\\\",\\n feedType: \\\"open-graph\\\"\\n});\",\n      \"language\": \"javascript\"\n    }\n  ]\n}\n[/block]\n\n**Headers And Footers In Object Feeds**\n\nYou can also configure whether to show the Yammer header or footer in your embed.  The sample below displays a basic Open Graph feed, but without the standard Yammer header or footer.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"yam.connect.embedFeed({\\n container: \\\"#embedded-feed\\\",\\n feedType: \\\"open-graph\\\",\\n config: {\\n   header: false,\\n   footer: false\\n }\\n});\",\n      \"language\": \"javascript\"\n    }\n  ]\n}\n[/block]\n\n**Custom Publisher Messages**\n\nThe publisher lets users start new conversations related to your Open Graph objects.  You can encourage your users to post more by providing custom publisher watermark text.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"yam.connect.embedFeed({\\n container: \\\"#embedded-feed\\\",\\n feedType: \\\"open-graph\\\",\\n config: {\\n   promptText: \\\"Comment on this customer\\\"\\n }\\n});\",\n      \"language\": \"javascript\"\n    }\n  ]\n}\n[/block]\n\n**Open Graph Previews**\n\nAnother option is to display an Open Graph preview of the target URL beneath the new message publisher, which provides users with a preview of the Open Graph summary they will see in the conversation they are starting.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"yam.connect.embedFeed({\\n container: \\\"#embedded-feed\\\",\\n feedType: \\\"open-graph\\\",\\n config: {\\n   showOpenGraphPreview: true \\n }\\n});\",\n      \"language\": \"javascript\"\n    }\n  ]\n}\n[/block]\n**Private Specified Object Feed**\n\nOnce placed on a page in your app, this will check the page URL and utilize the provided metadata details. It will also only authenticate users in the network specified. This can be helpful if you want to display a feed for a page that is different than the one you are placing Embed on. Note that the objectProperties parameter is optional.\n\nIf setting the \"private\" parameter as \"true\", any pages which are created in Yammer will be private to:\n\n     - The users who are specifically listed in the \"users\" collection.\n     - The group (if any) that you specify in the recipients list when posting.\n     - Any other members of the conversation thread that are added later. \n\nPlease note, you can add and remove users from the conversations. If a user is added to an OGO then removed from a conversion, they will still be able to see the OGO but not necessarily the comments.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"yam.connect.embedFeed({\\n container: \\\"#embedded-feed\\\",\\n network: \\\"fourleaf.com\\\",\\n feedType: \\\"open-graph\\\",\\n objectProperties: {\\n   url: \\\"https://box.com/file/abc123\\\",\\n   type:  \\\"file\\\",\\n   title: \\\"Yammer ROI.pdf\\\",\\n   image: \\\"https://dox.com/file/abc123.png\\\"\\n },\\n private: true,\\n users: [\\n   {name : \\\"Drew Dillon\\\", \\\"email\\\" : \\\"adillon:::at:::fourleaf.com\\\"},\\n   {name : \\\"Ryan Kennedy\\\", \\\"email\\\" : \\\"rkennedy@fourleaf.com\\\"}\\n ]\\n});\",\n      \"language\": \"javascript\"\n    }\n  ]\n}\n[/block]\nPlease note that OG Object Feeds support all of the properties available in the Activity Stream API. Not specifying any properties means that the object will attempt to gather the information from the page, either through <title> tags or <meta> tags per the Open Graph specification http://ogp.me/\n\n**Default Comment Destination for OGO Object Feeds\"\n\nYou can set a default group for comments in an OGO Object Feed that will appear in the destination box of the publisher by specifying a defaultGroupId. The user can change this and post to a group of their choice.\n\nIf you do not specify a defaultGroupId, the destination box will be left blank and the user will be prompted to add a group on their own when posting a comment.\n\nSpecifying defaultGroupId: 0 will set the default to All Company.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"yam.connect.embedFeed({\\n        container: '#embedded-feed',\\n        network: 'fourleaf.com',\\n        feedType: 'open-graph',       // can be 'group', 'topic', or 'user'    \\n        config: {\\n             defaultGroupId: 3257958  // specify default group id to post to \\n        }\\n    }); \",\n      \"language\": \"javascript\"\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"commenting","type":"basic","title":"Commenting"}
URLs pasted into Yammer messages create OG objects represented as Pages. These pages display all the OG metadata Yammer knows about that URL. When an OG object feed is placed on a page in your application, it will grab the URL and OG metadata from the page. The first user to authenticate will create the OG object for that page in Yammer (or find the existing OG object if one already exists). It will then load the feed for that object. Note that this embed feed is not restricted to a specific network and users from different networks can view this feed (although they will only see the feed for their own network). However, open graph objects are restricted to their related networks. [block:callout] { "type": "warning", "body": "OG feeds can effectively become a commenting system for internal blogs or any line of business application." } [/block] To display an OG Object Feed, add the following embed code to your HTML page. [block:code] { "codes": [ { "code": "yam.connect.embedFeed({\n container: \"#embedded-feed\",\n feedType: \"open-graph\"\n});", "language": "javascript" } ] } [/block] **Headers And Footers In Object Feeds** You can also configure whether to show the Yammer header or footer in your embed. The sample below displays a basic Open Graph feed, but without the standard Yammer header or footer. [block:code] { "codes": [ { "code": "yam.connect.embedFeed({\n container: \"#embedded-feed\",\n feedType: \"open-graph\",\n config: {\n header: false,\n footer: false\n }\n});", "language": "javascript" } ] } [/block] **Custom Publisher Messages** The publisher lets users start new conversations related to your Open Graph objects. You can encourage your users to post more by providing custom publisher watermark text. [block:code] { "codes": [ { "code": "yam.connect.embedFeed({\n container: \"#embedded-feed\",\n feedType: \"open-graph\",\n config: {\n promptText: \"Comment on this customer\"\n }\n});", "language": "javascript" } ] } [/block] **Open Graph Previews** Another option is to display an Open Graph preview of the target URL beneath the new message publisher, which provides users with a preview of the Open Graph summary they will see in the conversation they are starting. [block:code] { "codes": [ { "code": "yam.connect.embedFeed({\n container: \"#embedded-feed\",\n feedType: \"open-graph\",\n config: {\n showOpenGraphPreview: true \n }\n});", "language": "javascript" } ] } [/block] **Private Specified Object Feed** Once placed on a page in your app, this will check the page URL and utilize the provided metadata details. It will also only authenticate users in the network specified. This can be helpful if you want to display a feed for a page that is different than the one you are placing Embed on. Note that the objectProperties parameter is optional. If setting the "private" parameter as "true", any pages which are created in Yammer will be private to: - The users who are specifically listed in the "users" collection. - The group (if any) that you specify in the recipients list when posting. - Any other members of the conversation thread that are added later. Please note, you can add and remove users from the conversations. If a user is added to an OGO then removed from a conversion, they will still be able to see the OGO but not necessarily the comments. [block:code] { "codes": [ { "code": "yam.connect.embedFeed({\n container: \"#embedded-feed\",\n network: \"fourleaf.com\",\n feedType: \"open-graph\",\n objectProperties: {\n url: \"https://box.com/file/abc123\",\n type: \"file\",\n title: \"Yammer ROI.pdf\",\n image: \"https://dox.com/file/abc123.png\"\n },\n private: true,\n users: [\n {name : \"Drew Dillon\", \"email\" : \"adillon@fourleaf.com\"},\n {name : \"Ryan Kennedy\", \"email\" : \"rkennedy@fourleaf.com\"}\n ]\n});", "language": "javascript" } ] } [/block] Please note that OG Object Feeds support all of the properties available in the Activity Stream API. Not specifying any properties means that the object will attempt to gather the information from the page, either through <title> tags or <meta> tags per the Open Graph specification http://ogp.me/ **Default Comment Destination for OGO Object Feeds" You can set a default group for comments in an OGO Object Feed that will appear in the destination box of the publisher by specifying a defaultGroupId. The user can change this and post to a group of their choice. If you do not specify a defaultGroupId, the destination box will be left blank and the user will be prompted to add a group on their own when posting a comment. Specifying defaultGroupId: 0 will set the default to All Company. [block:code] { "codes": [ { "code": "yam.connect.embedFeed({\n container: '#embedded-feed',\n network: 'fourleaf.com',\n feedType: 'open-graph', // can be 'group', 'topic', or 'user' \n config: {\n defaultGroupId: 3257958 // specify default group id to post to \n }\n }); ", "language": "javascript" } ] } [/block]