Notifications can contain URL links that directly open objects using the ObjectPop functionality. Links can be static or dynamically generated based on the object from which the notification is generated.
To provide a static link to a specific object, the following format should be followed: http://<myServer>/<myVirtualdirectory>/workview/objectPop.aspx?objectid=<insert the object's ID # here>&classid=<insert the class's ID number here>
To provide a dynamic link to the object from which the notification is generated, the following format should be followed: http://<myServer>/<myVirtualdirectory>/workview/objectPop.aspx?objectid=<<objectID>>&classid=<<classID>>
The <<objectID>> attribute forces WorkView to grab the objectID of the current object being created, modified, or deleted. It then attaches this value in the URL.
In addition, you can specify a specific screen to use to display objects using ObjectPop. This is accomplished by providing the screen id in the URL. The following is an example: http://<myServer>/<myVirtualdirectory>/workview/objectPop.aspx?objectid=<<objectID>>&classid=<<classID>>&screenId=<<screenID>>
In addition, macros can be used to generate ObjectPop links in notifications, see Data Value Insertion Tags for more information.
You can also embed ObjectPop links in iFrames. In order to do this, you must include embed=true in the link. Here is an example: http://<myServer>/<myVirtualdirectory>/workview/objectPop.aspx?objectid=<<objectID>>&classid=<<classID>>&embed=true
By default, if you are embedding content from the OnBase Web Server into a web page, the page and the embedded content must be on the same domain. If your solution requires embedding Web Server content into a different domain, you can configure the Web Server to allow this. For more information, see the section on X-Frame-Options in the Web Server module reference guide.