Question: How to fix no match condition for application service template in workflows?


Answer:

  1. In Director view, select the Workflows tab in the top menu bar.
  2. Select Template > Application Steering in the left menu bar.
  3. Click the Add icon to create a template.
  4. Enter a name for the template and select an organization.
  5. Click Deploy.
  6. Select the Configuration tab in the top menu bar.
  7. Select the Templates > Service Templates in the horizontal menu bar.
  8. Click the Default Application. The view changes to Appliance view. 
  9. Select the Configuration tab in the top menu bar.
  10. Select Services > SDWAN > Policies in the left menu bar.
  11. Select the Rules tab in the horizontal menu bar. In the list of rules, check the Applications column to locate any rules for which applications are not defined. In the screenshot below, the red boxes highlight four rules that have no applications. These rules are SaaS Application, Database, Business Traffic, and File Transfer.
  12. Click the default application.
  13. Select the Home tab to return to Director view. select the Workflows tab in the top menu bar.
  14. Select Template > Application Steering in the left menu bar.
  15. Select the Template Name and Organization. 
  16. In the Business Critical (Assured Forwarding) box, locate SaaS Applications and click the Edit icon to edit the rule.
  17. Edit Rule to category Business Critical popup window displays and select the Application/URL tab.
  18. In the Predefined Application Filters box, select SaaS Applications.
  19. Click Continue.
  20. Under the Business Critical (Assured Forwarding) find the Database and click to edit the business-critical rule.
  21. Edit Rule to category Business Critical popup window displays.
  22. Select the Database from the drop-down menu for Predefined Application Filters/Groups.
  23. Repeat the above step for Business_Traffic and File-Transfer rule.

Note: This issue is applicable to application service templates created in Releases 16.1R2S9 and earlier. The problem has been fixed in Releases 16.1R2S10 and later.