Before you can effectively customize the Reach Extensions, it’s important to understand how Reach interacts with the host pages and the Socialcast community. The following diagram provides an overview of this process.
Initially, you must create the Reach Extension within Socialcast. At the end of the creation process, Socialcast generates a code snippet.
Next, you embed the code snippet or install the Web Part in the appropriate page or template of your application.
When the application page loads, the Reach parser reads all the page metadata and OGP metadata. For certain extensions, Reach uses the metadata to determine what information to display in the extension. For example, Dynamic Extensions might use email, group_name, or group_id. Reach builds the appropriate extension and loads it into the specified container on the page. Reach stores the rest of the metadata for later use.
If you want to process the metadata differently or if you want to extract other data from the page, you can create and use a custom parser. See Creating a Custom Parser or Interpreter for details.
When the user interacts with the extension and adds a comment or clicks a button, the Reach interpreter takes the user input and combines it with the page metadata to construct a message that is sent back to the community. This message may appear in the company stream or some other stream, depending on how you configured the extension.
You can customize the Reach messages that appear in the community by using a custom interpreter rather than the default. See Creating a Custom Parser or Interpreter for details.