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 It is too easy to lose changes to SLA clauses - no prompt to save changes
This means that your changes have been lost without warning. If you see that the Save and Discard "buttons" become active (not greyed out), you should remember to save when navigating inside the SLA definition.
CMS-XML SLA rules do not change to "Active" when start date arrives
For example, initially, the SLA is saved with the Status of Inactive and a "Starts On" date of '7/15/2013 12:00:00 AM'. After the "Starts On" date passes, the status is NOT changed to Active.
CMS-XML Warning when adding Notification to SLA "Sorry, You cannot modify clause action because SLA is out of date."
Steps to reproduce: - Create a new SLA - add a clause to the SLA
CMS-XML SLA does not become unbound if update transition and conditions changes
SLA's should become unbound if they no longer satisfy conditions of the clauses . This works fine except for with the update transition.
CMS-XML SLA Clause: Qualifying Conditions are not being saved when user leaves page using breadcrumb
EXPECTED RESULT: Qualifying Conditions must be saved with all changes . ACTUAL RESULT:
CMS-XML About SLA Load Level Settings
You configure SLA to run at one of these internals depending on the number of users and requests that are serviced in your environment. The SLA engine uses a set of user-defined clauses that are periodically compared against new items and change records, which then triggers specific actions if a clause comes true. The SLA level that you set determines how often the SLA engine compares its clause set to these items.
CMS-XML Error when creating SLA from service in SRC - Error in SQL statement reading TS_NOTIFICATIONCONDITIONS table
If you edit a project from the service in SRC and try and define a new SLA then when defining the condition in the clause you get the following error - "Error in SQL statement reading TS_NOTIFICATIONCONDITIONS table.
PDF SOO Installation and Configuration Guide
In the SLA Settings section, you throttle the load-bearing capabilities for SLA depending on the number of users and requests that are serviced in your environment. The SLA engine uses a set of user-defined clauses that are periodically compared against new items and change records, which then triggers specific actions if a clause becomes true. The SLA level that you set determines how often the SLA engine compares the clauses to these items.
PDF Installation Guide and Configuration Guide
In the SLA Settings section, you throttle the load bearing capabilities for SLA depending on the number of users and requests that are serviced in your environment. The SLA engine uses a set of user-defined clauses that are periodically compared against new items and change records, which then triggers specific actions if a clause comes true. The SLA level that you set determines how often the SLA engine compares the clauses to these items.
CMS-XML SLA Notifications from SSM Solutions also appear in the Application Administrator section for Notifications
(2) If you have edited the Notification via the App Admin Standard Notification Editor and are using it as a Standard Notification then please create a new Notification for this purpose and configure accordingly. ... This will fix the SLA Notification and remove the rule . You will also need to check your subscribers to this SLA Action Notification to ensure it is only going to those Users that should be receiving it.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs