Testing configured actions

Test the Slack action to verify configuration, view input or output data, and help ensure correct message delivery.

Procedure

  1. On the Test action window, you can see two tabs: INPUT and OUTPUT. By default, the INPUT tab is open, which displays the input details you have entered for the Slack-Post Message to Channel action.
  2. Scroll down and click the Test button to check whether you have configured the action properly.
    Note:
    • Testing a Logger action is supported up to 256 KB. If you test a Logger action with data greater than 256 KB, you get a message size too large error.
    • Testing any other action is supported up to 512 KB. If you test any action with data greater than 512 KB, you get a message size too large error.
    • To copy-paste the paths and values of input or output data, hover your mouse over the data, click the three dots, and then select the Copy value or Copy path options.
  3. When you click Test, webMethods Integration posts a message, which contains the tweet on the specified Slack channel, and shows the output of this action in the window.

    This step allows you to check whether the action is working as expected and also fetches the sample output for this action, which can be used when setting up the next actions.

  4. Click Skip if you prefer not to wait for the test action output to display. When you select Skip, the system continues testing the action in the background, which allows you to go to the next screen.

    After completing the workflow configuration, you can save and reopen the workflow to view the output from the tested action.

    Note:

    If you skip testing an action for the first time and later use that action's output keys in a subsequent action, you encounter an error during the second action's test. This occurs because skipping the test prevents the system from generating the necessary output data, making it unavailable for any following actions.

    If you skip retesting an action after changing its inputs and then use that action’s output keys in a subsequent action, the system will use the old output data from the first action to test the second action.

  5. Just like a trigger, you can set up filters for your actions. The process to set up filters for actions remains the same. Next, click Done, which takes you back to the canvas.