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 Deleted category and service comes back after a deploying Service Request
You can delete the out of box categories and services. However, after deploying Service Desk from Composer, all of the out of box categories/services came back and now appear in SRC.
CMS-XML isDeleted returns FALSE for deleted users in admin getUsers web service call if SECTIONS-SPECIFIED is used
Steps to reproduce: - log in to Application Administrator and delete one user - in SoapUI define a new getUsers (using the admin web services) web service request as follows:
CMS-XML Deleted out-of-box category comes back after a deploy
2) Delete the Facilities category. 3) Deploy Service Request . 4) Notice that the category re-appears.
CMS-XML "Please contact your administrator" errors thrown at the top of SSM - Service Request forms
After loading this process app in Composer, open the aforementioned custom forms and go to the Actions tab in the Property Editor. Edit the "Form Load: SSM Formatting" form action. One of the "Then" statements will be to execute a line of javascript that attempts to call a report by the reference name "TSM_CONFIG_ITEMS.CMS.ActiveServices". That entire "Then" statement can be deleted if you do not plan to use the CMS application.
CMS-XML Migrating Service Definitions and SLAs to a Different Environment
Includes service definitions and SLAs that reference projects that cannot be detected. For example, if a service request references a project that is later deleted , it will be exported.
PDF SOO Upgrade Guide
Depending on how you used the Service Request and Incident workflows in version 3.0, there are three upgrade options for the Service Desk process app: • Upgrade and delete all existing Service Desk data. For details, see Upgrading 3.0 Process Apps and Deleting Existing Service Desk Data [page 34].
HTML Serena® ChangeMan® ZMF 6.1 Readme File Last Updated on 2 December 2008
3.0 Known Issues There are known issues when you make Serena XML Services requests against change packages in deleted or archived (D/A) status. Refrain from building Serena XML Services calls that retrieve data from D/A packages.
HTML Serena® ChangeMan® ZMF 7.1 Readme File Last Updated on 5 January 2011
3.0 Known Issues There are known issues when you make Serena XML Services requests against change packages in deleted or archived (D/A) status. Refrain from building Serena XML Services calls that retrieve data from D/A packages.
HTML Serena® ChangeMan® ZMF 7.1 Readme File Last Updated on 12 November 2010
3.0 Known Issues There are known issues when you make Serena XML Services requests against change packages in deleted or archived (D/A) status. Refrain from building Serena XML Services calls that retrieve data from D/A packages.
HTML Serena® ChangeMan® ZMF Patch Release 6.1.1.01 Readme File Last Updated on 2 December 2009
5.0 Known Issues There are known issues when you make Serena XML Services requests against change packages in deleted or archived (D/A) status. Refrain from building Serena XML Services calls that retrieve data from D/A packages.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs