Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to identify an embedded page in a URL

Updated on May 3, 2020


The pyPrimaryPageName parameter passed in a URL can reference only a top-level clipboard page. Any sub-page reference is stripped off.

Why is this?



Suggested Approach

Clipboard pages are convenient to access, but present some risk and expense to the system - which must, among other precautions, make sure the page that you are referencing is present.  Sometimes the clipboard may not be in the condition that you expect or require. 

By restricting the pyPrimaryPageName parameter to top level pages by name, Process Commander can better manage the transaction and ensure the necessary page is available.  The further down into embedded pages it has to support such parameters, the harder it is to manage.  Thus, as you have seen, the server strips off embedded page references.

However, you can use this workaround:  

  1. Set a second parameter whose value is the path to the embedded page you wish to reference
  2. Pass both parameters to resolve to the fully-qualified page.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us