VAD Bug

Discussion in 'CRM / Helpdesk / App Integration' started by SWSDEV, Nov 14, 2010.

Thread Status:
Not open for further replies.
  1. SWSDEV

    SWSDEV Member

    Joined:
    Feb 23, 2008
    Messages:
    256
    Likes Received:
    0
    Create a custom component and then drop it on a call flow. Then delete the custom component from project explorer.

    The component ends up staying on the call flow where you dropped it, even though it has been deleted. If you double click on it in the call flow the VAD throws an error because it can't find the files.

    You probably want to warn when a component is deleted, whether or not it is currently in use on any call flows in the project, before deleting it.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. VAD_Support

    VAD_Support Active Member

    Joined:
    Aug 6, 2009
    Messages:
    690
    Likes Received:
    0
    Hi Shahzad,

    Thanks for your feedback. I think that the behavior should be the same than when you open a project and the component is not there. In that case the component is disabled in the designer, so you don't get any error, even when compiling it. Also, maybe an additional warning message should be shown when the component is being used.

    We'll check this and make the required changes for the next release.

    Thanks and regards,
     
  3. VAD_Support

    VAD_Support Active Member

    Joined:
    Aug 6, 2009
    Messages:
    690
    Likes Received:
    0
    Hi Shahzad,

    We have been working on this. Now, when you delete a custom component, we automatically disable that component everywhere it is used.

    Thanks for your help reporting this.

    Regards,
     
Thread Status:
Not open for further replies.