1b.app
Link copied -

The action "Turn a viber message into a business process" creates processes one time

The action "Turn a viber message into a business process" is configured, which creates a "Viber message" BP with the status NEW MESSAGE.

It includes options:

- Check for creation of business processes

- When checking for the creation of business processes, look only for tasks in the selected BP

When a new order enters the system, a sub-process is created in the "Viber message" BP in the ORDER CONFIRMATION status, in which a message is sent to viber with order confirmation. If the client does not have a viber id, then the message does not go away.

Also, an SMS is sent to the client with a link to the viber bot, in which a welcome message is written and the Share phone button is sent.

When a client shares a phone number, a contact is found in the box, and a search is made for the "Viber message" BP in the ORDER CONFIRMATION status. Then the status switches and a message is sent to viber with order confirmation. The message is delivered because have viber id.

---------------------------------

Correct operation of these settings occurs every other time.

The PROBLEM is that when receiving a phone number from the user, a new process is not created, and the comment is added to an already existing process. Despite the fact that at the time of receiving the phone number, the contact does not have a viber id.

I understand that this is due to the fact that all actions and procedures go in a row:

new client share number - process should be created --->

by number finds and merges client --->

because there is a client, no new process is created and the Share comment is added to the existing one.

---------------------------------

If this is the problem, then you can make sure that the process is created if the message is from a client who does not have a viber id?
Original question is available on version: ru

Answers:

Please close the thread, the issue has been fixed.
21.05.2023, 15:07
Original comment available on version: ru


Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment