{"_id":"546bdfb555639108002b1842","parentDoc":null,"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"},"category":{"_id":"546b9072b47b5d1400109edf","project":"545137a814af501a00b50cf9","version":"545137a814af501a00b50cfc","__v":6,"pages":["546bdfb555639108002b1842","546be31f52812008000414af","546be32e55639108002b184a","546be33c52812008000414b1","546be34a52812008000414b3","546be36255639108002b184c"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-11-18T18:31:14.459Z","from_sync":false,"order":4,"slug":"open-graph","title":"Open Graph"},"project":"545137a814af501a00b50cf9","__v":17,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2014-11-19T00:09:25.002Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"basic_auth":false,"results":{"codes":[]},"try":true,"auth":"never","params":[],"url":""},"isReference":false,"order":0,"body":"##**Open Graph Introduction & Format**\n\nOnce you have set up authentication to Yammer, you should complete the steps to write user activity from your app to Yammer. This activity will be displayed in engaging ways to the user’s Yammer network. People in the Yammer network will engage with the activity, connecting the experience to your app, helping grow usage. \n\n**Examples of engagement activity: **\n\n   * CRM App, MS Dynamics: A sales rep updates a sales opportunity. The OG object is updated for team members to coordinate next steps in Yammer.\n  \n   * Scheduling App, like Sched.do: An employee creates a lunch meeting invite. An Open Graph (OG) and a lightweight data integration protocol is used to define the activity which is posted to Yammer as an OG object.\n\n**Format**\n\nThe activity takes the format:\n\n<Actor> <Action> <Object> on <App Name>: <Message>\n\nUsing our two examples (above), the activities would look like 1) “Sidd Singh” updated “Contoso Ltd. Deal” on Dynamics CRM: Changed Probability from 90% to 60% 2) “Sidd Singh” created “Lunch Meeting” on Sched.do: Hey, let’s get sushi!\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/OlViFg87TMeKu771TXMg_ActivityStream-1024x575.png\",\n        \"ActivityStream-1024x575.png\",\n        \"1024\",\n        \"575\",\n        \"#456b90\",\n        \"\"\n      ],\n      \"caption\": \"From these actions user activity displayed in Yammer’s Activity Stream\"\n    }\n  ]\n}\n[/block]\n**Actor**\n\nWhen writing an activity into a Yammer network, an “actor” must be specified. The actor is a Yammer user that performs an action in your app. If the actor exists in the Yammer network, the story will be delivered to the actor and others depending on the delivery rules specified (please see below). If the actor does not exist, the story will not be delivered. The actor is linked to the user’s Yammer profile when the story is displayed in Yammer.\n\n**Action**\n\nSimilar the actor format, an “action” must also be specified. The action is a verb that describes what happened to the object (e.g. created, updated, deleted, followed, liked, etc).\n\n**Object**\n\nThe key piece of any activity is the Open Graph (OG) object, on which action was taken. An OG object represents an entity instance in your application, like a particular Event (Lunch Meeting) or a CRM Record (Contoso Ltd. Renewal Deal). OG objects are uniquely identified with their URL and their title is displayed in Yammer as a link to the URL. We recommend sending Yammer as many properties for your OG objects as you can for appropriate display.\nWhen your app sends an activity to a Yammer network, a corresponding OG object is created in the Yammer, if it doesn’t already exist. When an OG object exists (with the same URL), it is updated appropriately.\n\nFor general details on Open Graph outside of Yammer's implementation, check out: http://ogp.me/","excerpt":"","slug":"open-graph","type":"basic","title":"Intro & Format"}
##**Open Graph Introduction & Format** Once you have set up authentication to Yammer, you should complete the steps to write user activity from your app to Yammer. This activity will be displayed in engaging ways to the user’s Yammer network. People in the Yammer network will engage with the activity, connecting the experience to your app, helping grow usage. **Examples of engagement activity: ** * CRM App, MS Dynamics: A sales rep updates a sales opportunity. The OG object is updated for team members to coordinate next steps in Yammer. * Scheduling App, like Sched.do: An employee creates a lunch meeting invite. An Open Graph (OG) and a lightweight data integration protocol is used to define the activity which is posted to Yammer as an OG object. **Format** The activity takes the format: <Actor> <Action> <Object> on <App Name>: <Message> Using our two examples (above), the activities would look like 1) “Sidd Singh” updated “Contoso Ltd. Deal” on Dynamics CRM: Changed Probability from 90% to 60% 2) “Sidd Singh” created “Lunch Meeting” on Sched.do: Hey, let’s get sushi! [block:image] { "images": [ { "image": [ "https://files.readme.io/OlViFg87TMeKu771TXMg_ActivityStream-1024x575.png", "ActivityStream-1024x575.png", "1024", "575", "#456b90", "" ], "caption": "From these actions user activity displayed in Yammer’s Activity Stream" } ] } [/block] **Actor** When writing an activity into a Yammer network, an “actor” must be specified. The actor is a Yammer user that performs an action in your app. If the actor exists in the Yammer network, the story will be delivered to the actor and others depending on the delivery rules specified (please see below). If the actor does not exist, the story will not be delivered. The actor is linked to the user’s Yammer profile when the story is displayed in Yammer. **Action** Similar the actor format, an “action” must also be specified. The action is a verb that describes what happened to the object (e.g. created, updated, deleted, followed, liked, etc). **Object** The key piece of any activity is the Open Graph (OG) object, on which action was taken. An OG object represents an entity instance in your application, like a particular Event (Lunch Meeting) or a CRM Record (Contoso Ltd. Renewal Deal). OG objects are uniquely identified with their URL and their title is displayed in Yammer as a link to the URL. We recommend sending Yammer as many properties for your OG objects as you can for appropriate display. When your app sends an activity to a Yammer network, a corresponding OG object is created in the Yammer, if it doesn’t already exist. When an OG object exists (with the same URL), it is updated appropriately. For general details on Open Graph outside of Yammer's implementation, check out: http://ogp.me/