Financial Management Blog Posts by SAP
cancel
Showing results for 
Search instead for 
Did you mean: 
MilanMladenovic
Product and Topic Expert
Product and Topic Expert
401

Hello SAP Community members! 

I’m excited to share the improvements made to the Environment Screen in SAP Profitability and Performance Management Cloud Standard Model (SAP PaPM Cloud SM). In this blog we will explore the new design, which makes working with Environments easier and more intuitive. Actions like adding, editing, moving, and deleting are now clearer, with a structured and consistent flow. There’s no need to worry about accidental deletions or remembering to save—every change is confirmed and applied instantly. The interface is cleaner, and the process feels smoother, allowing users to focus on their work without unnecessary steps. With these improvements, managing Environments is now simpler, faster, and more reliable.

Adding, Copying, and Editing in Environments Screen

Before: 

Previously, adding, copying, or editing nodes and environments was done directly within the table through inline editing. Selecting “Add Node” or “Add Environment” activated an editable row where users could input the ID, version, and description. Copying through “Environment From” pre-filled these fields with data from the selected environment, allowing further change. Editing was accessed via a pencil icon on the right side of the row, enabling users to update only the description while the ID and version remained locked. 

MilanMladenovic_0-1739269165219.png

After: 

In the new implementation, actions such as adding, copying, and editing nodes and environments are now performed through pop-up dialogs instead of inline editing. Each dialog is labeled according to the selected action.  

Choosing “Add Node” or “Add Environment” opens a dialog where users can enter the ID, version, and description.  

MilanMladenovic_0-1739451473914.gif

Editing is now initiated from the header section, and the pop-up allows changes to the description while ID and version remain greyed out. 

MilanMladenovic_1-1739451572231.gif

Copying via “Environment From” opens a similar pop-up with pre-filled data for editing. 

MilanMladenovic_2-1739451593523.gif

Moving of Nodes and Environments

Before: 

Users can select the node or environment they wish to move, drag it, and drop it onto the available node on the screen. For instance, as illustrated in the image below, they can move the environment to one of two nodes in the same folder or to the parent node of its current location. To move it to a different node, they must first drag and drop it to a node that allows further movement to a child Node. For example, they can place it in the main folder and then continue the drag-and-drop process to reach the intended node. This method can be labor-intensive due to the manual selection of the target folder without a clear hierarchy, which may take some time.  

When the user moves to the target node, they must save the change by clicking the “Save” icon. If they make a mistake, they have “Undo” and “Redo” buttons to correct it.   

MilanMladenovic_2-1739269165222.png

After: 

In the updated Environment Screen, once users select their desired node or environment for moving, they need to click the “Move” option in the header. This action triggers a pop-up window, allowing the user to choose their preferred node either from the dropdown menu or from the node picker.  

MilanMladenovic_3-1739451658168.gif

The default value is set to Main (Root Node). Display between the main target field and the Node Picker hierarchy is synchronized. This feature is handy for users who don’t remember the exact name of the target node but know its parent. Choosing the parent node from the dropdown will highlight it in the node picker. After that, the user can select the child node where they want to move the selected node or environment.  

After clicking the “Move” button, the node or environment will be moved to the target node, which will be opened on the Environment Screen. This action will be saved automatically.  

Deleting of Nodes and Environments

Before: 

To delete a chosen node or environment, users should click the Delete button located in the header. This action will instantly remove the node or environment from the user interface, but users can undo or redo the change if they wish to revert it. Finally, they must click the Save button to confirm their changes. After saving, the undo and redo options will no longer be available.

After: 

In the new implementation, after selecting the node or environment they want to remove, users need to click on the “Delete” button in the header. However, this time, the node or environment will not be deleted immediately. Instead, a confirmation pop-up window will appear that shows how many nodes or environments will be deleted, and users need to confirm that they really want to delete them.  

After confirmation, users will receive an information blue message toast indicating that the process has started in the backend. Then, after it’s done, they will receive a successful green message toast. These messages provide clear feedback on the process and improve user experience. 

MilanMladenovic_0-1740408176856.gif

Conclusion 

The enhancement of the Environment Screen has made it more intuitive, efficient, and consistent. By replacing inline editing and drag-and-drop with pop-up dialogs, users now have a clearer workflow that aligns with other parts of the system. 

Key changes include: 

  • Automatic saving, eliminating the need for Save, Undo, and Redo buttons 
  • Edit and Move actions relocated to the header for better accessibility 
  • Deletion confirmation dialogs, preventing unintended data loss 
  • A move option with node picker, replacing manual drag-and-drop for environment movement 

These updates reduce complexity, minimize errors, and improve navigation, making interactions more intuitive and ensuring a more efficient workflow for users.  

I hope you find these updates helpful! If you have any questions or comments, feel free to post them in the comment section.

Stay tuned for the latest updates and insights on the next one. Thank you!