There were also other interesting

[hasibaakterss3309]

In B24, there is a connection between cities and projects. If the user selects a project, the city is automatically entered into the "Business Trip" business process launch form. As it turned out, this is not always necessary. For example, the central office of one of the group's companies is located in Moscow, but there are employees who work from St. Petersburg. If they go on a business trip from the central office, the departure city is defined as Moscow and the St. Petersburgers cannot fly out normally. To solve this problem, we added manual selection of the departure city, which entailed editing the form and refining the approval process.

Velesstroy accounting solves some of the tasks in kuwait telegram number database Bitrix24, but business trips are processed on the 1C:ZUP side. At the client's request, we developed a mechanism that generates the task text in B24 (title, person, dates, route, priority, etc.) and transfers it to ZUP. This solution has one drawback - the accounting department must manually transfer data from the task to 1C.

For this reason, the task of creating and transferring an object (JSON with business trip data) from B24 to 1C to form "Business Trip" documents and a business trip order on its basis has been moved to the backlog. After all, it is impossible to simply create and transfer JSON to 1C (so that it works right away), 1C needs to be modified. It will be necessary to organize the storage of this object, its processing (logic for collecting task text in 1C), add buttons to the task form, implement a mechanism for creating documents and storing a connection with the task.