Publish Failure in an Engage Record '404 - File or Directory Not Found' in Archer

[Kb-Sync]

Applies To

Product(s): Archer, Engage
Version(s): All Versions
Primary Deployment: On Premises/AWS Hosted/AWS SaaS

---

Description

When attempting to publish an Engage record using the Portal Button Custom Object, the publish fails with the message below:
Unexpected Error: 404 - File or directory not found.
0EMVM00000213dp.png

Cause

The portalURL is configured incorrectly in the Portal Button Custom Object.

Resolution

Modify the portalURL in the Portal Button Custom Object. Follow the steps below:

1. Expand Administration menu > Expand Application Builder > Select Applications > Open the affected module.
2. Go to the Designer tab > Layout sub-tab and locate the Portal Button Custom Object and expand its Properties.
3. Under the Custom Object Properties section, locate const portalURL and modify it so that it is written as follows:
const portalURL = '/Archer/engage/api/questionnaire/Publish';

0EMVM000007KNZ7.png

Notes

The same issue could occur when using the Publish button (at the top of the record) that is configured through the Engage tab in the Application Builder page of the module. In this case, the error will be:
PUBLISH FAILED
0EMVM00000214Rp.png
This would be caused due to that the Publish URL is incorrectly configured in the Engage tab (Administration menu > Expand Application Builder > Select Applications > Open the affected module > Navigate to the Engage tab).

The Publish URL should be adjusted directly from the Engage tab as follows:
/Archer/engage/api/questionnaire/Publish
0EMVM000007KC94.png
Note:

• The inclusion of Archer in the portalURL and/or the Publish URL depends on the website which Archer is installed in:
  • If Archer is installed directly in the Default Website then Archer will be excluded and the portalURL will be as follows: const portalURL = '/engage/api/questionnaire/Publish';
  • If Archer is installed in a separate website under Default Website then this website will be included and the portalURL will be as follows: const portalURL = '/WebsiteName/engage/api/questionnaire/Publish'; (e.g., '/Archer/engage/api/questionnaire/Publish').
• For Engage deployments and versions prior to the new Engage Unified Installer, the portalURL can be configured as '/vendorportalservice/api/questionnaire/Publish' instead of  '/engage/api/questionnaire/Publish'.