SLO does not allow for multiple selections | Service selection: The query in the service selection is invalid.

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

When creating an SLO object and attempting to set it up to get the notifications when two jobs completed, saving is not allowed when using the option ALL.  The following error shows up:

Service selection: The query in the service selection is invalid.

Error screenshot attached. 

Environment

Release : 12.x, 21.x

Cause

This is by design

Resolution

The dropdown "All" acts as an "AND" filter.  So in this case it is saying that:

The object name equals "JOBP.EBS.WEEKEND.PA.US"
AND
The object name equals "JOBP.EBS.WEEKEND.PA.CA"

This cannot be true since it needs to be one OR the other and cannot be both at the same time. 

Using the dropdown choice of "Any" will allow it to be one or the other.  Alternatively, you could use an operation of "contains" if it should contain both of those values.

There are possible workarounds for this - below are examples of how these might work:

The first way is if both the JOBP.EBS.WEEKEND.PA.CA and JOBP.EBS.WEEKEND.PA.US are in the same parent workflow - for the purposes of this example, it's called JOBP.TOP.  In this case:

1. Create a "dummy" script object, (here called SCRI.WEEKEND.END) it has Generate at Runtime in the Attributes tab and simple :WAIT 30 in the process tab
2. Place SCRI.WEEKEND.END in the JOBP.TOP and connect a line from JOBP.EBS.WEEKEND.PA.CA to SCRI.WEEKEND.END and then connect a line from JOBP.EBS.WEEKEND.PA.US to SCRI.WEEKEND.END and update Time & Dependencies so that the script is dependent upon both
   
3. Update the SLO object that the service level so that it uses the service selection of Object name equals "SCRI.WEEKEND.END"

The second way to do this is somewhat similar and could be used if the JOBP.EBS.WEEKEND.PA.CA and JOBP.EBS.WEEKEND.PA.US workflows are not in the same top workflow.  This will use them for a dummy script in its own workflow with both as external dependencies:

1. Create a "dummy" script object, (here called SCRI.WEEKEND.END) it has Generate at Runtime in the Attributes tab and simple :WAIT 30 in the process tab
2. Create a workflow (here called JOBP.WEEKEND.END)
3. Add the script to the workflow and connect the start and end nodes to the script
4. Add JOBP.EBS.WEEKEND.PA.CA and JOBP.EBS.WEEKEND.PA.US to the workflow and connect them each to the SCRI.WEEKEND.END (but not to the start or end nodes)
5. Right-click on each JOBP in the main JOBP and choose "Convert to External Dependency"
6. Update the Properties on each of the weekend workflow external dependencies, updating:
   Check Expected Status to ENDED_OK
   after the last workflow execution end
   Else This Task Wait
   
7. Update Time & Dependencies for the SCRI task in JOBP.WEEKEND.END so that both external dependencies are ENDED_OK
8. Save the changes
9. Schedule the workflow to run every weekend at some point (depends on your timing)
10. Update the SLO object that the service level so that it uses the service selection of Object name equals "SCRI.WEEKEND.END"