10-08-2021 09:07 AM
While looking more details at the new EP5 Users Administration section, I noticed that it is very skimpy in a lot of areas and missing options in others. So I wanted to put out there some questions regarding it.
There are other things I want to bring up surrounding the methods under the "Users" grouping, but this is just the start and I figured it would at least get a discussion going surrounding the future of this section of methods.
Thanks.
10-08-2021 11:18 AM
Hey Ryan,
Great questions as always.
To more broadly answer some of the items below, the ultimate goal of these administrative APIs is to support the modern configuration screens, which are actively being built out for EP6. The scope of the configuration options that we have made available through the APIs is very specific to those used most often by the administrators in a hosted environment. While we are ultimately building these APIs out for EP6, we wanted to provide some of the endpoints which were already completed with EP5 in an attempt to be more continuous with our deployments. Items such as Account Expiration, Service vs Regular Accounts, and locking/unlocking user accounts are all within scope for our configuration screens, and you should absolutely look for this in subsequent releases of our Admin APIs. The backporting of these APIs has yet to be determined but is very much limited by our bandwidth as we push forward with other initiatives for EP6.
Digging into two of your more specific questions below, we are following Hyland's standards for base item retrieval, meaning returning the most streamline, yet informative objects that can support the UIs. There is absolutely a balance here between too much info and not enough (i.e. name may be a great candidate to add in the future but the entire user object would not), while keeping our primary goal of being as performant as possible in mind.
We are actively looking into an enhancement to our framework called Expand Parameters, which would allow you to say "Give me all users and their emails/real names", however we expect some performance hits with these optional endpoints. I do not currently have an ETA on when you can expect this enhancement to be added.
As always, feel free to fill out an Idea on the Ideas Portal for enhancements that you see as being valuable to add in future releases. Calling out anything you believe we missed or use cases you'd like to see covered would be extremely valuable for our future development efforts.
Hopefully that provides some additional clarity.
Tyler Conn
Product Owner
Configuration Services and Change Control
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.