How to identify process models which are not published and are in draft state?

RE: How to identify process models which are not published and are in draft state?

Todd Tran — Mon, 25 Jul 2016 23:58:50 GMT

Issue resolved. Found a sub-process model recently deployed but was in un-published state.

RE: How to identify process models which are not published and are in draft state?

Ashvin Kapur — Mon, 25 Jul 2016 23:55:07 GMT

Tltran, have you gone through similar debugging steps as were suggested for Phanibabuk?

RE: How to identify process models which are not published and are in draft state?

Todd Tran — Mon, 25 Jul 2016 23:29:51 GMT

All the sudden, we run into this exact issue in one of our environments. Republished prior versions of the PM but didn't not help. Phanibabuk, could you share additional information...whether the issue was in the Startup process or one of the sub-processes? Thanks for your help.

RE: How to identify process models which are not published and are in draft state?

phanibabuk — Fri, 22 Jul 2016 08:25:50 GMT

Hi all,
Finally, I was able to resolve the issue.

I figured out the un-published process model using a trial and error basis and re-published it.

Everything started working after that.

Thanks for all the inputs.

RE: How to identify process models which are not published and are in draft state?

Ashvin Kapur — Fri, 22 Jul 2016 05:12:51 GMT

Have you tried temporarily replacing the subprocess nodes (one at a time) with empty script tasks, or simply deleting the subprocess nodes and connecting the rest of the process to determine which subprocess is causing the issue? If you have tried this, what was the result? Were you having similar issues publishing the parent when no subprocesses were being called?

RE: How to identify process models which are not published and are in draft state?

phanibabuk — Thu, 21 Jul 2016 20:13:50 GMT

Hi all,
We are still not able to resolve this issue.
Any pointers please.

RE: How to identify process models which are not published and are in draft state?

bhanuprakashm — Thu, 21 Jul 2016 18:42:46 GMT

Hi phanibabuk,

Finally can you please do one thing ..better to rename your process model and save it again and then configured in your sub process node..

I am also face the same issue.. I was did the same thing then it is working fine..

But it is good not practice. As per my knowledge this is one approach and
let see others points..

Thanks ...

RE: How to identify process models which are not published and are in draft state?

phanibabuk — Thu, 21 Jul 2016 16:26:09 GMT

We did almost all the above steps except creating an empty script task inside the sub-processes.

RE: How to identify process models which are not published and are in draft state?

phanibabuk — Thu, 21 Jul 2016 16:24:46 GMT

Hi all,
No luck so far.
We are still facing this issue.

Any pointers are appreciated.

RE: How to identify process models which are not published and are in draft state?

vishnuv — Thu, 21 Jul 2016 12:04:28 GMT

Let us know on the fix that worked when you were able to run the model successfully.

RE: How to identify process models which are not published and are in draft state?

vishnuv — Thu, 21 Jul 2016 12:02:50 GMT

Trial 1 - If you are starting the process using Start process for debugging, then please retry using opening the model again. Might be a scenario where someone has opened the process model and made some changes.

Trial 2- Can you try to republish the sub-processes again and check.

Trial 3 - Check if the setup of the end node in sub process is configured correctly.

If the issue still exists despite of above trail and error methods then please check the log files for the issue.

RE: How to identify process models which are not published and are in draft state?

abhinavg712 — Thu, 21 Jul 2016 01:24:48 GMT

try checking process model logs
forum.appian.com/.../Logging.html

RE: How to identify process models which are not published and are in draft state?

Ashvin Kapur — Thu, 21 Jul 2016 01:23:55 GMT

Checkout this link: forum.appian.com/.../b-18034

Publishing the subprocess models should be the fix, but if you have given that a shot, try replacing the subprocesses temporarily with blank script tasks to help debug the issue. This should narrow down which subprocess could be causing the issue. In addition, try to re-associate the subprocesses in the "Run this process model" field to ensure that you're not referencing outdated models.

Hope this helps, but let us know if that's still unsuccessful!