Rocket.Chat

Rocket.Chat 3.1.1 LATEST

Windows XP / Vista / Windows 7 / Windows 8 / Windows 10

Rocket.Chat 2021 full offline installer setup for PC 32bit/64bit

Rocket.Chat is the ultimate chat platform for Windows PC. Experience the next level of team communications! Rocket.Chat is an incredible product because it has an incredible developer community. Over 200 contributors have made this platform a dynamic and innovative toolkit, from group messages and video calls to helpdesk killer features. Access from anywhere: web browser, desktop, and mobile applications. Set up your system exactly how you want it. Rebrand as needed. The code is 100% Open Source under the MIT license. Fork it on GitHub. Packages are at the core of the software capabilities, offering an impressive array of features aimed at making your business succeed.

Rocket.Chat customizations and services at affordable rates! Including white labeling, custom integrations, data imports, and feature development. More services are available at request! Make your the tool installation your very own with your own branding everywhere! Get that feature you want or need with custom Rocket Chat feature development!

VIDEO CONFERENCE
Chat with your colleagues and friends face-to-face over audio and video.

HELPDESK CHAT
Have your website visitors contact you in real-time and increase conversions.

FILE SHARING
Drag-and-drop files or select them from your computer or mobile device.

VOICE MESSAGES
Record and transmit voice messages to a channel, group, or private conversation.

LINK PREVIEW
Post a link and immediately view its content. YouTube, Twitter, Gifs!

API
Integrate your chat to multiple services: GitHub, GitLab, JIRA, Confluence, and others.

EXTENDABILITY
Want a killer new feature? Add a new package. It is as simple as that.

NATIVE APPLICATIONS
Native client applications are available for download on Linux, Windows, and macOS.

MOBILE APPLICATIONS
Mobile client applications are available for iOS and Android in their respective stores.

Обзор корпоративного мессенджера RocketChat

Многие компании в качестве корпоративного мессенджера используют распространенные бесплатные продукты: Skype, Telegram, Viber и другие. Но не всем такие решения подходят, например, против часто выступает служба безопасности компании.

Основные недостатки публичных мессенджеров:

• Утечка информации внутри компании. Через публичный мессенджер сотрудник может легко переслать файлы или сообщения любому другому человеку, просто добавив его контакт в адресную книгу мессенджера. Для этого не нужно особых прав на компьютере, а также такую передачу информации никак не отследить.
• Нет возможности контроля внутренней службой безопасности. Сотрудники службы безопасности компании не могут читать переписку пользователей или как-то ее фиксировать, поскольку обмен сообщениями и файлами идет через серверы компании владеющей мессенджером.
• Раскрытие данных владельцем мессенджера. Известны факты записи, хранения и предоставление государственным органам переписки пользователей таких сервисов. Например, предоставление компанией Майкрософт доступов к переписке пользователей Skype. Конечно, есть другие мессенджеры, такие как Telegram, которые обеспечивают шифрование между конечными точками и избавлены от такого риска.

Тестовый стенд

Соответственно, чтобы решить вышеописанные проблемы, необходим мессенджер, который можно разместить на собственных серверах. Наше внимание привлек внимание продукт RocketChat по таким основным параметрам: он бесплатный, активно развивается и обладает приемлемым дизайном. В результате было решено выполнить его тестирование и проверить насколько удобно реализованы интересующие нас заявленные в нем функции.

Характеристики тестового стенда:

• Версия RocketChat Server: 0.59.1
• Версия NodeJS: 4.8.4
• Архитектура: x64
• Платформа CentOS 7

Продукт не требователен к ресурсам, поэтому характеристики сервера указывать смысла нет.

Результаты тестирования

Результаты тестирования предоставляем в виде 3-х блоков:

• Блок 1. Функции, при тестировании которых проблем не обнаружено
• Блок 2. Функции, при тестировании которых возникли замечания
• Блок 3. Функции, работоспособности которых не удалось добиться

Таблица 1. Функция при тестировании которых замечаний не обнаружено

№	Функция	Комментарий
1	Работа клиента в RDP сеансе	Работает
2	Работа клиента в WEB браузере	Работает
3	Работа клиента на платформе Android	Работает
4	Работа клиента на платформе iOS	Работает
5	Работа клиента на ОС Windows	Работает
6	Отработка уведомлений и push-сообщений на всех платформах	Работает
7	Основные функции чата — приватная переписка	Работает
8	Основные функции чата — создание групп и чатов	Работает
9	Основные функции чата — отправка всех типов файлов и скриншотов	Работает
10	Ограничение по типам передаваемых файлов	Работает
11	Ограничение по размерам передаваемых файлов	Работает

Данный блок комментировать не будем, так как заявленный функционал работает в полной мере и никаких проблем или замечаний по ним не обнаружили, ниже приведены скриншоты, иллюстрирующие дизайн и функционал продукта.

Рисунок 1. Мобильное приложение RocketChat

Рисунок 2. Push-сообщения в мобильной версии чата

Рисунок 3. Web-интерфейс программы и передача файла

Рисунок 4. Настройка передачи файлов, а также их типа и размера

В следующей таблице указан функционал, при тестировании которого возникли замечания.

Таблица 2. Функции, при тестировании которых возникли замечания

№	Функция	Комментарий
1	Чтение переписки сотрудников администратором или сотрудником службы безопасности	Доступ к логам переписки осуществляется только при обращении к БД непосредственно на сервере. Других возможностей извлечь логи нет. Как следствие, вопрос получения записей трудозатратный и выполняется в ручном режиме.
2	Шифрованное подключение	Реализуется через https, но требуется покупка и подключение SSL-сертификата.
3	Запись аудиосообщений в чате и их отправка	При использовании мобильных устройств функция работает только в Web-браузере, а в приложении не работает.

Чтение переписки сотрудников возможно, но сама переписка выводится в консоль и при большом количестве сотрудников и комнат это не удобно. Также сам синтаксис запроса относительно сложный. Было бы хорошо иметь какую-то оболочку, которая извлекала бы данные из базы и формировала наглядные отчеты.

Рисунок 5. Запрос администратора к базе данных и вывод в консоль переписки пользователей

Запись и отправка аудиосообщений работает аналогично, как и у других мессенджеров, но только из Web-версии. В приложении функционал не работает.

Рисунок 6. Запись и отправка аудиосообщения. Работает только в Web-браузере

В следующей таблице указан функционал, который пока не работает в мессенджере.

Таблица 3. Функции, работоспособности которых не удалось добиться

№	Функция	Комментарий
1	Запретить клиенту подключение к другому серверу RocketChat	Данная функция необходима для избежания утечки информации через чат. Пользователь, имея установленный клиент, может без каких-либо дополнительных прав подключится к своему серверу RocketChat и передать данные или файлы. Проблема решается только сетевым экраном, который запрещает все соединения изнутри сети, кроме разрешенных. Блокировка только стандартного порта RocketChat проблему не решает, поскольку сервер может быть настроен на нестандартный порт.
2	Отслеживание передачи файлов	Отследить передачу файлов в логах RocketChat нет возможности. Логирование передаваемых файлов не ведется.
3	Создание видеоконференций и показа во время них своего экрана	Функционал заявлен как экспериментальный и пока не гарантируется разработчиком, по факту не работает.
4	Аудио- и видеозвонки	Функционал заявлен как экспериментальный и пока не гарантируется разработчиком, по факту не работает.

Выводы

Тестирование показало, что некоторый функционал работает с замечаниями или пока не реализован в данному продукте, соответственно, продукту есть еще куда развиваться. В данный момент, RocketChat отстает по функционалу от публичных мессенджеров в плане аудио- и видеозвонков, демонстрации экрана и других функций, но продукт активно развивается и, скорее всего, эти функции появятся в ближайшее время.

По нашему мнению, RocketChat — продукт, заслуживающий внимания. Он занимает своеобразную нишу среди других мессенджеров и подходит для компаний, которые по разным причинам хотят иметь собственный мессенджер вместо публичных сервисов вроде Telegram, Skype, Viber, но не готовы внедрять достаточно тяжелые и дорогие продукты (например, Slack) и не используют аудио/видео связь.

EFSOL Системная интеграция. Консалтинг

Rocket chat windows клиент

Rocket.Chat Desktop App

Desktop application for Rocket.Chat available for macOS, Windows and Linux using Electron.

Share your story

We’d love to hear about your experience and potentially feature it on our Blog.

Subscribe for Updates

Once a month our marketing team releases an email update with news about product releases, company related topics, events and use cases. Sign Up!

You can download the latest version from the Releases page.

Launch the installer and follow the instructions to install.

On Windows you can run a silent install by adding the /S flag. You can also add the options below:

• /S — Silent install
• /allusers — Install for all users (requires admin)
• /currentuser — Install only the for current user (default)
• /disableAutoUpdates — Disable automatic updates

Now just clone and start the app:

