IDConsole feature parity - what is missing?

I understand what happened with IDConsole.  There is an issue in iManager, fixing it is will be hard/expensive, and no one knows the older framework it is running on to hire to do the work without starting learning it from scratch. (Cost goes up).  Budgets are limited.

Angualr is easy, and lots of people to hire who know it.  So we get IDConsole, UMC for OES and whatever the new console is called in Access Manager (Never seen it, but I assume it is Angular based as well). 

But they need feature parity before releasing it, so decisions were made.  I do not agree, but here we are where we are.

What have you found that is missing in IDConsole?  Please do not reply with Me Too, or discussion, grab the item I list out of here and start a new thread and discuss it there.  Lets see if we can try to generate a single thread to point engineering at..  I may police these responses to keep this format working.

Use upvotes on each item to indicate if this has hit you. 

Try and keep it to one per reply, so the votes can indicate something. If you have a workaround please include it. 

I will start with my list.  Please upvote or add your items. 

Sure we could do this with Ideas, but first we sort of need to see how bad the problem is.

Labels:

Identity Manager