In-Memory Execution

v8.2 and later

Define a workflow as In-Memory when you do not want to save the operation's details to the database. You can use this type of "black box" workflow as part of a larger process, such as a sub-workflow that calculates the score of a loan request. The calculation's results might be important to the overall process, but might not be important to track the intermediate steps inside the workflow during execution. 

If you configure your environment with the diagnostics feature, a trace file, SVC file, is created for the workflow's execution.

Set the workflow to In-Memory

Access the workflow in App Studio, in the the Properties panel, set the Persistence property to In-Memory.

In-Memory Limitations

Not all activities are supported in In-Memory workflow. To verify that the activities in a workflow support In-Memory, access the workflow, and from the top ribbon, click Validate. If you set the workflow to In-Memory, a warning message appears for unsupported activities.

Unsupported activities for In-Memory execution

  • Data Activities (all)
  • Human Activities (all)
  • Database Listener Activity
  • SharePoint Listener Activity
  • Sub Workflow Activity
  • Email Listener Activity
  • CRM Listener Activity

Enable Diagnostics

In the web.config file for the environment from where you are running the process, add the following service to the <sequence.engine>  > <services> section.

You can configure the following properties.

  • traceDirectory: directory where the SVC file is created. The default value is the current user's Temp directory.
  • traceLimit: maximum number of trace files. The default value is 1,000.
<add type="PNMsoft.Sequence.Runtime.Diagnostics.WorkflowExecutionDiagnosticsService, PNMsoft.Sequence.Runtime.Diagnostics, Version=8.0.0.0, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" traceDirectory="path to traces directory" traceLimit="#" />
About this Article
  • Created: 04/19/2017 9:07 am EDT
  • Last updated: 05/15/2017 7:16 am EDT
In This Article