Government agencies across the United States and around the world select Accela Automation as their system of choice for their Land Management, Licensing & Case Management and Asset Management operations.
One of the key reasons these governments choose Accela is versatility. Accela is one of the few platforms with a public sector focus that has the flexibility to serve the enterprise. The key factor behind the flexibility and power of the Accela system is its data model.
This is the first in a series of posts that will introduce you to the Accela data model as it applies to the Construct API.
The Bigger Picture
Most data in Accela is classified as one of the following:
- Transactional data – data that supports a process, for example: a permit application, a work order, a license renewal, a change amendment
- Reference data – data that represents a person, entity or location, for example applicant, a license holder, the parcel or address of a permit. Reference data enables us to organize data so we can see “all the permits for this address” or “all the licenses this person holds”
- Configuration data – data that specifies how the Accela system is setup to work. It defines what a permit or license “is” and the process it will enforce from start to end.
In this screencast I introduce you to these concepts further and highlight some of the common objects you will be working with in the Construct API.
In this screencast I used this presentation to walk through the data model. Stay tuned for more posts in this series. In each we will look at an individual object, discuss how our customers utilize the object, and explore the methods available looking at the API requests and responses to understand how to use and interpret the data.