Tag: SAP Cloud ALM

For posts relating to CALM

​​SAP Cloud ALM – What’s New in week 10​

Welcome back to our bi-weekly SAP Cloud ALM update! 

As SAP continues to enhance Cloud ALM, we’re here to bring you the latest innovations that streamline your processes and elevate your productivity. In this edition, we’re diving into the key updates from week 10 – giving you a closer look at how these new features help you work smarter and achieve more. Let’s get started! 

Implementation 

Tasks introduced search function for milestones. When linking a milestone to a date, it’s now possible to search for milestone names.

In Tasks, the item types of Project Task and User Story, the Create options are no longer restricted. These two items are always visible in the Create menu. 

In Processes, when selecting a solution activity, the documents assigned to that solution activity are now shown in a consolidated list, regardless of where the assignment was made. In other words, as well as showing documents that were assigned in scoping, this section now also shows any documents that were assigned to the solution activity in the list of solution activities within Process Authoring.

If a document has an icon in front of its title, this means that it was assigned to a solution activity in the Process Authoring app. Note that it’s not possible to unassign documents of this nature in this section. As documents always belong to a project, only documents belonging to the currently chosen project are displayed. 

To directly navigate to the respective document in the Documents app select a document’s title. 

Process Authoring introduced a new Delete button and checkboxes displayed to the left of the list of custom solution processes. Allowing now to delete multiple processes at once within the Process Authoring app. 

Note that if changing any of filter settings in the filter bar at the top of the UI, current selection disappears. Additionally, it’s also possible to clear current selection by choosing the “Clear Selection” icon to the right of the information banner. 

The Delete button only becomes active when selecting at least one solution process that is either archived or has a draft version only, as only these types of solution process can be deleted. 

Overview app has a new Defects card available showing an overview of the statuses and priorities of defects. 

Libraries allows now navigation directly to the Test Management app by using the assigned test cases of a library item. 

Documents has now relations to solution activities available. It’s now possible to assign or unassign relations to the solution activity from within the Documents app. The assigned relations are listed in the table “Solution Activities” on the object page of a document. 

In Analytics, addition to user types, it’s now possible to review checklists according to teams in the Quality Gates Reporting app. 

In Requirements, similarly to Tasks, the item type Requirement, the Create options are no longer restricted. The item type Requirement is always visible in the Create menu. 

In several Implementations applications it is now possible to split descriptions for items over multiple columns, allowing to maintain long descriptions for items. 

Operations 

Real User Monitoring has 2 new updates this time.  

The Real User Monitoring now supports data from SAP Analytics Cloud. It’s now allowing to see user interaction data within SAP Analytics Cloud in real-time. For instance, it can capture response times of individual stories, which are interactive reports in SAP Analytics Cloud. This feature currently focuses on the front-end components of SAP Analytics Cloud. Therefore, it can provide insights about real-time user experience on the front-end and help identify any performance issues quickly. 

Real User Monitoring has also now a new page called Change Points. A change point for a request name signifies a notable performance shift compared to the recent past, lasting for a brief period (not just single executions). Such a change point might suggest an event that warrants closer examination. Depending on the request type, different entities characterized by the request name are compared to detect change points. Now Real User Monitoring allows to monitor these change points.  

Integration & Exception Monitoring introduced us 3 new capabilities.  

The data collection for SAP Mobile Services is now orchestrated using Next Generation – Data Collection Infrastructure (NG-DCI). This simplifies the configuration process and allows for the automatic setup of services with SAP Cloud ALM. 

Integration & Exception Monitoring allows now to monitor messages for SAP Ariba Contract Price Renegotiation Add-on. Application gives a detailed status overview of the incoming and outgoing messages.  

Integration & Exception Monitoring has a new tab called Solving Tips in the exception details screen. This tab displays possible solutions to resolve the exception. These solutions are retrieved from an SAP knowledge base using the exception’s message. The proposed solutions are displayed as cards that show an extract along with the resource reference. It’s possible to choose a card and view the solution in detail in the corresponding resource, like SAP for Me. 

