...

...

...

...

...

...

...

...

...

1. 1. If a designer uploads a custom.js file to a project, it is only available for forms/flows workflows in that project. Refer to Method 1a below for the details.
   2. If a superuser/tenant admin uploads custom.js to the tenant, then the custom.js will be available to all forms/flows workflows in the tenant. Refer to Method 1b below for the details.

Method 2: Add a Message Control that contains your JavaScript. Refer to Method 2 below for the details.

...

Upload your custom JavaScript to  via the Scripts tab on the left menu inside your applicationproject.

Follow these steps:

1. Your custom JavaScript must contain the comment // frevvo custom JavaScript as the first line of the file or the upload will not be successful. Note the CustomEventHandlers JavaScript object. Application Project level custom js requires that you create a JavaScript object called CustomEventHandlers.

   Here is an example of code that will add dashes to a Social Security number control as the user is typing it in. See Custom JavaScript Examples for information on this sample code. Notice the JavaScript comment is the first line in the script file.
   
   
   
   

2. Login to  as a designer user. Click the name of the project (or select Edit from the Operations menuAction Menu) where you want to use the JavaScript. Click on the Script tab located on the left menu.

   

3. Browse your hard drive for your script file, Click Upload. Your file will be uploaded and it will display with the name Custom Script even though your script file may have another name.

   Warning
   Be Aware that existing JavaScript files will be overwritten. Download the existing custom.js file, append your new code to existing code then upload the combined file if you want to preserve the existing JavaScript.

   
   

4. If you need to modify the script, you must download it, make your modifications and then upload it again. When you download the script by selecting  Download from the operations menuAction Menu, it will be named custom.js.  
   

5. Once you have uploaded the JavaScript, it is available for all forms/flows workflows in the applicationproject. Remember to add the CSS class name to your form controls or your JavaScript may not work. Here is an image of an Employee Information form using uploaded JavaScript to enter dashes in the Social Security Number field while the user is entering the data.

   

...

1. Your custom JavaScript must contain the comment // frevvo custom JavaScript as the first line of the file or the upload will not be successful. Note the TenantEventHandlers JavaScript object. Tenant level custom js requires that you create a JavaScript object called TenantCustomEventHandlers.

   Here is an example of code that will add dashes to a Social Security number control as the user is typing it in. See Custom JavaScript Examples for information on this sample code. Notice the JavaScript comment is the first line in the script file.
   
   

2. Login to  as a superuser/tenant admin. Navigate to the Manage Tenant screen. Click the Manage Script link.
   
   
   
   

3. Browse your hard drive for your script file, then click Upload. Your file will be uploaded and it will display with the name Custom Script even though your script file may have another name.
   

   Warning
   Be Aware that existing JavaScript files will be overwritten. Download the existing custom.js file, append your new code to existing code then upload the combined file if you want to preserve the existing JavaScript.

   
   

4. If you need to modify the script you must download it, make your modifications and then upload it again. When you download the script by clicking on the  Download icon, it will be named tenantcustom.js.  

5. Once you have uploaded the JavaScript, it is available for all designers in your tenant to use in their forms/flowsworkflows. Remember to add the CSS class name to your form controls or your JavaScript may not work. Here is an image of an Employee Information form using uploaded JavaScript to enter dashes in the Social Security Number field while the user is entering the data.

   
   
   

What if I upload different custom JavaScripts to a project and the tenant?

If you upload custom JavaScript to the tenant and then upload a different custom.js file to a project, will load both files. The functionality of both scripts will be available to a designer creating forms/flows workflows in the project. For example, let's say you upload custom JavaScript to change the first letter of each word typed into a field to upper case. The class name is CorrectCase. You upload your custom JavaScript to the tenant.

...

You create another custom script to add the dashes to the Social Security Number as the user is typing. The class name is SSN1. You upload this custom script to an applicationproject.

// frevvo custom JavaScript
var CustomEventHandlers = {
    setup: function (el) {
        if (CustomView.hasClass(el, 'SSN1')) {
            FEvent.observe(el, 'keydown', this.formatSSN.bindAsObserver(this, el));
            FEvent.observe(el, 'keyup', this.formatSSN.bindAsObserver(this, el));
        }
    },
    formatSSN: function (event, element) {
        if (event.keyCode != 46 && event.keyCode != 8) {
            fldVal = element.value;
            var nom = fldVal.charAt(fldVal.length - 1);
            if (isNaN(nom) && nom != "-") {
                element.value = fldVal.substring(0, fldVal.length - 1);
            } else {
                if ((fldVal.length == 3) || (fldVal.length == 6)) {
                    element.value = fldVal + "-";
                }
                if (fldVal.length >= 12) {
                    element.value = fldVal.substring(0, fldVal.length - 1);
                }
            }
        }
    }
}

A designer creating forms/flows workflows in the application project will have access to both custom scripts. Both scripts will function properly.

...

Uploading custom.js files with the same class name on the application project and tenant levels is not recommended. This could result in unpredictable behavior. When two custom event handlers are bound to the same event (tenant level and project level), there is no guarantee which handler is called first. This is under the control of the JavaScript engine. Rewrite your JavaScript to avoid this situation.

...

 /*  
  * Custom Javascript here.  
  */   
   var CustomEventHandlers = {     
    setup: function (el) {       
        if (CustomView.hasClass(el, 's-submit'))       
        {  
            alert('setting up s-submit events');         
            FEvent.observe(el, 'click', this.submitClicked.bindAsObserver(this,el));         
            FEvent.observe(el, 'mouseover', this.submitMouseOver.bindAsObserver(this,el));         
            FEvent.observe(el, 'mouseout', this.submitMouseOut.bindAsObserver(this,el));       
        }     
    },     
    submitClicked: function (evt, el) {       
        alert ('Submit button was clicked');     
    },     
    submitMouseOver: function (event, element) {       
        alert ('Submit mouse over');     
    },     
    submitMouseOut: function (event, element) {       
        alert ('Submit mouse out');     
    } 
}

Extensions for

...

workflows

In addition to the above, flows workflows also support a few other methods.

...

1. onNextClicked() is called when the Continue button is clicked: this button might be labeled Continue or Finish or might have a custom label assigned by you. The parameters are the name and id of the current activity (step) in the flowworkflow.
2. onNavClicked() is called when the user clicks on a link in the Navigation toolbar if it is displayed. The parameters are the name and id of the activity (step) in the flow workflow that is clicked.
3. Finally, onSaveSuccess() and onSaveFailure() for flows workflows must be defined in the CustomFlowEventHandlers class.

...