The EPC 2.0 July '26 release is scheduled for July 11, 2026. With this release, we've included the following new features and improvements:

Platform updates

The following EPC platform updates are included in this release:

• New CREATE_FULFILLMENT_DISCLOSURE action to support creating a disclosure fulfillment [EPC-47075, EPC-47063]: The CREATE_FULFILLMENT_DISCLOSURE action can be used in both the Partner Documents Delivery flows and the standard documents category flows. The disclosureTrackingLogId parameter is optional. If it is not provided, the system automatically uses the most recent disclosure tracking log ID available in the transaction to create fulfillments. If no disclosure tracking log exists, the action fails and returns a valid error message through transaction.event. When a fulfillment is successfully created or updated, the system returns a transaction event object to the partner. This object includes the disclosureTrackingLogId and the fulfillments array. For more information, see Create disclosure tracking log fulfillment action.

 "result": {
        "format": "application/vnd.disclosure-fulfillment-create-1.0.0.json",
        "action": "CREATE_FULFILLMENT_DISCLOSURE",
        "details": {
            "disclosureTrackingLogId": "b22e6897-7435-465d-ad0c-da4b8d0b6ba7",
            "disclosedMethod": "ByMail",
            "orderedBy": "Test",
            "processedDate": "2023-03-24T11:11:11Z",
            "recipients": [
                {
                    "actualDate": "2023-03-29",
                    "comments": "Test Comments"
                }
            ]
        }
    }

{
    "id": "79e92af6-331c-43a4-9c03-14b4c9d73c03",
    "text": "Transaction response successfully processed",
    "type": "urn:elli:epc:transaction:response:processed",
    "from": "System",
    "sent": "2026-04-08T18:08:20Z",
    "comments": "Transaction response successfully processed",
    "details": {
        "status": "Success",
        "requestType": "NewOrder",
        "transactionId": "c906b062-c2a5-443d-bd72-45f0968b5d54",
        "requestCorrelationId": "e5761d61-bdd3-4f16-96a4-0230e77a8cd0",
        "disclosureTrackingLogId": "b22e6897-7435-465d-ad0c-da4b8d0b6ba7",   
        "fulfillments": [  
            {
                "id": "b9cdcb0e-f23a-4292-b3b0-5f5a46c50796",
                "recipients": [
                    {
                        "id": "recipient_id",
                        "recipientType": "Borrower"
                    }
                ]
            }
        ]
    }

• UPDATE_DISCLOSURE action enhanced to support fulfillment update [EPC-47075, EPC-47063]: This enhancement enables seamless fulfillment lifecycle integration within the UPDATE_DISCLOSURE workflow for v2.0.0. For more information on v2 schema, see Update disclosure tracking log v2 .
• Category recorded during Transaction creation and exposed in GetTransaction API [EPC-44957]: Prior to this release, transactions did not store category information. With this release, EPC captures and persists the category at the time of transaction creation and returns it in the GetTransaction API response.
• GET Change Log by ID [EPC-43552, EPC-43558]: To enable partners to track product registration changes, two new APIs - GET Change Log by ID, and GET ALL Change Logs - have been introduced with this release. Every update to your product using PATCH product API produce a change log entry. The id to this entry is returned in the PATCH product API response header Changelog-Location.
• Appraisal Service SSR JSON file support [EPC-46396]: Prior to this release, files are considered non-viewable files and are not stored in the eFolder, so they do not appear in the EPC Document Uploader. With this release a standard resource type have been introduced urn:ice:epc:ucdp:ssr:version:V2.0.0.

  "resources": [
    {
      "id": "d17fe9da-d432-43a9-a384-5d84ade7bfec",
      "name": "ssr.json",
      "mimeType": "application/json",
      "type": "urn:ice:epc:ucdp:ssr:version:V2.0.0"
    }
  ]

• If your integration needs access to JSON files that were previously uploaded, you need to specify partner as one of the allowed sources when calling getAvailableSources action. Example below. For more information, see UCDP and Support for UAD 3.6.

applicationObj.performAction("getAvailableResources", {"allowedSourceTypes": ["esign", "efolder", "partner"]})

JavaScript guest library updates

The following EPC JavaScript guest library are included in this release:

• Doc Uploader [EPC-46096]: eFolder container's borrower pair now included in the DocUploader data table and its filtering logic. Since many services operate at the borrower-pair level, this enhancement improves the DocUploader experience for both ordering users and partners.
  DocUploader now uses the borrowerPairId passed to EPC to prefilter documents in the data table. EPC will source the borrowerPairId from the launch contract rather than the getAvailableResources action contract. No code changes are required from partners to support this feature.
• getContext action [EPC-47213, EPC-47300]: getContext action extended in both admin and ordering flows to include the following new attributes:
  • clientId
  • instanceId
  • encompassUserId

📘

NOTE

This is supported in both Encompass desktop and web interfaces.

• getAvailableResources action upload size limits [EPC-39055]: Optional integer parameter maxAttachmentSize has been exposed to define the maximum allowed file size (in MB).
  When this parameter is provided, local files or eFolder documents that exceed the specified size are blocked from uploading and an error message is displayed. The EPC platform enforces a hard limit of 200 MB; if a partner sets maxAttachmentSize greater than 200 MB, the DocUploader UI does not display and an error displays instead. If no value is provided, the existing 200 MB validation remains in effect within DocUploader.
  File byte size is now returned as an attribute for each uploaded request resource when the application.performAction(getAvailableResources) UI is closed. This enables partners to perform client-side file size validations (for example, to prevent duplicate uploads) before orders are placed.