Add CRUDF cmdlets around UserPreferences API endpoints for easy management of the Client Tools List View Customization
Since Tridion Docs 13/13.0.0 the Client Tools List View can be customized in visibility, order, width, sorting across the various list views. The local configuration is eventually stored on the user profile inside the repository.
The Client Tools do this based on User25.SetPreferences, User25.FindPreferences, User25.RetrievePreferences and User25.DeletePreferences API calls introduced in 13.0.0
This enhancement is about proper cmdlets with objects to make debugging, correcting and provisioning easier.
- [ ] Set-…preferences like ishfield… format that memory only pipeline object. Remember that is preferences could become available on settings.
- [ ] Find-/Get-
- Take pipeline IshUser, if not present the IshSession IshUser
- Takes two filters according to Api and returns ishpreferences object
- [ ] Set-
- Take pipeline IshUser, if not present the IshSession IshUser... Allowing mass overwrite/update
- Takes either single key/value or ishfield like group object or hash key/value
- Returns ishpreferences object
- Take pipeline IshUser, if not present the IshSession IshUser... Allowing mass overwrite/update
- [ ] Remove-
- Take pipeline IshUser, if not present the IshSession IshUser
- Takes two filters according to Api
- Or takes keys from incoming ishfield like object
- [ ] Print/format like ishuser, key, value in a table
The idea is quite old, not picked up yet. Given the switch from either WcfSoapWithWsTrust or WcfSoapWithOpenIdConnect to OpenApiWithOpenIdConnect. This set of cmdlets might be a good candidate to directly implement on the future Public REST Api.