Best practice forum (Archived)

该论坛讨论已删除

该论坛帖子的内容已被删除，无法再访问。

Hi Jason,

Unfortunately the email audience criteria doesn't support partial matches - you would have to enter all the email addresses (separated by commas) for it to work.

I agree that's a big limitation - we actually already have a ticket open to fix it (T-10404) so hopefully we'll have some time to look at it soon.

Simon

永久链接 | 显示父帖子 | 回复

Hi Jason

To make this work you may be able to use another field such as an organisation hierarchy or a custom profile field that has the one value for Middlemore users in it for the audience rule.

regards

Craig

永久链接 | 显示父帖子 | 回复

该论坛帖子的内容已被删除，无法再访问。

永久链接 | 显示父帖子 | 回复

该论坛帖子的内容已被删除，无法再访问。

永久链接 | 显示父帖子 | 回复

Hi jason

Thanks for the screenshot - I think the problem may be because the changes you need to be approved or saved before they take affect.

From your screenshot they look as though they have been approved (can you check the membership tab again) I tried on the sandpit.tottaralms.com site and this worked.

Craig

永久链接 | 显示父帖子 | 回复

该论坛帖子的内容已被删除，无法再访问。

永久链接 | 显示父帖子 | 回复

Hi Jason,

A few questions - what version of totara are you on (including the minor version available on the Site Admin > Notifications page), and what custom field type is the "Organisation" custom field you created (text, textarea, menu of choices etc)?

Simon

永久链接 | 显示父帖子 | 回复

该论坛帖子的内容已被删除，无法再访问。

永久链接 | 显示父帖子 | 回复

Hi Jason,

What I'm wondering is, what is the "type" of the profile field you created?

When you go to "user profile fields" and you created it, which option did you choose from the "Create a new profile field" pulldown menu?

There is currently a bug that affects the "Menu of Choices" option so if that's the type you used that would explain your problem (it will be fixed in 2.2.17).

Simon

永久链接 | 显示父帖子 | 回复

该论坛帖子的内容已被删除，无法再访问。

永久链接 | 显示父帖子 | 回复

Hi Jason,

We'll put out a release tomorrow.

Simon

永久链接 | 显示父帖子 | 回复

Just to give you an update, 2.2.17 came out yesterday and includes the fix for this so let us know if you're still having problems after upgrading.

Simon

永久链接 | 显示父帖子 | 回复

该论坛帖子的内容已被删除，无法再访问。

永久链接 | 显示父帖子 | 回复

Hey Brandon,

Yes it should clear up all the case issues introduced around 2.2.14, case sensitivity once again depends on the collations you use when creating your database.

Cheers
David

永久链接 | 显示父帖子 | 回复

Hi Jason

Instead of adding the organisation as a new profile field you should consider adding this as an organisation hierarchy.

The advantages of this are

reports are able to be made on different levels of the organisation
audiences for different levels of organisation can be created - select level and include children
hierarchies can be created from csv import in Totara sync rather than manually inputting

It was however good to see the problem with menu choice in audiences fixed and this approach can be used for other requirements such as adding a custom field for qualifications and selecting users based on this.