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 DimCM: Pulse: When trying to open a request in Pulse, it returns an Internal Server error
DimCM: Pulse : When trying to open a request in Pulse , it returns an Internal Server error
CMS-XML Dim CM 14.x: EXT4700070E The request to Dimensions CM Pulse was not successful: Forbidden.
When selecting a Request in Desktop Client the following error is shown: EXT4700070E The request to Dimensions CM Pulse was not successful: Forbidden.
CMS-XML DimCM: Desktop Client: The request to Dimensions CM Pulse was not successful. SSL peer certificate or SSH remote key was not OK
When selecting a Request or a Review in the Desktop Client, an error occurs in the command line view of
CMS-XML DimCM: PulseUno: When attempting to open a request from within Pulse using the Open in Dimensions CM Web Client, a 'loading' page occurs when using Chrome
When using PulseUno and reviewing a Dimensions CM request , the Open in Dimensions CM Web Client will present a 'loading' page. If a refresh is done, an error of 'There may be problems with requested link' occurs.
PDF Dimensions CM Pulse Agile – Evaluation Tutorial
... 3: Configure Request Types .. ... : Create a Request (Story) ... : Update the request ... ... : Action the request ... ... and action the request ................................ ... .................... 10 Step 12: Modify the remaining story points and close the request ... ...
CMS-XML DimCM: Pulse: User cannot edit a Date attribute via Pulse
User is trying to edit a Date attribute of a request via Pulse . User is able to click the Calendar button next to the date attribute field, and click a date there. However, the attribute is not updated, it stays blank.
CMS-XML Dim CM 14: Default value of attribute in blocks (MFMV) not populated when creating request
The default values assigned to change request attributes are not populated when requests are created using Pulse CM. It was observed that the issue affects the block attributes (Multi Field, Multi Value) but not the Single Field/Single Value and Single Field/Multi Value attributes.
CMS-XML KM-Dim14: Pulse Agile SM attributes mapped to valid sets do not use always the correct columns
Single-field multi attributes created in 14.3 Pulse Agile requests will all use the first column in the valid set instead of using the assigned columns.
CMS-XML KM-Dim14: Cannot create request with empty summary/acceptance criteria when request type maps this to a CM attribute
When creating a request from the Pulse client it can return an error if a mapped attribute does not have a value entered before saving, even if the attribute is not mandatory.
CMS-XML CM 14.3 - Pulse Agile – Evaluation Tutorial
It allows you to do the following: Organize requests into backlogs. Execute requests in iterations.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs