Hi! I might be wrong, but I read that in saying that an attribute will either be a string or a boolean based upon the evaluation they provided. Meaning, lets say in the profile editor you have what they provided and you get "True" as a result. From that value you would be able to create the group rule. Thus anyone with "True" for the attribute specified would be placed into the group. Is that what you are currently using? The group rules would be based off of the value of the attribute, the profile editor is where the evaluation and result would take place, thus writing to the profile.

Thanks!

Hi @ChristopherS.22060 (Customer)​ , Thank you for reaching out to the Okta Community!

I ran a test to validate the Okta Expression language syntax via attribute mappings in a test app using the following example:

(Time.now()) > user.CustomStartDate ? "success" : "fail"  

→this resulted in a success confirming that the (Time.now()) > user.CustomStartDate expression would result in a boolean output. 

However, the same syntax is not supported in the Group Rules. 

The documentation is not specific enough (in my opinion) when it comes to constrains that apply here. 

I was unable to find any definitive answer to limitations that might apply, for example why some time functions would work (i.e. the doc you mentioned) while others do not. 

I would recommend opening a case to work with one of our Support Engineers to get a definitive answer and if it turns out it's definitely not supported, then perhaps get a documentation update on the Group Rules/Okta Expression Language side for clarity.  

If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

Hope my answer helps! 

--------------------------------

💡 Community Moderator Tip: Join a group today and connect with other Okta customers by region or product.