Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using Connectors
  9. System Services, Listeners and Connectors

2. Design

2. Design

Advanced Properties

Advanced Properties

You can configure advanced properties to define fault handling, tracing, and Cross-Origin Resource Sharing (CORS) support for a process.
You can configure the following advanced properties:

Suspend on Fault

By default, Process Server terminates a process when an uncaught fault occurs. You can configure Process Designer to suspend individual processes on uncaught faults.
If you select the
Suspend on Fault
option, Process Server suspends the process when an uncaught fault occurs. If you do not select the
Suspend on Fault
option, Process Server terminates the process if a fault occurs and the process does not explicitly handle the fault.
If the process is in the suspended state, review and identify error conditions. Then, you can then retry or complete the activity. For example, you can catch error conditions during employee or customer onboarding. After you resolve all the errors, the process moves out of the suspended state and continues from the faulted step.
If you select the
Suspend on Fault
option, Process Designer uses full persistence.
These process-specific properties work in conjunction with other exception management settings that you specify in the
Application Integration Console
.
For more information about managing and correcting faults, see
Monitor
.

Tracing Level

You can configure one of the following tracing levels to determine the type of run-time logging for a process:
  • None
  • Terse
  • Normal
  • Verbose
The tracing level that you configure in Process Designer maps to the persistence level and logging level in Process Developer as listed in the following table:
Tracing Level
Persistence Level
Logging Level
None
Brief
None
Terse
Brief
Fault
Normal
Brief
Execution with Service Data
Verbose
Final
Execution with Data
Persistence Level
Regardless of the tracing level that you configure, Process Server uses full persistence in the following situations:
  • When you select the
    Suspend on Uncaught Fault
    option
  • When a process includes a timer such as a Wait step, a message event, or a receive event
  • When one process invokes another process to provide subprocess coordination.
For more information about different persistence levels, see
Monitor
.
Logging Level
The Process Server logging level might be lower than the logging level that you set for an individual process. Regardless of the logging level that you set at the process level, the logging will not exceed the maximum process logging level specified for Process Server. For example, the
Max Process Logging Level
field might be set to
Execution with Service Data
. In this case, even if you select the tracing level as
Verbose
, Process Server applies the
Execution with Service Data
logging level for the process.
For more information about different logging levels, see the
Administrator
online help.

Enable CORS

By default, API consumers can invoke a process from the domain that is part of the service URL. API consumers can use the GET, POST, PATCH, PUT, and DELETE verbs to invoke a process.
Select the
Enable CORS
option to enable Cross-Origin Resource Sharing (CORS) support for a process. You can also specify the allowed domains and allowed verbs for CORS support.
In the
For Domains
field, specify additional allowed domains from which API consumers can invoke the process. Enter the wildcard character (
*
) to enable CORS for all domains. Enter a comma-separated list of domains to enable CORS for specific domains. For example, enter the following phrase to enable CORS for the abc.domain.com and xyz.domain.com domains:
abc.domain.com,xyz.domain.com
If you enable CORS but leave the
For Domains
field blank, you can invoke the process only from the domain that is part of the service URL.
In the
For Verbs
field, specify the allowed verbs that API consumers can use to invoke a process from the domains that you specified in the
For Domains
field. Enter a comma-separated list of verbs to enable CORS for specific verbs. For example, enter the following phrase to enable CORS for the POST, PUT, and GET verbs:
POST,PUT,GET
Default is all verbs.
API consumers can invoke the process with all verbs from the domain that is part of the service URL.