Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Unknown sender for SLA notifications from SBM
Unknown sender for SLA notifications from SBM
CMS-XML SLA Notifications from SSM Solutions also appear in the Application Administrator section for Notifications
SLA Notifications from SSM Solutions also appear in the Application Administrator section for Notifications
CMS-XML SLA Notifications display in the Admin portal after Promotion
SLA Notifications display in the Admin portal after Promotion
CMS-XML SLA Engine Service Appears in Configurator on Notification Server Machine in Distributed Installation with SSM 5.2.1 and SSM 5.2.2
SLA Engine Service Appears in Configurator on Notification Server Machine in Distributed Installation with SSM 5.2.1 and SSM 5.2.2
CMS-XML Stop or start notification server or mail client or SLA without using Configurator in SBM 10.1 and newer
To stop or start the notification server or mail client in SBM 10.1 and newer without using Configurator, you can edit the "server.pause.config.properties" file located in the:
CMS-XML View All Items role privilege is ignored for notifications - also in SSM SLA reports might show incorrect items
The "View All Items" privilege is ignored for notifications if the privilege is only granted to a user via a group that inherits the privilege from a role. If the user is added to the role directly, the privilege is honored and he or she will receive the notification.
CMS-XML Warning when adding Notification to SLA "Sorry, You cannot modify clause action because SLA is out of date."
Expected result: The notification should be saved. Actual result:
CMS-XML SLA calculation does not honour the calendar changes
SLA item does not recalculates upon changes (overrides) on the Calendar used. However the notification service recalculates continuously and it could cause some data discrepancies if there are notifications associate to this SLA item.
CMS-XML Journal fields or date/time fields in notifications can have incorrect date and/or time
The JVM timezone gets shifted to GMT by either SLA or SSF (part of common services since 10.1.1.4) that is installed on the server running the Notification Server, but this is done after the DB driver initialization which causes the Notification Server to think it is getting times in GMT when it is actually not which can cause date/time issues in notification emails.
CMS-XML How to stop the SLA service after installing SSM 5.3
To work around this problem, you can stop or pause the service manually by setting the sla_paused entry to 1 in the server.pause.config.properties file on the Notification Server. The file is located here:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs