One major drawback of the Attribute Assistant is that it doesn't support versioned databases. This is a concern because to edit feature classes that participate in a topology, network dataset [STREETS], or geometric network [UTILITIES], or edit the parcel fabric, you must register the data as versioned.
If support for versioning isn't possible (one workaround is to give each user a separate GenerateID table and have the auto-increment function vary to assure unique IDs), The Attribute Assistant instructions should explicitly state that because the GenerateID field cannot be versioned, the Attribute Assistant cannot readily be used to assign IDs to features participating in topologies, networks, or parcel fabrics.
Additional details from ESRI documentation:
By default, ArcMap edit sessions are set to perform versioned edits. This means you can only edit data that has been registered as versioned. To perform nonversioned edits on nonversioned data, you must first set an option on the Versioning tab of the Editing Options dialog box. Essentially, you must turn off versioned editing by unchecking Edit a version of the database with the ability to undo and redo.
Once you start editing, you cannot change the type of edit session while the edit session is open. If you later need to perform versioned edits, you must close the nonversioned edit session, recheck the Edit a version of the database with the ability to undo and redo option, and start a versioned edit session.