- SAP Managed Tags:
Hello SAP Community Member!
We are glad to introduce to you a new feature in SAP Profitability and Performance Management Cloud Content Management screen called Environment Locking.
Previously, in SAP PaPM Cloud, it was possible to import an environment while another user was making changes to it. To avoid the risk of damaging the work of others, we are happy to introduce to you the Environment Locking feature during import overwrite. This locking mechanism in Modeling and Process Management, is now implemented.
The locking mechanism works as follows:
Scenario 1: Accessing Modeling and Process Management During Import Overwrite.
User A is importing the environment with overwrite environment set to “Yes”. User B wants to access its corresponding modeling or process management screen. The system displays a message on user B’s side, indicating the environment is currently unavailable (see Screenshot 1 below). This is also true if the user wants to access the Modeling or Process Management screen using a direct link while an overwrite import is ongoing.
The system offers the following UI elements:
Page buttons
- REFRESH THE PAGE
- Upon refresh, the system displays a message (see screenshot 1 above) if the import overwrite is still ongoing,
- Upon refresh, the system loads the Modeling or Process screen if the import overwrite is finished
- GO TO ENVIRONMENTS PAGE
- The system redirects the user to the Environment screen.
Scenario 2: Save Changes in Modeling During Import Overwrite.
User A is making changes on the Modeling screen. User B starts importing and overwriting the environment that user A is currently working on. Once user A saves the changes, the system displays the popup message as seen in the first screenshot to user A.
If a user has no Application Monitor role assigned, the popup message displayed is slightly different as shown in Screenshot 2 below.
Screenshot 2: User without Application Monitor role
Scenario 3: Save Changes in Modeling After Import Overwrite.
While User A is making changes in the Modeling screen, User B initiates the import overwrite of the environment that User A is modifying. Once the import overwrite is finished, and User A saves the changes, the system displays a popup message as displayed in Screenshot 3 below.
Screenshot 3: Environment import finalized
Scenario 4: Run Execution Activity in Process Management Before Import Overwrite.
If User A is currently working in Process Management and runs the activity, user B starts performing an importing overwrite while the activity is currently running. In this case, the system displays a popup message, on the Content Management screen of user B (see Screenshot 4 below).
That concludes this blog post! I hope you've found this informational blogpost about the Environment Locking feature interesting. Stay tuned for our next update. Thank you!
