Agents and Rule Resolution

How does the Rule resolution work for Agent rule? Can someone justify below example?

I have an agent rule present in 2 different versions.

1) XYZ:01-01-07(Availability : yes)

2) XYZ:04-01-01(Availability : Not Available)

Application stack has XYZ:01-01.

At runtime, Master agent is picking up the agent rule from 04-01-01 even though availability of agent rule is set to NO and creating agent schedules.

Is this the expected behaviour. I saw that rule resolution works differently for Agent rule in one of the article but will it not consider the availability?

This is one of the article i have found above.

***Edited by Moderator Marissa to update platform capability tags****


Keep up to date on this post and subscribe to comments

November 21, 2018 - 7:08am

Is there are access group specified for this agent on the security tab?  If so does the assigned access group give access to version 04-01-07?

December 5, 2018 - 9:21pm
Response to Marc Alderman

Yes, Access groups are defined in both the versions of agent rule.

But both the different accessgroups are pointing to 01-01 version of a rulese and not pointing to 04-01-07.

December 19, 2018 - 11:46am

Waiting for the response.

December 27, 2018 - 1:24pm

I tried it on my system and the agent schedule was generated from the available version. Did you delete the agent schedule after the XYZ:04-01-01 version was changed to Not Available?

December 27, 2018 - 3:20pm
Response to CarissaW_GCS

Yes, i think i have deleted the agent schedule but will it regenerate the new agent schedule from the higher version which is set to Not available?

How does rule resolution work with Agents?

December 27, 2018 - 3:33pm
Response to SaurabhG7566

In my test, the schedule was regenerated from the available version. I was using a 7.3.1 system.

I created an agent in ruleset 01-01-01 with a recurring schedule. I then saved the agent rule into 02-01-01 with a different recurring schedule. When the initial schedule was created, it used the 02-01-01 version since they were both available at that time. Then I changed my 02-01-01 version to Not Available and deleted the agent schedule. When it regenerated, it had the schedule from the 01-01-01 version, which was Available.