<?xml version="1.0" ?>
<!-- Exception types can be configured to define certain actions which will take place in the event of a process or task exception -eg  the roles of the users who will be notified of the exception and the content of the note that will be attached to the process or task with which the exception is associated. The exception types defined below will be registered at application server start-up. Additional exception types may be added to this file.   -->

<!-- The root element (required). -->
<!-- <exception-types> -->
  
  <!-- The exception type that will be registered. The "local-id"
       attribute is required and must be unique among all exception types. -->
  <!-- <exception-type local-id=""> -->

    <!-- The type of object with which this exception is associated.
         Possible values:
            21 = Task (TypedVariable.TASK)
            22 = Process (TypedVariable.PROCESS)
         (Required) -->
    <!-- <associated-object-type></associated-object-type> -->
    
    <!-- The content of the note that will be attached to the associated object. The 
         note should contain a description of the exception, and the steps that need 
         to be taken to resolve it.
         (Required) -->
    <!-- <note-content><![CDATA[This is a note]]></note-content> -->
    
    <!-- Should the process initiator be notified in case of an exception? 
            0 (or false) = No
            1 (or true) = Yes
         Optional. Defaults to "true". -->
    <!-- <notify-process-initiator>[1/0]</notify-process-initiator> -->
    <!-- Should the process administrators be notified in case of an exception? 
            0 (or false) = No
            1 (or true) = Yes
         Optional. Defaults to "true". -->
    <!-- <notify-process-administrators>[1/0]</notify-process-administrators> -->
    <!-- Should the system administrators be notified in case of an exception? 
            0 (or false) = No
            1 (or true) = Yes
         Optional. Defaults to "true". 
         NOTE: This is currently interpreted as the administrator of the Process
         server, rather than the system administrator(s).  -->
    <!-- <notify-system-administrators>[1/0]</notify-system-administrators> -->
    <!-- Should the task acceptor be notified in case of an exception? 
            0 (or false) = No
            1 (or true) = Yes
         Optional. Defaults to "true". -->
    <!-- <notify-task-acceptor>[1/0]</notify-task-acceptor> -->

  <!-- </exception-type> -->
<!-- </exception-types> -->


