Overview
The Self Service Process Unarchive (SSPU) is an Appian plug-in and application that enables users to unarchive a subset of processes from within the Appian environment. This will be useful for most Appian Cloud customers as they do not have direct access to the server backend to either directly search for archived processes or to unarchive processes using a script.
Preconditions:
What the application will NOT do:
== SSPU Application features ==
Key Features and Functionality
== SSPU Plug-in features ==
Hi Andre, thanks for letting me know. Just to rule out the version, can confirm whether the latest version (v1.0.1) of the plugin is currently deployed in your environment? The quickest way to check would be to go to the plugins page in the admin console (/suite/admin/page/plugins).
Hi Richard, we seem to have another error this time, but very similarI've provided the output from the log below.
Cheers, Andre
Hi Stephan,
The plugin has been updated so the process shouldn't fail when parsing your process names anymore.
Hi Richard, will you update the plugin today?
Thanks for confirming. I'm currently aiming to get an update out for this by the end of next week.
Hi Richard,
Yes, that is correct. There is a comma in the process name. When do you think you will have an update available?
Thanks,Stephan
Hi Andre,
Thanks for attaching the stack trace. It appears that the issue is related to parsing the process model ID and I believe its likely because the process name has a comma in it which is causing the code to look at the wrong string to parse.
Can you confirm if one or more process names in your Appian environment have commas in them?
Either way, my plan is to update the code to handle this situation since one of the preconditions for parsing the removed_processes files was that columns would always be consistent given its a csv file but this doesn't appear to be the case anymore.
Thanks for getting back to me.
Here is the snippet that you asked for
Cheers,
Andre
Can you post a snippet of the stack trace related to this error so that I can review it? You should be able to find this in the application server log with the help of the timestamp the error occurred.
This will help me narrow down which specific method in the plugin threw this exception.