Interfacing Technologies Corporation

10.9 Advanced

Advanced settings empower organizations to tailor their EPC to their specific needs, allowing for enhanced functionality and customization. Within this topic, we’ll explore how to access these settings, as well as extensive details on each available setting enabling you to fine-tune your experience with EPC. Get started by selecting a section below or searching for a specific setting.

How to Access & Edit Advanced Settings

  1. Ensure you have EPC System Administrator access.
  2. Go to the ‘System Admin’ section within the ellipsis menu on the right side of the navigation bar.
  3. Click the ‘Advanced’ tab to access advanced settings.
  4. Scroll to the desired setting
  5. Click on the setting’s corresponding ‘pen’ icon () to edit it.

Settings

AI_FEATURES_IN_UI
Choose the AI functionalities displayed in your EPC system:
If the field is left empty, no AI features will be displayed in the UI, regardless of whether a ChatGPT key is entered.

Input ‘generate‘ in the field to exclusively display generation options (e.g.: object and text generation)

Input ‘improve‘ to exclusively show improvement options (e.g.: process diagram and text improvement)

Input ‘generate, improve‘ to display both functionalities.



Default: empty.
AI_IMS_ENABLED
Controls whether AI features are enabled globally across the new IMS suite. This setting acts as a master switch for all AI functionality, allowing administrators to turn AI on or off for the entire tenant.
  • Required Format: true or false
    • true → AI is enabled globally. Feature-level settings determine which AI capabilities are available.
    • false → AI is completely disabled across IMS, regardless of feature-level configuration.

  • Default: true
API_KEY
Enables API key usage for integrations with the system by setting a random UUID.

Default: empty.
APPS_URL
Specifies the URL for external apps added to the Module Explorer. For more instructions on how to link external apps, see here.

Default: empty.
BOOK_FORCE_PDF
Forces object books or SOPs to generate as PDFs automatically, ensuring consistent output for sharing or printing.

Required format: ‘true’ or ‘false’

Default: false (disabled)
BOOK_HTML_STYLES
Customize the appearance of generated object books by inputting the desired HTML code in this field. Organizations can adjust various text attributes such as:
  • Font
  • Color
  • Size
  • Line height
  • List styles
  • And more!

Here is an example of the code and the results:

