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 Tom A couple of questions. 1) Are the forms in the same Maintain procedure or are you using CALL to branch from one Maintain to another?
2) How are you retrieving the User id? And when you do, how are you storing it? If you retrieve it and store it in a variable, it should be available to the entire application and all of the forms.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
You will need to pass the variable containing the User Id on the Call command line if you want it to be available in the next Winform. A child or CALLed Maintain does not inherit values from the parent. You can pass in stacks and variables to bring those values in.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
Originally posted by Maintain Wizard: You will need to pass the variable containing the User Id on the Call command line if you want it to be available in the next Winform. A child or CALLed Maintain does not inherit values from the parent. You can pass in stacks and variables to bring those values in.
Mark
Can the new form not query the IBIMR_user variable embedded in the cookie just like the first?
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
Although I cannot find reference anywhere, I think that the CALLed procedure cannot access these variables and cannot use WINFORM, it is basically a dumb process.
Most variables you get for a maintain are passed in on, or through, the command line or in the header; but no WINFORM => no header => no header variables.
As it is not called from WebFOCUS then no &variables will be around, like IBIMR_user.
That sort of makes sense to me, does it to you?
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007
A CALLed procedure can absolutely have Winforms. However, If the variable was passed into the Parent (or CALLing) Maintain, then it will not be available to the child. You will have to pass it in.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
Must admit I haven't used a CALL for 12 years now, so am rusty with it! However, the CALLed Maintain, even when running on the same server, does not pick up any variables that the parent can access.
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007