Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding JavaScript code to Pega Platform applications when sourcing large data pages from a connector, activity, or data transform

Updated on March 3, 2022

To source large data pages from a connector, activity, or data transform, add the text file that contains the JavaScript populator function to your application.

Before you begin: Define the JavaScript populator function in a Pega Platform text file. For more information, see Defining a JavaScript function when sourcing large data pages from a connector, activity, or data transform.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Technical category, and then click Static Content Bundle.
  3. In the Bundle Name column, open the configuration tab for the rule by clicking pypega_ui_userscripts_offline.
  4. On the Definition tab, click the Add item icon.
  5. In the added row, add the JavaScript code to the UI rule:
    1. In the App name field, enter webwb.
    2. In the File extension field, enter js.
    3. In the File name field, enter the name of the text file that contains the JavaScript function, for example, expenses_datapage_api.
  6. Check out the pypega_ui_userscripts_offline rule to your development branch:
    1. Click the arrow next to the Private edit button, and then select Check out to branch.
    2. In the Check Out to Branch dialog box, in the Branch menu, select the branch that you created.
    3. Click Check out to branch.
  7. Click Save.
What to do next:
  • Previous topic Data population for large data pages in offline-enabled mobile apps
  • Next topic Declaring a data page as large

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us