To refine the suggested solutions, entering more information such as program name or reporting components in the Fine-tune results with additional keywords field. After choosing Apply, the suggested solutions are then adapted based on the given keywords. 

Administration 

User Management introduced Table View to the Users page, offering a more convenient and organized way to manage large numbers of users. This view allows displaying the entire list of SAP Cloud ALM users in a grid format. 

The following user properties are available in the table columns: 

  • Name 
  • User ID 
  • Status 
  • Email 
  • Roles 

To view the user details, change a user’s role authorization, or process an approval request click on the respective row. 

Jira or SAP Cloud ALM? An exchange of blows between four test managers

Stefan: Welcome to our exchange of blows! Today, two teams meet to present their arguments in favor of their preferred test management tools. On the one side is Team Jira, on the other Team SAP Cloud ALM. Team Jira, why is your tool the best?

Team Jira: Clearly, because it is even more flexible than a Swiss army knife and not as cumbersome as your old SAP Solution Manager, which has been dubbed a pocket knife! With Jira, we can customize everything the way we need it.

Team SAP Cloud ALM: Well, but flexibility can also lead to chaos! Especially when you already have complex projects like an S/4HANA transformation, the customer wants nothing more than a solid framework and guidance. SAP Cloud ALM offers clear structures and guidance. We SAP customers pay nothing extra, and the tool is not licensed per user. The setup is simple and efficient, so even interns can easily get started. If you like, I can provide you with your own SAP Cloud ALM tenant within minutes.

Team Jira: But do you also have a wide range of variants? In Jira, for example, we have flexible dashboards. We can filter and tag everything as required by the project. And the onboarding of external testers? It’s quick and easy, as long as the company provides enough user licenses.

Team SAP Cloud ALM: Variant diversity is all well and good, but we rely on proven SAP best practice templates and use them to bring the SAP Activate Methodology to life. Have you tried mapping SAP Activate in Jira? Have fun with it…
Efficiency and structure lead us to our goal. And the development of Cloud ALM is based on user requirements. We have a strong community and SAP implements the “Influence Requests” of the community. That’s what you call customer orientation with a plan!

Team Jira: Structure is good, but innovation is better. We can expand with add-ons such as Xray or Confluence. No wish remains unfulfilled – everything just as the customer needs it.

Team SAP Cloud ALM: Oh yeah? I think you need your own Jira project so that you don’t lose track of the costs and the add-ons!

But let’s move on to the technical topics. How does defect management work for you, for example? We have complete end-to-end traceability with transport links – nota bene without having to configure anything. Defects are transparent, everyone knows immediately which retests are pending. And now hold on tight: we even have a direct link to the transport requests. No guessing game as to which correction belongs to which defect.

Team Jira: Defects run as bugs and are flexible to handle. The developer pushes it on, and that’s it. And for reporting? We set up our dashboards individually and thus maintain an overview at all times. Sure, a mistake can happen with the tags, but that’s solved quickly.

Team SAP Cloud ALM: Oh, you bend your reports to fit the evaluation. With you, reporting is an effort every time! With us, the dashboards are available out-of-the-box – there’s no need to make any improvements.

Team Jira: And what do you think of the test phase classification? I can easily control this in Jira via release cycles.

Team SAP Cloud ALM: Release cycles that do not control transports and changes are gugus for me. Naming and tags are completely sufficient for us. We have best practices for the test scope that can be used immediately. No step is left to chance and not a penny is spent extra. We have test plans that can also be tagged for the relevant phase. And again: we can even start deployments to the next system via our release cycles. But you’ll probably have another expensive add-on for that.

Team Jira: Right, there’s an add-on for that. Flexibility has its price!

Let’s talk about transparency. With our reports, we answer the question of whether everything has been completed without any problems.

Team SAP Cloud ALM: We have transparency thanks to the process hierarchies. Everything remains traceable and what was created in the project can simply be transferred to operations. We can tell you at any time whether the processes have been tested or whether a requirement is still being tested. No wishes remain unfulfilled.

