Candidate User Expression for (;)
This should be straightforward, but I’m stumped.
Has anyone using {role(<roleName>;<relationName>)} user expressions noticed any issues? In my 2022.10 installation, it appears that Candidate User Expressions will yield empty results when the current asset is not on the source-side of the relation.
For example… Given:
- business terms Academic Administrator, Academic Manager,
- where both assets are in the same domain where an SME is assigned
- Academic Administrator groups asset Academic Manager
- When a test workflow is run against Academic Administrator
- User Expression of
{role(Subject Matter Expert;groups)}evaluates to the SME
- User Expression of
- When a test workflow is run against ** Academic Manager**
- User Expression of
{role(Subject Matter Expert;grouped by)}evaluates to []
- User Expression of
Can anyone corroborate this?
Tom Friesen
Posted 3 years ago · Edited 1 year ago·Last reply 3 years ago
4 comments
Tom Friesen
OP3 years ago · EditedHey all,
Just wanted to update on this issue.
This was reproduced by engineering. I have been notified that the team has fixed the issue and it will be implemented on version 2023.02.
Cheers,
Tom
arthurburkhardt
·3 years ago · EditedJust did this little test for you:
FeedItemBestCommentIdcolumn (which is part of tableFeedItemThis is the code
This is the data
Those are the logs
It seems it’s working with both the role and the co-role.
Tom Friesen
OP3 years ago · EditedHey @arthur.burkhardt… Thanks for testing!
Do you also have success when running it from the
FeedbackItemasset? This is where I run into issues…When run from
Academic AdministratorBusiness Term…When run from
Academic ManagerBusiness Term…And… Am I missing something? Why does it not come up blank when the source asset and the co-role are specified? In your case, I would have expected:
When run from BestCommentId …
And when run from FeedItem …
arthurburkhardt
·3 years ago · EditedAh… Interesting.
When run from BestCommentId …
And when run from FeedItem …
It looks like the user expression does not care about the role or co-role, and only works from source to target, not the other way around.
I guess it would be safer to stop using this type of user expression and focus on querying through the workflow APIs instead.