...
You can also edit or delete the licenses.
Database Schema
The database schema
...
can
...
be found in the application
...
is the user has database::read permission by going to menu: Admin -> Database -> List Tables, then clicking on the
...
Code Block | ||||
---|---|---|---|---|
| ||||
CREATE TABLE `licenses` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(200) NOT NULL DEFAULT '',
`org_id` int(10) unsigned NOT NULL DEFAULT '1',
`org_descendants` enum('y','n') NOT NULL DEFAULT 'y',
`purchase_count` int(10) unsigned NOT NULL DEFAULT '0',
`used_count` int(10) unsigned NOT NULL DEFAULT '0',
`description` text NOT NULL,
`match_string` text NOT NULL,
`edited_by` varchar(200) NOT NULL DEFAULT '',
`edited_date` datetime NOT NULL DEFAULT '2000-01-01 00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8; |
A typical entry looks as below.
...
language | text |
---|---|
theme | Eclipse |
...
details button for the table.
API / Web Access
You can access the
...
collection using the normal Open-AudIT JSON based API. Just like any other collection. Please
...
see The Open-AudIT API documentation for further details
...
Access is provided as part of a roles permissions. Licenses is a standard resource and can have create, read, update and delete permissions.
...
.
...
API Routes
...
...
...
...
...
...
...
...
...
Web Application Routes
...
...
...
...
...
...
...
...