@tiledesk/tiledesk-server 2.3.9 → 2.3.10

package/CHANGELOG.md

@@ -1,15 +1,106 @@
+curl --location --request POST 'https://console.native.tiledesk.com/api/62ea3c58cd9923001a6ccdf3/requests/support-group-62ea3c58cd9923001a6ccdf3-088a9b9d28d3427ea99ab928a7aeb9d4/messages' \
+--header 'Authorization: JWT eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ3ZWJob29rX2VuYWJsZWQiOmZhbHNlLCJ0eXBlIjoiZXh0ZXJuYWwiLCJsYW5ndWFnZSI6ImVuIiwiX2lkIjoiNjJlYTNkOGFjZDk5MjMwMDFhNmNjZjQ1IiwibmFtZSI6IkhlbGxvQm90IiwidXJsIjoiaHR0cHM6Ly9Cb3RUaW1lc3RhbXAuZ2FicmllbGVwYW5pY28ucmVwbC5jby9ib3QiLCJpZF9wcm9qZWN0IjoiNjJlYTNjNThjZDk5MjMwMDFhNmNjZGYzIiwidHJhc2hlZCI6ZmFsc2UsImNyZWF0ZWRCeSI6IjYxYmRkMGM0ZDBhMmE3MDAxYTI4YjliNCIsImNyZWF0ZWRBdCI6IjIwMjItMDgtMDNUMDk6MTk6MDYuNDMyWiIsInVwZGF0ZWRBdCI6IjIwMjItMDgtMDNUMDk6MTk6MDYuNDMyWiIsIl9fdiI6MCwiaWF0IjoxNjU5NTE4NzI1LCJhdWQiOiJodHRwczovL3RpbGVkZXNrLmNvbS9ib3RzLzYyZWEzZDhhY2Q5OTIzMDAxYTZjY2Y0NSIsImlzcyI6Imh0dHBzOi8vdGlsZWRlc2suY29tIiwic3ViIjoiYm90IiwianRpIjoiMzY3ZWI4YzAtNjczZi00NzUwLThhNmEtNzUyMzA4YmNhMGIyIn0.B4cq9b9V__S0uR9xYkuxykBKfQ4vU0DyO278KAJG4Us' \
+--header 'Content-Type: application/json' \
+--data-raw '{"text":"Cheers! You said:"}'
 
+curl --location --request POST 'https://console.native.tiledesk.com/api/62ea3c58cd9923001a6ccdf3/requests/support-group-62ea3c58cd9923001a6ccdf3-088a9b9d28d3427ea99ab928a7aeb9d3/messages' \
+--header 'Authorization: JWT eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ3ZWJob29rX2VuYWJsZWQiOmZhbHNlLCJ0eXBlIjoiZXh0ZXJuYWwiLCJsYW5ndWFnZSI6ImVuIiwiX2lkIjoiNjJlYTNkOGFjZDk5MjMwMDFhNmNjZjQ1IiwibmFtZSI6IkhlbGxvQm90IiwidXJsIjoiaHR0cHM6Ly9Cb3RUaW1lc3RhbXAuZ2FicmllbGVwYW5pY28ucmVwbC5jby9ib3QiLCJpZF9wcm9qZWN0IjoiNjJlYTNjNThjZDk5MjMwMDFhNmNjZGYzIiwidHJhc2hlZCI6ZmFsc2UsImNyZWF0ZWRCeSI6IjYxYmRkMGM0ZDBhMmE3MDAxYTI4YjliNCIsImNyZWF0ZWRBdCI6IjIwMjItMDgtMDNUMDk6MTk6MDYuNDMyWiIsInVwZGF0ZWRBdCI6IjIwMjItMDgtMDNUMDk6MTk6MDYuNDMyWiIsIl9fdiI6MCwiaWF0IjoxNjU5NTE4NzI1LCJhdWQiOiJodHRwczovL3RpbGVkZXNrLmNvbS9ib3RzLzYyZWEzZDhhY2Q5OTIzMDAxYTZjY2Y0NSIsImlzcyI6Imh0dHBzOi8vdGlsZWRlc2suY29tIiwic3ViIjoiYm90IiwianRpIjoiMzY3ZWI4YzAtNjczZi00NzUwLThhNmEtNzUyMzA4YmNhMGIyIn0.B4cq9b9V__S0uR9xYkuxykBKfQ4vU0DyO278KAJG4Us' \
+--header 'Content-Type: application/json' \
+--data-raw '{"text":"Cheers! You said:"}'
+
+- ABILITA REOPEN CHAT IN PROD IN PRE C?é GIA ????? VALUTARE VEDI INTERCOM
+https://www.intercom.com/help/en/articles/3449698-prevent-replies-after-you-close-a-conversation
+
+visitor counter fa uscire errore mongo
+
+# # 2.3.10 -> PROD
+- Added tilebot submodule
+- Askbot endpoint fix for tilebot and auto create faqs for tilebot
+- Added /widgets/ip endpoint   
+- Added bot and subscription as permission check for /intents or /faq
+
+# 2.3.9
+- Rasa process env variable read fix
+
+# 2.3.8
+- @tiledesk/tiledesk-rasa-connector": "^1.0.10
+
+# 2.3.7
+- Find by intent_display_name parameter intents
+
+# 2.3.5
+- CHAT_REOPENED updated conversation true
+
+# 2.3.4
+- download pdf fix
+- added no_count and no_textscore fields query parameters to request search endpoint
+
+# 2.3.3
+- Follower notification fix by email
 
 # 2.3.2
 - Dowload trascript as csv, pdf and txt endpoint
 - Added closed_by field to the request model
