Browser Extension Conflict (Important!!)

When using the Online Form Designer, BP Logix STRONGLY recommends that you disable Grammarly, or any other broswer extension that works by rewriting the page HTML/Javascript. These rewrites occur in the browser after Process Director serves the page to you. So, the page you're looking at isn't the page that was delivered to you. Grammarly has rewritten it. If you then save the Form in the OFD, all of those re-writes get saved with the Form you're designing. Re-opening the Form in the OFD can cause parsing errors that result in section or other dontrols disappearing from the Design surface, HTML parsing errors, etc. Upgrading the product will not resolve these Form issues, because the browser extension has rewritten the Form's source code, and the rewritten code has been saved with the Form.

BP Logix does not have a reliable method to prevent these browser extensions from rewriting the Form's source code.

If this has happened to you already, the Engineering team recommends the following fix:

1. Open the form in source view.
2. Search for all <div> elements with the class bp-section-body.
3. Make sure each one is exactly: 
   <div class="bp-section-body"> 
   Remove any extra attributes (such as aria-label, spellcheck, etc.) that may have been added by browser extensions.
4. Save the form.

Returning the Form's Source to the expected elements should resolve the issue.