You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the rollback is the scope of the provider component that uses the RBus APIs to set the DM parameters. Incase, if the set fails, the provider to revert to the original value
This approach creates an bug when using the rbus_setMulti API to set multiple DM parameter using this single API call.
If one or more DM parameter set fails during this multiSet operation, the current API only logs the failure, but still returns success to the provider. This eventually leads to error condition.
The implementation for rollback to be handled in the Rbus layer itself, so as if any DM parameters set fails it should revert to the original value and notify the provider with the right return code
This is of the requirement for USP for the atomic set operations.
The text was updated successfully, but these errors were encountered:
Currently the rollback is the scope of the provider component that uses the RBus APIs to set the DM parameters. Incase, if the set fails, the provider to revert to the original value
This approach creates an bug when using the rbus_setMulti API to set multiple DM parameter using this single API call.
If one or more DM parameter set fails during this multiSet operation, the current API only logs the failure, but still returns success to the provider. This eventually leads to error condition.
The implementation for rollback to be handled in the Rbus layer itself, so as if any DM parameters set fails it should revert to the original value and notify the provider with the right return code
This is of the requirement for USP for the atomic set operations.
The text was updated successfully, but these errors were encountered: