|
|
All Operating Systems: | | | | | All Solution Types: | | | | | Source: | | | |
| |
|
|
|
| |
Results |
|
Dim 12.2: Find Baseline works incorrectly with trailing space on Baseline ID field
|
Dim 12.2: Find Baseline works incorrectly with trailing space on Baseline ID field
|
|
|
|
Database error in deploy task when promoting baselines in parallel
|
Deploying baselines in parallel sometimes results in "Promotion of deployment unit < baseline id > to stage <new stage> has failed : DBI0004527E DBIO: Database I/O error occurred"
|
|
|
|
Dim12: Using Colon in the name of objects, such as projects, baselines and releases
|
When, in turn, you attempt to use the rename command or change id , the colon character is not a valid character and the following error is reported: Error: /NEW_ ID cannot be a full object specification, just an id . Prefixing the colon character with the "escape" symbol, i.e. "@:" makes no difference, but omitting the colon character allows the rename operation to complete successfully. Note: Release does not have a rename command.
|
|
|
|
Dim 10: PCMS_BASELINE_INFO doesn't show REPLICATED baseline
|
CREATE VIEW PCMS_ BASELINE _INFO ( PRODUCT_ ID , BASELINE _ ID , BASE_SEQ_NO, DATE_TIME, TOP_NODE_PART_ ID , TOP_NODE_PART_VARIANT, TOP_NODE_PART_PCS, TEMPLATE_ ID , OWNER, CREATION_MECHANISM, BASELINE _TYPE, TYPE_NAME, STATUS, DESCRIPTION, LIFECYCLE_ ID , LC_SEQ, WORKSET_UID, WORKSET ) AS SELECT
|
|
|
|
KM-DIM12.2: Reported Bug: Web Client: Fetch items from baseline fails for items no longer part of the project
|
Actual Result: For the removed item this error appears: "COR0005423E Item <ITEM SPEC> is not in Project <PROJECT ID >" Workaround:
|
|
|
|
RLM 4.5.0.3 (4.5.0 Hotfix 3) - Task status not updated; Redeploy Dimensions task; SOAP RequestTimeout; Same baseline going to multiple deployment areas
|
DEF262165 FF: Release Automation Deployment task does not update Release Control when it fails DEF262166 FF: Get "Invalid User ID or Password" errors in rlm.log file and Deploy Tasks are stuck at "In Progress" even though the task is complete DEF262168 FF: Unable to do a re-deploy to Dimensions.
|
|
|
|
DM12: The deploy script variable DMBLNID is truncated at 40 characters
|
A pre or post deploy script that makes use of the template variable DMBLNID to return the baseline ID , may have difficulty if the baseline ID is longer than 40 characters. When the variable is substituted, it will receive only the first 40 characters of the baseline ID.
|
|
|
|
SRA: Dimensons Plugin: How to use the GetBaselines step
|
Plugin execution reveals that the following property is generated and populated with the selected baseline ID . UIP Simply reference this property value as {p:UIP} in any subsequent steps.
|
|
|
Serena Application Release Manager Installation and Configuration Giude
|
APPLICATION DESCRIPTION ===> Application 1 OPTIONAL SKELETON RELEASE ID ===> APL1 (* for list) NORMAL BUSINESS HOURS FROM ===> 0001 TO ===> 0002 (HHMM) KEEP BASELINE BY SITE ===> NO (Y/N) ALLOW TEMPORARY PACKAGES ===> NO (Y/N) AUDIT LEVEL ===> 5 (0,1,2,3,4,5) CHECKOUT ENFORCEMENT RULE ===> 1 (1,2 ...
|
|
|
|
Slow performance with Desktop client over WAN
|
A defect has been submitted to R&D on this issue. A workaround would be to Customize views, remove some fields from the Primary view of Items, Requests, Baselines etc, such as Stage ID . Closing secondary views in the right-hand size of Desktop client should help as well
|
|
|
|
|
|
|
|
