Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
8 replies
Subscribers
6 subscribers
Views
4154 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Using User Input Task Activity Node with an expression based task assignment to
abhinavg
over 9 years ago
Using User Input Task Activity Node with an expression based task assignment to assign task to groups
Issue: Set re-assignment privileges for assignees in task node changing to default rights (Can reassign the task to anyone) even on using other rights,while using expression based assignment
Task Assignment Expression Used : if(testCondtion, getgroupbyname("ABC_Location_475"), getgroupbyname("ABC_Location_145") )
ABC_Location_# groups already exist in Appian
Is it not possible to have expression based assignment with changed re-assignment privileges ? or group functions is causing some issues ?
Thanks,
Abhinav
OriginalPostID-161633
OriginalPostID-161633
Discussion posts and replies are publicly visible
0
Chris
over 9 years ago
The reassignment setting should have no effect. You are most likely running into an issue with the process initiator not having permissions to see the groups you are trying to retrieve, thus the function getgroupbyname() returns no data. What I've done for this same situation is to create 2 group-type variables inside the process model, or one for each potential group assignment, then use the pv!groupValue1 variables for the assignment expression.
In the model, I use a script task run under the designer account to default pv!groupValue1 to getgroupbyname("ABC_Location_475"), then pv!groupValue2 to getgroupbyname("ABC_Location_145"), then you can set your assignment expression to:
if(testCondtion, pv!groupValue1, pv!groupValue2)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
@csteward There is no issue in task assignment and it happening as per design
But i'm running into issue while changing re-assignment privileges for assignees to set to "No Privilege"
On changing the re-assignmentat design time and saving it to "No Privilege" , if re-opne the node and check with settings it's getting reset to default ( i.e ALL Privileges )
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 9 years ago
Hi abhinavg, I see what you are saying now - and also am able to reproduce this issue in my environment (7.10) - would be worth sending to support.
If assignment is set using either getgroupbyname() or getgroupnamed(), reassignment privilages will not save. Other functions do not seem to cause this issue. As a work-around, can you set the assignment to a group variable in a prior node, then use that variable for assignment on the task? This should allow you to set reassignment privileges correctly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
@csteward Correct i did by that way only and will raise SR for the issue !
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tom Ryan
Appian Employee
over 9 years ago
This issue is caused by expressions including double quotes. The current workaround for this issue is to use a pv or constant instead, eg
getgroupbyname(pv!groupName) or getgroupbyname(cons!GROUP_NAME)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 9 years ago
Thanks Tom. Is there a reference # so we can track the resolution of the issue?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
abhinavg
over 9 years ago
AN-61183
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 9 years ago
Thanks.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel