Difference between revisions of "UE"
From AMTech WikiDocs
| Line 9: | Line 9: | ||
*The navigation through resources properties and their relations is done with a single component "tree editor" allowing users to move from branches and edit, create or delete resource's properties or relations | *The navigation through resources properties and their relations is done with a single component "tree editor" allowing users to move from branches and edit, create or delete resource's properties or relations | ||
[[File:ue1.png]] | [[File:ue1.png]] | ||
| − | *The three editor has a cohesive experience to CRUD | + | *The three editor has a cohesive experience to CRUD, filter and navegate the resources to be configured or followed. |
| + | **Create | ||
| + | **Clone supported just for things and observations instances | ||
[[File:ue-create.png]] | [[File:ue-create.png]] | ||
| + | **Delete | ||
[[File:ue-delete.png]] | [[File:ue-delete.png]] | ||
| + | **Update | ||
[[File:ue-save.png]] | [[File:ue-save.png]] | ||
| + | **View resource jsonld | ||
[[File:ue-view-jsonld.png]] | [[File:ue-view-jsonld.png]] | ||
| + | **Move forward to tree's brunch | ||
[[File:goto-branch.-jsonld.png]] | [[File:goto-branch.-jsonld.png]] | ||
| + | **Move back to tree's brunch | ||
[[File:ue-bc.png.-jsonld.png]] | [[File:ue-bc.png.-jsonld.png]] | ||
| + | **CRUD operations are control by access control polices, green lock full access, red luck read only | ||
[[File:ue-resource-info.-jsonld.png]] | [[File:ue-resource-info.-jsonld.png]] | ||
| + | **Filter resources to be configured or followed | ||
| + | [[File:ue-search.-jsonld.png]] | ||
| + | **There are multiples filter criteria depending of the metadata of the resource type, following example is to filter resources type topics | ||
[[File:ue-search-form.-jsonld.png]] | [[File:ue-search-form.-jsonld.png]] | ||
Revision as of 14:39, 21 April 2016
AMTech user experience "platform" as known by the development team, is a single page web application driven by the semantic of the resources to be configured. It leverages AMTech IoT DAP semantic and Restful API.
- The application offers functionality for 2 types of users:
- "activity creators" configure business activities monitoring
- "followers" instantiate a service for specific customer, deployment or location
- invite user with specifics role(s)
- create instances of things
- follows things
- The navigation through resources properties and their relations is done with a single component "tree editor" allowing users to move from branches and edit, create or delete resource's properties or relations
- The three editor has a cohesive experience to CRUD, filter and navegate the resources to be configured or followed.
- Create
- Clone supported just for things and observations instances
- Delete
- Update
- View resource jsonld
- Move forward to tree's brunch
- Move back to tree's brunch
- CRUD operations are control by access control polices, green lock full access, red luck read only
- Filter resources to be configured or followed
- There are multiples filter criteria depending of the metadata of the resource type, following example is to filter resources type topics
