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 Multi-User and Multi-Group fields in SLA Clause Qualifying Conditions don't return any values
Multi-User and Multi-Group fields in SLA Clause Qualifying Conditions don't return any values
CMS-XML Example for using SLA details in SBM reports via Advanced SQL Conditions
There is often a need to use Advanced Query to show listing or distribution reports than utilitise the SLA information: SQL SERVER Example: Items that violated their SLAs in the last 30 days by user To achieve this you can create a distribution report with the row by the necessary user field and using the Advanced SQL Conditions for SQL Server to filter similar to below:
CMS-XML SLA Clause: Qualifying Conditions are not being saved when user leaves page using breadcrumb
Adding a condition and parenthesis will loose parenthesis after saving. STEPS TO REPRODUCE: Log on App Admin -> Projects -> Edit any project -> SLA.
CMS-XML SBM: When saving an SLA Clause, the open parenthesis is removed and the AND condition is changed to OR
When adding and SLA Clause (App Admin > Projects > any project > SLA ), parenthesis are not removed automatically. For example, when this condition is saved:
CMS-XML Calendar without any time ranges may cause infinite loop in SLA engine - No SLA status
Calendar without any time ranges may cause infinite loop in SLA engine - No SLA status
CMS-XML Error getting SLA data: Not Found and ERROR obtaining SLA Status from: http://localhost/sla/slaServices/reportService/getSLAInfoForItem/1040/20?sdfServerURL=http://localhost
Error getting SLA data: Not Found and ERROR obtaining SLA Status from: http://localhost/ sla /slaServices/reportService/getSLAInfoForItem/1040/20?sdfServerURL=http://localhost
CMS-XML Calendar without timeranges may cause infinite loop in SLA engine - The SLA widget shows “No SLA status” for these items - CPU high on Common Services server
Calendar without timeranges may cause infinite loop in SLA engine - The SLA widget shows “No SLA status ” for these items - CPU high on Common Services server
CMS-XML Occasional user cannot see SLA status on an item they can see
Occasional user cannot see SLA status on an item they can see
CMS-XML How can I get a listing report that shows items that I own at a high risk of breaking an SLA?
Example of using the Advanced SQL Conditions on a listing report to give all items that a user owners that has a high risk SLA are shown. This example is based on the Service Request Process App delivered as part of SRC but can be changed according to your requirements.
CMS-XML Running SLA Report get "No entity found for query"
When you run the SLA Status Report you may see the following error. "No entity found for query"
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs