(Urgent Issue) Background: I am working on an old process model and se

manojj over 10 years ago

(Urgent Issue)
Background:
I am working on an old process model and seems like it was saved in corrupted form way back, some 100 versions back. Now the process model in the dev environment seems corrupted with missing swimlanes and connector lines in zig-zag shape. I can also see that the exception flow lines are replaced with connector lines.

I know that someone might have deleted the CDT and might have uploaded a new one with new namespace, and they might have saved it so the process model in dev environment is corrupted.

Problems:
1. They have implemented lots of Change Requests in dev which are to be pushed to prod.
2. The testing went well earlier, but in regression testing we came across one issue..
A quick task is assigned to one user but he cant see it, i checked and all seemed fine. Then I deleted the node and created a new node with all exact same values, it worked fine for 1-2 instances and now it has again stopped working. I monito...

Discussion posts and replies are publicly visible

0 manojj over 10 years ago

...red the process and it seems it is referring to corrupted one again.

What the best approach to deal with such scenarios? I will try to delete the node and will create a new node and check if it works fine but the problem is the behavior of the nodes are not predicted .....
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

Since you already saved the changes you may need to do the following:

1. Open a previous version while monitoring the application server log to understand the root cause
2. Fix the root cause
3. This will allow you to see the previous version in the right format (the only versions that cannot be automatically fixed are the ones were you explicitly saved the "bad" structure
4. The quick task issue is because swim lanes used for assignment were lost too as part of this issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 manojj over 10 years ago

Hey Eduardo, thanks for replying. For assignment of quick task, we had overridden the swim lanes assignment and had set one user and a groups explicitly for quick task. So I hope that swim lanes assignment should not affect it.

Going back to the older version is a bit difficult as the older developers published after every save and I checked that the CDT^ references were there even in 200 version older process model. So it is difficult to revert back to that and accommodate all the changes done from there onwards.

Is there any other solution?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

You shouldn't use the CDT^ annotation as an indication of those versions having the issue; that's actually not an accurate way to find what versions were impacted. What you need to do is to open some previous versions and see what error the log throws.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 manojj over 10 years ago

ok, but in that case I will need to keep on checking for each version log till I reach at the corrupted version and then rectify it. Long way down :(
Another point is that we have proper model in production environment. If we wish to backport it from there..whats the proper process?
Should we delete the related application/process/object from dev environment, import the app from production and then add the changes related with CRs manually?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

Any version should show the error.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

If the model on PROD is up-to date then you can definitely re-import it from PROD to this environment without any additional steps
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 manojj over 10 years ago

it's not up-to date, but it is not corrupted...so if I wish to backport it from prod to dev, will I need to delete the process model in dev. environment first and then import from prod?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

What if you try opening a couple of previous versions and monitor the log, you should search for the word ProcessDesignServiceXmlImpl in the application-server.log to find out the root cause; if you don't find anything then it's ok to back port from PROD without deleting anything.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel