In ArcMap, you could edit data in tables or feature classes that were not registered with an enterprise geodatabase. Thad made it convenient to make small edits to ancillary tables in the database when needed rather than having to open up a separate tool to make the edits like SSMS, Oracle SQL Developer or PGAdmin.
This capability was never added to Pro. Instead when you try to edit a non-registered table standard table all the editing features are greyed out and you get a warning "This enterprise database table is not registered with the geodatabase. Edits cannot be made"
I would like to see this ability added to Pro so it works like it did in ArcMap. I know this has it's limitations, like having to start an edit session to make edits, click save to commit, and lack of undo functions), but sometimes you just want to use Pro to do this kind of work instead of opening separate applications.
I'll also say that just registering these other tables everything with the database isn't always an option...for example in SQL Server you can't register a table that uses an identity column as it's primary key....which are much less of a pain then managing sequences.
I'll also clarify that I think this would apply to tables or feature classes in a relational database that has been configured as an Esri Enterprise Geodatabase, but just aren't registered for specific business needs. Or it could also be tables of feature classes in a relational database that is not configured as an Esri Enterprise Geodatabase, such as a SQL Server or Postgres database with some tables with geometry columns.
