Adding Publish Table Actions

Use a publish table action to publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publish.

  1. Navigate to where you want to add the action, as described in Adding and Editing Actions in Message Flows.
  2. Select Add an Action > Communication > Publish Table.
  3. Click <Expression>. The XQuery Expression Editor page is displayed. Create an XQuery expression, which at run time returns the value upon which the routing decision will be made. See Creating and Editing Inline XQuery and XPath Expressions.
  4. From the Operator list, select a comparison operator. Then, in the adjacent field, enter a value against which the value returned from the XQuery expression will be evaluated.
  5. Click <Service> to select a service to which messages are to be published if the expression evaluates true for the value you specified. The Select Service page is displayed.
  6. Select a service from the list, then click Submit. This is the target service for the message.
  7. If the service has operations defined, you can specify the operation to be invoked by selecting it from the invoking list.
  8. If you want the outbound operation to be the same as the inbound operation, select the Use inbound operation for outbound check box.
  9. In the Request Actions field, to configure how the message is packaged and sent to the service, click Add an Action, then select one or more actions that you want to associate with the service. To learn more about the type of action you want to add, see Adding and Editing Actions in Message Flows.
  10. Note: There is a nesting limit of four cumulative levels in the stage editor. If you attempt to add a fifth level, nesting action is not displayed. Cumulative levels include all branching actions: if... then... conditions, publish tables, and route tables. For example, you can have 2 levels of conditionals, then a publish table with a route table inside of it, bringing the total to 4 levels. If you attempt to add another conditional (to the last publish table), the conditional is not displayed.
  11. To insert a new case, click the  Case icon, then select Insert New Case.
  12. Repeat steps 4-8 for the new case.
  13. Add additional cases as dictated by your business logic.
  14. Click the  Case icon of the last case you define in the sequence, then select Insert Default Case to add a default case at the end.
  15. Configure the default case-the configuration of this case specifies the routing behavior in the event that none of the preceding cases is satisfied.

After you finish

When you complete the configuration of this action, continue by configuring other actions or by saving your configuration, as described in Adding and Editing Actions in Message Flows.