Process procedures are similar to Report procedures in that they too are organized as flowcharts of executable components, with the ability to retrieve data from database tables, export data in a file, perform various calculations and text formatting operations, etc.
However, there are differences:
In other words, the primary purpose of Processes is not to report on the database content, but to modify it. This capability to make changes to the database takes Scribe beyond the scope of a regular report generator, and turns it into a graphical database programming tool. In addition to this, Processes can combine multiple lower-level Processes and Reports, streamlining their execution as one coherent unit. For example, a Process can be scheduled to automatically run a Report, and then add a record to the report log table with the name of the executed report and date/time of the execution.
The following components are available to Processes, in addition to the standard components in the Report Palette:
| Component | Description |
| Insert | Add row to the database table |
| Update | Update row in the database table based on the given selection criteria |
| Delete | Delete row from the database table based on the given selection criteria |
| Success? | Test the success or failure of the Inser, Update or Delete operation |
| Transaction Packet | Provides the BEGIN, COMMIT and ROLLBACK database transaction brackets |