Jump to content

Recommended Posts

Posted

Thanks for the update, it looks like our leaver/starter BPMs could be affected by this as they have the Error Xmlmc method invocation failed for BPM invocation node 's1/flowcode-dd25eaf0-ba90-44c5-4536-27690c47120a': 0200 apps notifyEmailExternalAddress FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/notifyEmailExternalAddress): nodeName: Exception; nodeId: acd1ebbe-1cd9-4aed-bf14-50ce53f9a013; At 303/1: "Uncaught FCSException: The email template specified is invalid. Please contact your Hornbill Administrator." throw(e); _fc_node_exec_acd1ebbe_1cd9_4aed_bf14_50ce53f9a013

Once the first activity is resolved.

Posted

@Ann-MarieJones - as you noticed we have created a separate thread for the issue you reported as it is not related to the issue discussed in this thread:

 

The reason for the error you encounter is specified in the error message: "The email template specified is invalid. Please contact your Hornbill Administrator.". This means in your process, you have an email node configured with a template that is not valid. My advice is to review your process configuration and ensure all email nodes are using valid email templates.

Posted

Thank you @Victor,

I have taken a look at the business process for New Starter and Staff Leaver process, as these are the BPMs with the errors.  The error occurs once the 'Review the details supplied' Activity is completed and the email node that follows is 'Email Multiple External Addresses' 

P1.png.9fefd406c4785f41ae4237104e313e9d.png

P2.png.fe594244fd08b3c431b44505431245fa.png

I have checked the email templates in Admin and can see they haven’t been updated since 28/09/18 and are still valid.

P3.png.75372854c19d7336603fa0adcced8c84.png

I have also checked the email recipients and they are live mailboxes  .An example call is

 image.png.898f33c6c4e19dc98ea5d411ca62fc2e.png

 

Any advice is greatly appreciated.

Posted

@Ann-MarieJones -  just a quick FYI, to fix this issue we would need to stop a service in your instance (the indexer service) for a few seconds so we can start the maintenance work at 17.30. You might notice some issues for a very short/brief period of time but usually, this should go unnoticed... 

Posted

@Ann-MarieJones - the issue which caused the process to fail when sending the email has been fixed. I have also restarted the process on SR00016743 successfully. I am also doing some more work which will hopefully fix the searching issue you raised in a separate thread.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...