R2022x FD01 (FP.2205)
- Removing Change Required from Objects
- You can now configure the minimum role required to remove change control from an
object to be based on access privileges.
Benefits: When this
option is selected, any user with access privileges to demote or modify the object
can remove Change Required from a change controlled object.
- Allowing Maturity Change to Released if Content is the Latest Revision
- You can use the new access rule Allow change maturity to Released if used
content is the latest released revision along with the maturity
transition control Reject if any of the Governed Children is not on Target
State to allow maturity transition to the Released state only of the
content is the latest released revision.
- Automatically Freeze Objects Impacted by a Change Action
- You can now configure the option to automatically promote the objects impacted by a
change action to the Frozen state when the change action is promoted to the In
Approval state.
Benefits: In the context of a single designer,
this option helps to reduce the number of interactions to promote a change action to
the In Approval state.
- Change Request Orchestration
- Your business administrator can configure the option to create change actions only
under change orders. In this case, a change order is created when the change request
moved to the Approved state and the change actions are added to the change order.
R2022x GA
- Change Action Approval Process
- You can now use a business logic to define the approval process for a change
action.
For more information, see Change Management in
the Data Setup guide.
- Subtyping
- Subtyping of change objects (change request, change order, change action, and impact
analysis) is supported only on on-premise and private cloud environments. Public cloud
environments are not supported.
|