REPORTSCHED would solve this problem because it would then utilize that on the reportrunqueue automatically. However, it would prevent you from knowing who originally scheduled the report (which is important when you have issues with it) and would prevent them from managing the scheduled report (changing when it runs, who gets the email notifications, canceling when it's no longer needed, etc.). Anyone with Report Administration access can see and manage scheduled reports but in the core applications (like WOTRACK), only the person that scheduled the report sees it. It causes an additional burden on the Maximo Admin side which is why I would avoid it.
As for setting the email on the MAXADMIN (or other user account you use to execute the reports), this is correct. We set the MAXADMIN address to the Maximo email account address along with other system properties like mxe.int.adminfromemail, mxe.esigresetemailfrom, etc. And then of course ensuring the sendfrom on communication templates match and disable the ability to override the send from on communication templates (mxe.commlog.SendFromEditable set to 0).
------------------------------
Steven Shull
Naviam
------------------------------
Original Message:
Sent: 10-10-2025 16:08
From: Pradeep Rout
Subject: ROSA MAS 9.1 and are experiencing an issue where scheduled reports are not being received
Thanks @Steven Shull. Looking forward for your blog . I have voted too for the Idea. Another Workaround i found to update teh reportsched object userid to MAXADMIN and then update MAXADMIN user to SES email sender address.
------------------------------
Pradeep Rout
TCSL
Original Message:
Sent: 10-10-2025 14:51
From: Steven Shull
Subject: ROSA MAS 9.1 and are experiencing an issue where scheduled reports are not being received
Scheduled reports will send as the user that scheduled which is often problematic because sending on behalf of others is typically disabled in the organization. For example, if your email inbox is maximo@mycompany.com and the email of the user that scheduled the report is bob@mycompany.com, what happens is maximo@mycompany.com account tries to send the email as bob@mycompany.com. While this can be configured to allow on the email server, this is almost never allowed because of the security ramifications.
There have been ideas (like SendFrom option for | IBM Sustainability Software - Ideas Portal) to change this but it's not implemented. I provided some additional details on this thread (SMTP Error "SendAsDenied" when Sending Emails from BIRT | Maximo Open Forum) but still haven't had a chance to document all the pieces we configure for customers in our cloud. I'll try and work on this for a blog post soon.
------------------------------
Steven Shull
Naviam
Original Message:
Sent: 10-10-2025 09:58
From: Pradeep Rout
Subject: ROSA MAS 9.1 and are experiencing an issue where scheduled reports are not being received
Hello Experts,
We are currently using ROSA MAS 9.1 and are experiencing an issue where scheduled reports are not being received. It's important to note that email communications are functioning correctly for other features, such as Work Order workflow notifications and electronic signature reset emails.
We would appreciate your guidance on resolving this issue.
#Reporting
------------------------------
Pradeep Rout
TCSL
------------------------------