-- Added followers field to the request model 
+- Added followers field to the request model
 - Added lead index
-- Added widget v5 code loader /widgets/v5/:project_id -> heroku blocca cache-control 
+- Added widget v5 code loader /widgets/v5/:project_id -> heroku blocca cache-control PROVA IN PROD
 - Bugfix  Cannot read property 'profile' of null 
 - Added filter by channel offline and online 
-- Updated Rasa Connector to 1.0.7  
+- Updated Rasa Connector to 1.0.7   -- QUANDO PORTI IN PROD AGGIORNA SUL DB PER FARLI PUNTARE QUI..
 - Send info message on lead.fullaname.update
+- Follower email notification
+
+https://support.zendesk.com/hc/en-us/articles/4408822451482-Using-CCs-followers-and-mentions#topic_wm2_zgq_qgb
+
+Followers allow you to include additional internal users (agents or administrators) on ticket notifications. Internal users can add followers to tickets. There's no limit to the number of followers you can include on a ticket.
+
+Agents and administrators can use the Followers field in the properties panel of the ticket interface to add internal users to a ticket. 
+
+Internal users who can view the ticket can add followers to the ticket.
+
+Followers can:
+
+* Receive public comments and private comments added to the ticket conversation.
+* Ability to make a private comments and public comment.
+* Replying to a private comment creates a private comment and likewise for public comments.
+* Remove themselves from the ticket conversation.
+* Remain hidden from end users copied on the ticket.
+* Access any ticket that they are following, even if they would not normally be allowed to access the ticket.
+
+# Adding agents as followers from the ticket interface
+If followers have been enabled by the administrator, internal users (your company's agents and administrators) can add followers from the Followers field from the properties panel in the ticket interface. Followers are internal users such as agents, light agents, and administrators that receive email notifications when a ticket is updated.
+
+Note these things about using followers:
+
+* Followers can add and receive public comments and private comments.
+* Followers can reply to a public comment with a public comment, and reply to a private comment with a private comment.
+* Followers can remove themselves from the ticket.
+* Followers are hidden from copied (CC'd) end users and other followers on email notifications. Their name and email address don't appear in email notifications sent to other users. For more information about the email notifications that followers receive, see Best practices for using email clients with CCs and followers.
+* If your administrator has enabled Automatically make an agent a follower, you can added internal users, such as agents and admins, to tickets as followers from ticket notifications by adding them to the reply as a CC. In this case, the agent becomes both a CC and a follower.
+## To add agents as followers from the ticket interface
+* Select a ticket from one of your views.
+The Followers field appears in the ticket properties panel on the left side.
+
+* In the Followers field, enter a user's name, email domain, or organization name and the relevant results appear.
+Internal users such as agents, light agents, and administrators can be followers.
+
+* To quickly add yourself as a follower, click follow.
+
+
+
+## To remove a follower from the ticket interface
+* Click the delete button (X) in the person's name box in the Followers list
+
+
+* To quickly remove yourself as a follower, click unfollow.
+
+* To add agents as followers from ticket notifications
+
+* From your email client, open the ticket notification.
+* Open the CC line, per your email provider’s instructions.
+* Add the name of the user you want to add as a follower. Repeat as necessary.
+* Add your comment and send the email.
+
 
 
 # 2.3.1

package/app.js

@@ -175,6 +175,8 @@ if (process.env.CREATE_INITIAL_DATA !== "false") {
 
 
 
+
+
 var app = express();
 
 
@@ -456,8 +458,8 @@ app.use('/:projectid/tags', [passport.authenticate(['basic', 'jwt'], { session:
 app.use('/:projectid/subscriptions', [passport.authenticate(['basic', 'jwt'], { session: false }), validtoken, roleChecker.hasRole('admin')], resthook);
 
 //deprecated
-app.use('/:projectid/faq', [passport.authenticate(['basic', 'jwt'], { session: false }), validtoken, roleChecker.hasRole('agent')], faq);
-app.use('/:projectid/intents', [passport.authenticate(['basic', 'jwt'], { session: false }), validtoken, roleChecker.hasRole('agent')], faq);
+app.use('/:projectid/faq', [passport.authenticate(['basic', 'jwt'], { session: false }), validtoken, roleChecker.hasRoleOrTypes('agent', ['bot','subscription'])], faq);
+app.use('/:projectid/intents', [passport.authenticate(['basic', 'jwt'], { session: false }), validtoken, roleChecker.hasRoleOrTypes('agent', ['bot','subscription'])], faq);
 
 //Deprecated??
 app.use('/:projectid/faqpub', faqpub);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@tiledesk/tiledesk-server",
   "description": "The Tiledesk server module",
-  "version": "2.3.9",
+  "version": "2.3.10",
   "scripts": {
     "start": "node ./bin/www",
     "pretest": "mongodb-runner start",

package/pubmodules/emailNotification/requestNotification.js

@@ -78,7 +78,6 @@ listen() {
         } else {
           winston.debug("sendUserEmail chat channel");
                        
-            //TODO  mandare email se ultimo messaggio > X MINUTI configurato in Notification . potresti usare request.updated_at ?
 
             
             
@@ -684,7 +683,7 @@ sendUserEmail(projectid, message) {
 
 
       if (process.env.DISABLE_SEND_OFFLINE_EMAIL === "true" || process.env.DISABLE_SEND_OFFLINE_EMAIL === true ) {
-        return winston.info("DISABLE_SEND_OFFLINE_EMAIL disabled");
+        return winston.debug("DISABLE_SEND_OFFLINE_EMAIL disabled");
       }
       if (message.attributes && message.attributes.subtype==='info/support') {
         return winston.debug("not sending sendUserEmail for attributes.subtype info/support messages");
@@ -697,7 +696,7 @@ sendUserEmail(projectid, message) {
 
       
       if (!message.request.lead || !message.request.lead.email) {
-        return winston.info("The lead object is undefined or has empty email");
+        return winston.debug("The lead object is undefined or has empty email");
       }
 
       if (project.settings && project.settings.email && project.settings.email.notification && project.settings.email.notification.conversation && project.settings.email.notification.conversation.offline && project.settings.email.notification.conversation.offline.blocked == true ) {

package/pubmodules/pubModulesManager.js

@@ -31,6 +31,8 @@ class PubModulesManager {
         this.trigger = undefined;
         this.triggerRoute = undefined;
 
+        this.tilebot = undefined;
+
     }
 
   
@@ -257,6 +259,24 @@ class PubModulesManager {
             }
         }
         
+
+
+
+        try {
+            this.tilebot = require('./tilebot');
+            winston.debug("this.tilebot:"+ this.tilebot);    
+            this.tilebot.listener.listen(config);      
+
+            winston.info("PubModulesManager initialized tilebot.");
+        } catch(err) {
+            if (err.code == 'MODULE_NOT_FOUND') { 
+                winston.info("PubModulesManager init tilebot module not found");
+            }else {
+                winston.info("PubModulesManager error initializing init tilebot module", err);
+            }
+        }
+
+
     }
 
     start() {

package/pubmodules/tilebot/index.js

@@ -0,0 +1,3 @@
+const listener = require("./listener");
+
+module.exports = { listener: listener };

package/pubmodules/tilebot/listener.js

@@ -0,0 +1,51 @@
+const botEvent = require('../../event/botEvent');
+var Faq_kb = require("../../models/faq_kb");
+var winston = require('../../config/winston');
+
+var port = process.env.PORT || '3000';
+
+const TILEBOT_ENDPOINT = process.env.TILEBOT_ENDPOINT || "http://localhost:" + port+ "/modules/tilebot/";
+winston.debug("TILEBOT_ENDPOINT: " + TILEBOT_ENDPOINT);
+
+winston.info("Tilebot endpoint: " + TILEBOT_ENDPOINT);
+
+class Listener {
+
+    listen(config) {
+
+        winston.info('Tilebot Listener listen');
+        // winston.debug("config databaseUri: " + config.databaseUri);  
+        
+
+        var that = this;
+
+      
+        botEvent.on('faqbot.create', function(bot) {
+            if (TILEBOT_ENDPOINT) {
+
+                winston.debug('bot.type:'+bot.type); 
+                if (bot.type==="tilebot") {
+
+                    winston.debug('qui.type:'+bot.type); 
+
+
+                    Faq_kb.findByIdAndUpdate(bot.id, {"url":TILEBOT_ENDPOINT+bot.id}, { new: true, upsert: true }, function (err, savedFaq_kb) {
+
+                    // bot.save(function (err, savedFaq_kb) {
+                        if (err) {
+                         return winston.error('error saving faqkb tilebot ', err)
+                        }
+                        winston.verbose('Saved faqkb tilebot', savedFaq_kb.toObject())      
+                    });
+                }
+            }
+        });
+        
+    }
+
+}
+
+var listener = new Listener();
+
+
+module.exports = listener;

package/routes/faq_kb.js

@@ -133,7 +133,7 @@ router.post('/askbot', function (req, res) {
     }
     winston.debug('faq_kb ', faq_kb.toJSON());
     winston.debug('faq_kb.type :'+ faq_kb.type);
-    if (faq_kb.type =="internal") {
+    if (faq_kb.type =="internal" || faq_kb.type =="tilebot") {
 
 
 

package/routes/request.js

@@ -778,8 +778,8 @@ router.get('/', function (req, res, next) {
    *  THE SEARCH FOR DATE INTERVAL OF THE HISTORY OF REQUESTS ARE DISABLED AND 
    *  ARE DISPLAYED ONLY THE REQUESTS OF THE LAST 14 DAYS
    */
-                                                                        //secondo me qui manca un parentesi tonda per gli or
-  if ( history_search === true && req.project && req.project.profile && (req.project.profile.type === 'free' && req.project.trialExpired === true) || (req.project.profile.type === 'payment' && req.project.isActiveSubscription === false)) {
+                                                                        //fixato. secondo me qui manca un parentesi tonda per gli or
+  if ( history_search === true && req.project && req.project.profile && ((req.project.profile.type === 'free' && req.project.trialExpired === true) || (req.project.profile.type === 'payment' && req.project.isActiveSubscription === false))) {
 
 
     var startdate = moment().subtract(14, "days").format("YYYY-MM-DD");
@@ -992,7 +992,7 @@ router.get('/', function (req, res, next) {
     winston.debug('REQUEST ROUTE - objectToReturn ', objectToReturn);
 
     const endExecTime = new Date();
-    winston.info('REQUEST ROUTE - exec time:  ' + (endExecTime-startExecTime));
+    winston.verbose('REQUEST ROUTE - exec time:  ' + (endExecTime-startExecTime));
 
     return res.json(objectToReturn);
 

package/routes/widget.js

@@ -190,7 +190,42 @@ router.get('/', function(req, res, next) {
   
 
 
+  router.get('/ip', function(req, res, next) {
   
+     var xforwarded = req.headers['x-forwarded-for'];
+     winston.info('xforwarded'+ xforwarded);
+
+     var connectionRemoteAddress  = req.connection.remoteAddress;
+     winston.info('connectionRemoteAddress'+ connectionRemoteAddress);
+
+     var socketRemoteAddress = req.socket.remoteAddress;
+     winston.info('socketRemoteAddress'+ socketRemoteAddress);
+
+    if (req.connection.socket ) {
+      var connectionSocketRemoteAddress = req.connection.socket.remoteAddress;
+      winston.info('connectionSocketRemoteAddress'+ connectionSocketRemoteAddress);
+
+    }
+    
+
+    var ip = req.headers['x-forwarded-for'] || 
+     req.connection.remoteAddress || 
+     req.socket.remoteAddress ||
+     (req.connection.socket ? req.connection.socket.remoteAddress : null);
+    winston.info("ip:"+ ip);
+
+
+
+
+    const ipStandard = (req.headers['x-forwarded-for'] || '').split(',').pop().trim() ||        //https://stackoverflow.com/questions/8107856/how-to-determine-a-users-ip-address-in-node
+    req.socket.remoteAddress
+
+    winston.info("standard ip: "+ipStandard); // ip address of the user
+
+    res.json( {ip:ip, ipStandard:ipStandard} );
+
+
+  });
 
   
 

package/services/faqService.js

@@ -39,7 +39,7 @@ class FaqService {
           
           winston.debug('type '+ type)      
 
-          if (type==="internal") {      
+          if (type==="internal" || type==="tilebot") {      
             
             if (!template) {
               template = "example";