Skip to main content

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

Modifying user permissions for Snowbound VirtualViewer annotations

Updated on February 26, 2019

To faciliate effective communication and collaboration over documents, define when users can view, add, and modify annotations to case and Pulse attachments and document case types. For example, you can define a when rule to specify that users can view or edit annotations only when the status of a case is Open.

By default, every user can view, add, and edit annotations.

Note: If a user cannot view annotations, the user cannot also add or modify annotations.
  1. In the header of Dev Studio, search for a when rule for the VirtualViewer component:
    • To define a when rule for viewing annotations, open the CanViewAnnotation rule.
    • To define a when rule for adding and editing annotations, open the CanSaveAnnotation rule.
  2. Copy the rule into your application ruleset.

    For more information, see Copying a rule or data instance.

  3. Modify the when condition:
    1. In the header of Dev Studio, search for the rule in your application ruleset, and then open the rule.
    2. Click the Conditions tab.
    3. Click Actions, and then enter the condition.

      For example:

      pyWorkPage.pyStatusWork != Open


  4. Test your changes:
    1. Open a case attachment by using the Snowbound VirtualViewer component.
    2. Add an annotation when the case status is new, and then click Save.
    3. Change the status of the case to Open.
    4. Open the case attachment. 

Result: Users cannot view or edit the annotations. 

For more information, see Snowbound VirtualViewer, Implementing Snowbound VirtualViewer on Pega Platform.

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