<style> p { font-family: Verdana, sans-serif; font-size: 16px; line-height: 1.6; color: #0033A0; } h1, h2, h3, h4, h5, h6 { font-family: Georgia, serif; color: #FFA500; } ul { font-family: Verdana, sans-serif; font-size: 16px; color: #004D40; list-style-type: square; margin-left: 20px; } </style>


CHATBOT_COLORS
Customize the appearance of the AI Chat Assistant button by selecting any two colors to create a gradient background.

To do this, enter the desired primary and secondary hex color codes using the following format: {"primary":"#HEXCODE,"secondary":"#HEXCODE"}

For example, the colors shown in the video below are represented by the following code: {"primary":"#65b3f2","secondary":"#04a91d"}


CHATBOT_SOURCE_COUNT
Number of sources that the AI Chat Assistant retrieves and analyzes per query to return results.

Required format: number.
Default: 2
CHECK_NOTIFICATION_INTERVAL
Sets the time interval for EPC to check changes that trigger user notifications.
  • Denomination: Milliseconds.
  • Default: 60000
CHECK_SERVER_AVAILABILITY_IN_BROWSER
Enables or disables server availability notifications in the browser.

Required format: Set to `true` to enable, or `false` to disable

Default: false (disabled)
COGNOS_URL
Specifies your Cognos server URL required for Process Validation and Translation features.

Required Format: https://YOURCOGNOS.com/reporting/bi/ (ensure trailing slash after `bi/`)
CONFIRMATION_DUE_DATE_DELAY
This setting allows to set a default deadline for confirmation tasks. When a new confirmation is created, the system automatically calculates when it should be completed. This improves audit tracking and task accountability.

Required Format: Days
Default: 0 (no deadline if left empty or set to 0)

CONVERT_WORD_TO_PDF_IN_PUBLISHED
Automatically converts Word files viewed in Published mode to PDFs.
  • Required Format: Set to `true` to enable, or `false` to disable.
  • Default: true (enabled)
DBP_TASK_LIST_URL
Specifies the URL of your Digital Business Platform (DBP) task list, required to integrate training assignments in EPC. Adding this URL also creates a new ‘DBP’ tab in the To Do module, allowing users to access DBP directly within EPC.


DEFAULT_EMPTY_LANES_CREATE
Defines the number of empty lanes created automatically when a new process is created.

Required Format: 0 to 9

Default: 1
DELAY_REQUIRED_CUSTOM_ATTRIBUTES
Allows users to create or update objects without being blocked by incomplete mandatory UDAs, while ensuring that all required fields are completed before approval or publishing.

  • Required format: ‘true’ or ‘false’
    • ‘true’ → Object creation is blocked until mandatory UDAs are filled
    • ‘false’ → Objects can be created even if UDAs are incomplete
  • Default: true (disabled, object creation is blocked)
DESCRIPTION_DEFAULT_DOCUMENT
Default description that will be applied when creating documents, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures.

Required format: HTML
  • Here are some formatting options that can be added:
    • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
    • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
    • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.
Example:
<h2>Document Overview</h2> <p>This document provides details on <strong>[subject matter]</strong> and serves as a reference for <em>[audience or department]</em> to support <strong>[business function or compliance requirement]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Purpose:</strong> This document is intended to <em>[explain, guide, or formalize]</em> <strong>[specific topic]</strong>.</li> <li><strong>Intended Audience:</strong> The primary users of this document are <em>[departments, teams, or roles]</em>.</li> <li><strong>Applicability:</strong> This document is relevant to <em>[specific processes, regulations, or business areas]</em>.</li> <li><strong>Usage Guidelines:</strong> It should be used for <strong>[specific scenarios, decision-making, training, compliance, etc.]</strong>.</li> </ul>


DESCRIPTION_DEFAULT_FLOW_OBJECT
Default description that will be applied when creating flow objects, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>Flow Object Overview</h2> <p>This flow object represents a <strong>[specific type of flow object: Start Event, End Event, Task, Gateway, etc.]</strong> within <em>[business process or system]</em>, ensuring smooth execution and transition of activities.</p> <h3>Key Details</h3> <ul> <li><strong>Function:</strong> It serves to <em>[trigger, process, route, or complete]</em> <strong>[specific action or decision]</strong>.</li> <li><strong>Execution Mode:</strong> This object operates in <strong>[manual, automated, or semi-automated]</strong> mode.</li> <li><strong>Rules & Conditions:</strong> If applicable, it follows <strong>[specific business rules or conditions]</strong>.</li> <li><strong>Dependencies:</strong> This object relies on <em>[systems, approvals, or data sources]</em> for execution.</li> </ul>

Which will result in this default description:

DESCRIPTION_DEFAULT_KCI
Default description that will be applied when creating KCIs, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>KCI Overview</h2> <p>This KCI evaluates <strong>[specific control mechanism]</strong> in <em>[business area]</em>, ensuring adherence to <strong>[compliance or operational standards]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Purpose:</strong> This KCI validates the effectiveness of <em>[specific control]</em> in managing <strong>[risk or compliance requirement]</strong>.</li> <li><strong>Threshold:</strong> The acceptable control performance level is <strong>[target value]</strong>.</li> <li><strong>Review Frequency:</strong> It is reviewed on a <em>[timeframe]</em> basis.</li> <li><strong>Data Source:</strong> Information is derived from <strong>[audit logs, compliance reports, or systems]</strong>.</li> <li><strong>Accountable Party:</strong> <em>[department or individual]</em> ensures ongoing compliance.</li> </ul>

Which will result in this default description:

DESCRIPTION_DEFAULT_KPI
Default description that will be applied when creating KPIs, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>KPI Overview</h2> <p>This KPI measures <strong>[specific performance metric]</strong> within <em>[business area or function]</em>, ensuring alignment with <strong>[organizational goal or strategy]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Purpose:</strong> This KPI tracks <em>[key business performance aspect]</em> to support <strong>[strategic initiative]</strong>.</li> <li><strong>Target Value:</strong> The desired benchmark is <strong>[specific value or range]</strong>.</li> <li><strong>Measurement Frequency:</strong> This KPI is monitored on a <em>[daily/weekly/monthly/quarterly]</em> basis.</li> <li><strong>Data Source:</strong> Information is collected from <strong>[system or report]</strong>.</li> <li><strong>Responsible Team:</strong> <em>[team or department]</em> is accountable for tracking and improvement.</li> </ul>

Which will result in this default description:

DESCRIPTION_DEFAULT_KRI
Default description that will be applied when creating KRIs, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>KRI Overview</h2> <p>This KRI identifies potential risks related to <strong>[specific risk category]</strong> within <em>[business function or process]</em>, helping to mitigate <strong>[potential impact]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Purpose:</strong> This KRI serves to detect early signs of <em>[specific risk event]</em>.</li> <li><strong>Threshold:</strong> The risk tolerance level is set at <strong>[acceptable risk range]</strong>.</li> <li><strong>Monitoring Frequency:</strong> It is assessed on a <em>[periodic schedule]</em>.</li> <li><strong>Data Source:</strong> The risk insights come from <strong>[specific reports, audits, or tools]</strong>.</li> <li><strong>Responsible Entity:</strong> <em>[team or individual]</em> ensures risk mitigation actions.</li> </ul>

Which will result in this default description:


DESCRIPTION_DEFAULT_OBJECTIVE
Default description that will be applied when creating objectives, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>Object Overview</h2> <p>This object focuses on <strong>[specific objective or goal]</strong>, addressing <em>[particular process or business area]</em>. It tracks progress or compliance by monitoring <strong>[relevant metrics or data points]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Purpose:</strong> This object is designed to achieve <em>[specific goal or initiative]</em> within the organization.</li> <li><strong>Target:</strong> The target outcome for this object is <strong>[desired result or benchmark]</strong>.</li> <li><strong>Monitoring Frequency:</strong> This object is reviewed on a <em>[frequency of measurement]</em> basis.</li> <li><strong>Data Source:</strong> The data for this object is sourced from <strong>[data source]</strong>.</li> <li><strong>Accountable Team:</strong> [responsible person or team] is responsible for ensuring its performance.</li>

Which will result in this default description:


DESCRIPTION_DEFAULT_PROCESS
Default description that will be applied when creating a process, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>Process Overview</h2> <p>This process outlines <strong>[specific workflow or procedure]</strong> within <em>[business function]</em>, ensuring efficiency and alignment with <strong>[organizational standards]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Purpose:</strong> The process is designed to <em>[achieve specific outcome]</em>.</li> <li><strong>Steps:</strong> The main stages include <strong>[step 1, step 2, step 3]</strong>.</li> <li><strong>Inputs:</strong> Required resources or data include <strong>[necessary elements]</strong>.</li> <li><strong>Outputs:</strong> Expected results or deliverables are <strong>[output description]</strong>.</li> <li><strong>Responsible Party:</strong> The <em>[department or team]</em> is accountable for execution.</li> </ul>

Which will result in this default description:


DESCRIPTION_DEFAULT_RULE
Default description that will be applied when creating rules, which is particularly useful for standardizing information and formatting across the same object type that requires consistent introductions or structures. It is possible to include formatting. Here are some examples:
  • Headings: Use <h1>, <h2>, or <h3> tags to organize the content.
  • Bullet Points: Use <ul> and <li> tags for listing key details or instructions.
  • Bold/Italics: For emphasis, you can use <strong> for bold and <em> for italics.

Below is an example of a default description for an object using HTML formatting:
<h2>Regulation Overview</h2> <p>This regulation establishes <strong>[specific compliance requirement]</strong> in accordance with <em>[industry or government standard]</em>, ensuring adherence to <strong>[legal or business mandate]</strong>.</p> <h3>Key Details</h3> <ul> <li><strong>Scope:</strong> This regulation applies to <em>[business area or jurisdiction]</em>.</li> <li><strong>Compliance Requirements:</strong> Organizations must <strong>[mandatory actions or restrictions]</strong>.</li> <li><strong>Enforcement:</strong> Compliance is monitored through <em>[audits, reports, or inspections]</em>.</li> <li><strong>Effective Date:</strong> This regulation takes effect on <strong>[date]</strong>.</li> <li><strong>Governing Body:</strong> The regulation is enforced by <em>[authority or regulatory agency]</em>.</li> </ul>

Which will result in this default description:

DETAILS_PAGE_DEFAULT_EXPAND_ALL_SECTIONS
Controls whether all Details sections are expanded by default (excluding Versioning and Impact). Designed to reduce clicks and streamline navigation for users reviewing large amounts of information.

Required format: ‘true’ or ‘false’
  • true → Automatically expand all applicable Details sections.
  • false → Sections remain collapsed unless opened by the user.

Default: false (sections collapsed)

DETAILS_PAGE_DEFAULT_TABLE_OF_CONTENTS_PANEL_OPEN
Determines whether the Table of Contents (TOC) panel opens automatically when loading the Details page, enabling quicker access to page structure and navigation.

Required format: ‘true’ or ‘false’
  • true → TOC panel is expanded by default.
  • false → TOC panel remains closed until the user opens it.

Default: false (panel closed)

DETAILS_PAGE_ID_VISIBILITY
Controls which identity-related fields (UID, Identifier, SSN) are visible on the Details page. Helps organizations meet compliance and privacy requirements by limiting which identifiers appear in the UI.

Required format: Comma-separated list using any of the following values: UID, Identifier, SSN
  • Example → “UID, Identifier”
  • To hide all fields → (empty value)

Behavior: Fields removed from the configuration are hidden dynamically in the UI but remain accessible via backend/API.
Default: UID, Identifier, SSN (all fields visible)
DEV_CONFIG
For Interfacing internal use only.
DISABLE_NOTIFICATION_MINOR_VERSION
Controls whether users are notified when minor versions of objects are published. Useful for organizations that publish frequent minor updates and want to reduce notification noise, or conversely, for teams that need to be aware of all changes.

Required format: ‘true’ or ‘false’
  • ‘true’ → Disable notifications
  • ‘false’ → Enable notifications

Default: true (disabled)
DISABLE_RELATIONSHIPS_FILTERING
Determines whether relationships that the user cannot access are hidden. Users attempting to follow non-readable relationships will encounter errors.

Required Format: true or false.
  • true → Return all relationships, including non-readable ones.
  • false → Filter out relationships the user cannot access.

Default: false (filtering enabled)
DISPLAY_DOCUMENTS_IN_TREE
Controls whether documents appear in the hierarchy tree with sets and folders.

Required format: ‘true’ or ‘false’
  • true → Display documents in the tree.
  • false → Documents are not displayed in the tree.

Default: true (documents displayed)


DISPLAY_RULES_IN_TREE
Determines if rules are visible in the hierarchy tree.

Required format:
  • true → Display rules in the tree.
  • false → Rules are not displayed in the tree.

Default: true (rules displayed)


DISPLAY_TASKS_IN_TREE
Controls whether tasks appear in the hierarchy tree under processes and sub-processes.

Required Format: true or false.
  • true → Display tasks in the tree.
  • false → Tasks are not displayed in the tree.

Default: true (tasks displayed)


DOCUMENT_CONTROLLED_COPIES
Enables download and print authorizations to control document distribution. Useful for organizations that require an highly regulated environment.
Required format: true or false
  • true → Enforce the download and print authorizations
  • false → Any user can download or print documents

Default: false (authorizations disabled)


When this setting is enabled, the Share Preview option is unavailable from More Options:


Disabled:

Enabled:

DOCUMENT_INJECT_COVER_PAGE
Automatically adds the template’s cover page (defined in the DOCUMENT_INJECT_HEADERS_FOOTERS setting) to the beginning of new EPC documents. For more details, click here.

Required Format: true or false.
  • true → Adds the selected template cover page to documents automatically.
  • false → Does not add a cover page.

Default: false (disabled)
DOCUMENT_INJECT_CUSTOM_PROPERTIES
Injects dynamic metadata (e.g., name, version, status, etc.) in .docx documents that will automatically update each time a document is created or saved after making changes. For more details, click here.

Required Format: true or false.
  • true → Enables automatic injection of metadata.
  • false → Disables the feature.

Default: false
DOCUMENT_INJECT_HEADERS_FOOTERS
Specifies which EPC document will be used as the template for automatically adding headers, footers, and a cover page to new documents. For more details, click here.

How to configure: Copy and paste the UID of the desired template document into this setting.
Required Format: UID value, e.g., 59E401AE-BC80-4DEF-84FF-6FE7260A5B1B
Default: empty
DOCUMENT_INJECT_QR_CODE
Controls whether an SSN-based QR code is automatically added to PDF documents during download, preview, or printing. The QR code enables quick identification and improves traceability for compliance and audit purposes. For more details, click here.

Required format: true or false
  • true → A QR code is embedded in the bottom-right corner of the first page of PDFs
  • false → No QR code is added

Default: false
Notes: Original files stored in the system are not modified
DOCUMENT_INJECT_WATERMARK_DRAFT
Controls whether a visible status watermark is added to draft PDF or Word documents when they are downloaded, previewed or printed. The watermark helps users immediately recognize that the document is still a draft and not finalized. For more details, click here.

Required format: true or false
  • true → A “Draft” watermark is applied to draft documents
  • false → No watermark is applied to draft documents

Default: false
Notes: Original files stored in the system are not modified
DOCUMENT_WATERMARK_PUBLISHED
Controls whether a visible status watermark is added to published PDF or Word documents when they are downloaded, previewed or printed. This helps users identify uncontrolled copies of finalized documents. For more details, click here.

Required format: true or false
  • true → An “Uncontrolled” watermark is applied to published documents
  • false → No watermark is applied to published documents

Default: false
Notes: Original published files remain unchanged
DOCUMENT_MAX_SIZE
Sets the maximum size for documents stored in EPC to prevent large files from impacting system performance or storage.

Required format: MB
ENABLE_ATTESTATION
Activates the attestation cycle, which requires users assigned to the object through the specified RASCI-VS roles to review and confirm the content before publication. If no approval cycle is configured for the object, the attestation cycle is not triggered.

Required Format: true or false.
Default: true (enabled)
ENABLE_COPY_COUNTS_INJECTION
This setting lets the system automatically track and display how many times a document has been downloaded or printed. The counts are added to PDF files and recorded in the audit trail for document objects.

How it works

  • Download counts: Tracks downloads of the published version of a document, including from the preview window, List view, and mass downloads. Draft versions and SOP generation are not counted.
  • Print counts: Tracks printing from the preview window of the published document only if DOCUMENT_CONTROLLED_COPIES is set to ‘true’. Draft versions and printing from the Details page are not counted.

Rules

  • If this setting is enabled, the injected count will appear at the bottom left corner of the first page, but only for PDF files.
  • If CONVERT_WORD_TO_PDF_IN_PUBLISHED is enabled, the count will always be injected within the files since all files will automatically be converted to PDF in published mode.

The following table illustrates when the count is injected:

Latest Mode Latest Mode Published Mode
Draft Version Published Version Published Version
Office No Yes, if no print authorization Yes, if no print authorization OR CONVERT_WORD_TO_PDF_IN_PUBLISHED is enabled
PDF No Yes Yes
Other No No No

Required format: ‘true’ or ‘false’

  • ‘true’ → Download and print counts are tracked and injected into PDF files
  • ‘false’ → Counts are not tracked

Default: false (feature disabled)

ENABLE_ENDORSEMENT_CYCLE_EDIT
Determines whether users can edit objects during an active endorsement cycle. Useful when content may require updates while endorsements are still in progress.

Required Format: true or false
  • true → Allow edits without closing the cycle.
  • false → Prevent edits until the endorsement cycle is closed or completed.

Default: false
ENABLES_FLOWCHART_STENCIL
Enables the use of custom flow object shapes in the graph editor, expanding modeling options.

Required Format: true or false.
  • true → Allow use of custom shapes.
  • false → Restrict shapes to BPMN only.
ENABLE_GOOGLE_ANALYTICS
Integrates Google Analytics data into EPC, making it available in Home Page Google Analytics widgets for insights on usage and traffic.

Required Format: true or false.
ENABLE_HARMONIZATION
Activates data association harmonization, which controls how changes to associated objects are synchronized.
  • Required Format: true or false.
  • Related setting: HAMONIZATION_CONTROL_DEFAULT (Sets the default control level)

    See this topic for more information on how to manage Data Harmonization
ENABLE_LANGUAGE_IN_URL
Allows the content language to be specified directly in URLs, supporting organizations that publish in multiple languages and making it easier to share or bookmark content in a specific language.

Required Format: true or false.
ENABLE_MASS_APPROVAL
Allows user to approve multiple objects at once from the To Do module, saving time when handling large approval task lists.

Required Format: true or false.
See Mass Approval for more information.
ENABLE_MASS_CONFIRMATION
Allows users to confirm multiple objects at once from the To Do module, saving time when handling large confirmation task lists.

Required Format: true or false.
See Mass confirmation for more information.
ENABLE_MASS_ENDORSEMENT
Allows users to endorse multiple objects at once from the To Do module, saving time when handling large endorsement task lists.

Required Format: true or false.
See Mass Endorsement for more information.
ENABLE_NAV_BAR_ERROR
Description to come.
ENABLE_SAML_SYNC_GROUPS
Enables synchronization of EPC user groups with the identity provider (IdP) via SAML SSO. This supports centralized group management through your IdP.

Required Format: true or false
Default: false (sync disabled)
See this topic for more information.

ENABLE_SAML_SYNC_TITLE
Enables synchronization of user titles (roles) with the identity provider (IdP) via SAML SSO. This supports centralized user management through your IdP.
Required Format: true or false.
Default: false (sync disabled)
See this topic for more information.

ENABLE_SWIMANE_RESIZE
Controls whether modelers can resize swimlanes in the diagram editor. Useful for managing consistency in process diagram layouts.

Required Format: true or false
  • true → Allow resizing of swimlanes and adding phases.
  • false → Prevent resizing and block adding phases.

Default: true
ENABLE_TRACK_CHANGES
Enables change tracking in files, allowing users to view revisions and edits made over time.
Required Format: true or false.
See this topic for more information.
epc.inbound.url
Defines the URL prefix where EPC is deployed. This is the base address used to access the system.

Required format: The full URL where your EPC is hosted (e.g., https://epc.company.com)
epc.license
Stores your EPC license.
epc.signature.enabled
Enables or disables the digital signature option in approval cycles, allowing users to authenticate approvals with a secure signature.

Required Format: true or false.
  • true → Enable digital signatures
  • false → Disable digital signatures
    See this topic for more information.
epc.sysadmin.email
Defines the system administrator’s email address, used for system notifications and alerts.

Required format: Enter a valid email address (e.g., admin@company.com)
FILE_PREVIEW_MAX_FILE_SIZE
Sets the maximum file size that can be previewed in EPC. Larger files must be downloaded instead of previewed.

Required format: Numeric value (e.g., 500000)
Denomination: MB
GOOGLE_ANALYTICS_BLACK_LIST
Defines a list of REGEX patterns that should be excluded from Google Analytics tracking. Useful for filtering out sensitive paths or internal traffic.

Required format: Enter one or more REGEX expressions.
GRAPH_HIGHLIGHT_COLOR
Sets the color used to highlight paths in process diagrams.

Required Format: Hex color code (e.g., #ff0000)
Default: #ffff00 (yellow)
GRAPH_HIGHLIGHT_THICKNESS
Controls the thickness of highlight bands in process diagrams, improving visibility.

Required Format: Numerical value, 1 to 9
Default: 3
GRAPH_SHAPE_AUTO_RESIZE
Determines whether task shapes automatically resize to fit full task names, or whether names are truncated.

Required Format: true or false
  • true → Task shapes auto-resize to fit text.
  • false → Task names truncate if they exceed shape size.

Default: true
HAMONIZATION_CONTROL_DEFAULT
Sets the default harmonization control level automatically applied to new objects, determining how strictly associations are enforced.

Required Format: high, medium or low.
  • high → No updates are applied automatically. Users review every change to associated objects.
  • medium → Minor version updates to associated objects are applied automatically. Major version updates require review.
  • low → All updates, major and minor, are automatically applied. Users are not prompted to review associations before they are updated.

Default: low.
Related Setting: ENABLE_HARMONIZATION (Activates Data Harmonization)
See this topic for more information on control levels.
HIDE_PERSONAL_INFO_TO_NON_SYSTEM_USERS
Controls whether personally identifiable information (PII) about users is hidden from non-admins. Helps protect privacy and comply with regulations.

Required Format: true or false
  • true → Hide personal info from non-admins
  • false → Display personal info normally

Default: false
See this topic for more information.
IDENTIFIER_SORT_ALGORITHM
Sets the sorting algorithm for Identifier columns in List views.

Required Format: ALPHANUMERIC or NUMERIC
  • NUMERIC → EPC groups digit-only values and sorts them numerically by value and by length (e.g., 1, 2, 10, 11, 20).
  • ALPHANUMERIC → EPC sorts values in alphanumeric order, where letters precede numbers (e.g., A1, A2, A10, B1, 10A).

Default: NUMERIC
IMPORT_USER_SIZE
Sets the maximum number of users that can be imported at once as resources.

Required Format: Numeric value
Default: 1000
INHERIT_APPROVAL_CREATE
Determines whether newly created objects automatically inherit approval cycles from their parent object.

Required Format: true or false
  • true → Inherit approval cycles
  • false → Do not inherit approval cycles

Default: false

INHERIT_ENDORSEMENT_CREATE
Determines whether newly created objects automatically inherit endorsement cycles from their parent object.

Required Format: true or false
  • true → Inherit endorsement cycles
  • false → Do not inherit endorsement cycles

Default: false
INHERIT_IMPLEMENTER_CREATE
Determines whether newly created objects automatically inherit the Author (previously Implementer) from their parent object.

Required Format: true or false.
  • true → Inherit author from parent
  • false → Do not inherit author

Default: false
JIRA_AUTHORIZATION
Defines the authorization header used when calling Jira from EPC, enabling integration.

Required format: Jira authorization token string.
JIRA_USER_ACCOUNT
Sets the Jira user account ID used for API authorization when connecting EPC with Jira.

Required format: Jira account ID. See this topic to learn more on the feature. See this topic for the full Jira integration procedure.
LEGACY_RESTRICT
Controls whether users with Read Published permissions can see the full version history of objects.


Required format: true or false
  • true → Read Published users see only the latest published version (default)
  • false → All users can access the full version history, regardless of permission

Default: true
LLM_API_KEY
Configuration parameter for the AI object and rich text generation. Copy and paste the API key into this field.

  • To learn how to obtain your API key, please click here.
  • If you prefer the AI features not to appear to users, remove the API key from this field.
LLM_CHAT_MAX_TOKENS
Specify the desired limit for the number of tokens (words) that the AI will generate when a user makes a request in the AI object and rich text generation features by entering a value in this field.

LLM_CHAT_MODEL
Configuration parameter for the AI object and rich text generation.

While the default model available in EPC is ChatGPT 3.5, you can modify it to gpt-4 or any other available model in this field.
LLM_CHAT_TEMPERATURE
Controls the response variability of the LLM during chat-based requests. This value is passed directly to the provider’s API as the temperature parameter. Lower values (e.g., 0.1) produce more deterministic and consistent outputs, while higher values increase randomness and creativity.


  • Required Format: Decimal number (e.g., 0.1, 0.7, 1.0)
  • Default: Provider default (if not specified)
  • Behavior:
    • Lower values (e.g., 0.1) → More deterministic and consistent responses
    • Higher values (e.g., 1.0) → More varied and creative responses
LLM_CHAT_TIMEOUT
Defines the maximum time (in seconds) the system waits for a response from the configured LLM provider.

Required Format: Number (Seconds)
Default: 30
LLM_CHAT_URL
Organizations using their own private ChatGPT accounts can configure the AI Completion API endpoint here. This setting controls AI-powered object generation and improvement.

Default: https://api.openai.com/v1/chat/completions
LLM_CHAT_EMBEDDINGS_URL
Organizations using their own private ChatGPT accounts can configure the AI Embedding API endpoint here. This setting controls the AI Chat Assistant.

Default: https://api.openai.com/v1/embeddings
LLM_PROVIDER
Specifies which Large Language Model (LLM) provider the application uses for AI-powered functionality. This setting determines which external service the system connects to when processing LLM requests.

Required Format: String (e.g., openai)
mail.debug
For Interfacing internal use only.
mail.enabled
Controls whether EPC sends email notifications (e.g., approval tasks, reminders).

Required Format: true or false
Default: true (notification emails enabled)
mail.from
Sets the display name that will appear as the sender when EPC sends notification emails.

Required format: Enter a customer sender name (e.g., company-noreply@interfacing.com)
mail.password
Defines the password used to authenticate with the mail server. Can be stored as plain text or encrypted.
mail.smtp.auth
Specifies whether the system should attempt SMTP authentication when connecting to the mail server.

Required format: true or false
  • true → Use SMTP AUTH for authentication.
  • false → Do not use SMTP AUTH.

Default: false
mail.smtp.encryption
Sets the encryption protocol for SMTP connections.

Required format: TLS or leave empty.
  • TLS → Use a TLS-protected connection.
  • Leave empty → No encryption.
mail.smtp.host
Defines the hostname of the mail server EPC should connect to.

Required format: Enter a valid host (e.g., mail.example.com)
mail.smtp.port
Sets the port number used for SMTP connections.

Required format: Enter a valid port number (commonly 25, 465, or 587).
mail.transport.protocol
Defines the message transport protocol used for sending email.

Required format: Enter a valid transport protocol (commonly smtp)
mail.user
Defines the username used to authenticate with the mail server.
MAP_PAGE_BREAK_DEFAULT
Defines the default Map Page Break Option when generating Object Books, controlling how process maps are displayed across pages.


MICROSOFT_APP_CLIENT_ID
Microsoft 365 integration parameter. Required to enable the Edit in Microsoft 365 feature.

See this topic for the full MS 365 integration procedure.
MICROSOFT_APP_CLIENT_SECRET
Microsoft 365 integration parameter. Required to enable the Edit in Microsoft 365 feature.

See this topic for the full MS 365 integration procedure.
MICROSOFT_SYNC_CLOSE_DELAY
Sets the number of seconds EPC waits after a Microsoft 365 editing tab is closed before synchronizing the file with OneDrive. This setting is used in the Edit in Microsoft 365 feature.

Required format: Numeric value
Denomination: Seconds
See this topic for the full MS 365 integration procedure.
MICROSOFT_TENANT
Microsoft 365 integration parameter. Required to enable the Edit in Microsoft 365 feature.

See this topic for the full MS 365 integration procedure.
MSTEAMS_APP_CLIENT_ID
MS Teams Bot integration parameter. Required to enable tagging Teams users in EPC Collaboration topics.

See this topic for the full MS Teams integration procedure.
MSTEAMS_APP_CLIENT_SECRET
MS Teams Bot integration parameter. Required to enable tagging Teams users in EPC Collaboration topics.

See this topic for the full MS Teams integration procedure.
MSTEAMS_TENANT
MS Teams Bot integration parameter. Required to enable tagging Teams users in EPC Collaboration topics.

See this topic for the full MS Teams integration procedure.
ONE_RESOURCE_APPROVES_ENDORSES_FOR_ENTIRE_ROLE
Defines whether only one resource per role is required to complete approval and endorsement tasks, instead of all resources assigned to the role.

Required Format: true or false.
  • true → One user per role is sufficient.
  • false → All users in the role must approve and endorse.

Default: false.
PASSPORT_AZURE
Defines Azure Active Directory authentication protocol settings for Single Sign-On (SSO).
PASSPORT_COGNITO
Defines Cognito authentication protocol settings for Single Sign-On (SSO).
PASSPORT_JUST_IN_TIME
Defines Just-in-Time authentication settings for Single Sign-On (SSO).
PASSPORT_KERBEROS
Defines Kerberos authentication protocol settings for Single Sign-On (SSO).
PASSPORT_KERBEROS_KEYTAB
Stores the Kerberos keytab file (Base64 encoded) used for authentication.

Required format: Paste the Base64 keytab content.
PASSPORT_LDAP
Defines LDAP authentication protocol settings for Single Sign-On (SSO).
PASSPORT_NTLM
Defines NTLM authentication protocol settings for login.
PASSPORT_SAML
Defines SAML authentication protocol settings for Single Sign-On (SSO).
PASSPORT_STRATEGY_TO_USE
Selects which authentication protocol EPC should use for login.

Required format: Input one of these protocols:
  • Local
  • KERBEROS
  • LDAP
  • NTLM
  • SAML
PRIVATE_CACHE_URL
Defines the internal cache port address.
PROCESS_SET_MAX_GRAPH_SIZE
Sets the maximum number of processes displayed in a Diagram Set before requiring the user to click the Display All button.

Required format: Numeric value
PURGE_PERIOD
Defines the default retention period for archived objects before they can be purged from the system.

Required Format: Numeric value
Denomination: Years
Default: 13
See this topic to learn how to purge objects.
RASCIVS_ATTESTATION
Specifies which RASCI-VS roles receive attestation tasks. This ensures the right stakeholders are designated for this task and receive the relevant notifications.

Required Format: Input one or more of: responsible, accountable, support, consulted, informed, verifier, signatory
Default Value: verifier
Prerequisite: the ENABLE_ATTESTATION setting must be set to true.
See this topic to learn more about the attestation cycle.
RASCIVS_COLLABORATION
Specifies which RASCI-VS roles receive collaboration notifications. This level of customization helps ensure that the right stakeholders receive the relevant notifications in alignment with your organization’s specific requirements.

Required Format: Input one or more of: responsible, accountable, support, consulted, informed, verifier, signatory
Default Value: all RASCI-VS values.
Rules:
  • Collaboration notifications apply to all topic types (change requests, discussion, incident, question).
  • The accountable (A) receives notifications only if they are included in this setting, or if they created/replied to the topic.
  • Subscribed users also receive notifications.

See this topic for more information

RASCIVS_CONFIRMATION
Specifies which RASCI-VS roles receive confirmation tasks. This level of customization helps ensure that the right stakeholders are designated for the task and receive the relevant notifications in alignment with your organization’s specific requirements.

Required Format: Input one or more of: responsible, accountable, support, consulted, informed, verifier, signatory
Default Value: all RASCI-VS values.
See this topic to learn more about confirmation tasks
RATE_LIMITER_MAIL
Controls the rate at which notification emails are sent to users, preventing them from being sent all at once. For example, if 300 users need to be notified about a newly published object requiring confirmation, this setting ensures the emails are sent gradually instead of simultaneously.

Denomination: seconds
Required format: number
Default: 10 (emails are sent at a rate of 10 per second)
REMINDER_INTERVAL
Defines the interval between reminder notifications.

Required Format: Numeric value
Denomination: Days
Default: 1
REMINDER_NEXT_DATE
Defines the earliest date on which reminders can be sent.

Required format: Date and time (e.g., 2025-05-29T10:00:00.000)

REMOVE_AUTO_LAYOUT_BUTTON
Controls whether the auto-layout button is available in the Diagram Editor toolbar.

Required Format: true or false
Default: false (button displayed)
REVIEW_INTERVAL_DAYS
Defines how many days before the Review Deadline users will receive review cycle tasks, if the cycle does not have a fixed Start Date.

Required Format: Numeric value
Denomination: Days
Default: 60
See this topic to learn more about review cycles.
RICHTEXT_CUSTOM_STYLE
Allows to customize the appearance of text in the Details view by applying custom HTML/CSS styles. This enables consistent branding through adjustments such as font, size, colors, line height, and list styles.

Required Format: HTML
Example:
<style> p { font-family: Verdana, sans-serif; font-size: 16px; line-height: 1.6; color: #0033A0; } h1, h2, h3, h4, h5, h6 { font-family: Georgia, serif; color: #FFA500; } ul { font-family: Verdana, sans-serif; font-size: 16px; color: #004D40; list-style-type: square; margin-left: 20px; } </style>
Results:

S3_ACCESS_KEY_ID
Amazon S3 access key ID for connecting EPC to external storage.
S3_BUCKET_NAME
Name of the Amazon S3 bucket where files will be stored.
S3_REFRESH_DELAY
Sets the interval for pushing files to external storage.

Required format: Numeric value
Denomination: Seconds
S3_REGION
Defines the AWS region of the S3 bucket.
S3_SECRET_ACCESS_KEY
Secret key used to authenticate with Amazon S3.
S3_STORAGE_PREFIX
Prefix added to object keys in S3 for organization or namespacing.
SEARCH_CUSTOM_EXTENSIONS
Specifies which file types should be indexed by the search engine. This allows organizations to override the default set of indexed file extensions and include only the file types relevant to their workflow.

Required format: Comma-separated list of extensions (e.g., docx, pdf , txt, xml, xlsx)
Default: If left empty, the system users the list below:
doc, docx, html, key, mbox, ods, odt, odp, pages, pdf, ppsm, ppsx, ppt, pptm, pptx, rtf, txt, xml, xls, xlsx, msg
SEARCH_EMBEDDING_ENABLED
Enables or disables the AI Chat Assistant for content queries.

Required Format: true or false.
Default: false (AI Assistant disabled).
Prerequisite: Configure the AI Embedding API endpoint in the AI_EMBEDDING_API setting.
See this topic to learn more about the AI Chat Assistant.
SEARCH_EXCLUDED_ATTRIBUTES
Exclude specific attribute IDs from search indexing.

Required Format: Comma-separated list of values to exclude.

SEARCH_MAX_FILE_SIZE
Maximum file size that can be indexed.


Required format: Numerical value
Denomination: Bytes.
Default: 20,971,520 bytes or 20 MB
SEARCH_QUERY_ALLOWED
Controls when Elasticsearch is used for search operations in EPC List views and keyword filtering in the new suite. This setting helps balance performance and functionality by determining when Elasticsearch is used instead of database queries.

Required format: One of the following values
  • NEVER → Elasticsearch is never used. Keyword filtering in the new suite is disabled, and all EPC List views use database queries only.
  • REQUIRED → Elasticsearch is used only for keyword filtering and in List views.
  • PREFERRED → Elasticsearch is used automatically when a database query would be slow (for example, name-based filtering), while faster filters may still use the database.
  • ALWAYS → Elasticsearch is always used when available, for both List views and keyword filtering.

Default: REQUIRED

SEARCH_QUERY_HIGHLIGHT_FILE_CONTENT
Highlights matching text in search results for file content.

Required Format: true or false.
Default: true (highlighting enabled).
Example: Searching for ‘Change Management’ will highlight both words in the results, as shown below:

SEARCH_QUERY_HIGHLIGHT_UDAS
Highlights UDAs that match search queries.

Requires Format: true or false.
Default: true (highlight enabled).
Example: Searching for ‘Canada’ highlights all matching UDAs, as shown below:

SEARCH_SERVER_PASSWORD
Password for connecting to the search server.
SEARCH_SERVER_URL
URL of the search server.
SEARCH_SERVER_USERNAME
Username for connecting to the search server.
SECRET_EXPIRY_DELAY
Sets the validity duration of the digital signature’s secret code.

Required Format: Numerical value.
Denomination: Minutes.
Default: 10 (if left empty)
See this topic for more details.
SORT_SERIAL_NUMBER_NUMERIC
Controls how System Serial Numbers (SSNs) are sorted in List views.

Required Format: true or false
  • true → Sort by numeric value, ignoring text prefix
  • false → Sort alphabetically including text prefix

Default: true (numeric, ignoring prefix)
TENANT_ID
For Interfacing internal use only.
UPLOAD_ALLOWED_MEDIA_TYPES
Defines allowed file types for upload, based on MIME types (e.g., PDF, Word).

Required Format: Comma-separated list of MIME types.
Prerequisite: This setting only works if the UPLOAD_VALIDATE_MEDIA_TYPES setting is enabled.
Example: application/pdf, text/plain, application/vnd.openxmlformats-officedocument.wordprocessingml.document.
See this topic to learn more on the feature.
UPLOAD_VALIDATE_MEDIA_TYPES
Validates that uploaded files’ content matches their file extension, preventing disguised or unsafe files. If the content does not match the declared extension (e.g., a .pdf that is not actually a PDF), the upload will be rejected by EPC.

Required Format: true or false.

  • true → Enable validation
  • false → Disable validation

Default: true.
See this topic to learn more on the feature.
WEB_CACHE_MAX_FILE_SIZE_DAILY
Maximum file size eligible for caching for one day.

Required Format: Numerical value.
Denomination: Bytes or MB
Default: 10485760 (or 10MB)
WEB_CACHE_MAX_FILE_SIZE_HOURLY
Maximum file size eligible for caching for one hour.

Required Format: Numerical value.
Denomination: Bytes or MB
Default: 52428800 (or 50MB)
WEB_CACHE_MAX_FILE_SIZE_WEEKLY
Maximum file size eligible for caching for one week.

Required Format: Numerical value.
Denomination: Bytes
Default: 1048576 (or 1MB)
WEB_SERVICES_LOGGER_DEFAULT_LEVEL
Sets the minimum log level for web services.

Required Format: error, warn, info, verbose, debug or silly.
Default: warn
WEB_SERVICES_LOGGER_PER_MODULE
Allows to configure different log levels for individual EPC modules. This provides more control and makes it easier to troubleshoot issues in specific areas without generating unnecessary logs system-wide.

Required Format: JSON key-value pairs
Allowed Log Levels: error, warn, info, verbose, debug or silly
Default: Empty (all modules use the level defined in WEB_SERVICES_LOGGER_DEFAULT_LEVEL)
WEBTOKEN_EXPIRES_IN
Duration after which web tokens expire.

Default: 10000d.
Value Examples:

As minimum requirements, we recommend 2 GB of RAM for the Web App Search docker. Some search settings (SEARCH_FETCH_DELAY_BETWEEN_PAGES, SEARCH_FETCH_ITEM_PER_PAGE, SEARCH_MAX_FILE_SIZE) are interrelated and must be edited consequently so as to correctly manage available RAM and avoid Search Docker RAM overload. An Out Of Memory issue on the docker can lead to Web App slow-down or complete unresponsiveness.

As shown in the above table for System Settings, default search index parameters will load 25 objects per page every 1000 Milliseconds. Each object of the page will be loaded into RAM while indexing. With a default maximum file size of 20,917,520 Bytes (20 Mb), this means there is a maximum potential RAM load of (25 objects * 20 Mb) 500 Mb occupied by a search index. This will leave ample space for adequate search performance during indexing without substantially affecting the total total time period required to fully index the specific environment.

We highly recommend that any combinations of these parameters not exceed half of the allocated RAM for the search docker. For safe measure we have defined them to occupy 25% of recommended RAM. If you wish to adjust any of these three parameters, especially “SEARCH_MAX_FILE_SIZE’, RAM for the Search docker may need to be adjusted correspondingly.

Use this formula to ensure safe use of search settings:
(SEARCH_FETCH_DELAY_BETWEEN_PAGES * SEARCH_FETCH_ITEM_PER_PAGE * SEARCH_MAX_FILE_SIZE) <= (0.5 * Allocated Search docker RAM)

Need more help with this?
Visit the Support Portal

Thanks for your feedback.