Oh I am on 10.3.1 in this environment, thought it was 10.4.1. I will schedule another upgrade for this weekend. It certainly does not work here though. I can verify that I am doing it right by using the forms history (read-only view) which DOES abide by the clause.

$(document).ready(function() {    
if ($('[name=IsLocked]').val() == 'True'){
            $('.preEventTotals').removeClass('preEventTotals');
	}

I have this in my document ready function, which removes the class from the section.

The section is moved off the form and set static while the user is filling it out so that it is always on screen.

I can verify that the class is removed correctly using the IsLocked clause by looking at the submissions in the forms history where I see the section is back on the form, due to my code above

But the archive image in the repository and any PDFs sent in emails do not abide by it, they leave the class there and push the data off the screen.

I have also tried if(!document.title) or if(document.title == '') which I am surprised does not work, since I know the title is blank during creation of the final archive.

I tried your custom js with the following css:

.preEventTotals { color: red; }

And it worked on form submission/file saved to repostiory.

So I guess the issue might be related with the css content, can you

• Give me your css for preEventTotals, and
• Try if custom js works using my css above?

Thanks for testing! I did try your CSS instead and experienced the same thing. I put an HTML element in the section so that I could see the text change color to red.

When viewing in the forms history, I could see that the text changed back to black, again indicating that this method is triggered when images are being created by Forms.

But the resulting archive TIFF and PDF contain red text still.

This was all on 10.4.1 when I tested today. I can give you my CSS but since we are simply removing the class, I don't think the actual CSS matters.

I am going to try jumping on a VAR webinar.

.preEventTotals {
  position: fixed;
  width: 300px;
  height: 100%;
  top: 21px;
  left: 1000px;
  background-color: rgba(255, 255, 255, .5) !important;
  overflow: auto;
}

Jumped on the VAR webinar and Karina gave me another idea that is working really well.

        if (window.location.href.includes('Forms')){
		//Form is actively in use
	}

        if (window.location.href.includes('Forms') == false){
		//Form is being saved to repository
	}

Yeah I was not able to reproduce with your CSS.

Glad to see it resolved.

I could use a Javascript example of how to set a class specifically during the "Save to Repository".

The above worked really well for me. However if your using 10.4.3+ they have switched to a new save to repository module. Not sure if this has changed anything, might just give it a try.

Our Forms is 10.4.0.  I've been going in circles trying to get styles set via Javascript to be included in forms saved to the repository.

I went down that crazy road once too. Always keep in mind that field values are not accessible in the save to repository image. So if you are including any conditionals which include any variables set by the value of a field on the form IE:

IF($('.myField input').val() == "hello world")
$('.myField').addClass('something')

This will not work because the field values are not accessible.

Yeah, my code isolates the divs that correspond to where the fields were in the form like this

    $( "div" ).each(function( i ) 
    {
      if(this.id.includes("Field117("))
      {
        var currRow = GetIndexFromElementID(this.id); 

        // Field119 is simply a single line (in a collection) that I save the class name to at runtime.
        this.className = this.className + " " + $('#Field119\\('+ currRow +'\\)').text();
      }
    });  
 

This works on the readOnly form display that happens when the form is first submitted, but does not for the actual SaveToResository.  I've tried your example of checking for the absence of "Forms" in the href on document.Ready, but it's still not working.  What am I doing wrong?

This is the roadblock I ran into on every other post I made on the subject.

Without access to the DOM layer, how can you troubleshoot?

I went as far as creating a custom console by creating a div on the form and printing out to that, however I still needed to look at the DOM layer to see why the DIV I was looking for was not there or did not have the child object I was expecting.

True, all of the PDF generation is done server side, no way to hook into it.  

The new module is supposed to grab a screen image of the current state of the form on submission, so anything you build now might be wiped anyways.

I wonder how this new module works when you save a different form, one that the user did not see, and has different javascript, but contains shared fields.