Skip to main content

Does anyone have experience in overriding the connector instance (mail) on report rules?

On the report rule, Route to Connect, I can’t get this to work.

If there is a mail sender that is marked as ‘default instance’ it will be used when sending the mail. If there is no default mail sender, IFS will select the first mail sender in alphanumerical order. Which means that if you create a mail sender with name ‘AAA’ it will be used before ‘BBB’.

On an event action, of type E-mail, it is possible to override the Mail sender.

Is this a bug or am I missing something?

In  my testing I have created a very simple report rule, that will trigger each time a specific report is printed - and mail it to me. Not a real world scenario but a simplified example that is easy to test.

 

If I select action ‘Send Email’ I can’t override the mail sender at all, seems to only be available on ‘Route to connect’.

 

Reported to R&D and it was a bug and will be fixed in 24R2

Hi ​@GISANCAR 

 

Two years ago I reported closely related problem with procedure API(Command_SYS.Mail) but unfortunately solution hasn’t been provided. May I know the planned update version?

The only information I received on my support ticket is that R&D states that it is fixed from 24r2 and onwards. Don’t know which service update it is on respective release. It did not work on 24.1.4.

Hi ​@GISANCAR 

May I know the ticket number?

Hi ​@knepiosko,

My ticket number is CS0300983. But I can’t find any references to this in the list of corrected issues for 24.2 in IFS Cloud 24R2 Service Updates - Fixed Issues & Release Approvals 21-August-2025 | IFS Community

Nor can I find any ‘mail/connector’ related fixes that matches this either, so I hope it is fixed through something else.

It doesn’t work in 24.1.9, we are going to upgrade to 25.1.3 shortly and I will test and see if this has been fixed or not.

 

Under Your ticket there should be a Jira ticket number. This is related to “physical” correction in code. May I know this number?

No such information was added into the ticket. No reference to a Jira ticket number. The only relevant information was:

“Based on the comments from R&D, we have verified that the issue has been fixed in 24R2 and onwards. We kindly recommend updating to the latest version of IFS Cloud to ensure you receive this fix.”
 

Terms & ConditionsCookie settings