Behaviour Identification Guidelines
By Nicola D'Andrea and Mikaela Robertson 2 April 2020 Codebots Basics
The Behaviour Identification Guidelines define the functionality of our Codebots behaviours.
Use the following table to help you recognise where a behaviour is similar to one of your business patterns. Since our bots write these behaviours for you, this process will help you identify how much time you can save using Codebots.
For each behaviour, the guidelines tell us the following:
- Functionality: the basic purpose of the behaviour
- Use cases: examples of the most common applications of the behaviour
- Default capabilities: what is capabilities are packaged with the behaviour out-of-the-box.
- Custom capabilities: what the behaviour can achieve using the Codebots protected regions
- Not applicable: actions that the behaviour is not suited for
|Behaviour||Functionality||Use cases||Default capabilities||Custom capabilities||Not applicable|
|CRUD||Managing structured data||Managing users, bookings or events, or any data that can be displayed in a spreadsheet||Accessing a list of data; creating, reading, updating and deleting data; sorting and filtering data; searching data||Custom views||Displaying and managing unstructured data (such as Forms submission)|
|Dashboard (Coming Soon)||A configurable page that displays data from an entity or entities||Administration home pages, front page dashboarding and individual dashboards within an application.||Displaying data from the application as a list, line, bar, pie or donut graph.||Extend the pre-defined queries in the custom code to unlock further dashboarding options and extend our graphing types using entirely custom dashboard tiles.||Displaying unstructured data (such as Forms submission), displaying data on specific user levels|
|Developer API||Accessing data||Third-party integration, microservice architecture||Accessing data||Data aggregation, custom extensions|
|File Upload (Coming Soon)||Associates files with an entity||Uploading images, documents, multimedia; can be part of a form||Upload single or multiple files; storage of files; determining how files will be stored||Media capture||Presentation of uploaded files|
|Forms||Runtime configurable forms based on user submissions||Surveys; creating articles/documents/submissions||Configuring and versioning forms; collecting unstructured data; end of survey message||Custom data input types||Creating structured data; managing data|
|Timelines (Coming Soon)||Visual representation of changes to an entity over time||Audit trail; booking history; log of bot actions||Timeline view; list/feed view; display what changes were made at what times||Custom security considerations; showing a specific set of information that is not configurable with the default options||Versions - cannot see a snapshot of the entity at a point on the timeline|
|User||Ability to create users with additional metadata associated||Linking information like profile pictures, student IDs, etc. to a user||Defining user types; login, registration and forgotten password functionality||Custom authentication providers (e.g., Facebook login)|
|Versioning||Ability for an instance of an entity to have versions||Anything that has copy (e.g., changing the description of a property); library articles; documentation; used by Forms and Workflows||Option to create version automatically or explicitly; view snapshot of an entity at a specific moment; revert entity to a previous version; drafting changes||Tracking changes over time|
|Workflows||Runtime configurable transitions between states on an entity||Booking status; application status, issue management (e.g., kanban board); sales pipeline||Booking status; application status; issue management (e.g., kanban board); sales pipeline||Simple actions occurring on transitions (e.g., sending a single email)||Complex actions occurring on transitions|