After you've created Objects within JFBConnect to apply to your pages, you can create Actions that users can take on those objects. Things like "Reading an article" or "Cooking a recipe" can be created using actions and object pairs. This section continues with the "I cooked a recipe" example from previous sections, but the settings are similar for many types of actions.
To begin, go to the Open Graph -> Actions section in JFBConnect. Then click "New" to create a new action that you'll be able to apply to Objects you've created. You'll see a screen like below:
We'll be creating a "New Custom Action". Custom actions are independent of any specific extension. In our example, the "Cook" action could be applied to any recipe whether that recipe is a Joomla article, K2 item, EasyBlog post, or something else. Similarly, if we want to create a "Read" action, that would work for any Joomla extension. These types of actions are triggered when either:
These types of actions are triggered when the user does something that's already built-in to supported extensions. For example, if you want to post to a user's Timeline when leaving a review in JReviews, voting on a Joomla article, or other actions that are defined in the Open Graph plugins, you can select those from the options.
Once you've created the new Action, you'll see options like in the image below:
These should be enabled however you have enabled them in your Facebook Application. When enabled here, the Open Graph Action popup will display the user entered values like Friend Tagging, User Message, or Place Tagging.
Explicitly Shared is an option that means the user is fully aware that the action will be posted to their Timeline. Since there is a popup that clearly explains the action will be going to Facebook, this setting is ok to be enabled. However, using Explicitly Shared makes the approval process for your Action more rigorous. Additionally, you may not want every post to show in the Timeline. Some actions are 'lightly social', like "I'm interested in xyz" or even "I cooked". In these cases, you may not want the explicitly shared option so that it still goes to the user's Activity Log and can be seen in the news ticker and news feed but isn't guaranteed to display on that user's Timeline.
In this area, select any objects you've created to which this action can act upon. In our case, we want our "cook" action to be allowed on "recipes", so we check that box.
These settings determine how the action is triggered. Almost all actions you create will be "Manual" actions, in that the user needs to do something on your site for them to post. For consumption actions, like "reading an article", "watching a video", or "listening to a song", those actions would be automatic as they trigger a set amount of time after a page has loaded:
Whew! Lots of settings, but hopefully not too complex. From here, your actions are ready to be triggered by your users.