Maintenance e-docs can be routed for FYI, Acknowledgement or Approval.
A Maintenance e-doc usually has a Document Overview, Notes & Attachments, Ad Hoc Recipients, and Route Log tab.
OLE can apply unique permissions per user, or route maintenance docs.
Complex: used for entities like Vendors, Accounts, Locations-- often many attributes, notes, and rules.
Simple: used for populating controlled value lists, or lists of possible values for a given Attribute.
(See linked templates for transactional e-docs).
Maintenance document can be looked at as a form that sits on top of a database table to edit business data. Very simple interface on top of the database for example: in KFS, the account document allows you to maintain the account table. These are generally auto-generated. structured off of a database table. Generally have a small or no workflow process behind them. Essentially a CRUD framework that sits on top of your database.
Technical/Local Config: Can (remove/not display tabs)be done in the declaration of the JSP for transactional documents. Could also be done conditionally to allow for display or not via a setup. Could be added later for local config if conditional routing needs added.
| 
(Sample Complex: Account)
(Sample Simple: Note Type) |