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
5 replies
Subscribers
5 subscribers
Views
3448 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
How to take action or trigger a process based on Task state change
tobil
over 7 years ago
We are attempting to write task information to the database based on the changing state of a task: Opened, Assigned, Accepted, Completed. Is there a way to accomplish this?
OriginalPostID-237255
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 7 years ago
In order to use the a!writeToDataStoreEntity(), the user would have to interact with any of the components(that has 'saveInto' attribute) on the interface. So the status won't be known really unless the user starts working on the form post accepting the Task. Also, we might not be able to track the events such as Reject, Return, Reassign etc with this approach. Next to it, we need to think about the component under which we want to use the a!writeToDataStoreEntity(). If we are creating a field for interaction especially intended for this functionality, that should be fine. Else we should place either under all the components in the form or under the saveInto of Submit button, and obviously, the earlier one may not be great. Also, there is a restriction that we can use only one smart service function inside a 'saveInto'.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 7 years ago
In order to use the a!writeToDataStoreEntity(), the user would have to interact with any of the components(that has 'saveInto' attribute) on the interface. So the status won't be known really unless the user starts working on the form post accepting the Task. Also, we might not be able to track the events such as Reject, Return, Reassign etc with this approach. Next to it, we need to think about the component under which we want to use the a!writeToDataStoreEntity(). If we are creating a field for interaction especially intended for this functionality, that should be fine. Else we should place either under all the components in the form or under the saveInto of Submit button, and obviously, the earlier one may not be great. Also, there is a restriction that we can use only one smart service function inside a 'saveInto'.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data