As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Hi, While working on the infoassist, I am getting the error message saying "Unexpected Behaviour Notification" with following details; "Code: 0 Type: xValidateFex". The error does not appear on regular basis, it occurs while performing various operations, like sometimes when we drag and drop the fields to the canvas or when we select different themes and so. Also the error is not specific to a report or master file and there is no javascript error. Have anyone received this kind of error earlier and any resolution they found for this or any idea to debug this issue? Please suggest.
Thanks in advance.This message has been edited. Last edited by: Kerry,
Hi Waz, The case is already raised for this issue.This issue is not specific to any fex.It can come for any report which has different mas and fex file associated with it. It is a completely random issue which comes any time while creating any report.There is no specific set of steps we perform to reproduce this error. Is it a known issue in IA? If yes, then Is there any fix available for this issue? Have anyone faced it anytime in past? Please provide guidance.