The EPC 2.0 August '25 release is scheduled for August 09, 2025. With this release, we've included the following new features and improvements:

Platform updates

The following EPC platform updates are included in this release:

TPO support in eFolder [EPC-41816]: TPO Portal checkbox is now automatically selected for TPO service orders when creating eFolder documents.
Comments update in Tasks [EPC-40344]: Prior to this release, comments were appended to the task description with a 300 character limit. As a result, task updates were limited when the 300 character limit was reached. To address this, a new Comments section has been created within Tasks.
Vendor Allocation Percentage calculation update [EPC-40977]: Record service orders count excluded from vendor allocation percentage calculations if:
- Category == MI
- Request type == RateQuoteDirect
Transaction patches to trigger Workflow rules [EPC-40998]: Workflow Rules that create or update service orders and rely on triggers like field modifications or attachments added were not firing if the triggers were a result of a transaction patch. This safeguard constraint was in place to protect internal platforms from poorly configured automation rules. This safeguard is now configured to allow WFE rules to fire while still protecting internal platforms.
Plugin Support Updates[EPC-40893, EPC-40856]:
- create product API now uses PSS API for OAuth clientId (if integrationType is plugin)
- Product registration now accepts partner name for tools/plugins

Documents/Attachment updates

isActive Flag Support [EPC-41872, EPC-42119, EPC-41969]:

isActive flag now accepted from transaction response resources.

{
    "status": "completed",
    "loanFormat": "application/vnd.plm-2.0.0+json",
    "resources": [
        {
            "id": "B2.be11176282KS*391ec0a3-52c6-4379-b35a-920f59e8072fKS*a2deebc9-2369-4371-9291-a8495ccc46b1",
            "name": "SamplePDFUpload2_EPC",
            "mimeType": "application/pdf",
            "isActive": true
        },
        {
            "id": "B2.be11176282KS*391ec0a3-52c6-4379-b35a-920f59e8072fKS*9cc58179-0177-4352-b769-835c74a1e69b",
            "name": "SamplePDFUpload2_EPC",
            "mimeType": "application/pdf"
        }
    ]
}

isActive flag supported for new and viewable resources

Current version [EPC-36436]: Services partners can now select and clear the Current Version checkbox on attachments pushed to the eFolder via EPC. This helps support automation for scenarios where multiple orders have been placed. This is supported only in the folder to which the attachment was pushed to by the service partner. If the attachment is moved to a different folder (manually or by automation), partners will no longer be able to select and clear the attachment versioning checkbox.
eFolder attachment current version [EPC-41524]: When an ASO rule has a partner document assigned and a transaction is triggered on a loan, all attachments flagged as current version and assigned to the eFolder container are added as request resources.
preConfiguredResources [EPC-42012]: When preConfiguredResources are set up using the classic approach (not using stacking template) and there are two matching document containers in eFolder, all matching document containers will be considered, not just the more recent container.

JavaScript guest library updates

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

Document Container ID [EPC-41032]: Upload payload in Doc Uploader now includes Document container ID (EFolderDocId) to help identify/distinguish documents sent with the same service category orders.
Document Groups dropdown [EPC-41901]: Issue occurred prior to this release where the Document Groups dropdown in the Select Documents and Files window was not displaying any value. This has been fixed so that when document groups are created, they are displayed in the mentioned dropdown list.
getDocumentStackingTemplates [EPC-41894]: Starting with this release, partners can retrieve document stacking templates configured on the lender instance using getDocumentStackingTemplates action. Sample response payload below:

[
    {
        "id": "1",
        "name": "stacking template 1",
        "isDefault": false
    },
    {
        "id": "2",
        "name": "stacking template",
        "isDefault": true
    }
]