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.
Originally ACCEPTS applied to MODIFY only in that they were to automatically screen out bad data. However under 7.6 they have started working like screening conditions.
I have
FIELD=EET_OVERTIME_ENTITLED, ALIAS=OVERTIME_ENTITLED, ACCEPT= '0' OR '1', USAGE=A5, ACTUAL=A5, MISSING=ON, TITLE='Entitled,to,Overtime', DESCRIPTION='Entitled to Overtime 0 or 1', $
on an Oracle table. Mistakenly I thought the codes were 0 or 1 but they are actually TRUE and FALSE.
However when you run a report that references this field the ACCEPTS apply and you get 0 records!
This may be a result of the new HOLD format XFOCUS since report generation is actually insertion of records into FOCSORT an XFOCUS database so accidentally the rules may have been allowed to apply.
This is not a great problem to me because I will remove all ACCEPTS from tables but I suggest someone gets it fixed.
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
FYI, if you think it is an issue to be fixed, please contact Information Builders' Customer Support Services and open a case to submit the request. This is the official way to work on it. You can either contact the local branch, or call 1-800-736-6130 (if you are domestic), or access online at InfoResponse.
Thank you.
Cheers, Kerry
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004
In 764, TABLE will revert to the 761 and prior behavior where the accepts clause has no affect on TABLE retrieval. It will only be used to enforced database updates.
Brian Suter VP WebFOCUS Product Development
Posts: 200 | Location: NYC | Registered: January 02, 2007