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
  • Hi are there any documentation available around this plugin, particularly around Upgrade Processes? i am trying to upgrade processes to a particular version but I keep getting an error 

    "An error occurred while trying to retrieve the process model [id=7,682] Details: Does not exist: Version"

    I have made sure I am providing the correct process model ID. Does anyone have any inputs?

  • v2.3.0 Release Notes
    • Removed use of deprecated APIs. Due to this, REMOVED the following service: Change Process Locale
    • Furthermore, Change Model Locale v2 has been REMOVED. Any occurrence of Change Model Locale in you process models must be manually changed to use v3, which can no longer change the locale of existing process instances.
    • If you use the functionality to change the locales of existing process instances, which should be exceedingly rare, do not upgrade your plug-in.
  • Hi Alvaro,

    I am trying to unarchive the process (have process id available) by using the smart service Unarchive processes V2 in the process model ,because we have appiancloud .Could you please help us in configuring the value. 

    1.Node input value : process ids ( I have entered the process id to be unarchived)

    2.At Node output , what should be configured in the Result Codes(number(integer)).

    I have referred the community documentation , but could not unarchive  even after referring those documentation.Any help in this regard is much appreciated .

    Thanks,

    Priyanka

  • Hi, 

    I used Change Model Locale 

  • Hi ,

    How did you configure to set language? I got confused with Change Model Locale and Change Process Locale, not sure what is the difference between those two

  • Hello, I'm using the plugin on an Appian 19.4 server. The "Find Archived Processes by date" node does not find any results no matter what UUID or date i set. Is there any issue with the version or am i missing something? The unarchive node works as expected as well as the archive nodes.

  • Thyous April, that has worked

  • Hi , have you tried Change Model Locale or Change Process Locale?

  • Hi, recently installed IDP and all the process models have their language set to en US. As a UK site, this means all model names are appearing as ???. KB1193 recommends using this plug in to reset the model names, but there does not seem to be a smart service for this

  • Hi, we are using this plug-in to restart specific nodes, by using smart-service "Restart all nodes v2" when they are failed to be able to resume a large amount of instances in one go.
    When we are passing a pv! variable in the node input parameter "Within Process IDs"  which is empty (null) this smart-service will start triggering instances in what looks like a random order, inlcuding instances which are already completed instead of paused. Is this expected behaviour or a bug for not handling the scenario of null input?