Brava Viewer with Salesforce (Extended ECM).

mbarben

Hi There,

I am working on a Salesforce xECM project using Brava Viewer and I have some questions/comments:

• Is there a URL that can be used to force the Smart UI-based Brava Viewer? Right now the ?func=brava.bravaviewer&nodeid={nodeid} format only renders in the class Desktop ui-variant instead of the DesktopUX2 ui-variant used by Smart UI.
• Is there a way to create an audit event for Publish events? - The Smart UI ui-variant will force users to create a markup before publishing the markup. This creates an audit event for the markup - but there is no audit even for publish (which means that if you publish to a new document there is no document referencing - which smells like a compliance gap).
• Is there a way to configure the Brava Viewer to create an elegant fallback if the Mimetype is not supported? The suggested configuration option is ?func=brava.bravaviewer&nodeid={nodeid}. For now, I have created a WebReport link instead that will read the mime type from the document and either direct a user to the property screen or the Brava Viewer - but again it seems like a gap in the product. 
• Provide the user with some feedback when publishing a document. When you publish a document using the Brava Viewer and you have the option to save - the button doesn't disable when clicked giving the user no feedback as to when the create document or version add event has been completed.

It also opens up a new game of spamming the button and adding multiple versions (my record is 83 versions)

Thanks again

Matthew Barben

bartemsa

URL for Smart UI-based Brava Viewer: It appears that you are looking for a way to force the Brava Viewer to use the Smart UI variant instead of the Desktop variant. This might require specific configurations or settings within the Brava Viewer or Salesforce xECM integration. Without the latest information, I can't provide a precise answer. You may want to refer to the Brava Viewer documentation or reach out to their support team for assistance on this matter.

Creating audit events for Publish events: It's important for compliance purposes to have an audit trail for important actions like publishing documents. If there is no audit event being generated for the publish action, this could be considered a gap in the product's capabilities. You may want to check the Brava Viewer and Salesforce xECM documentation for any specific settings or configurations related to audit events. If none are available, consider reaching out to their support or development teams to discuss this requirement further.

Configuring fallback for unsupported MimeTypes: If the Brava Viewer doesn't support certain MimeTypes, it's a good idea to have a graceful fallback mechanism to handle those scenarios. Your approach of creating a WebReport link and directing users to the property screen or Brava Viewer based on the document's Mime type is a sensible workaround. Again, this may not be a built-in feature, so consider submitting this as feedback to the product team or support channels.

Providing user feedback when publishing documents: User feedback is crucial for a smooth user experience. If the publish button doesn't disable or provide any feedback after being clicked, users may not be aware of the status of their action. This could be another usability issue to address or provide feedback to the Brava Viewer development team.