Summary

UPGRADING If you are upgrading your system please pull the changes and do the following to install the new custom_docs table and update the sections table

Run DB Migrations

php artisan migrate

##General Changes

Admin Page Bot Properties

This release fixes a bug with the bot properties which meant that bot properties were not assigned a section on save

Custom Documentation Area

The ability to create and view custom documentation for the app

SUMMARY

A number of changes to make the administration of the bots and it's linked data simpler. And the addition of a new "avatar" tag to allow the botmaster to specify facial expression that will be read by a Lemurtar bot.

UPGRADING

If you are upgrading your system please pull the changes and do the following

1. Update the class paths...

composer dump-autoload -o

2. Run DB Migrations

php artisan migrate

3. Run DB Seeder for the new table

php artisan db:seed --class=SectionTableSeeder

CHANGELOG

Admin Page Sections

This release improves the bot knowledge and bot properties administration pages by creating a new table called sections. This will allow the user to assign sections to knowledge groups and properties so that they are grouped together on those admin pages.

Allowed Sites Setting

A setting to prevent access based upon the referring host. This does not replace the CORS update that happened a few releases back. But actually adds a layer on top of that to disallow access to a bot based upon the referring host. If left blank then only the CORS rule will be applied. The setting is on a bot by bot basis and can be accessed via a tab in the bot admin area.

Critical File Setting

To prevent unintended deselection of the critical AIML file you can now specify it on the main bot admin page. This was previously a setting in the .env file but now that has been removed and you can define the file here.

Lemurtar facial express tag

A new tag called Avatar has been created. This tag allows you to assign facial expressions to the avatars. You can read more about its usage here: https://docs.lemurengine.com/aiml.html#avatar You can download an example AIML file here: https://github.com/theramenrobotdiscocode/lemur-aiml/blob/master/aiml/TestAvatarActions.aiml

General bug fix release and added a few new features to make life a bit easier.

• Added a feature to auto check the suggested set of AIML files in the bot admin area
• Added a feature to prevent the unlinking of critical AIML files in the bot admin area
• Added a feature to enabled CORS configuration from the .env file
• Added an extra mime type to the category upload
• Added better error messages when uploading files
• Correct all the 'CVS' typo
• Fixed a bug which was preventing the normalisation of accented letters
• Fixed a bug which was preventing CSV from uploading when they had quotes and newlines in the fields
• Fixed a bug that was prevent the chat window from displaying in the portal when the conversation returned blank

• Statistic changes - previously stats and counts were including none-human turns from the turns table. This has been fixed now so it will only count human (actual turns)

• Fixed the foreign chars not displaying correctly
• Created and commented out a dummy author user for testing (see UserTableDataSeeder.php)
• If user is an 'author' they can no longer see other users categories in the categories table - they can only see their categories and master categories
• If user is an 'author' they can no longer see other users category groups in the category_groups table - they can only see their category groups and master categories
• Removed the unique key for the name column on the category_groups table and created a new unique key for the name and the user_id instead
• Added the author details to the bot > category page so that users can see who created the category group
• Added a new color coding to make this super clear on the bot > category page
• Added the ability to download conversations in a CVS format
• Added the ability to view conversations in a plain text format

SUMMARY

This release addressed a number of usability issues relating to restoring and hard deleting users and bots. UX changes to improve the updating of bot, client, conversation, language and user slugs. And quick buttons to allow users to return to a category they are updating. Update of the input size rules to allow larger messages from the user and config to limit this to a defined limit to ensure backward compatibility.

UPGRADING

If you are upgrading your system please pull the changes and do the following

1. Run DB Migrations

php artisan migrate

2. Update Config And add the following config settings to your .env file

SHOW_DETAILED_ADMIN_ERRORS=false MAX_USER_INPUT_CHARS=255

CHANGELOG

Slug fixes

Removed the ability to update a slug for all models except from

• Bots
• Clients
• Conversations
• Languages
• Users

Updated the method (UI/backend) to edit slugs to simplify the whole experience

Category Form

Added an option to 'Save and Continue' to allow users to return to the category when they have saved it to continue editing

Hard Delete Bots

Allow the hard deletion of a bot and all its related entities First you must soft delete the bot then you will presented with an option to hard delete it in the datatable A new migration script has been created to alter the foreign key relationships to ON DELETE CASCADE for the bot related tables.

Restore Soft Deleted Bots

Allow the restoring of bots which have been soft deleted First you must soft delete the bot then you will presented with an option to restore it in the datatable

Hard Delete Users

Allow the hard deletion of a user. Hard deletion is prevented if they have related entities - you must hard delete the users bots first. First you must soft delete the user then you will presented with an option to hard delete it in the datatable

Restore Soft Users

Allow the restoring of users which have been soft deleted First you must soft delete the user then you will presented with an option to restore it in the datatable

Alter Input DB Field

The turns.input has been updated from a varchar(255) to a text field. And additional config has been added to the lemur.php config field. Set 'max_user_char_input' to set the allowed max client message length. A validation method has been written and a lengthException will be thrown if over this limit.

Consolidated And Improved Feedback

Consolidated the two form submit feedback message mechanisms into one single file And added ability to show extra details where available to admins when form submit operations fail Set 'show_detailed_error_messages' to true or false to show a more detailed message to admins. This should be used wisely as it might leak more information about your system than you would like. Messages are only displayed to ADMIN users and only if set to true.

Additional Config

Override default settings for max_user_char_input and show_detailed_error_messages in .env by setting SHOW_DETAILED_ADMIN_ERRORS MAX_USER_INPUT_CHARS

Some bug fixes which were discovered in the first release and the critical update of charts.js which was flagged as a security issue.

This release is dedicated to my friend and Program O dev - Dave Morton. We always wanted to rewrite Program O. It took a global pandemic for me to find the time to actually be able do it. I wish you were here to see this day - this one is for you mr!

For the rest of the world this is the first release of the Lemur Engine. A new chatbot engine written in Laravel and using AIML. It's a fun non complicated bot with lots of power. Create chatbots, text based games and virtual assistants.