The placeholder [%$FORM_INBOX_LINK%] links directly to the process within the mailbox. Sometimes a 404 error page is displayed instead, stating that the resource could not be found.
The reason for this is that the form inbox link is generated context-based. This means that if the form is called up previously via the frontend server, e.g. via form-provide-link or can only be called up there and is then sent, the placeholder [%$FORM_INBOX_LINK%] is also returned relative to the call. For example:
https://my-forms.de/frontend-server/inbox/review.xhtml?fcpuid=b85193a3-505b-407d-9984-6b81ec75e4c5
By default, the mailbox is only accessible via the master server (formcycle). The call will therefore fail in this case. The following options are currently available:
- Install the frontend server with mailbox (see Release notes > Version > frontend-server-inbox.war)
This would make the form inbox link accessible, but the mailbox can also be called externally. This is also protected with a login, just like on the master server. - Use the [%$FORM_REVIEW_LINK%] instead of the inbox link. This is also available without a mailbox, but does not include the mailbox frame.
- In the corresponding action, use a separate URL placeholder instead of the inbox link, which refers to the internal inbox URL. The placeholder can be created under Files & Templates > URLs. Example:
Name: Form-Inbox-Link-Internal
Value: https://my-forms-internal.de/formcycle/inbox/review.xhtml?fcpuid=[%$PROCESS_ID%]
The value up to /formcycle is equivalent to the basic URL (under Client > Settings > Basic settings).
The new placeholder can then be used as usual via Placeholder selection > URL template:
[%$$Form-Inbox-Link-Internal%]
If no frontend server is used, the problem should not occur.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article