Configuration Parameter 🆕
Flows for APEX Configuration Parameter Options
Configuration parameters can be changed from the Flows for APEX application.
Configuring Event Logging
Event logging is currently designed to be configurable, so that an installation can capture more or less event data depending upon business ad security needs.
Logging is configured using Flows for APEX configuration parameters, which are stored in the FLOW_CONFIGURATION table.
|logging_level||off||logging is disabled|
|standard||logs instance and step events||yes|
|secure||logs model, instance and step events|
|full||logs model, instance, step and process variable events|
|logging_hide_userid||true||does not capture user information about the step|
|false||captures userid of the process step as known to the Flow Engine||yes|
|logging_language||en||error messages generated in the Flows for APEX engine will be placed in the Instance Event Log in this language. If the message is not available in the required language, it will appear in English (en)||yes|
|fr||event log messages in French (fr)|
Configuring Diagram Versioning
|engine_app_mode||production||versioning controls are strictly enforced.
|development||versioning controls are not strictly enforced. diagrams in
General System Configuration
|duplicate_step_prevention||strict||requires step keys to be provided on all step operations, thus preventing multiple users from attempting to make the same step transition but instead moving the process forward multiple steps||yes (new installations)|
|legacy||allows null step keys. Incorrect step keys will still cause an error. Only use this until you migrate your v21 and earlier apps to use Step Keys||only for migrated systems|
|version_initial_installed||records the version first installed (do not change)|
|version_now_installed||records the current version installed, after any migrations have occured|
|default_workspace||should be set to your default APEX workspace used for Flows for APEX. This is used as a last-resort for scriptTasks and serviceTasks when creating an APEX session or looking for mail templates|
|default_email_sender||should be set to your default email sender, in case outbound mail serviceTasks do not have a sender defined|
Default APEX Session Configuration for Asynchronous Calls
These parameters are used to create an APEX session for non-APEX originated calls to Flows for APEX. An APEX session is required for correct operation of ceratin features, incuding:
- correct operation of Variable Expressions of type PL/SQL Expression and PL/SQL Function Body
- generation of debug files
- Gateway Routing Expressions
Default parameters are used if session configuration has not been provided in either process variables (on a timer), or in the Process Diagram. The values provided in the system configuraton will be used if no other sets of session config data is found. Administrators of high security systems may want to leave these configuration parameters unset, so that specific values have to be provided at call or diagram level. Any calls made without call level or diagram level parameters will then raise an error – which might be what you want rather than relying on system-level dafault parameters.
|applicationID||the application ID of one of your APEX apps||none|
|pageID||the page ID of one of your apps that will be provided to create a session||none|
|username||the username to be user on the APEX session to create a session if no other username is provided||none|