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 Internal Names for States, Transitions, and Projects in SBM
Internal Names for States, Transitions, and Projects in SBM
CMS-XML Transition/state internal name validation is case sensitive
Transition/state internal name validation is case sensitive
CMS-XML Serena Request Center: Internal names created with high ascii characters fails
Serena Request Center: Internal names created with high ascii characters fails
CMS-XML The SBM Composer deployed two states with the same Internal name.
The SBM Composer deployed two states with the same Internal name .
CMS-XML SSM links should use Internal Names for transitions, but do not
SSM links should use Internal Names for transitions, but do not
CMS-XML RLC: List of internal plugin action names if needed for Task Action Rules
You can get this name by copying it from a deployment or failure task, using the provided copy button beside the action field. However, this requires the privileges to edit a task, and you may not have access.
CMS-XML DA: Launching Agents with conflicting names - do they need a different internal id?
This feature does indeed give the agent a new name . However, the id should always be unique, this is how we distinguish agents. The general recommendation for such cases is to keep the internal id empty in the AMI.
CMS-XML SRA Agent registration uses internal UID to register rather than agent name
#Sat Apr 13 20:17:04 BST 2013 install.service. name =SRA-Agent locked/agent.brokerUrl=failover\:(ah3\://WIN-8KB096R5C2A\:7918)
CMS-XML "Internal project "PRODUCT:PROJECT_NAME" may not be directly upgraded." message during upgradevrs operation
" Internal project "PRODUCT:PROJECT_ NAME " may not be directly upgraded." message during upgradevrs operation
CMS-XML SBM: Internal variables ids_transition_name, ids_project_name, ids_item_name contain extra ' '
There are a few internal variables used by the Application Engine when rendering forms. Some of these (ids_transition_ name , ids_project_ name , ids_item_ name ) now include an extra non-breaking space on the end of the value. If a customer was using these variables within a custom script, the scripts may not behave as expected.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs