09-19-2023 09:30 PM
Hello all,
I would like to access callee sequence local variables from calling sequence without using any parameters passing method.
Could anyone please advise on this?
Best regards,
Thank you.
09-20-2023 06:32 AM
Why trying to bypass proven methods?
You will create tight coupling which is bad programming practice after all
09-22-2023 10:21 AM
There are other fundamental issues with what you are asking than what Oli pointed out. Unless you call it asynchronously you cannot do it. This is because the context only lasts for the life of the call. There's nowhere in the Caller that you can access the context, unless like i said, it is in parallel. So basically from the Caller's perspective the life of the Callee is literally the Module call of the sequence call step in which it resides.
Maybe you can help us understand why this is a requirement and we can help you arrive at a solution that works?
09-23-2023 12:56 PM
Hi ,
Please try this in the called sequence :
RunState.Caller.Locals.variablename
Ravi
09-25-2023 05:10 PM
@RaviShrigiri wrote:
Hi ,
Please try this in the called sequence :
RunState.Caller.Locals.variablename
Ravi
I understood it the opposite direction as you have here.
09-25-2023 09:54 PM
Hi Jiggawax,
I have many times read your suggestions/solutions and its very helpful. Thanks for all your support.
For this case do you mean to say that the user wants to access variables of a called sub sequence from a main sequence.
Ravi
09-26-2023 04:43 AM
Still... there is no description of the actual use case and why this tight coupling is neccessary.
01-18-2024 03:34 AM
@~jiggawax~ wrote:
There are other fundamental issues with what you are asking than what Oli pointed out. Unless you call it asynchronously you cannot do it. This is because the context only lasts for the life of the call. There's nowhere in the Caller that you can access the context, unless like i said, it is in parallel. So basically from the Caller's perspective the life of the Callee is literally the Module call of the sequence call step in which it resides.
Maybe you can help us understand why this is a requirement and we can help you arrive at a solution that works?
Hi jigg,
The reason i wanted to do so is because i cannot afford to add new parameters to my existing sequence architecture. I am not allowed to do so as i am not the only one who use the sequence.
Best regards,
01-18-2024 03:35 AM
@RaviShrigiri wrote:
Hi ,
Please try this in the called sequence :
RunState.Caller.Locals.variablename
Ravi
I believe i tried this method before but somehow it doesn't work for my case.