Events and sources
Every event in Audit has a level and a source. This page explains both, lists the events you can expect to see, and says which fields every event carries.
Levels
| Level | Meaning |
|---|---|
| Information | Something happened as normal, for example a user opened a product or saved a change. Most events have this level. |
| Warning | Something unusual happened that you may want to look at. |
| Error | Something failed. |
In the Audit application each level has its own badge and its own tile on Home.
Sources
The Source filter in the Audit list offers these names. A source is the product or service that recorded the event.
| Source | Events from |
|---|---|
| Doc Gen | The Doc Gen start page and Administration, such as team, access group and archive settings. |
| Smartforms | Studio, for example creating, updating and publishing a dialog definition. |
| DigitalSigning | Signature. |
| MFDX | MFDX. |
| Viewpoint | Viewpoint. |
| TextLibrary | Text Library. |
| WebEditor | Editor. |
| IdentityServer | Signing in and out, and changing company, as recorded by the earlier Doc Gen sign-in. Your company may have few or no events from this source. |
| Workflow | Workflow. |
| MetaTool | Metatool. |
| Archive | Archive. |
| PingDoxAdmin | PingDox Admin. |
| Support | Support. |
| Metaforce Solution | Metaforce solutions. |
| Interact Admin | Interact administration. |
A source only appears in the list of results when it has recorded events for your company in the dates you search. Choosing a source with no events gives an empty list.
Events you can expect
Audit records what people do in the Doc Gen products and some system actions. Each product decides which of its actions it records, and the list grows as products add events. These are events seen in a working company:
| Source | Event | Raised when | Level |
|---|---|---|---|
| Doc Gen | Change user properties | A user’s role or state is changed under Team in Administration. | Information |
| Doc Gen | Users Added to Group | Users are added to an access group. | Information |
| Doc Gen | Access Group Created | An access group is created. | Information |
| Doc Gen | Add Archive Folder | An archive folder is added. | Information |
| Doc Gen | Add a new Retention Polocy | A retention policy is added. The event name is spelled this way on screen. | Information |
| Smartforms | Dialog definition created from template | A dialog definition is created from a template. | Information |
| Smartforms | Dialog definition created from command file | A dialog definition is created by importing a file. | Information |
| Smartforms | Dialog definition folder added | A folder for dialog definitions is added. | Information |
| Smartforms | Dialog definition updated | A dialog definition is saved. | Information |
| Smartforms | Dialog definition rules updated | The rules of a dialog definition are saved. | Information |
| Smartforms | Dialog definition published | A dialog definition is published. | Information |
| Smartforms | Dialog definition version promoted | A version of a dialog definition is promoted. | Information |
| Smartforms | Object template created | An object template is created. | Information |
| Workflow | Workflow created | A workflow is created. | Information |
| Workflow | Workflow activated | A workflow is activated. | Information |
| Workflow | Workflow deactivated | A workflow is deactivated. | Information |
| Workflow | Workflow folder created | A workflow folder is created. | Information |
| Workflow | Workflow table created | A workflow table is created. | Information |
| Archive | Adding document or its newer version | A document or a new version of it is added to the archive. | Information |
| Viewpoint | Access the ViewPoint application | Someone opens Viewpoint. | Information |
| DigitalSigning | User visited Digital Signing Dashboard | Someone opens the Digital Signing dashboard. | Information |
Some event names end with an identifier, for example Object template moved to folder followed by a number. Search for the start of the name to find them all.
To see which events your company has, open the Audit list, choose a Source and search. Open an event to read its Description.
Fields every event carries
Every event has the fields shown on the event details page: Source, Event Name, Event ID, Level, User, Logged, OpCode, Category, Keyword, IP and GDPR. The Audit application explains each one, and the Audit API names them as they are sent and received.
The GDPR flag is set by the product that wrote the event. It tells you the event may hold personal data.
Personal data
The Description of an event can hold the names of the user and the company, and names of the items that were changed. Treat events as business data when you export them or forward them to another system, and follow your own rules for personal data. Events belong to one company. Only its administrators and its own API clients can read them.