get an argument value from grand parent ux in grand child ux

[RichCPT]

Re: get an argument value from grand parent ux in grand child ux

Frank,
The "Arguments" are passed to the called component. The called component may not always use the arguments, but it will pass them along to the next component. Sometimes, I put stuff into the state variable for the component.

Gandhi,
The problem with the global variable approach comes into play when you have a tabbedUI interface, or anything like it, that allows multiple instances of the same parent or grandparent. If you set a global variable and are able to capture it at just the right time and save a local copy to the child component then you are okay. But when you are trying to use arguments at both the client and server side it becomes quite difficult. Then when you throw in the fact that components can be cached, everything goes haywire. Alpha had to remove the caching option when arguments were used in Text Box with associated Lookup Grid, that I had pointed out to them.

[RichCPT]

Re: get an argument value from grand parent ux in grand child ux

Frank,
Here is an Alpha Workspace that shows the various techniques I have used for passing arguments:
https://drive.google.com/open?id=0Bz...lhfaTJPOXhVU3M

I posted this example here a long time ago and just uploaded a fresh copy to google drive.

I have always hoped someone would share a better way of doing some of the things that you will see in there. I've especially been hopeful that Alpha could build in a framework for cleanly handing arguments with Grid components on the Client Side.

You will find a tabbedUI component in it, run that in working preview.

[frankbicknell]

Re: get an argument value from grand parent ux in grand child ux

Thanks for sharing your help on this Rich. I don't see how to pass arguments from one ux to another. I can only know how to pass arguments to controls and from controls to arguments. I look forward to seeing your example.

[Davidk]

Re: get an argument value from grand parent ux in grand child ux

Hey Rich, could you open up your posted example? It's locked up right now and needs permission to get it.

[RichCPT]

Re: get an argument value from grand parent ux in grand child ux

David,
I just downloaded it and opened it okay in Build 2689, aa sensed that the workspace was not in its original location and analyzed the components and it opened okay. I unzipped it fresh again from the download and opened it in build 2999 okay. So, I don't know what kind of error you are getting. Did the file perhaps get corrupted during your download?

[Davidk]

Re: get an argument value from grand parent ux in grand child ux

When I click on the link I get a Google Drive... You need permission page... with a button to request access... which I did... but haven't seen any permissions come through. You can probably open it because you're the owner.

[RichCPT]

Re: get an argument value from grand parent ux in grand child ux

See if this link is any different:
https://drive.google.com/file/d/0BzF...ew?usp=sharing

[Davidk]

Re: get an argument value from grand parent ux in grand child ux

Yes... thanks... got it this time.

This also shows that the {dialog.Object}.argumentValue(); works well. In M36_UX2_Called you can add a button with this code for the click event...

var tlArg = {dialog.Object}.argumentValue('TLArg');
alert(tlArg);

Then, run M36_Main... even in LivePreview. When rendered, click to open UX1_Caller... and from there click the Test Var Passing Button. This will open UX2_Called... where the TLArg lives.

Clicking your new button to run the code above will show that passed in argument value.

So... there are many ways to access arguments, values, controls... you name it... Alpha has provided it.

[frankbicknell]

Re: get an argument value from grand parent ux in grand child ux

Thanks for helping me sort this out.

It seems that this method

var myArgVariable = {dialog.Object}.argumentValue('myArgument'), myArgVariable = po.argumentValue('myArgument'), myArgVariable = gpo.argumentValue('myArgument'), etc

works perfectly for me.