<exception-types>  
  
  <!-- Task exception types. -->
  <exception-type local-id="runtimeMismatch">
    <!-- This exception is used solely to pause the task by exception, the alert will be sent separately. -->
    <associated-object-type>21</associated-object-type>
    <exception-description>The value provided in the configuration does not match the expected type.</exception-description>
    <recommended-action>Provide values that match the expected type. </recommended-action>
    <note-content>The value provided in the configuration does not match the expected type. The alert will contain more specific information regarding this error.</note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>false</notify-process-administrators>
    <notify-system-administrators>false</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="ip">
    <associated-object-type>21</associated-object-type>
    <exception-description>Activity Class parameters are invalid.</exception-description>
    <recommended-action>Correct the Activity Class parameters and then resume.</recommended-action>
    <note-content><![CDATA[Invalid AC Parameters: Activity Class parameters are invalid.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="he">
    <associated-object-type>21</associated-object-type>
    <exception-description>Server Error has occurred.</exception-description>
    <recommended-action>Correct error indicated in description and resume.</recommended-action>
    <note-content><![CDATA[Handle Error.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="eju">
    <associated-object-type>21</associated-object-type>
    <exception-description>The amount of time allocated for the completion of an unattended activity was insufficient to allow the activity to complete.</exception-description>
    <recommended-action>Contact the System Administrator to increase the allocated time and resume or cancel the task.</recommended-action>
    <note-content><![CDATA[Unattended Java Activity Timed Out: The amount of time allocated for the completion of an unattended activity was insufficient to allow the activity to complete.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="ace">
    <associated-object-type>21</associated-object-type>
    <exception-description>An error occurred in executing an Activity Class.</exception-description>
    <recommended-action>Examine the activity class to correct the error and then resume.</recommended-action>
    <note-content><![CDATA[Activity Class Exception: An error occurred in executing an activity class.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="lsubd">
    <associated-object-type>21</associated-object-type>
    <exception-description>The task tries to invoke a sub-process that would exceed depth limit.</exception-description>
    <recommended-action>The sub-process process was not instantiated. Please examine any process variable mapping and start the next node if necessary.</recommended-action>
    <note-content><![CDATA[The task tries to invoke a sub-process that would exceed depth limit.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="load">
    <associated-object-type>21</associated-object-type>
    <exception-description>The execution engine has reached maximum load.</exception-description>
    <recommended-action>The sub-process or link-process was not started. Processes must be archived to free up space before continuing.</recommended-action>
    <note-content><![CDATA[The execution engine has reached maximum load.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="spcanc">
    <associated-object-type>21</associated-object-type>
    <exception-description>The sub-process started by this activity has been cancelled.</exception-description>
    <recommended-action>This node cannot complete. Please start the next node if necessary.</recommended-action>
    <note-content><![CDATA[The sub-process started by this activity has been cancelled.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="spdel">
    <associated-object-type>21</associated-object-type>
    <exception-description>The sub-process started by this activity has been deleted.</exception-description>
    <recommended-action>This node cannot complete. Please start the next node if necessary.</recommended-action>
    <note-content><![CDATA[The sub-process started by this activity has been deleted.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="spsec">
    <associated-object-type>21</associated-object-type>
    <exception-description>The user does not have privilege to the process that the activity attempted to start.</exception-description>
    <recommended-action>The process is not started, and this node cannot complete. Please start the next node if necessary or if you believe the permissions are incorrect, please try logging out and logging back in.</recommended-action>
    <note-content><![CDATA[The user does not have privilege to the process that the activity attempted to start.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="datacap_arv">
    <associated-object-type>21</associated-object-type>
    <exception-description>This activity contains activity return variables in excess of defined limits.</exception-description>
    <recommended-action>The task was not completed. Please reconfigure the node.</recommended-action>
    <note-content><![CDATA[contains activity return variables in excess of defined limits.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="datacap_acp">
    <associated-object-type>21</associated-object-type>
    <exception-description>This activity contains activity class parameters in excess of defined limits or activity class data exceeded the defined limits.</exception-description>
    <recommended-action>The task was not completed. Please reconfigure the node.</recommended-action>
    <note-content><![CDATA[This activity contains activity class parameters in excess of defined limits or activity class data exceeded the defined limits.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="subproc_param_missing">
    <associated-object-type>21</associated-object-type>
    <exception-description>The sub-process could not be started because the input mapping was missing required process parameters.</exception-description>
    <recommended-action>Add the missing process parameters to the input mapping and start a new instance of the sub-process node.</recommended-action>
    <note-content><![CDATA[The sub-process could not be started because the input mapping was missing required process parameters.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="subproc_param_invalid">
    <associated-object-type>21</associated-object-type>
    <exception-description>The sub-process could not be started because the input mapping contained process parameters with incorrect types.</exception-description>
    <recommended-action>Modify the input mapping and start a new instance of the sub-process node.</recommended-action>
    <note-content><![CDATA[The sub-process could not be started because the input mapping contained process parameters with incorrect types.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="subproc_param_null_or_empty">
    <associated-object-type>21</associated-object-type>
    <exception-description>The sub-process could not be started because the required process parameters were null or empty.</exception-description>
    <recommended-action>Provide the values to the required parameters and start a new instance of the sub-process node.</recommended-action>
    <note-content><![CDATA[The sub-process could not be started because the required process parameters were null or empty]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>

  <!-- Process exception types. -->
  <exception-type local-id="nsn">
    <associated-object-type>22</associated-object-type>
    <exception-description>An attempt was made to start a process without a Start Node.</exception-description>
    <recommended-action>In the process modeler, create a Start Node for the process.</recommended-action>
    <note-content><![CDATA[No Start Node: An attempt was made to start a process without a Start Node.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="ix">
    <associated-object-type>22</associated-object-type>
    <exception-description>A timeout error occurred in the evaluation of a function within an expression.</exception-description>
    <recommended-action>Check the function's requirements and resume.</recommended-action>
    <note-content><![CDATA[Invalid Expression: A timeout error occurred in the evaluation of a function within an expression.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="invx">
    <associated-object-type>22</associated-object-type>
    <exception-description>An invalid expression has been encountered.</exception-description>
    <recommended-action>Check the expression including any function requirements and resume.</recommended-action>
    <note-content><![CDATA[Check the expression including any function requirements and resume.  The alert will contain more specific information regarding this error.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="datacap_expression">
    <associated-object-type>22</associated-object-type>
    <exception-description>This activity contained an expression that generated data in excess of defined limits.</exception-description>
    <recommended-action>The task was not completed. Please reconfigure the node.</recommended-action>
    <note-content><![CDATA[This activity contained an expression that generated data in excess of defined limits.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="lspwn">
    <associated-object-type>22</associated-object-type>
    <exception-description>A node tries to spawn too many instances at once.</exception-description>
    <recommended-action>The node has spawned to the maximum number allowed. Please examine any problems that may occur due to this limit and resume the process.</recommended-action>
    <note-content><![CDATA[The node tries to spawn too many instances.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="lnins">
    <associated-object-type>22</associated-object-type>
    <exception-description>The number of tasks of a process model node exceeds the limit.</exception-description>
    <recommended-action>A new node was not started. Examine any problem that may occur due to this limit. Then, resume the process and start the next node if necessary.</recommended-action>
    <note-content><![CDATA[The number of tasks of the process model node exceeds the limit.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="lnts">
    <associated-object-type>22</associated-object-type>
    <exception-description>A process model node has exceeded the node traversal limit.</exception-description>
    <recommended-action>The next node in this process model's flow will not be started. Examine any problem that may occur due to this limit (e.g. never-ending logic loops, etc.) and refactor this process model to avoid the node traversal limit.</recommended-action>
    <note-content><![CDATA[A process model node has exceeded the node traversal limit.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="incrup">
    <associated-object-type>22</associated-object-type>
    <exception-description>Process Analytics Incremental Update Problem.</exception-description>
    <recommended-action>This problem requires further diagnostics, as available from the database diagnostic scripts.  No user action is necessary.</recommended-action>
    <note-content><![CDATA[Process Analytics Incremental Update Problem: No further analytics will be available on this process.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="inactive">
    <associated-object-type>22</associated-object-type>
    <exception-description>This process has been inactive for a time period exceeding defined limits.</exception-description>
    <recommended-action>Resume the process and take action to complete the process.</recommended-action>
    <note-content><![CDATA[This process has been inactive for a time period exceeding defined limits.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="spawn_too_few">
    <associated-object-type>22</associated-object-type>
    <exception-description>A node configured to run multiple instances cannot be started because the requested number of instances is 0. The number of instances must be greater or equal to 1.</exception-description>
    <recommended-action>Check the node's configuration for multiple instances (MNI), ensure that the number of instances to spawn is greater or equal to 1, resume the process, and start the node.</recommended-action>
    <note-content><![CDATA[A node configured to run multiple instances cannot be started because the requested number of instances is 0. The number of instances must be greater or equal to 1.  Check the node's configuration for multiple instances (MNI), ensure that the number of instances to spawn is greater or equal to 1, resume the process, and start the node.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="invxt">
    <associated-object-type>21</associated-object-type>
    <exception-description>An invalid expression has been encountered in a task.</exception-description>
    <recommended-action>Check the expression including any function requirements and resume.</recommended-action>
    <note-content><![CDATA[Check the expression including any function requirements and resume.  The alert will contain more specific information regarding this error.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
  <exception-type local-id="abortua">
    <associated-object-type>21</associated-object-type>
    <exception-description>An unattended task has failed.</exception-description>
    <recommended-action>Check the requirements of the task, stop the task, and restart it where applicable.</recommended-action>
    <note-content><![CDATA[Check the requirements of the task, stop the task, and restart it where applicable.  The alert will have more specific information regarding this error.]]></note-content>
    <notify-process-initiator>false</notify-process-initiator>
    <notify-process-administrators>true</notify-process-administrators>
    <notify-system-administrators>true</notify-system-administrators>
    <notify-task-acceptor>false</notify-task-acceptor>
  </exception-type>
</exception-types>
