Introduction
With the release of ST-OST Support Package 14 (SP14) for Focused Build in SAP Solution Manager, we have come up with some new and exciting features in Mass Change Operations application and Requirements Management application. The release also contains improvements in some areas of these applications. You can find more information about all the improvements in different areas of the Requirements-To-Deploy process in this blog.
Mass Change Operations:
Change of Project Name and Project Phase for Defect Corrections:
In the Defect Corrections process type, users can now modify the Project Name and Project Phase columns in the result list table, provided the following prerequisites are fulfilled:
An Open Defect Correction:
is set to a user status below ‘Handed Over to Release’, andhas the Priority ‘Medium’ or ‘Low’ andhas no Work Package Assignment.
Changing only the project name for a defect correction is not permissible. If a project name is selected without selecting any project phase, an error message is raised at the line-item level in result list table and at the field level in the Mass Change dialog.
Fig 1. Mass Change Operations – Defect Corrections Screen
In addition to this, the value help for Project Phase would list only those project phases for the selected project name which fulfil the below condition:
The status of the release assigned to project phase must be Prepare or Build. Reassignment is not allowed for the Release Phase ‘Created’.If the open Defect Correction has a DocFlow/Task List Assignment, then the Target Release, that is assigned to the selected Project Phase for reassignment, must have a Task List as well.If the open Defect Correction does not have a DocFlow/Task List Assignment, then the Target Release, that is assigned to the selected Project Phase for reassignment, must not have a Task List as well.
The Project Phase value help in the Mass Change dialog also follows the above conditions for the display of project phases.
Redesign of Mass Change Dialog as per SAP Fiori Design Guidelines:
The re-design of Mass Change Dialog is now extended to all the process types. The new Mass Change Dialog follows the SAP Fiori Design guidelines and has the same behavior that was introduced in the Mass Change Dialog for Requirements process type in the past. Please refer this blog for more information.
Requirements Management:
Assignment of Work Packages to Requirements with no Solution Documentation:
Users can now assign Work Packages, whether they are assigned to a Solution Documentation or not, to Requirements that do not have a Solution Documentation assigned.
In the past, the Assign Work Package dialog would default the Solution filter to ‘No Solution’ if the selected requirement in the work list had no Solution Documentation assigned to it. This behavior restricted the users from assigning Work Packages with Solution Documentation to such requirements.
Fig 2. Previous behavior – Solution filter was defaulted to ‘No Solution’
With the recent update to the Assign Work Package dialog, the Solution filter becomes editable when the selected requirement has no Solution Documentation assigned. This will allow users to search for Work Packages with or without Solution Documentation.
Fig 3. Updated behavior – Solution filter is now editable only for Requirements with No Solution
It is important to note that there is no change in the behavior for Requirements with Solution Documentation. The filter for Solution in Assign Work Package dialog will remain non-editable in such cases.
This fix is available till ST-OST Support Package 12 (SP12) for Focused Build in SAP Solution Manager.
Redesign of WRICEF Sub-Classification field:
Fig 4. Re-designed UI field for WRICEF Sub-classification
The WRICEF Sub-Classification field has been updated to include standard SAPUI5 control, enhancing accessibility and aligning with our product standards. The core functionality of the field remains the same. However, this field has been updated throughout our Focused Build Fiori applications.
Key Takeaways:
Project name and Project phase can be changed from the result list for open Defect Corrections in Mass Change Operations provided certain criteria are met.The new Mass Change Dialog in accordance with Fiori Design guidelines is now available for all the process types in Mass Change Operations.Work Packages with Solution Documentation can now be assigned to Requirements that do not have any Solution Documentation assignment.WRICEF Sub-classification field is re-designed using a standard SAPUI5 control to enhance accessibility. There is no change in the core behavior of the field.
Please feel free to leave feedback in the comment section or submit any questions you may have on this page. You are also encouraged to follow SAP Solution Manager and Focused Build for SAP Solution Manager to stay updated with the new features and improvements.
Important Links and Resources
Usage RightsUnwrapping the Latest Innovations: Support Package 14 for Focused Build Learn how SAP Activate and Focused Build with SAP Solution Manager is working togetherALM Community page
IntroductionWith the release of ST-OST Support Package 14 (SP14) for Focused Build in SAP Solution Manager, we have come up with some new and exciting features in Mass Change Operations application and Requirements Management application. The release also contains improvements in some areas of these applications. You can find more information about all the improvements in different areas of the Requirements-To-Deploy process in this blog. Mass Change Operations: Change of Project Name and Project Phase for Defect Corrections:In the Defect Corrections process type, users can now modify the Project Name and Project Phase columns in the result list table, provided the following prerequisites are fulfilled:An Open Defect Correction:is set to a user status below ‘Handed Over to Release’, andhas the Priority ‘Medium’ or ‘Low’ andhas no Work Package Assignment.Changing only the project name for a defect correction is not permissible. If a project name is selected without selecting any project phase, an error message is raised at the line-item level in result list table and at the field level in the Mass Change dialog.Fig 1. Mass Change Operations – Defect Corrections ScreenIn addition to this, the value help for Project Phase would list only those project phases for the selected project name which fulfil the below condition:The status of the release assigned to project phase must be Prepare or Build. Reassignment is not allowed for the Release Phase ‘Created’.If the open Defect Correction has a DocFlow/Task List Assignment, then the Target Release, that is assigned to the selected Project Phase for reassignment, must have a Task List as well.If the open Defect Correction does not have a DocFlow/Task List Assignment, then the Target Release, that is assigned to the selected Project Phase for reassignment, must not have a Task List as well.The Project Phase value help in the Mass Change dialog also follows the above conditions for the display of project phases.Redesign of Mass Change Dialog as per SAP Fiori Design Guidelines:The re-design of Mass Change Dialog is now extended to all the process types. The new Mass Change Dialog follows the SAP Fiori Design guidelines and has the same behavior that was introduced in the Mass Change Dialog for Requirements process type in the past. Please refer this blog for more information.Requirements Management: Assignment of Work Packages to Requirements with no Solution Documentation:Users can now assign Work Packages, whether they are assigned to a Solution Documentation or not, to Requirements that do not have a Solution Documentation assigned.In the past, the Assign Work Package dialog would default the Solution filter to ‘No Solution’ if the selected requirement in the work list had no Solution Documentation assigned to it. This behavior restricted the users from assigning Work Packages with Solution Documentation to such requirements.Fig 2. Previous behavior – Solution filter was defaulted to ‘No Solution’With the recent update to the Assign Work Package dialog, the Solution filter becomes editable when the selected requirement has no Solution Documentation assigned. This will allow users to search for Work Packages with or without Solution Documentation.Fig 3. Updated behavior – Solution filter is now editable only for Requirements with No SolutionIt is important to note that there is no change in the behavior for Requirements with Solution Documentation. The filter for Solution in Assign Work Package dialog will remain non-editable in such cases.This fix is available till ST-OST Support Package 12 (SP12) for Focused Build in SAP Solution Manager.Redesign of WRICEF Sub-Classification field:Fig 4. Re-designed UI field for WRICEF Sub-classificationThe WRICEF Sub-Classification field has been updated to include standard SAPUI5 control, enhancing accessibility and aligning with our product standards. The core functionality of the field remains the same. However, this field has been updated throughout our Focused Build Fiori applications.Key Takeaways:Project name and Project phase can be changed from the result list for open Defect Corrections in Mass Change Operations provided certain criteria are met.The new Mass Change Dialog in accordance with Fiori Design guidelines is now available for all the process types in Mass Change Operations.Work Packages with Solution Documentation can now be assigned to Requirements that do not have any Solution Documentation assignment.WRICEF Sub-classification field is re-designed using a standard SAPUI5 control to enhance accessibility. There is no change in the core behavior of the field.Please feel free to leave feedback in the comment section or submit any questions you may have on this page. You are also encouraged to follow SAP Solution Manager and Focused Build for SAP Solution Manager to stay updated with the new features and improvements.Important Links and ResourcesUsage RightsUnwrapping the Latest Innovations: Support Package 14 for Focused Build Learn how SAP Activate and Focused Build with SAP Solution Manager is working togetherALM Community page Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
+ There are no comments
Add yours