Hi George
First off, thank you for the notes here. We figured out the issue so I wanted to provide you wilh some notes. Here is what my developer discovered.
--------
Ok I did some looking through there code and I figured out the problem.
It's checking for lowercase text matches, which doesn't work on picklists. You may notice if you add a rule for a text field, it saves it as lower case (no matter what you type in). But if you add a rule for a picklist, it doesn't alter the case.
The database query it uses when running the rules checks for lowercase data on a user.
So basically, it's looking for: lowercase(userdata) = 'Vidyo Partner Sales Certification Program'
Which of course would never happen since the string has uppercase letters.
To verify I created another program that is all lowercase, and that one worked.
So Totara will need to modify the code to either save the rules text string in lowercase, or to not use the lower() function in the SQL query when checking picklist values. I'm thinking that they should probably just not use lower() because I'm pretty sure Moodle would consider "Test" and "test" to be 2 different strings (case sensitive), so Totara should also be observing case in those situations.
---------
I'm not sure how to submit this to the Totara development team. Can you point me in the right direction?
thanks
Matt