Hi,
Thank you for your enquiry.
When a publication created in Opus Pro 04 or Opus Pro XE 04 launches, it checks to see if any parameters have been sent (passed) to it. If the publication finds parameters, it creates new COMMAND_PARAM variables that stores the parameter information. You can then use this information in conjunction with If statements to change the behaviour of your publication.
For example, if you launch an external publication using a Launch File action and the parameter field contains the following:
/Summary /On
the following variables will be populated in the new publication:
COMMAND_PARAM_1 will contain the value Summary
COMMAND_PARAM_2 will contain the value On
You can now add actions to the start of the publication (for example, actions assigned to a Pre Show trigger on the first page) to check the values of these variables and issue the required actions. Please note that you MUST create the new COMMAND_PARAM variables in the second publication as variables do not already exist and will not be available in the list of preset variables when setting up the If statement.
So, if you wanted the second publication to launch at the page indicated by the first parameter (in this case, Summary), you would need to add a Pre Show trigger to the first page of your publication which checks to see if COMMAND_PARAM_1 equals Summary. If so, a Go To Page <Summary> action can be triggered and the second page will be shown.
If you wanted to show or hide an object based on the value of the second parameter sent to the publication, you would use an If statement which checks to see if COMMAND_PARAM_2 equals On. If so, a Show action will display the object. If not, the object remains hidden.
More information about this functionality can be found in the help file (simply search for 'parameter' and view the 'How to use Parameters in the new publication' article).
Kind regards,
_________________ Robin Garrett
Digital Workshop Technical Support
|