Information
  • Author: Appian Corporation
  • Type: Plug-in (Function & Smart Service)
  • Support: This is an Appian supported plug-in. To the extent that this plug-in does not conform to its documentation, please submit a ticket to Appian Technical Support. Appian does not support customer-created customizations or outdated versions of the plug-in.
  • Industry: All Industries
  • Compatible Version(s): 7.1+
  • First Released:
  • Last Updated:
  • Cost: Free - Appian Supported
Share
Home » AppMarket » Process Management Services

Process Management Services

Overview

Contains smart services to allow processes to manage other processes, manage node activity, upgrade process version and update locales.

Example use cases:

  • Orchestrate process removal and archival within your application (e.g. synchronize the deletion/archival of subprocesses and related processes)
  • Bulk delete testing processes that are no longer needed
  • Cancel a process (or many) from another process without using messaging or MNI
  • Set the status of a process to Cancelled for reporting purposes
  • Orchestrate node activity
  • Override or make additions to the security role-map of a list of process instances.

NOTE: The unarchival functionality of this plug-in is incompatible with distributed environments and will not function. Instead, utilize the OOTB unarchival functionality available in Appian 25.2 and later.

Key Features & Functionality

Smart Services included:

  • Find Archive Processes
  • Delete Processes
  • Cancel Processes
  • Pause Processes
  • Resume Processes
  • Archive Processes
  • Unarchive Processes
  • Find Archived Processes
  • Start All Nodes
  • Restart All Nodes
  • Cancel All Nodes
  • Update Security For Processes
  • Upgrade Processes
  • Upgrade Processes From Version
  • Change Model Locale

All the Smart Services must run in a context with Administrator rights and return a result code indicating whether or not the operation was successful.

Anonymous

  • I'm not sure why this is just occurring to me to ask, but is there some reference explaining the difference between "Start Node(s)" and "Restart Node(s)"?  Is one or the other of them ineffective when trying to launch a node when instances are in different states, etc?  They both have the exact same parameters and no particular description, and the plug-in download does not contain any particular documentation.

    My use case is simply that I'm trying to bulk-terminate a bunch of instances at once in my TEST environment (i do NOT want to "cancel" or "delete" them, so the tools available in the /design process monitor are unhelpful to me at the moment) - but it leaves me unsure which of these I should use (or if it makes any particular difference).

  • v2.3.1 Release Notes

    • Updated the regex pattern to find all archived process in a optimised way.
  • in reply to Sneha Yada

    Resolved and "INVALID_STATE" error no longer appears when Dry Run is set to true.

  • in reply to ignacioa0620

    Facing the same issue, are you able to delete the completed process?

  • Hi! We are testing Delete Processes v2 but for Completed process instances it returns "INVALID_STATE". Is this an expected behaviour? Is it possible to delete Completed process instances by using this or any other Smart Service?

  • the Smart service Restart All Nodes v2 is not working, 

    I have passed the node uuid and process instance id in field Node UUIDs and Within Process IDs. and passed Dry Run as true

    is there any reason for that.

    i am getting result code = 4

  • The Smart Service "Find Archived Processes by Date & PM UUID v2" still not working which return nothing. Is there anyway we can have a documentation for this Plug-in? 

    Thanks!

  • Hi All,

    I tried using Start all Nodes and Restart all nodes smart service to start a specific node(which is already completed) in one process model, but these smart services not triggering the node. Any reason

  • The smart service "Find Archived Processes by Date & PM UUID v2" isn't working. It is always returning empty result for the given process UUID with correct archive date.

    Any idea when will it get fixed?

  • in reply to Mike Schmitt

    For future reference: in this case, "INVALID_STATE" originated from trying to update the version of a completed process instance.  Once I restarted it (for example, restarting an arbitrary task within the completed instance), the version update worked fine for that instance. 

    I sorta wish we didn't have to do that, though, because in this case I need to update some completed instances then restart them on an added path.

© 2026 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.