[DOCS-7851] Document that the allDbs field is no longer valid for use via the API Created: 11/May/16 Updated: 05/May/17 Resolved: 17/May/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Barry O'Neill | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 29 weeks ago | ||||
| Epic Link: | C/OM Update API | ||||
| Description |
|
Hi, We should document that the allDbs field is now deprectated in the UserDeleted section of the automation config when using the API and that the dbs now need to be explicitly specified when deleting users. Thanks, Barry |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |