Reusable packages
We are using a lot of web-based applications throughout the company. I'd prefer to not to have to "re-sequence" shortcuts every time a new site is added to the list. I'd rather copy and modify an existing OSD file and just add it to the softgrid applications...
However, I ran into this issue: an existing OSD file, when copied, re-touched, and added to the softgrid applications, takes out the original application shortcut, no matter where it was located... What, in addition to the application parameters and shortcut names, needs to be modified inside of the OSD file to prevent it from removing the original shortcut? (like SOFTPKG/ CODEBASE GUIDs, may be?)
For example, in the original OSD, I specify URL parmeter http://site1.com for iexplore.exe to start with. Additional shortcuts down the road are added by:
copying original OSD file + editting parameter to have http://site2.com and a different shortcut name
As soon as the new OSD is added through console, the shortcut for site1.com is getting removed for the user.
However, I ran into this issue: an existing OSD file, when copied, re-touched, and added to the softgrid applications, takes out the original application shortcut, no matter where it was located... What, in addition to the application parameters and shortcut names, needs to be modified inside of the OSD file to prevent it from removing the original shortcut? (like SOFTPKG/ CODEBASE GUIDs, may be?)
For example, in the original OSD, I specify URL parmeter http://site1.com for iexplore.exe to start with. Additional shortcuts down the road are added by:
copying original OSD file + editting parameter to have http://site2.com and a different shortcut name
As soon as the new OSD is added through console, the shortcut for site1.com is getting removed for the user.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
kkaminsk
17 years ago
Hmm sounds like you probably are not doing something right such as editing the DISPLAY attribute. To add an OSD to the sequence WITHOUT using the sequencer you should do the following.
1> Copy the OSD file.
2> Rename the OSD file to suit your standards.
3> Change the NAME and DISPLAY attributes of the OSD as a bare minumum or you will cause issues.
4> Make any other changes you see fit to the OSD and save it.
5> Edit the SPRJ file for the sequence in notepad and add the new OSD file to the shortcuts node so that if the SPRJ is imported or the sequencer opens the sequence all shortcuts are noted to the application.
I.E. <SHORTCUT Path="NewApp-V1.0.osd"/>
1> Copy the OSD file.
2> Rename the OSD file to suit your standards.
3> Change the NAME and DISPLAY attributes of the OSD as a bare minumum or you will cause issues.
4> Make any other changes you see fit to the OSD and save it.
5> Edit the SPRJ file for the sequence in notepad and add the new OSD file to the shortcuts node so that if the SPRJ is imported or the sequencer opens the sequence all shortcuts are noted to the application.
I.E. <SHORTCUT Path="NewApp-V1.0.osd"/>
Posted by:
revizor
17 years ago
That's what it was... I never looked into changing NAME property (left it the way it was captured from the MSI source). Editting SOFTPKG GUIDs seem to be unnecessary...
Posted by:
ksaunam
17 years ago
SOFTPKG GUID servers no purpose so it has no effect on anything, present or not present. CODEBASE GUID is the package-identifying GUID.
Posted by:
revizor
17 years ago
I realize that, but my guts are telling me to keep SOGPKG GUIDs unique - who knows, may be those will give us more granular software metering or... not?[8|]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.