‘Link’ to other database’s conversation.

Announcements, support questions, and discussion for the Dialogue System.
Post Reply
wodnr97
Posts: 4
Joined: Sat Jul 31, 2021 2:59 am

‘Link’ to other database’s conversation.

Post by wodnr97 »

Hi.
We are small team, and co-working on making dialogues by making multiple databases.

We want:
- Link Database A’s conversation to Database B’s conversation. (Ex: when end of conversation, link to other database’s conversation)
- Is it possible to do this in dialogue database editor?

Is there any way to achieve it?
Thanks.
User avatar
Tony Li
Posts: 21970
Joined: Thu Jul 18, 2013 1:27 pm

Re: ‘Link’ to other database’s conversation.

Post by Tony Li »

Hi,

You can't create a cross-conversation link from one database to another database inside the Dialogue Editor.

Technically you can created a link by closing the Dialogue Editor and manually adding an Outgoing Link element:
Cross-database link (use caution)
unsafeCrossDBLink.png
unsafeCrossDBLink.png (69.44 KiB) Viewed 399 times
However, it may be better to use two Dialogue System Triggers. Configure one to start normally. Set the other to OnConversationEnd:

linkedDBs.png
linkedDBs.png (53.5 KiB) Viewed 399 times
wodnr97
Posts: 4
Joined: Sat Jul 31, 2021 2:59 am

Re: ‘Link’ to other database’s conversation.

Post by wodnr97 »

Thanks for your reply. :)

In your first picture, I can see that you used 'id' of other database.
does this mean 'id' is only matters for linking other database?
If it is true, will it be important that assign different conversation IDs for each database? (like 100-200 to Database A, 201 - 300 to Database B)
User avatar
Tony Li
Posts: 21970
Joined: Thu Jul 18, 2013 1:27 pm

Re: ‘Link’ to other database’s conversation.

Post by Tony Li »

Yes. IDs must be unique across all databases. (See Working With Multiple Databases.) Normally you will use the Unique ID Tool to make IDs unique.

In version 2.2.19, you will also be able to specify the 'starting ID' for each database -- for example, database A can use IDs 0 - 999, database B can use IDs 1000-1999, etc. This way you can usually avoid using the Unique ID Tool.
Post Reply