Stefan: Thank you, Team Jira and Team SAP Cloud ALM! Your exchange of blows has given us an exciting insight into the strengths and weaknesses of both tools. Do you still have a feature that you are currently missing in your tools?

Team Jira: Yes, a PowerPoint export at the touch of a button would be brilliant.

Team SAP Cloud ALM: That would be handy! I would also like to see a comprehensive mass upload function with clear sequences for test cases.

Stefan: Many thanks to Team Jira and Team SAP Cloud ALM – that was exciting! Whether you prefer the flexibility and adaptability of Jira or the structure and clear lines of SAP Cloud ALM, both tools have their specific advantages in test management. Team Jira stands for agile customization and individualization, which is particularly useful in complex and variable projects. Team SAP Cloud ALM, on the other hand, focuses on efficiency and user guidance, perfect for SAP-driven projects in which best practices can be directly integrated.

In the end, the respective project or perhaps even the overall organization and the specific requirements will probably decide which tool best meets the test management requirements.

One thing is certain: both teams love their tools and use them optimally to ensure quality and transparency in their projects.

It can therefore be said that it is not just a question of the tool, but also of the correctly set up and utilized test strategy.

Thanks for reading and see you in the next exchange of blows!

SAP Cloud ALM – What’s New in week 8

Welcome back to our bi-weekly SAP Cloud ALM update blog! As SAP continues to refine and enhance the Cloud ALM experience, we’re here to keep you informed about the latest innovations designed to boost efficiency and simplify your workflows. In this edition, we’ll walk you through the key enhancements from week 8, showcasing how SAP is helping you achieve more with every update. Let’s dive in!

SAP Business Transformation Center

This time SAP has made 4 new features available for Scoping.

In the Manage Digital Blueprints app, there is a new chart which displays the distribution of transactional data per year. The chart is visible in the Solution Patterns section for time slice. This allows visualizing the impact of a time slice-based data reduction on the scope of digital blueprint and helps to make an informed decision when selecting a year for a time slice.

In the Select Company Codes app, it’s now possible to check the fiscal year start date of each company code in the company code list view. This helps to make scoping decisions for a digital blueprint for which it’s planned to activate the time slice solution pattern.

When a system scan fails due to an incorrect setup in the backend system, SAP Business Transformation Center now displays detailed instructions on how to fix the issue. These messages are visible in the system scan´s Activity Log section in the in the Manage System Scans app.

Additionally In the Manage System Scans app, when the software component check of a system scan fails, the activity log now provides more information on the missing system requirements, including the necessary SAP Notes to install on the source system and which software components are missing the minimum version required for the system to pass the check.

Implementation

Test Preparation has 2 new features.

To prevent accidental loss of test results, the deletion of test cases with existing test runs is now restricted to users with the role Project Administrator or Project Lead. Users with the Project Member role can still delete test cases that haven’t been executed yet.

It’s now possible to assign application library elements to test cases. This helps to ensure the application’s test coverage and improve overall traceability throughout the implementation project. It also allows to track the statuses of related test cases from the Libraries app.

The assignment itself takes place in the new Relations tab, which now also contains process hierarchy nodes.

Test Plans introduced Role-based restrictions on deleting and unassigning. To prevent accidental loss of test results, the following actions are now restricted to users with the role Project Administrator or Project Lead:

  • Deleting test plans that contain test cases with existing test runs
  • Unassigning test cases with existing test runs from test plans

Users with the Project Member role can still delete test plans and unassign test cases that haven’t been executed yet.

Processes allows now to display configurations for a solution process or solution activity.

When calling up the details for a solution process or solution activity in the Solution Process Viewer, we see information about any configurations that are assigned to them. As well as the name of any assigned configurations, we can also see their respective IDs and a icon, representing the Process Authoring app as the origin of where these configuration library types were created.

The Configurations section is currently only shown if corresponding assignments exist.

