Dimensions CM and Pulse are using the ALM Octane REST API for External Request integration functionality. Some of the used APIs are available only in the technical preview mode requiring its enablement in the ALM Octane site configuration. Without this external request functionality Dimensions may fail with HTTP errors 400 or 403 or Pulse may fail to transition the ALM Octane ticket to the next phase once the associated Review in Pulse is approved.
Halt on failure is used within an Expert chain to determine whether the rest of the chain can be processed. The step will check the result of the last expert run and if a failure has been returned any further processing in the chain will be halted and the expert chain will return a failure status back to Pulse.
When user launches the Action dialog for an item (not Request) the dmpool process dies. The first clue is that when the dialog finally loads (take a moment) the file name field displays "Unknown" while the rest of the dialog looks normal. If you progress to the end you get a java connection reset message.
Copied item/directory structure from a Subversion system. Created the different worksets in the Desktop client as project type workset, empty project with baseline deployment selected (manual deployment) and left the rest of the options as default.
From ALM Octane release 15.1.90 the External Request integration with Dimensions CM may not function as expected following a change to make the REST API more secure. The change that was introduced affects the output of Octane REST APIs hiding user details from them. As a result Dimensions CM could mistakenly fail during Deliver operations reporting that the current user is not the owner of an Octane request used for Deliver when the user actually owns that request.
