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 while creating / editing an existing notification the affected part table (top right corner) is filtered in the frontend. This leads to several issues.
Pagination (is not correct as frontend filters data)
Autocomplete Filter (shows all available assets and not only affected assets)
When we use the assetAsBuilt API to retrieve assets additionally filtered by the affectedPartIds then the frontend pagination is fixed and we do not need to filter this data in frontend.
Additionalliy to fix the autocomplete issue we would also need to adapt the input to accept a assetId to only show autocomplete suggestions based on available data in the affectedParts table.
Acceptance Criteria
Pagination of affected part works.
Frontend uses the backend filter mechanism to:
only get a subset of the parts (affected parts) to control this it will use the affectedPartIds as filter on all assetsAsBuilt.
only get a subset of the parts (available parts) to control this we give the affectedPartIds as a exclusion filter to the assets api
Backend accepts a list of asset ids which should be excluded from the result set of assets api (to be able to filter the available parts by the parts which have been moved to the affected parts table)
GIVEN Edit or Create Notification Dialog is open WHEN adding assets from available parts to affected parts table the assets are removed from available parts table
GIVEN Edit or Create Notification Dialog is open WHEN removing parts from affected parts the assets are added to available parts table
Out of Scope
...
The text was updated successfully, but these errors were encountered:
ds-mwesener
changed the title
[Backend] Notification Create/Edit: Adapting AssetsAsBuilt API to allow filtering for partIds (affectedParts)
[Backend] Notification Create/Edit: Adapting AssetsAsBuilt API to allow filtering for partIds (affectedParts) and (available parts)
Apr 16, 2024
Tested on E2E.
Pagination works. Filter mechanism works.
Some problems are present. Those are already addressed here: #844
This issue is ready for review and I will retest 844 once the issues are resolved.
As ... , a user
I want ... , to see only affected parts on my notification
so that ... I have control what asset is within my notification
Link
Hints / Details
When we use the assetAsBuilt API to retrieve assets additionally filtered by the affectedPartIds then the frontend pagination is fixed and we do not need to filter this data in frontend.
Additionalliy to fix the autocomplete issue we would also need to adapt the input to accept a assetId to only show autocomplete suggestions based on available data in the affectedParts table.
Acceptance Criteria
GIVEN Edit or Create Notification Dialog is open WHEN removing parts from affected parts the assets are added to available parts table
Out of Scope
The text was updated successfully, but these errors were encountered: