Issue with Virtual agent Designer

Sathya10
Tera Expert

Hi All,

I'm trying to create a new flow for virtual agent where i'm redirecting the user to a service portal URL based on his choices. I'm receiving the following message in the test window.

[PREVIEW ONLY] subflow link_unfurling was called. Please view execution details in Flow Designer using context ID

find_real_file.png

Can anybody guide me on how to remove this message ? 

1 ACCEPTED SOLUTION

Filipe Cruz
Kilo Sage
Kilo Sage

Hello Sathya,

One option is to avoid the link unfurling error by disabling link unfurling property:

com.glide.cs.enable_link_unfurling

 

  • Select "Global" in the Application Picker
  • sys_properties.list
  • New
    • Suffix: com.glide.cs.enable_link_unfurling
    • Application: Global            (scoped application will not work)
    • Description: Enable/disable link unfurling (previewing).
    • Type: true | false
    • Value: false
  • Click on "Update"

The link unfurling error should no longer appear since link unfurling has been disabled. 
Please notice that link unfurling is now disabled for the entire instance.

Please, if this answer is relevant for you and solved your issue, please mark it as correct and helpful.

Thanks,

Filipe

View solution in original post

2 REPLIES 2

Filipe Cruz
Kilo Sage
Kilo Sage

Hello Sathya,

One option is to avoid the link unfurling error by disabling link unfurling property:

com.glide.cs.enable_link_unfurling

 

  • Select "Global" in the Application Picker
  • sys_properties.list
  • New
    • Suffix: com.glide.cs.enable_link_unfurling
    • Application: Global            (scoped application will not work)
    • Description: Enable/disable link unfurling (previewing).
    • Type: true | false
    • Value: false
  • Click on "Update"

The link unfurling error should no longer appear since link unfurling has been disabled. 
Please notice that link unfurling is now disabled for the entire instance.

Please, if this answer is relevant for you and solved your issue, please mark it as correct and helpful.

Thanks,

Filipe

Hi @Filipe Cruz - we get a similar error however slightly different.

Do you know how we could resolve this?

 

DanielR2_0-1721895785664.png