Process Authoring allows now to call up a history of actions from the icon located at the top of the list of custom solution processes. This history tracks every action that has been performed on custom solution process, along with the user who performed the action and the date and time. By default, we see the actions in chronological order with the latest action at the top, but it’s also possible to switch the order to show the oldest first.

In addition, we can also use the search or filter by a specific time range or action type, as listed below:

  • Created
  • Restored
  • Published
  • Created Draft
  • Edited
  • Archived
  • Deleted

Where appropriate, it’s also possible to open the corresponding custom solution process from the link within history.

Libraries now displays test cases that were assigned to applications.

Analytics allows now to see both direct and indirect assignments in the Solution Process Traceability app.

By clicking a bar chart in the Defects column, we can now view defects that are directly assigned to a solution process in the popup. If we also want to see indirect assignments, it’s necessary to enable them by using the Indirect Assignments button.

In several applications new test preparation owner and priority filter functionalities were introduced.

In the Solution Process Traceability, Requirement Traceability, and User Story Traceability apps, we can now find the test case owner in the popup that appears when clicking on a bar chart in the Test Preparation column.

In the Cross-Project Analysis app, by employing the test case owner and Priority filters, the Test Preparation and Test Execution charts are filtered accordingly, and clicking on the bars of the Test Preparation bar chart reveals the test case owner’s user name in a popover.

In the Project Overview app, the Test Preparation card responds to filters Assigned to: Me and Assigned to: All and features new display options By Status and By Priority. Additionally, it features a classification between automated and manual test cases, while the Test Execution card introduces a new By Priority dropdown filter.

In the Implementation area there is a new application called Deployment.

With the Deployment app, we can schedule and automate transport deployments of several features of a deployment plan throughout the system landscape. The central entity of the Deployment app is the deployment plan. For the deployment, all or only a subset of TMS managed transport requests assigned to the deployment plan are selected.

As a deployment manager it’s possible to use the app for:

  • Creating deployment schedules to deploy changes to quality, pre-production or production systems (this is not possible for ATO).
  • Creating feature status and/or release dependent, and recurring deployment schedules for features within the same project.
  • Editing and deleting deployment schedules.
  • Viewing scheduled deployments (target tenant only for TMS, not for ATO and CTMS).

Services

Issues and Actions Management has 2 new features available.

It’s now possible to create follow-up tasks of Type Requirement for the desired Project and Project Phase helping to organize and maintain tasks efficiently.

Issues and Actions Management now also synchronizes follow-up task status to actions meaning that change in the Status of the task in SAP Cloud ALM Tasks are now synchronized to actions in SAP Cloud ALM. Additionally, for tasks of Type Requirement, the Requirement Status in SAP Cloud ALM Tasks is synchronized to actions in SAP Cloud ALM.

If the Status of the action is Done and there is a change in the Status of the task in SAP Cloud ALM Tasks, the system does not overwrite the Status of the action in SAP Cloud ALM.

IT monitoring concept: How to secure your SAP landscape in the long term

As experienced SAP experts, we know how crucial good IT monitoring is for system stability, performance and business continuity. Nevertheless, it is often given a low priority – until disruptions occur. While the big projects are in the spotlight, monitoring remains in the background, although it is a critical success factor for business processes.

A well-thought-out monitoring concept not only ensures smooth operations, but also minimizes risks and costs:

  • Detecting problems early – performance bottlenecks or integration errors before they become critical and escalate
  • Aligning IT with business objectives – smooth processes for better service quality
  • Reducing downtime – proactive instead of reactive troubleshooting

SAP Cloud ALM (Application Lifecycle Management) offers a powerful solution for strategically and seamlessly integrating monitoring into your IT processes – for cloud, on-premise and hybrid SAP environments.

Developing a monitoring concept

An effective monitoring concept requires clear goals and a well-thought-out implementation. Here are the most important steps:

Evaluate the current situation

Who needs what monitoring data? What tools are already in place? Identify gaps and optimization potential. Analyze the landscape and stakeholders, and determine who will be affected by the monitoring process and how the data will be used. If available, evaluate existing monitoring practices and tools to understand what is already working well and where there are still gaps.

Define goals

What do you want to achieve? Is it performance, compliance, security or risk management? Monitoring should not only collect IT data, but also support key business processes.

Determine what you want to achieve through monitoring – identifying problems, improving performance, compliance or risk management. Don’t just focus on technical system metrics, but align your monitoring efforts with the priority of your business processes within the organization.

Determine what to monitor

Which systems and processes are critical? Choose meaningful metrics that provide actionable insights rather than just data overload.

From the identified systems and objectives, select the most important systems and processes to monitor, focusing on the most relevant metrics that provide actionable insights into the performance and health of your services and systems.

Implementation

Research and select monitoring tools that can collect and analyze data quickly and easily. For SAP-centric landscapes, SAP Cloud ALM is the ideal tool because it supports a variety of SAP products – cloud services and on-prem systems. Connect your systems agent-less and activate the various use cases available.

Analyze and interpret data

After the first round of data collection, you should evaluate the collected data based on your KPIs and objectives. Determine the normal operating ranges for your selected metrics and set a baseline. Based on this, you can set up thresholds, alerts and notifications.

Continuous improvement

IT systems continue to evolve – so should your monitoring. Think of monitoring as a living framework. Perform regular reviews to assess the relevance of current metrics and thresholds. Check whether monitoring is still aligned with business priorities after major system changes, such as upgrades or the introduction of new features. Ideally, the topic of “monitoring” should already be part of projects or enhancements so that monitoring is already active from day 1 after their introduction.

Conversely, the same applies to the monitored systems: Use the insights from the monitoring data to make continuous improvements to your systems.

Stay up to date

Train your team and managers so that they can make optimal use of new monitoring features and functions. Monitoring is a dynamic process that requires continuous development.

Why monitoring with SAP Cloud ALM is indispensable for “operational excellence”

SAP Cloud ALM is much more than a simple monitoring tool. It not only enables you to monitor your IT systems, but also to control the entire SAP operations and pave the way for operational excellence.

The capabilities of SAP Cloud ALM enable you to go beyond pure technical monitoring and to monitor relevant “business-critical” and application-related metrics to ensure that business processes are working. With its ability to integrate into hybrid landscapes, along with intelligent automation and transparent reporting capabilities, it is becoming an indispensable resource for any head of an SAP competence center or anyone responsible for SAP operations.

By integrating SAP Cloud ALM into your monitoring strategy, your team can ensure a resilient, efficient IT environment that supports the growth and long-term stability of your business.

Leverage blue.works’ proven expertise

Implementing an effective monitoring strategy in SAP Cloud ALM requires not only technical knowledge but also practical experience and a deep understanding of best practices. At blue.works, we bring the expertise gained from numerous successful SAP Cloud ALM projects to help companies develop and implement monitoring concepts that deliver real business value.

We can create a tailored, proven alerting and monitoring approach within SAP Cloud ALM that is customized to your specific needs and ensures that your systems remain optimized and resilient. Contact us to discuss how we can support you on your SAP Cloud ALM journey.

SAP Cloud ALM – What’s New in week 6

Welcome to the latest SAP Cloud ALM update blog! SAP continues to drive innovation and enhance the Cloud ALM experience with user-focused improvements. This bi-weekly series keeps you up to date with the newest features, enhancements, and optimizations. In this edition, we’ll cover the key updates from week 6, highlighting how SAP is helping you work more efficiently and achieve greater results.

RISE with SAP

RISE with SAP page in SAP Cloud ALM launchpad has now new application System View.

System View Dashboard displays system’s clean core compliance. From there it’s possible to:

  • Check if the current SAP S/4HANA product version installed on system is up to date and plan next system upgrade.
  • Monitor that system is configured for clean core data collection.
  • Review current extensions to evaluate and prepare for any potential issues on next upgrade.