Structure of the project

The source is located in the src folder. Everything in this folder will be built automatically when running the app with yarn start .

The build process compiles all stuff from the src folder and puts it into the app folder, so after the build has finished, your app folder contains the full, runnable application.

Following the ongoing changes in Rocket.Chat codebase, the app was rewritten in TypeScript 4 to address issues regarding maintainability.

The build pipeline

The build process is founded upon rollup bundler. There are three entry files for your code:

src/main.ts , the script running at the main Electron process, orchestrating the whole application;

src/rootWindow.ts , the script that renders the UI of the root window, the app’s main window;

and src/preload.ts , which runs in a privileged mode to connect the app and the webviews rendering Rocket.Chat’s web client.

Adding Node.js modules

Remember to respect the split between dependencies and devDependencies in package.json file. Only modules listed in dependencies will be included into distributable app.

Follow the installation instruction on node-gyp readme.

You will need to install the following packages:

You will need to install the following packages:

On Windows 7 you may have to follow option 2 of the node-gyp install guide and install Visual Studio.

We use Jest testing framwork with the Jest electron runner. It searches for all files in src directory that match the glob pattern *.(spec|test). .

Making a release

To package your app into an installer use command:

It will start the packaging process for operating system you are running this command on. Ready for distribution file will be outputted to dist directory.

All packaging actions are handled by electron-builder. It has a lot of customization options.

Rocket chat windows клиент

