To ensure that the advisor and the student can simultaneously edit the draft proposal, configure the locking on the case type to allow multiple users (B). This setting enables a shared access model, where multiple users can work on the case at the same time. Additionally, Pega's conflict resolution mechanisms can be utilized to check for changes before committing them to the database, ensuring that any concurrent edits are properly managed and the integrity of the proposal is maintained.Reference: Pega Community documentation on case locking and concurrent editing.

Managing encrypted data in Pega Platform comes with certain limitations, one of which is that encrypted properties cannot be referenced using filter conditions in reports (A). This is because the encryption obscures the actual value of the property, making it impossible for the reporting engine to perform comparisons or filtering based on the encrypted data. This limitation is essential for maintaining data security, as it prevents unauthorized access to sensitive information through report queries.Reference: Pega Community documentation on encryption and reporting.

B: Mashup requests are checked for the corresponding mashup channel ID parameter to ensure that the request is coming from a trusted source and is intended for the Pega application.
D: A user can view their worklist in an external portal and select items on which to take action, which is one of the key features of the Pega Web Mashup as it extends Pega's capabilities to external web pages. Reference: Pega official documentation on Pega Web Mashup capabilities.

To implement the requirement of associating users in different units to the same work queue, you associate the users to a common work group and then associate a work queue to that work group. This allows users from different units, who are part of the same work group, to access the same work queue. Reference: Pega official documentation on work groups and work queues.