I fixed my Process Model with help from the forums. When I ran the Record Related Action that was using it, I realized older version of my Process Model was getting picked.
So I made sure my latest corrected Process Model version had been published. It was and all older versions showed disabled. For good measure I deleted my Related Action on my Record and recreated it. Same problem. I know for sure the last but one version of my Process Model getting picked because when I monitor the instance and look at Variables in Process Details, I see the debug variables I had introduced.
In frustration, I deleted all previous versions of Process Model and only kept the one which works and which does not have any debug process variables. Once again, I deleted Record Related Action and created it again. For good measure, I also unpublished Application and published again.
I ran my Related Action again. SAME Problem. How in the world is my Related Action able to find a non-existent version of my Process Model and instantiate it?
The only way that could happen is if that related action is triggering a process model that is running (not a new one).
When you publish a new process model, non-completed processes of old process models are still running. You should check
1) Create a new record and do the necessary steps to execute that related action
2) Check in the monitoring non-completed running instances of your related action. If that is the case, delete those instances.
Let me know if that hel
When you configure a process model for record related action, the process models latest published version will be picked to trigger an instance.
Is the process model published, without any errors? We often face issues, with deleting the process model versions. I would not recommend to delete the previous version, it will impact the parent processes that are using these.
Make sure that the latest version is in state "Published" not "Published disabled".
I assume that the PM configured as a related action is not a wrapper model which in turn calls a subprocess.
I understand the latest should be picked up. That's exactly my quesiton.
Now I did delete old older process models since I wanted to stop pulling my hair. I'm just learning right now, so there is no other Record referencing the process model. Status is indeed just published and not disabled. Also no subprocesses.
I've just been suffering from n00b syndrome where some basic things are working for me (like in the other thread I'm reading a CDT instance which will not get assigned to my pv! variable while process model throws no error). This is for the same process model.
Thanks for replying and improving my understanding. I'll keep at it and hope to reply with something different.
I have deleted all existing process instances. This happens when creating new instances. As unbelievable as it may sound...
I'm just going to start from scratch with new process model, record action, etc. for my sanity sake.
I think conceptually there is something wrong of what you are doing.
You said that you introduced some debug variables to know which version of your process model you are running. For checking which version of the process model you are running, you should go to your application, select monitoring and check the version that the "Process Model" columns shows you.
That will help you to
1) check that the correct process model version is being picked up
2) See which values you variables are picking.
Additionally, if you have a process model with a start form, you can do "start process from debugging", that way you see better what is running.
I would not be removing and adding references and old versions of process models as it can leave you a mess behind. If you want to do further test, I would suggest to do a dummy interface with a constant that points to your process model and link to start the process model with a given parameters (for instance that way you can test with the values you should be giving from the related action)
There's a way you can try this without having to start from scratch with your process model. From your current process model, select "File" --> "Save As", which will save a copy of the original as a separate / new PM. Name it something noticeably different, then choose it as the related action PM instead of the original one, and see what happens when you try running it. If it works well, you could just switch to using the new one as your main related action PM, and ditch the old one.
For sanity sake, how about creating a new PM that has nothing to do with any that have come before. Let it be just start node and end node. Configure the related action to run that PM and do nothing instead of whatever it was doing. Confirm that you can at least do that.
Afterward, try reconfiguring your related action to use the new PM you've been trying to get it to run.
Because deleting in Appian is super weird, perhaps create a related action with a completely different name, then make sure the PM you're trying to run doesn't have the same name as anything you deleted.
It could be that Appian sees an object with the same name as a deleted previous object, and runs the previously deleted one because it goes by names for reasons.
It's stuff like this that gave colleagues of mine the best practice of never deleting anything in Appian ever.
Great advice. I thought the same thing. The behavior is consistent. I've done this 3 times since morning.
I created a dummy CDT, a dummy process with User Input Task, a dummy interface form. Saved. Published.
I debugged process model, went To Tempo Tasks, completed User Input Task. Looked in my database table for record. All good.
I went to process model. Pretended to change something. Literally, I checked the
option, then immediately unchecked it. Saved Properties. Saved PM. Published. So NO Change really.
I debugged process model. Task will not show up in Tempo.
I created new application. Did everything all over again. First time works. After pretending to change PM, second time it fails.
Then one more time I repeated the process. 2nd publish...wrecks it.
I'm seeing such inconsistencies with my Appian for the last 2 weeks I've been actively learning. I've published and unpublished the application. No dice (while this trick has worked in the past).
I really don't know what to do. I apologize to anyone reading this if I'm wasting their time.
appianfreak said:I'm seeing such inconsistencies with my Appian
By any chance are you running a local install that you installed yourself? In the past I've seen cases where incomplete / incorrect configurations result in weird / inconsistent behavior on the front end.
No its a testbed environment setup in my organization so folks such as I can go learn.
One thing I did learn is sometimes when debugging within Process Modeler, it picks up the draft version. I've learnt that the hard way. I do know I'm picking up the current process model version now (v 23.0 since I've been thinking my Process Model changes not getting saved).
One clue I have when I know Task is not going to show up in Tempo is this. The Instance shows up in Appian Designer Monitoring tab, BUT inside the Process Designer Process Instances tab, it is not visible. Anytime this happens Task item will not show in Tempo. Nevermind that if I click the Instance from Appian Designer Monitoring tab, it will open up in Process Designer, and I can check the properties and I can SEE my User Input Task, while if I go and check Process Intances in Process Designer, I still don't see the instance!.
So I know the symptoms that tell me I'm going to have a problem, but the cause still eludes me. Sometimes unpublishing / publishing Application solves my problem. However, that's not been working lately. Accidently things work and I'm able to make some changes, but then again it will fail. All of which is taking so much of my time.
The version of Appian is 19.4. Maybe there is a bug list and patches that have not been applied in my environment. That's my only hope.
Okay, I think I have it now.
Whenever I make a change to the Process Model, it will not get picked up UNLESS I re-configure/re-save dependents. So in my case, I had to go to the Record Type Related Action, remove the Process Model reference, re-add it, and Save. For Application Action also I had to do same thing. THEN unpublish/publish application so that the "Related Action" will pickup the Process Model changes and therefore render Task link under Tempo Tasks, and also so that "Application Action" under Tempo Tasks picks up the Process Model changes and therefore render Task link under Tempo Tasks.
This is absolutely Insane!
For now, I'm going to ignore and focus on continuing my learning. Essentially I'm going to discover real quick whether if I modify ANY Appian artifact, it means I have to walk UP the dependent tree and re-save all references to the modified artifact so I can be certain, my changes are going to get picked up.
appianfreak said:Whenever I make a change to the Process Model, it will not get picked up UNLESS I re-configure/re-save dependents. So in my case, I had to go to the Record Type Related Action, remove the Process Model reference, re-add it, and Save.
If this is true and you can reproduce this behavior on demand, then you should consider opening a support case with Appian if possible, because this does not reflect the intended behavior or my experience whatsoever.
Just to double check, you are using the "save and publish" functionality (ctrl-alt-S) every time you save your process model, right? Most experienced designers I know of do this by default in most situations, since not doing so can cause unexpected issues.
Yes, Save and Publish every time on the PM. And yes, now that I know what the heck is going on, I can reproduce the problem at will.
What I also know is that this behavior I only started noticing around 10 days back, and I also know the environment was patched with something. So it's possible something simply messed up.
I will report to my org CoE so they can independently verify if its some install issue or case should be opened with Appian. I'm hoping it is something at our end because I cannot believe no one else outside my organization is seeing this behavior with 19.4. So as of right now, I will assume problem at my end.
Good luck, let me know if you hear anything definitive from them.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.