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
6 replies
Subscribers
7 subscribers
Views
2890 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
As soon as a user accepts a task, I need to change the value of a pv!. I saw a l
padmanabhanv
over 11 years ago
As soon as a user accepts a task, I need to change the value of a pv!. I saw a lot of threads on this but none served my purpose. Is there a workaround for this, or do I need to create a dummy form where the user goes and clicks a button "I accept" to achieve this requirement?...
OriginalPostID-96030
OriginalPostID-96030
Discussion posts and replies are publicly visible
0
Sathya Srinivasan
Appian Employee
over 11 years ago
What are you using the set value for? Can you not execute a report at the point of time where this value is required on the task report and identify what the task status is, i.e. Assigned or Accepted and use this as an indicator accordingly?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
padmanabhanv
over 11 years ago
Not exactly. I am tracking the status of a request as it progresses in its lifecycle. Certain user actions can change the request status. An user accepting a task should change the status to "Accepted". Now the status I am talking about is the status of a custom variable I use for reporting and is no way tied to the Appian Process or task statutes. Is there a way to achieve this?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 11 years ago
Hi padmanabhanv, Consider this solution if usage of js/ jquery is allowed. Create a dummy user input task and write a autosubmit event on load of the form, such that the form gets submitted automatically whenever someone accepts the task. Also capture the tp!owner of this task. Now place a script task which updates your status variable, or else this could be done in the dummy user input task itself. Now have the original task after this in an activity-chained fashion.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 11 years ago
And finally provide the assignment of original task to the tp!owner captured in the dummy user input task.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
padmanabhanv
over 11 years ago
@ sikhivahans - Thats a cool idea. Thank you
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jim Beckley
Appian Employee
over 11 years ago
For a more Tempo-friendly solution, I would try using the getTaskAcceptedTimestamp() function in the Task Smart Services plugin, and then (in a rule event) use APN_isEmpty on the pv you're saving the timestamp into to check for that status change.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel