All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Land Revenue Management
  2. Data model
Reference

The tables behind Land Revenue Management

Land Revenue Management ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
14
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Service configuration

Organizations own public services and People; source mappings describe fields for a service definition.

Case work

Cases belong to an organization, service definition and owner. Case requirements, case documents and case actions attach supporting work to a case.

Independent review

Decisions identify the reviewed case revision and reviewer. State history records transitions with an actor.

Execution trace

Operation runs connect to Cases, operation steps connect to runs, and execution attempts connect to Cases.

Access

Users holds account identity and role information.

Every table, by feature

Service configuration

5 tablesAbout this feature
  • Organizations

    Agencies, departments and service organizations that own public services and cases.

  • People

    Staff, officers, reviewers and assigned team members.

    Linked to Organizations
  • Public services

    Published service definitions, programmes and entitlements offered by an organization.

    Linked to Organizations
  • Source mappings

    Reviewed field mappings and transform rules between source payloads and target fields.

    Linked to Public services
  • Cases

    Requests, applications and cases submitted for a public service.

    Linked to Organizations, People, Public services

Case intake

6 tablesAbout this feature
  • Cases

    Requests, applications and cases submitted for a public service.

    Linked to Organizations, People, Public services
  • Public services

    Published service definitions, programmes and entitlements offered by an organization.

    Linked to Organizations
  • Organizations

    Agencies, departments and service organizations that own public services and cases.

  • People

    Staff, officers, reviewers and assigned team members.

    Linked to Organizations
  • State history

    Immutable workflow-written status transition history for each case.

    Linked to Cases, People
  • Case actions

    Assigned outstanding actions, corrections and outstanding requests for a case.

    Linked to Cases, People

Requirements and documents

5 tablesAbout this feature
  • Case requirements

    Observation-level requirement, document and line detail captured against a service application.

    Linked to Cases
  • Case documents

    Uploaded and verified supporting documents and source evidence.

    Linked to Cases, People
  • Case actions

    Assigned outstanding actions, corrections and outstanding requests for a case.

    Linked to Cases, People
  • Cases

    Requests, applications and cases submitted for a public service.

    Linked to Organizations, People, Public services
  • People

    Staff, officers, reviewers and assigned team members.

    Linked to Organizations

Independent review

6 tablesAbout this feature
  • Decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Cases, People
  • Cases

    Requests, applications and cases submitted for a public service.

    Linked to Organizations, People, Public services
  • Case requirements

    Observation-level requirement, document and line detail captured against a service application.

    Linked to Cases
  • Case documents

    Uploaded and verified supporting documents and source evidence.

    Linked to Cases, People
  • People

    Staff, officers, reviewers and assigned team members.

    Linked to Organizations
  • State history

    Immutable workflow-written status transition history for each case.

    Linked to Cases, People

Delivery and actions

5 tablesAbout this feature
  • Case actions

    Assigned outstanding actions, corrections and outstanding requests for a case.

    Linked to Cases, People
  • Cases

    Requests, applications and cases submitted for a public service.

    Linked to Organizations, People, Public services
  • Execution attempts

    Each recorded attempt to execute an approved action for a service application.

    Linked to Cases
  • Operation runs

    Workflow-maintained execution runs with operation key, input hash and persisted result reference.

    Linked to Cases
  • Operation steps

    Ordered steps inside an operation run with input, output and external receipt state.

    Linked to Operation runs

Execution provenance

6 tablesAbout this feature
  • Operation runs

    Workflow-maintained execution runs with operation key, input hash and persisted result reference.

    Linked to Cases
  • Operation steps

    Ordered steps inside an operation run with input, output and external receipt state.

    Linked to Operation runs
  • Execution attempts

    Each recorded attempt to execute an approved action for a service application.

    Linked to Cases
  • Source mappings

    Reviewed field mappings and transform rules between source payloads and target fields.

    Linked to Public services
  • Cases

    Requests, applications and cases submitted for a public service.

    Linked to Organizations, People, Public services
  • State history

    Immutable workflow-written status transition history for each case.

    Linked to Cases, People

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

A case number is the working identifier, while the source and parent references keep child records attached to the right case. The case revision and decision source revision identify the exact material reviewed. Operation keys, input hashes and result references distinguish execution work and its outcome. Keep source record identifiers and external references when migrating existing applications so earlier correspondence remains traceable.

Migration order

  1. Organizations and people. Establish service owners and staff references.
  2. Services and mappings. Add public services and review source mappings against representative source values.
  3. Cases and supporting work. Bring in Cases, then case requirements, case documents and case actions with their references intact.
  4. Review history. Import Decisions and state history with the original revision and actor details.
  5. Execution evidence. Bring in operation runs, operation steps and execution attempts after their parent references are stable.

Set up Land Revenue Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started