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.
OK. If you are using Designer, I am interesting in knowing why would you like to use a Service Object and not Process Object? When using a Process Object, it gives you a total list of all pFlows published on the registry which makes it easier for you to make a single-click selection.
If you are using iIT, have both the pFlows, that is, the calling and the called in the same project. Drag and drop the sub pflow on to the process flow editor of the calling pFlow and run a test, which by default, prompts for publishing to registry.
I am guessing it to be a packaging problem. Let me know the result.
- SriiThis message has been edited. Last edited by: Srii,