FAQ About Wiki Tool

The knowledge developed by Mobilize members is divided throughout the company into different tools or sectioned through projects in Azure, this has led to a decentralization of information that prevents knowledge from being shared among members.

On the other hand, over the years, Mobilize Net has made use of different tools provided by third parties that have not fully met the company's expectations. This has caused much of the documented knowledge to be lost in the process, either because the tool does not provide any form of migration or because not as many resources can be allocated to migrate that knowledge to a new tool.

Finally, the procedure currently used to search for wikis can sometimes become a tedious process, since searches such as the person who created the wiki, topic related to the wiki, or creation date cannot be performed. This causes that on some occasions the wikis created previously cannot be found.

At the moment the tool, as in Azure, will not have any parallel work system. However, it is intended to use Web Sockets or some other technology to achieve the connection between the different participants in the documents. Which would be being implemented in future professional practices.

As in Azure, the Markdown format will be used to write and display the wikis, for the moment it will be using the angular markdown tool that you can visit at the following link: https://github.com/lon-yang/ngx-markdown-editor . However, this may change in during the rest of the development

It will be as fast as an Azure, with the difference that there are new types of attributes that will make the search easier and will improve the user experience, such as tags, authors, and collaborators.

One of the features to implement is the notification system, which will allow the user to receive these types of messages, both in the application and by mail.

Notifications will be divided into two sections:

Actions

• Someone has modified the wiki in which I am an author
• Someone has requested the revision of the wiki in which I am a reviewer
• Someone has posted a wiki where I am: contributor/author/reviewer
• Someone has created a review on your wiki
• Someone has reviewed your wiki

Achievements

• You have reached the 10th position in the top of most-read wikis
• This month you have achieved 200 readings among all your wikis
• You are the user with the most wikis created in the month

Yes, it will be possible to stop the sending of notifications by mail.

Yes, it can be done, however, when the application is launched, this will only be possible by asking the application administrator for help. In the future, a system similar to Google Drive will be implemented to obtain past versions of the document.

Users are going to be authenticated through the Microsoft library: Microsoft Authentication Library (MSAL), which is responsible for keeping user credentials safe and ensuring that only people who are part of the organization enter.

Wiki tool does not use any sensitive information, it only stores the ID provided by Microsoft along with the display name and the company email. The other information displayed in the application (such as the User image) is taken directly from the Microsft Graph API.

No, the user will be only authorized to add new tag names, but only the moderators of the application will be able to assign an image and a respective color to the new tag.

At the moment the formats offered are the Markdown and the PDF type.

When starting the application, the user will be able to search for wikis by the following parameters:

• Wiki title
• Tag name
• Author name
• Date range

However, through the Wiki Tool API, it is possible to perform almost any type of query thanks to the Odata implementation. You can see a little more of the actions that can be performed from the Wiki Tool API by following the following link: https://collaboration.artinsoft.com/tfs/Product/Services/_wiki/wikis/Services.wiki/1007/How- to-use-the-Wiki-Tool-API