Updated for v0.9.0

Updated documentation with all the changes that were made for v0.9.0 of
the Python implementation.

Author: Alex Meadows

.gitignore

@@ -164,3 +164,4 @@ venv.bak/
 .idea/modules.xml
 .idea/process_tracker.iml
 .idea/vcs.xml
+/.idea/inspectionProfiles/

docs/source/model/extract.rst

@@ -99,7 +99,7 @@ This table tracks the valid types of files and their formats that available.
      - Integer
      - Auto incrementing unique sequence
    * - extract_filetype_code
-     - String(5)
+     - String(25)
      - The file extension used by the filetype (i.e. csv)
    * - extract_filetype
      - String(75)

docs/source/model/overview.rst

@@ -7,4 +7,26 @@ Support is also enabled for Oracle, MS-SQL, and Snowflake, but has not been full
 should Just Work (tm) until they can be tested thru the build stack and not just locally their status must remain
 'available but untested'.
 
-Each subsection of the Model section covers a specific topic of the data store.
+Each subsection of the Model section covers a specific topic of the data store.
+
+New with version 0.9.0, all tables are now equipped with stock audit fields:
+
+.. list-table:: stock audit fields
+   :widths: 25 25 50
+   :header-rows: 1
+
+   * - Column Name
+     - Column Type
+     - Column Description
+   * - created_date_time
+     - timestamp (with timezone, if available)
+     - The date/time that the record was created.
+   * - created_by
+     - integer
+     - The id of the actor who created the record. Implied foreign key to the :ref:`actor_lkup` table.
+   * - update_date_time
+     - timestamp (with timezone, if available)
+     - The date/time that the record was last updated.
+   * - updated_by
+     - integer
+     - The id of the actor who updated the record. Implied foreign key to the :ref:`actor_lkup` table.

docs/source/python/process_tracker.rst

@@ -43,7 +43,7 @@ Those variables will be used to populate the data store backend as explained in
      - :ref:`process_tracking`
      - Yes
    * - process_type
-     - The type of process being run.
+     - The type of process being run. Optional if process already exists.
      - :ref:`process_type_lkup`
      - Yes
    * - actor_name
@@ -93,7 +93,7 @@ Those variables will be used to populate the data store backend as explained in
      - The general frequency at which the process should run.
      - :ref:`schedule_frequency_lkup`
      - No
-   * - process_run_id
+   * - process_tracking_id
      - When recreating a Process Tracking instance, provide the process_tracking_id and it will re-instantiate as it was
        originally created, with the current status, objects, etc.
      - :ref:`process_tracking`, plus all other objects created on instantiation of ProcessTracker
@@ -107,7 +107,7 @@ Re-initializing An Instance
 To set up a previous instance, pass the process tracking id to ProcessTracker.  Instead of creating a new instance of
 the given process, it will retrieve the specific tracking record and all of it's ancillary data.::
 
-        restored_process_run = ProcessTracker(process_run_id=123)
+        restored_process_run = ProcessTracker(process_tracking_id=123)
 
 This should ideally only be used when a process is still running - like when switching between services within your
 cloud provider.
@@ -518,7 +518,7 @@ Processes can have an optional schedule frequency.  To find all processes of a g
 
         process_run.find_process_by_schedule_frequency(frequency="hourly")
 
-This will return a list of process ids with the given frequency.
+This will return a list of process objects with the given frequency.
 
 Finding Process Filters
 ***********************