To be able to access the System View dashboard on the SAP Cloud ALM launchpad, you must be a customer with a valid RISE with SAP contract.

SAP Business Transformation Center

SAP Business Transformation Center now supports the full migration of SAP Human Capital Management (HCM) data from SAP ECC to SAP S/4HANA.

SAP Human Capital Management (HCM) data is migrated entirely, without any filtering.

Modeling has new data dictionary scan restart option in the Manage Transformation Models app.

Now if data dictionary scan encounters an error, it’s possible to trigger it again by choosing Restart.

Implementation

  • Processes has new solution scenarios available in the list of supported solutions for Process Management:
  • SAP Services Content for Integrated Utilities
  • SAP Business Network for Supply Chain
  • SAP Best Practices for SAP S/4HANA Cloud Public Edition, Public Sector

Processes now also allows to display applications assigned to a solution activity. When calling up the details for a solution activity in the Solution Process Viewer, users now see information about the applications that are assigned to it. As well as the name of the application, it displays which application type it belongs to. Some examples of possible application types are the following standard content types, although other customer content application types are also possible:

  • SAP Fiori Application
  • Transaction
  • URL
  • SAP Web Dynpro Application

Additionally, if the application shown is a custom application and not a standard one, users also see the Display ID of the custom application that is stored in the Library for reference.

Keep in mind that the Applications section is only shown if the solution activity actually has an application assigned to it, otherwise it is not displayed.

In Process Authoring it’s now possible to upload solution activities and custom solution processes to a project. If there is a need to import content, for example as part of a migration, users can now upload custom solution processes to a project using a ZIP file or solution activities using a spreadsheet. There’s also provided templates in the system if needed.

Libraries now displays in detail view solution activities that were assigned to configurations. There’s also links available to navigate to the Solution Activity app.

Operations

Health Monitoring now supports SAP Datasphere.

Available metrics for it are Storage and Events.

Intelligent Event Processing has a new section, Outbound Logs, in the Event Situation Details page. 

In this section, it’s possible to view the status of event payload storage, the count of available payloads, and the time stamps of the first and the last payloads. The payloads are stored for events that have Store Event Payload for 24 Hours event action enabled.

The log count is also displayed in the Event Situations table in the Overview page.

Services

Issues and Actions Management has new Issue Status: Accepted. Setting a status of an issue to Accepted acknowledges the issue to SAP.

* Several areas

SAP is planning to remove the Belize themes shortly. It’s recommended to switch one of the SAP Horizon themes in user’s settings.

SAP Cloud ALM – What’s New in week 2 and 4

Welcome to the first SAP Cloud ALM update blog of 2025! As we embark on a new year, SAP continues its commitment to innovation and user-centric improvements in Cloud ALM. This bi-weekly update series keeps you informed about the latest enhancements, features, and optimizations. In this edition, we’ll delve into the highlights from the updates rolled out during week 2 and week 4, showcasing how SAP is enhancing the ALM experience to help you work smarter and achieve more.

SAP Business Transformation Center

It’s now possible to use Cloud Integration Automation Service (CIAS) to onboard the source and target systems for use with SAP Business Transformation Center. This service guides through the workflow and contains instructions for the manual and automated tasks, enabling an easy and quick integration configuration setup.

Modeling has 2 new features available.

There is now a new tab called “Filters” in the Transformation Object Details app, where is displayed a list of all transformation filters applied to a selected transformation object.

There is also a new tab called “Solution Patterns” in the Manage Transformation Model app, where are displays a list of the solution patterns applied to a selected transformation model. A “Solution Patterns” tab is also available in the Transformation Model Versions app, where it displays which solution patterns have been applied to the corresponding transformation model version.

The solution pattern that SAP Business Transformation Center currently offers is time slice.

Scoping allows now to use the time slice solution pattern to selectively exclude data before a defined fiscal year from migration scope, while ensuring that data related to open items, even if outside the time slice, is included. This allows to reduce the migration scope only to data that is necessary for operational, reporting or auditing purposes. This data reduction not only simplifies the migration process but also ensures a more relevant and valuable dataset at the end of the migration.

