How My Request Filter works on the Mobile App<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Symptom: On Now Mobile -> Home -> My Item -> My Requests Incident Item Stream and RITM My Request Stream List Streams are not accessible. The purpose is to use the My Request Filter to maintain the Data Item of the List Streams. How this is implemented: 1. Read only Allow if Read ACL on the sys_sg_item_stream. /sys_security_acl.do?sys_id=bb1c8be187403300e0ef0cf888cb0b42 It returns false if request_filter created for the Mobile and the item_stream. Hence, the admin user cannot maintain the List Stream to change the Data Item. 2. A similar ACL on the sys_sg_data_item to prevent the admin user from modifying the data item directly. /sys_security_acl.do?sys_id=78290f2187403300e0ef0cf888cb0b9e 3. Business Rule "My Request Mobile Metadata" is created to sync filter condition to the Data Item of the List Stream. /sys_script.do?sys_id=92f5dea487003300e0ef0cf888cb0bea The customer can create their own filter and associate it with the List Stream. If the customer needs to hide the List Applet associated with the My Request Filter, they need to remove the List Applet. Deactivating My Request Filter just gives Data Item maintenance back to Data Item form/Mobile App Builder.