2025.5.0 - Process Builder Integration, MDG Integration and other bug-fixes
This release has major improvements
Features
-
Process Builder has now the feature to regenerate in case there are any changes in the Change Record or the Task rule.
- Regeneration has to be triggered manually by the user before performing process action.
- Regeneration can be done with or without version.
- Regeneration with version provides the option to copy custom tasks added manually by the user.
- Finalize action should be performed to continue with the regenerated version.
- Fixed the issue with parallel task and sequential task adding to the right hierarchy of the Process Builder tree
- Editing and Deactivating of task is restricted to only optional task as per BRF+
- Deleting of task is possible only for custom added task
- Deactivating a parent task automatically deactivates its child tasks, and a child task cannot be activated independently.
- For more details, refer to Process Builder
-
MDG-M Integration is now part of Change Record processing
- Option to create MDG-M request during the Change Record processing in the process route is enabled
- User has the flexibility to create requests for the materials relevant using the exits for choosing materials relevant for MDG processing.
- API to complete the CR process route when the MDG process is completed is available.
- Automatic completion of CR process work-item based on the MDG status.
- Overview on the list of MDG process is available as a Fiori App first version which will be further improved with more features in next version.
- For more details, refer to PLM CR Integration with SAP MDG-M
-
Handle Process Exception and Agent Exception using new BRF+ decision table
-
During the Change Record processing various process exceptions are handled and the corresponding admins are addressed with the task to correct them and proceed the process.
- Exception during status change due to missing customization
- Exception during task creation due to missing customization or BRF+ decision table entry for a particular status
- Exception during missing agent for a specific task
-
Admin gets the exception task in the same status with error log written to the work-item log of the previous background service function.
-
For more details, refer to Exception Handling in Process Control
-
-
Cancelling of existing work item when the status is changed manually so that on-going work-items are cancelled and work-item for new loaded status is created.
- When the admin or key user with valid role changes the status of Change Record manually while the workflow is still in progress, ongoing tasks are cancelled and new process route tempalte is loaded and work-items created for the loaded status.
- When the admin or key user with valid role changes the status of Change Record manually while the workflow is not started, new process route template is loaded and the existing template will be cancelled without creating work-items.
Bug Fixes / Improvements
- Removed Entity Name in Field control BRF+ as this is not relevant for Change Record Header based field control implemented currently.
- Mass Upload of Teams is now controlled by authorization to restrict only the right administrators to perform the creation of Teams.
- Fixed ATC checks and removed the usage of restricted APIs causing ERROR for clean core checks and used the released API wherever possible.
- Fixed the issues with Process Builder refresh. Additionally Refresh button is available to refresh data on demand.
- Process Builder now shows the agent determination source. When a agent is fetched from Teams and Responsibility, the name of the Team is displayed in the Agent pop-up of Process Builder.
- Process Builder has the option to show only Active Tasks or all Tasks
- Search help for maintaining the Task ID, Agent Type and Agent in BRF+ is now available making it convenient for the Admins to maintain without referring to the customization.