Add tag input to Closing Chat modal (#21462)

Admin Users list pagination (#21469)

• Fix Administration/Users pagination

App installation from marketplace not correctly displaying the permissions (#21470)

Fixes the marketplace app installation not correctly displaying the permissions modal.

Close chat button is not available for Omnichannel agents (#21481)

Error when editing Omnichannel rooms without custom fields (#21450)

Header component breaking if user is not part of teams room. (#21465)

Make Omnichannel’s closing chat button the last action in the toolbox (#21476)

Omnichannel queue manager returning outdated room object (#21485)

The Omnichannel Queue Manager is returning outdated room object when delegating the chat to an agent, hence, our Livechat widget is affected and the agent assigned to the chat is not displayed on the widget, only after refreshing/reloading.

Wrong useMemo on Priorities EE field. (#21453)

👩‍💻 👨‍💻 Core Team 🤓

sampaiodiego released this Apr 5, 2021

2021-04-03 · 7 🎉 · 11 🚀 · 36 🐛 · 60 🔍 · 38 👩‍💻👨‍💻

Engine versions

• Node: 12.21.0
• NPM: 6.14.8
• MongoDB: 3.4, 3.6, 4.0
• Apps-Engine: 1.24.0

🎉 New features

You can easily group your users as Teams on Rocket.Chat. The feature takes the hassle out of managing multiple users one by one and allows you to handle them at the same time efficiently.

Teams can be public or private and each team can have its own channels, which also can be public or private.
It’s possible to add existing channels to a Team or create new ones inside a Team.
It’s possible to invite people outside a Team to join Team’s channels.
It’s possible to convert channels to Teams
It’s possible to add all team members to a channel at once
Team members have roles

Quickly onboard new users with Autojoin channels

Teams can have Auto-join channels – channels to which the team members are automatically added, so you don’t need to go through the manual process of adding users repetitively

Instantly mention multiple members at once (available in EE)

With Teams, you don’t need to remember everyone’s name to communicate with a team quickly. Just mention a Team — @engineers, for instance — and all members will be instantly notified.

APPS: Map description as a room value in Apps (#20811)

Add the description value of a room as a mapped value in the Apps-Engine. That way developers can get the description information from a room in their app.

APPS: New event interfaces for pre/post user leaving a room (#20917)

Added events and errors that trigger when a user leaves a room.
That way it can communicate with the Apps-Engine by the IPreRoomUserLeave and IPostRoomUserLeave event interfaces.

Enterprise: Omnichannel On-Hold Queue (#20945)

About this feature

This feature has been introduced to deal with Inactive chats. A chat is considered Inactive if an Omnichannel End User (aka Visitor) has not replied back to an agent in some time. These types of inactive chats become very important when an organisation has a limit set for Max Simultaneous Chats per agent which is defined by the following setting 👇 , as more number of Inactive chats would directly affect an agent’s productivity.

Before this feature, we only had one option to deal with such Inactive/Abandoned chats — which was to auto close abandoned chats via this setting 👇

however closing a chat isn’t a best option for some cases. Let me take an example to explain a scenario

An agent is assisting a customer for installing a very huge software which is likely to take more than 20-30 minutes to download. In such scenarios closing a chat isn’t the best approach since even after the lengthy download the customer might still need some assist from the agent.
So basically this chat is going to block the agent’s queue until the customer is able to finish his time-consuming download task in which he/she doesn’t require any agent’s assistance. Due to the Max Simultaneous Chats per agent limit, the agent is also not able to use this extra time to help other customer thus affecting his overall productivity.

So how does the On-Hold feature solve this problem?
With the On-Hold feature, an agent is now able to place a chat on-hold. On-Hold chats don’t count towards the maximum number of concurrent chats an agent can have. So in our above example, the agent can simply now place the customer on-hold for 20-30 minutes until the customer downloads the software and within this time, the agent can serve other customers — hence increasing the productivity of an agent.

Working of the new On-Hold feature

How can you place a chat on Hold ?

A chat can be placed on-hold via 2 means

Automatically place Abandoned chats On-hold

Via this 🔝 option you can define a timer which will get started when a customer sends a message. If we don’t receive any message from the customer within this timer, the timer will get expired and the chat will be considered as Abandoned.

The via this 🔝 setting you can choose to automatically place this abandoned chat On Hold

Manually place a chat On Hold
As an admin, you can allow an agent to manually place a chat on-hold. To do so, you’ll need to turn on this 👇 setting

Now an agent will be able to see a new On Hold button within their Visitor Info Panel like this 👇 , provided the agent has sent the last message

How can you resume a On Hold chat ?

An On Hold chat can be resumed via 2 means

If the Customer sends a message
If the Customer / Omnichannel End User sends a message to the On Hold chat, the On Hold chat will get automatically resumed.

Manually by agent
An Agent can manually resume the On Hold chat via clicking the Resume button in the bottom of a chat room.

What would happen if the agent already reached maximum chats, and a On-Hold chat gets resumed ?

Based on how the chat was resumed, there are multiple cases are each case is dealt differently

If an agent manually tries to resume the On Hold chat, he/she will get an error saying Maximum Simultaneous chat limit reached

If a customer replies back on an On Hold chat and the last serving agent has reached maximum capacity, then this customer will be placed on the queue again from where based on the Routing Algorithm selected, the chat will get transferred to any available agent

Ability to hide ‘Room topic changed’ system messages (#21062 by @Tirieru)

Add Omnichannel Livechat Trigger option for when user opens the chat window (#20030 by @reda-alaoui)

Quick action buttons for Omnichannel (#21123)

🚀 Improvements

Add spacing between elements in Profile Page (#20742 by @cyberShaw)

Added modal-box for preview after recording audio. (#20370 by @Darshilp326)

A modal box will be displayed so that users can change the filename and add description.

Before

After

Adds toast after follow/unfollow messages and following icon for followed messages without threads. (#20025 by @RonLek)

There was no alert on following/unfollowing a message previously. Also, it was impossible to make out a followed message with no threads from an unfollowed one.

This PR would show an alert on following/unfollowing a message and also display a small bell icon (similar to the ones for starred and pinned messages) when a message with no thread is followed.

Back to threads list button on threads contextual bar (#20882)

Better new channel popover (#21018)

grammatical typos in pull request template (#21115 by @sumukhah)

Improve Apps permission modal (#21193)

Improve the UI of the Apps permission modal when installing an App that requires permissions.

New UI:

Old UI:

Make debug logs of Apps configurable via Log_Level setting in the Admin panel (#21000 by @meomay503)

Re-design Omnichannel Room Info Panel (#21199)

Set description in create channel modal (#21132)

Sort Users List In Case Insensitive Manner (#20790 by @aditya-mitra)

The users listed in the admin panel were sorted in a case-sensitive manner , where the capitals came first and then the small letters (like — A B C a b c). This Change fixes this by sorting the names in a caseinsensitive manner (now — A a B b C c).

Before

With This Change

🐛 Bug fixes

‘Chats in Progress’ Section is not rendering when the routing algorithm is not Manual Selection (#21324)

«Taken At» and «Average of Response Time» fields not rendering properly on Room Information panel (#21365)

Apps: Fix Game Center icon disappeared after the React refactor (#21091)

APPS: Warn message while installing app in air-gapped environment (#20992)

Change error message to a warn message when uploading a .zip file app into a air-gapped environment.

The error message was giving the impression for the user that the app wasn’t properly being installed , which it wasn’t the case:

A more detailed warn message can fix that impression for the user:

Add missing unreads field to users.info REST endpoint (#20905)

Added hideUnreadStatus check before showing unread messages on roomList (#20867 by @yash-rajpal)

Added hide unread counter check, if the show unread messages is turned off, now unread messages badge won’t be shown to user.

Broken message fields attachment handling (#21069)

Avoids an undefined value to break a rendered attachment.

Correct direction for admin mapview text (#20897 by @aKn1ghtOut)

The text says the share button will be on the left of the messagebox once enabled. However, it actually is on the right.

Correct ignored message CSS (#20928 by @aKn1ghtOut)

Modified the CSS to not affect the ignored sequential messages exactly like the non-ignored messages, which is what was causing the second and further ignored message o appear weirdly when unhidden one by one.

Correct Inline reactions behaviour (#20743 by @aKn1ghtOut)

The $().data function was returning outdated values for re-assigned emoji buttons with new data. Changed that to use the .attr() function. This works perfectly.

Correct Typo — donwload to download (#21096 by @aditya-mitra)

Correct the spelling of donwload to download in TitleLink of Attachments.

Custom emojis to override default (#20359 by @aKn1ghtOut)

Due to the sequence of the imports and how the emojiRenderer prioritizes lists, the custom emojis could not override the emojione emojis. Making two small changes fixed the issue.

With the custom emoji for :facepalm: added, you can check out the result below:

Before

After

Empty URL in user avatar doesn’t show error and enables save (#20440 by @im-adithya)

Added toast and disabled save.

Ensure E2E is enabled/disabled on sending message (#21084)

Rooms which were encrypted somewhere in the past still could encrypt messages due to a race condition due to a query over Subscriptions collection.

Fix the search list showing the last channel (#21160 by @shrinish123)

The search list now also properly shows the last channel
Before :

Follow thread action on threads list (#20881)

Iframe flags for audio and video on the BigBlueButton integration (#20879 by @fcecagno)

Inactivity Time field displaying wrong information (#21363)

Incorrect time format of the Queue Time field on the room information page (#21394)

Make custom emoji file required (#19583 by @m-shreyansh)

Missing app permissions translation (#21066)

Add missing translations for some app permissions

Missing Keywords in Permissions (#20354 by @im-adithya)

The keywords were added to the i18n folder. (Default only)

Multi Select isn’t working in Export Messages (#21236 by @PriyaBihani)

While exporting messages, we were not able to select multiple Users like this:

Now we can select multiple users:

New Channel popover not closing (#21080)

OEmbedURLWidget — Show Full Embedded Text Description (#20569 by @aditya-mitra)

Embeds were cutoff when either urls had a long description.
This was handled by removing overflow:hidden;text-overflow:ellipsis; from the inline styles in oembedUrlWidget.html .

Earlier

Reactions list showing users in reactions option of message action. (#20753 by @Darshilp326)

Reactions list shows emojis with respected users who have reacted with that emoji.

Removing truncation from profile (#20352 by @aKn1ghtOut)

Truncating text in profile view was making some information completely inaccessible. Removed it from the user status and the custom fields where if the information is longer, the user would actually want to see all of it.

Before

After

Replace wrong field description on Room Information panel (#21395)

Reply count of message is decreased after a message from thread is deleted (#19977 by @yash-rajpal)

The reply count now is decreased if a message from a thread is deleted.

Set establishing to false if OTR timeouts (#21183 by @Darshilp326)

Set establishing false if OTR timeouts.

Sidebar scroll missing full height (#21071)

undefined in PruneMessages deleting DM (#20873 by @vova-zush)

Fix undefined in Prune Messages in direct

Unexpected open or close visitor info (#21094)

The VisitorInfo component closes or open every time a new message was sent, this PR fix that.

Use the correct icons for DMs (#21125)

Visitors.info endpoint being called multiple times (#21350)

Wrong license seats number administration info panel (#21222)

The administration info panel was showing the total of users as the number counted for the usage of the license seats. Now it’s showing the correct number that is active users. This was not affecting the license validation on the server-side, only causing confusion for the administrators to check how the usage was being counted.

[Fix] Broken useEffect opened new BBB Tab twice (#20770 by @Cosnavel)

Bump Livechat Widget (#21264)

Update Livechat version to 1.9.0

Change the order of Sort Setup Wizard options (#21073)

Sort options in select fields of settings during Setup Wizard according to browser’s locale.

Chore: Add tests for Meteor methods (#20901)

Add end-to-end tests for the following meteor methods