preethi
18th August 2010, 11:04
Hi all,
i have gone through the posts containing how to add a session through the 'special' option. I am facing some problem pertaining to the same issue.
i want to add a session to a standard session for which we don't have the source code. This standard session is already having a session added in its 'special'. I tried creating a menu and adding the existing session and my customized session into it. this menu i added in the 'special'.
When i am running the standard session i couls see both the sessions(existing & customized) in the special option. But what ever i select only the old session which already existed is opening. I think that has been hard coded in the script.
in this case is there any option where i can activate my customize session through the standard session.
Any ideas are welcome.
Thanking you in Advance.
mark_h
18th August 2010, 16:48
I doubt it is hard coded. I recommend creating and convert RDD on the session and forms and menus. Log out and back in - try again. Also if you provided the session and sub-session name maybe someone could look and confirm if it is hardcoded somewhere..
sameer.don
19th August 2010, 14:42
Preethi,
This may not be hard coded always.
In some case zoom sessions could depend upon parameter settings
or It could be maintained in master data, like for Maintain transaction sessions, which are specified in master data "Maintain Transaction Type"
If you can post the session names, it will be helpful in analyzing you problem.
However, in case it was hard coded in program script, there is another way, a bit complex and unorthodox method, to change the zoom session without making changes in standard script.
(I have tried this solution once when we faced a similar problem. We did not have program script of main session and wanted to control the zoom session which opened on Continue button.)
What you can do is:
(Assuming old session which opened on zoom:tfacp1120s000)
1. Copy the old he session to you development VRC with different name.
for eg, old session was tfacp1120s000, copy it to tfacp1210stmp.
Make sure that it still has links to original forms/script/reports, so that if works exactly same as original one.
2. Create a new program script in your development VRC. Lets name it as zzabc0000
In section before.program, write following code:
|* Start of code
before.program:
if <condition> then
zoom.to$("tfacp1120stmp",Z.SESSION,"","",0)
else
zoom.to$("xxabc9999s000",Z.SESSION,"","",0)
||* Assuming xxabc9999s000 is your customized session
endif
end()
|* End of code
Also define all form fields in declaration section of the script
3. Copy old session to development VRC with same name. But do not copy any other object linked to the session. In development VRC, link program script zzabc0000, which was created in step 2, to the session tfacp1120s000
How this works:
When session tfacp1120s000 opens after zoom, it works with the program script zzabc000. In before.program, as we put the logic of selecting zoom session, depending upon the condition it will open either old or new customized session. Note that, as we have written code in before.program, tfacp1120s000 will not be visible, instated only tfacp1120stmp or xxabc9999s000 will appear for user.
But, this method looks too complex. So, use this if it is very much required to have customized session, and you really don't have any other option.
preethi
20th August 2010, 12:21
the main standard session is tdpur4121m000. The customized session is of different package & different module when compared to standard session.