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.
Hello, I created a DQC Plan where I have extract filter which is connected to an Update step at out connection and another Update step at out_extract connection. Right now when I run my plan both the Update steps are getting processed in parallel. I would like the Update step connected to out edge process first and then kick off the Update step connected to out_extract edge. Can someone suggest a pattern or a technique I could use to achieve this sequencing? Thanks.This message has been edited. Last edited by: Tamra,
iSM 616 iDM 7705 iDQC 802 WF 77 Windows 2008 Server
The easiest way to do this is to place a join after the update on the 'out' step but before the update on the 'out_extact' step. You may also want to have another filter to remove the duplicate records since the 'out' side will contain all records while 'out_extract' will on contain those meeting the filter criteria?