Manage External Links to Process Content
It is possible to directly link to process content from outside of Stages (“deep links”).
Simply copy the URL from the browser and put it in a document or web page.
If the user is not logged in when following the link, the login dialog will show up. After a successful login, the respective content will be displayed.
Links to the Valid Version
In most cases, links should always point to the Valid Version of the process, regardless of which specific version is valid at the time of access. Those links should be generated from the Valid Version.
Links to the Valid Version are most useful to put in static documents, templates, tool configurations, web pages, and other static content.
These links will contain
_vv within the URL:
Links that contain
_vv will always point to the valid version of the content.
The only case those links will break is when the linked content has been deleted in the valid version or when the element is being moved to a different workspace.
Links to the Working Version
Links to the Working Version will contain
_wv in the URL. They are best created from the Working Version of the content:
Links to the Working Version are most useful to be sent to other process modelers.
Please note: a special Process Version read permission is required to access the content. If the person using the link does not have the required permissions, Stages will direct the person to the Valid Version of the content instead.
Links to a Specific Version
If a link to a specific, non-valid version of the content is being created, the respective version identification will be part of the URL:
Similar to Working Version links, those links will only be accessible to persons with the respective access permissions.
Please note: those links will break, if the version that was used to create the link is being renamed or deleted or when the element is being moved to a different workspace.
Links that are published in static documents, templates, tool configurations, web pages, and other static content should not point to the modeling workspaces, because those are typically not accessible for normal end users.
The links should be taken from the standard process workspaces instead, that are typically accessible by the end users.