Hi,

Did you have any problems with rule resolution on Branch, that do not replicate in Application rulesets?

I have an activity MainActivity on class Corp-Int-FE (integration with some Front End application) that needs to run newly created SecondaryActivity on pyWorkPage (Corp-FW-MyApp-Work).

Now, MainActivity is defined in FEInt ruleset (which uses application validation) and I want to create SecodaryActivity in MyAppFW ruleset (which also uses application validation) because I find that SecodaryActivity is doing some application logic, not service layer logic.

If I use a Branch MyBranch and create  SecodaryActivity in myBranch, ruleset MyAppFW, and attempt to change MainActivity in MyBranch to call SecodaryActivity, on save I get an error like: 

Method— "Corp-FW-MyApp-Work.SecondaryActivity" exists, but may not be used by this rule due to the ruleset’s validation mode and/or your current application context.(found activity Corp-FW-MyApp-Work.SecondaryActivity in MyAppFW_Branch_MyBranch:01-01-01)

If so, how did you resolve it?

I was able to resolve it by creating SecodaryActivity in FEInt. I am not very happy with this solution, as this means that I would have to implement the app logic in FEInt. Otherwise I have to place FEInt bellow MyAppFW in my application ruleset stack.

I must say that this behavior does not occur outside of the branch. If I create/modify the rules in the application rulesets directly, there seems to be no issue with rule resolution.

Kind regards,

Ioana