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
11 replies
Subscribers
8 subscribers
Views
2951 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Hello, I had to change a task in a Process Instance (more than one ac
mjmallet
over 11 years ago
Hello,
I had to change a task in a Process Instance (more than one actually). The task is almost at the end of the process, and when I did the change on one particular instance, the process was in the timer. It did not update the process history to show that I did some changes to the process. But it kept the changes I did in the task, and when the process came to that task, it did not show the changes I had made. (it was showing the older version of the task)
Would the timer be the cause of this?
I had to cancel that task and restart it so that the changes would appear. ...
OriginalPostID-39960
OriginalPostID-39960
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 11 years ago
Does that mean you made the change before the task was created? Because you edited the activity after the task instance was created then the "Cancel-then-restart" approach is mandatory.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mjmallet
over 11 years ago
yes the modification was made before that task was created.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 11 years ago
What do you mean by the process was in the timer?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mjmallet
over 11 years ago
It's the Travel Process, we have a couple of tasks that gets the necessary information. And then after the user confirms that the travel was booked, it goes into a "timer event' and waits until departure date to assign the next task. I noticed that when I did my modification in my process it was in that "timer" mode. It did not even register me doing work on the process in the history.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 11 years ago
But is the timer in the task directly? or is a timer before the task?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mjmallet
over 11 years ago
It's an event timer. (a couple of tasks before the one I made modifications too)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 11 years ago
As long as the instance hasn't been started yet the new instance created should show the changes. I've never seen this before.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mjmallet
over 11 years ago
Should I do more test on DEV, will you guys investigate this situation also?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 11 years ago
The process history doesn't explicitly show when you do an "Apply Changes" or "Save New Version" while editing a process instance. You only see entries of this type:
Aug 10, 2012 3:10 PM My Process Model Pause eduardo.fuentes
Aug 10, 2012 3:10 PM My Process Model Resume eduardo.fuentes
indicating you paused and resumed the process which can mean that you edited the process or explicitly paused and resumed it.
Only if you change the values of variables, start new instances of nodes, or cancel them, a new explicit entry is added to the process history; but editing a form doesn't get logged in there in other way than a "Pause" - "Resume" entry.
I tried to reproduce this with a model placing a timer before a user input task and updating the form before the timer completed. In my case the form was instantiated correctly and showed the changes.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 11 years ago
My suggestion would be to check the process history and search for any entries of type "Pause" - "Resume" and see if the "Started Time" of the instance that you canceled (the one that DIDN'T show the change) is less than the Date & Time value of the "Resume" action; if it is then it's expected as the task was instantiated before the process was resumed (meaning before the change was applied).
If you are able to consistenly reproduce this in a simple process model let me know so I can try the same steps, but I definitely suggest to check what I just mentioned (i.e. Pause - Resume entries in the process history)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>