|
Results |
|
KM-Dim9: Originator and Creator in Dimensions
KM-Dim9: Originator and Creator in Dimensions
|
|
|
DIM:$Originator role is only role which allows items to be actioned to new state in lifecycle
DIM:$ Originator role is only role which allows items to be actioned to new state in lifecycle
|
|
|
10.x / 2009Rx / 12.x : how to change the owner of an item ?
This can be achieved by using the command UIA with the / originator = option. This is documented in the Command-Line Reference Guide.
|
|
|
DIm cm : how to pass parameters when executing dmpmcli addrules.js script?
To Status = RAISED Role = $ ORIGINATOR displayable = true
|
|
|
Dim12: Baselines: What role is needed to create a baseline ?
"Generally, to create a baseline you must have one of the roles for its specified top design part that are required to action it from its initial lifecycle state to a new state. However, if a user with the role PRODUCT-MANAGER has assigned the top design part role $ ORIGINATOR to the first transition in the lifecycle for this baseline type, any Dimensions user can create a baseline of this type provided they have a role (any will suffice) on the top design part on which the baseline is being created."
|
|
|
KM-Dim7: If you move an item backwards in the lifecycle - in which pending list will the item appear?
The only exception is when items are actioned from $TO_BE_DEFINED to the initial lifecycle state, then the item will pend only for the $ ORIGINATOR . In the case that an item is actioned from any other state to the initial lifecycle state, the item will pend for all users holding the appropriate role for the item.
|
|
|
KM-Dim7: Making Detailed Descriptions Mandatory
9. Click on the pull-down arrow and select PCMS_CHDOC_DETAIL_DESC. 10. Select the $ Originator role. 11. Deselect the 'Display in the Role Section Button'.
|
|
|
Dim10: New Request dialog - General Tab - Description Field Cannot Be Added
In the Administration Console, under Request, user needs to select the affected request type, then go to the Lifecycle tab and open the Lifecycle Edit dialog. Select the Attribute Rules tab and look for the PCMS_CHDOC_DETAIL_DESC attribute, which should apply to FROM state of $TO_BE_DEFINED for Role $ ORIGINATOR . If it is not there, user needs to add it; this should correct the problem.
|
|
|
DimCM: Are there reserved attribute names which should not be used when defining new attributes?
CREATE_DATE ORIGINATOR PHASE
|
|
|
Dim 10: MAIL_OPTION values for e-mail templates
MAIL_OPTION. = 1 => new chdoc MAIL_OPTION. = 2 => email originator when closed MAIL_OPTION. = 3 => email parent holder when child closed
|
|
|