Merge pull request #4223 from TovaCohen/post-release-updates

Post release updates

doc/connecting/topics/adding_amq_connection_middle.adoc

@@ -43,6 +43,18 @@ to send messages to.
 .. For the *Destination Type*, accept *Queue* or select *Topic*.
 .. In the *Message Selector* field, if you want to receive only responses
 that satisfy a particular condition, enter a filter expression.
++
+A message selector is a string that contains an expression. The syntax of 
+the expression is based on a subset of the SQL92 conditional expression syntax. 
+The message selector in the following example selects any message that has a 
+`NewsType` property whose value is set to `Sports` or `Opinion`:
++
+`NewsType = ’Sports’ OR NewsType = ’Opinion’`
++
+The message consumer receives only those messages whose headers and 
+properties match the message selector expression. A message selector cannot select messages on 
+the basis of the content of the message body.
+
 .. In the *Named Reply To* field, enter the name of
 a queue or topic. The destination sends its response
 to this queue or topic. 

doc/connecting/topics/adding_amq_connection_start.adoc

@@ -28,6 +28,17 @@ close and reopen without missing messages, enter the durable
 subscription ID. The destination type must be a topic. 
 .. In the *Message Selector* field, if you want to receive only 
 data that satisfies a particular condition, enter a filter expression.
++
+A message selector is a string that contains an expression. The syntax of 
+the expression is based on a subset of the SQL92 conditional expression syntax. 
+The message selector in the following example selects any message that has a 
+`NewsType` property whose value is set to `Sports` or `Opinion`:
++
+`NewsType = ’Sports’ OR NewsType = ’Opinion’`
++
+The message consumer receives only those messages whose headers and 
+properties match the message selector expression. A message selector cannot select messages on 
+the basis of the content of the message body.
 
 .  Click *Next* to specify the action's output type. 
 

doc/connecting/topics/adding_amqp_connection_middle.adoc

@@ -44,6 +44,19 @@ to send messages to.
 .. For the *Destination Type*, accept *Queue* or select *Topic*.
 .. In the *Message Selector* field, if you want to receive only responses 
 that satisfy a particular condition, enter a filter expression. 
++
+A message selector is a string that contains an expression. The syntax of 
+the expression is based on a subset of the SQL92 conditional expression syntax. 
+The message selector in the following example selects any message that has a 
+`NewsType` property whose value is set to `Sports` or `Opinion`:
++
+`NewsType = ’Sports’ OR NewsType = ’Opinion’`
++
+The message consumer receives only those messages whose headers and 
+properties match the message selector expression. A message selector cannot select messages on 
+the basis of the content of the message body.
+
+
 .. In the *Named Reply To* field, enter the name of
 a queue or topic. The destination sends its response
 to this queue or topic. 

doc/connecting/topics/adding_amqp_connection_start.adoc

@@ -28,6 +28,18 @@ close and reopen without missing messages, enter the durable
 subscription ID. The destination type must be a topic. 
 .. In the *Message Selector* field, if you want to receive only 
 data that satisfies a particular condition, enter a filter expression.
++
+A message selector is a string that contains an expression. The syntax of 
+the expression is based on a subset of the SQL92 conditional expression syntax. 
+The message selector in the following example selects any message that has a 
+`NewsType` property whose value is set to `Sports` or `Opinion`:
++
+`NewsType = ’Sports’ OR NewsType = ’Opinion’`
++
+The message consumer receives only those messages whose headers and 
+properties match the message selector expression. A message selector cannot select messages on 
+the basis of the content of the message body.
+
 
 .  Click *Next* to specify the action's output type. 
 

doc/tutorials/topics/amq2api_confirm_works.adoc

@@ -8,7 +8,7 @@ After you create and publish the AMQ to REST API sample integration,
 you can confirm that it works as defined. 
 
 .Prerequisite
-* In {prodname}, in the list of integrations, 
+In {prodname}, in the list of integrations, 
 *Running* appears next to the AMQ to REST API 
 integration that you created and deployed. 
 
@@ -40,3 +40,13 @@ the two vendors.
 ID, for example, to `1234`.
 .. Click *Send JMS Message*. The To Do app client API returns a new
 task with the item ID that you just entered.
+
+. Optionally, view the integration log to troubleshoot an
+unexpected result or to learn more about integration execution: 
+
+.. In {prodname}, in the left panel, click *Integrations*.
+.. Click the entry for your AMQ to API integration.
+.. In the integration's summary page, click the *Activity* tab.
+.. Optionally, enter date and/or keyword filters to limit the executions
+listed.
+.. Click the integration execution for which you want to view activity information.

doc/tutorials/topics/sf2db_confirm_works.adoc

@@ -36,3 +36,14 @@ OpenAPI (Swagger) file for the To Do app to create an API client connector.
 
 . In the *To Do App* display, you should see a notification that a new 
 lead was created in the database. 
+
+
+. Optionally, view the integration log to troubleshoot an
+unexpected result or to learn more about integration execution: 
+
+.. In {prodname}, in the left panel, click *Integrations*.
+.. Click the entry for your Salesforce to database integration.
+.. In the integration's summary page, click the *Activity* tab.
+.. Optionally, enter date and/or keyword filters to limit the executions
+listed.
+.. Click the integration execution for which you want to view activity information.

doc/tutorials/topics/t2sf_confirm_working.adoc

@@ -47,3 +47,14 @@ account.
 The new contact record should have the name that is associated with the 
 Twitter account that you used to tweet. The text of your tweet should be in the
 *Description* field, and your Twitter screen name should be in the *Title* field.
+
+
+. Optionally, view the integration log to troubleshoot an
+unexpected result or to learn more about integration execution: 
+
+.. In {prodname}, in the left panel, click *Integrations*.
+.. Click the entry for your Twitter to Salesforce integration.
+.. In the integration's summary page, click the *Activity* tab.
+.. Optionally, enter date and/or keyword filters to limit the executions
+listed.
+.. Click the integration execution for which you want to view activity information.