Implementation

Test Preparation enhanced it’s feature inserting images to test cases. Images that are inserted in test case are now retained when downloading and reuploading the test case.

Projects and Setup allows now to search by the system title or ID in the selection list of System Groups tab. This helps in finding the preferred system in a long list of systems.

Analytics displays now all deliverables that are not completed by using the “Not Completed” button in the Deliverables tab of the Project Progress Reporting app. By default, the “All” button is enabled to show all deliverables. Additionally, the “Completed” button shows all completed deliverables.

In Features, a Cross-Reference Check now includes object conflict details. In the “Check Details” view when selecting the conflict reason, now displays detailed information on how to solve the issue.

Features also allows now to download transport check results of all the conflicting or missing objects belonging to the same check type and target tenant in a single spreadsheet.

Guided Implementation has 4 new features available.

  • It’s now possible to manage the quality gates of a project in the app to ensure that all phase-specific quality criteria are met. The quality gate status and the checklist completion are now shown. Use the newly added link “Go to Checklist” to navigate to the Tasks app.
  • Phases without tasks are now clearly indicated. If no roadmap was selected for a new project that just has tasks in the Prepare phase, all other phases are hidden in the tab bar.
  • There are now icons for the different item types and statuses.
  • A filter for quality gate statuses was added to the app.

Process Authoring has new “Usage Status” filter in the list of solution activities. If there’s a need to delete solution activities, for example after performing a migration, a new filter helps to simplify the process. As it’s only possible to delete solution activities that are not used in a solution process, filter allows to display all activities that are not used anywhere. This gives opportunity to choose “Select All” in the list and delete all unused entries at once.

Process Authoring introduced also a two-step deletion process for custom solution processes using archiving to prevent users from unintentionally deleting data by mistake. It behaves slightly differently depending on the versions that exist.

  • If a custom solution process has draft and published versions, it’s possible to either choose to delete its draft directly or archive the custom solution process. Keep in mind that only unscoped custom solution processes can be set to Archived in Process Authoring.
  • If a solution process has a draft version only, it’s possible to delete this draft directly.
  • If a solution process has a published version only, it’s necessary to first archive the process and then delete it in a subsequent step.

Archived processes can then either be deleted or set back to active by choosing the “Restore” button. Restored custom solution processes are handled in the same way as active, unscoped custom solution processes.

Archived custom solution processes have the prefix [Archived] added to their title in the list of solution processes in the Processes app.

When a custom solution process has been archived, it’s no longer possible to edit its details, related diagrams or elements. Creating new diagrams, publishing and copying is also no longer possible unless restoring it to an active state.

Archived solution processes can no longer be scoped or mass edited, it’s not possible to change their status, Process Owner or Tag assignments in the Processes app.

Tasks has also 2 new features available.

  • Tasks allows now to use the spreadsheet upload to assign quality gates to project tasks and to assign requirements to user stories.
  • It’s now possible to assign responsible teams to checklist items.

Operations

Real User Monitoring continues to evolve, now extending its capabilities to include several new supported solutions:

  • SAP Task Center
  • SAP Data Quality Management, microservices for location data
  • SAP Predictive Replenishment
  • SAP Build Work Zone, standard edition
  • SAP Build Work Zone, advanced edition
  • SAP SuccessFactors Work Zone
  • SAP Cloud Portal service

Job & Automation Monitoring has new filters available in Analysis page, to further refine the jobs and automations displayed. Filters can be found under “Additional filters”, and they are:

  • Step/Executable: Filter by the step/executable name of the job or automation.
  • Executed By: Filter by the user who has executed the job or automation.
  • Scheduled By: Filter by the user who has scheduled the job or automation.

In Intelligent Event Processing, it’s now possible to view the Event Name and Service Type for the variant in the “Where Used” pane. Additionally, it’s now possible to use the “Live Search” to find variants using Event Name and Service Type information.