Advanced Customisation and Code Samples

21. Setting a Rich Text / Enhanced Rich Text Field

This rule allows you to populate a Rich Text or Enhanced Rich Text field dynamically. It’s useful for displaying formatted content such as line breaks, lists, or HTML elements directly in your form.

Why use it?
Automatically inserts formatted content without manual editing.

How to Add This

• In your form: Go to the Logic tab and click + Add a Rule.

• Set the Condition: Choose None (or any condition you want the content to appear under).

• Add the Step: In the Steps section, drag the step: Execute JS and paste in one of the code examples below:

Example 1 – Line Breaks:

setValue("MultipleLinesOfText", "Alice Johnson<br/>Brian Kelly<br/>Carla O'Neill");

Example 2 – Ordered List:

setValue("MultipleLinesOfText", "<ol><li>Alice Johnson</li><li>Brian Kelly</li><li>Carla O'Neill</li></ol>");

Now, when the rule runs, the MultipleLinesOfText field will display formatted content with line breaks or a numbered list.

22. Show a Toast Message (Small Temporary Notification)

This rule displays a toast message to the user. It’s useful for giving immediate feedback, warnings, or confirmations without changing the form layout.

Why use it?
Alerts users about missing or incorrect information. Provides a non-intrusive notification directly on the form.

How to Add This

• In your form: Go to the Logic tab and click + Add a Rule.

• Set the Condition: Choose the condition under which the message should appear (e.g., a required field is empty).

• Add the Step: In the Steps section, drag the step: Execute JS and paste in the code below:

  showMessage("One or more mandatory fields are missing data, please review the form", "error");

  Now, when the condition is met, a toast message will appear with your custom text and style (error, success, or info).

23. Duplicate a Form (Without a Linked List)

This approach allows users to duplicate an existing form’s data into a new form. It requires two rules: one to populate the fields and another to add a button for triggering the duplication.

Why use it?
Speeds up form creation by reusing existing data.
Ensures consistency and reduces manual entry errors.

Rule 1: Populate Form Fields from an Existing Form

Condition: Form is in Create Mode

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Form is in Create Mode.
• Add the Step: Execute JS and paste the code below:

const formID = queryParam("copyFrom"); if (formID) { getFilteredFirstListItem(formID, "Forms", "ID", [ "ID", "Requestor", "WWID", "JobTitle", "Department", "Area", "Shift", "Manager", "DepartmentManager", "Title", "AcademicInstituteChoice", "Qualification", "Level", "ECTSCredits", "ModeOfDelivery", "CourseLink", "FEStatus", "Currency", "SpringboardFunded", "Question1", "Question2", "Question2b" ]).then(data => { setValue('Requestor', data.Requestor); setValue('WWID', data.WWID); setValue('JobTitle', data.JobTitle); setValue('Department', data.Department); setValue('Area', data.Area); setValue('Shift', data.Shift); setValue('Manager', data.Manager); setValue('DepartmentManager', data.DepartmentManager); setValue('Title', data.Title); setValue('AcademicInstituteChoice', data.AcademicInstituteChoice); setValue('Qualification', data.Qualification); setValue('Level', data.Level); setValue('ECTSCredits', data.ECTSCredits); setValue('ModeOfDelivery', data.ModeOfDelivery); setValue('CourseLink', data.CourseLink); setValue('FEStatus', data.FEStatus); setValue('Currency', data.Currency); setValue('SpringboardFunded', data.SpringboardFunded); setValue('Question1', data.Question1); setValue('Question2', data.Question2); setValue('Question2b', data.Question2b); }); }

Now, when the form is in Create Mode with a copyFrom parameter in the URL, the fields are automatically populated with the existing form data.

Rule 2: Add a “Duplicate this Request” Button

Condition: Form is in View Mode or Edit Mode

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Form is in View Mode or Edit Mode.
• Add the Step: Execute JS and paste the code below:

  const formContext = getFormContext(); let url = formContext.formCreateUrl; url = url + "&form_copyFrom=" + getValue("ID"); addCustomButton("Duplicate this Request", "OpenInNewTab", url);

This adds a button that opens a new form pre-filled with the current form’s data.

24. Duplicate a Form (With a Linked List)

This approach allows users to duplicate a form including any linked sublist items. It uses multiple rules: one to initialise variables and copy data, another to add a button, and optionally a third to copy the user’s previous form.

Why use it?

Reuses both the main form fields and any linked sublist items. Reduces repetitive data entry for recurring forms like purchase orders.

Rule 1: Initialise Variables and Copy Form Data

Run Once

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Run Once.
• Add the Step: Execute JS and paste the code below:

  // Initialize global variables window.supplier = null; window.supplierItems = []; // Function to copy main form and linked sublist items window.copyFormValues = function (formId) { // Copy main form fields getFilteredFirstListItem(formId, "Purchase Orders", "ID", ["ID", "Supplier", "OrderFor", "Note", "DateReceived"]).then(data => { setValue('Supplier', data.Supplier); setValue('OrderFor', data.OrderFor); setValue('Note', data.Note); setValue('DateReceived', data.DateReceived); }); // Copy linked sublist items getFilteredListItems(formId, "Sublist_purchaseOrderItems", "PurchaseOrderId", ["LineItem", "Description", "Title", "Quantity", "UnitPrice", "VAT", "Supplier"]).then(data => { // Clear existing items setValue("Sublist_purchaseOrderItems", []); // Insert copied items insertSublistItems("Sublist_purchaseOrderItems", data); }); } // Auto-copy if "copyFrom" parameter exists in URL var existingCopyFromId = queryParam('copyFrom') || 0; if (existingCopyFromId > 0) { window.copyFormValues(existingCopyFromId); }

Rule 2: Add a “Duplicate this PO” Button

Condition: Form is in View Mode or Edit Mode

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Form is in View Mode or Edit Mode.
• Add the Step: Execute JS and paste the code below:

  const formContext = getFormContext(); let url = formContext.formCreateUrl; url = url + "&form_copyFrom=" + getValue("ID"); addCustomButton("Duplicate this PO", "OpenInNewTab", url);

Optional Rule 3: Copy User’s Previous Form

Condition: Form is in Create Mode

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Form is in Create Mode.
• Add the Step: Execute JS and paste the code below:

  addCustomButton("Copy my previous order", "Copy", copyUserPreviousForm); function copyUserPreviousForm() { var submitter = getCurrentUser(); getFilteredListItems(submitter.displayName, "Purchase Orders", "Author", ["ID", "Supplier", "OrderFor", "Note", "DateReceived"]).then(data => { var last = _.first(_.orderBy(data, ["ID"], ["desc"])); if (last) { window.copyFormValues(last.ID); showMessage('Last values copied.', 'info'); } else { showMessage("No previous entries found.", "warning"); } }); }

   

This setup ensures that both the main form fields and any linked sublist items are copied automatically or via a button, making duplication seamless.

25. Query User Values in a List and Write Them into User Fields

This setup allows you to automatically populate user fields in a form based on a selection in another field (in this case, QualitySystem). It requires two rules: one to define the JavaScript function and one to call it whenever the form changes.

Why use it?
Automatically retrieves the relevant agents and process owner from a lookup list and populates the corresponding user fields, reducing manual entry and errors.

Rule 1: Initialise JS Function

Run Once: True
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: None (Run Once).
• Add the Step: Execute Custom JS and paste the code below:

  var customLogic = function() { var self = this; self.getAgentsAndProcessOwner = function () { let searchedValue = getValue('QualitySystem'); if (searchedValue && self.resolvedId != searchedValue) { let targetListInternalName = "LookupQualitySystem"; let targetListFieldInternalName = 'ID'; getFilteredFirstListItem(searchedValue.id, targetListInternalName, targetListFieldInternalName, ["Agents", "ProcessOwner"]).then(data => { setValue('QualitySystemAgents', data.Agents); setValue('QualityProcessOwner', data.ProcessOwner); self.resolvedId = searchedValue; }); } }; }; window.SFCustomLogic = new customLogic();

Rule 2: Set Agents and Process Owner Based on Selected Quality System

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: None.
• Add the Step: Execute Custom JS and paste the code below:

  window.SFCustomLogic.getAgentsAndProcessOwner();

How it works:

• Rule 1 defines a function to fetch the agents and process owner from the LookupQualitySystem list.

• Rule 2 executes the function whenever the form changes or the QualitySystem field is updated.

• The results automatically populate the QualitySystemAgents and QualityProcessOwner fields, keeping your form up-to-date with the correct user assignments.

26. Read Values in a Linked List and Write Them into a Multiline Text Field

This setup allows you to automatically populate Multiline Text (MLT) fields in the main form based on items from a linked list. It requires two rules: one to define the JavaScript functions and one to call them whenever the form changes.

Why use it?
Reduces manual data entry by combining values from a linked list into single MLT fields, making it easier to review or export aggregated information.

Rule 1: Initialize JS Functions

Run Once: True
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Run Once.
• Add the Step: Execute Custom JS and paste the code below:

  // Function to combine TrainingItem values into one MLT field window.getDocumentnumbers = function () { const items = getValue("3f391f85-2d2b-43b9-bafa-b26f8ea8c1ce") || []; const codesText = items.map(item => `${item.TrainingItem}`).join("\n"); setValue("DocNoCombined", codesText); }; // Function to combine Title values into one MLT field window.getDocumenttitles = function () { const items = getValue("3f391f85-2d2b-43b9-bafa-b26f8ea8c1ce") || []; const codesText = items.map(item => `${item.Title}`).join("\n"); setValue("DocTitleCombined", codesText); };

Rule 2: Set Fields Based on Related List

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: None.
• Add the Step: Execute Custom JS and paste the code below:

  window.getDocumentnumbers(); window.getDocumenttitles();

How it works:

• Rule 1 defines two functions: one to aggregate TrainingItem values and another for Title values from the linked list.

• Rule 2 executes these functions whenever the linked list updates or the form changes.

• The aggregated values are written into the DocNoCombined and DocTitleCombined MLT fields for easy reference.

27. Validate Dates in a Form

This setup ensures that date fields maintain a logical order, preventing users from selecting a “desired” or second date that occurs before an “available” or first date.

Why use it?
Prevents data entry errors by validating the relationship between two date fields, ensuring consistency in scheduling or delivery data.

Rule 1: Validate Earliest Available vs Desired Date

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: None.
• Add the Step: Execute Custom JS and paste the code below:

  const dateAvailable = getValue("DateAvailable"); const dateDesired = getValue("DateDesired"); if (dateAvailable && dateDesired) { const isAvailableSmallerThanDesired = moment(dateAvailable) < moment(dateDesired); if (!isAvailableSmallerThanDesired) { setErrorMessage("DateDesired", "You can only choose a desired date after the Earliest Available Delivery Date"); } }

Rule 2: Validate Two Simple Date Fields (No Time)

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: None.
• Add the Step: Execute Custom JS and paste the code below:

  const date1 = getValue("Date1"); const date2 = getValue("Date2"); if (date1 && date2) { if (date2 > date1) { setErrorMessage("Date2", "You can't choose a date after Date 1"); } }

How it works:

• Rule 1 uses the moment library to compare the “Earliest Available Delivery Date” against the “Desired Date” and displays an error if the logic is violated.

• Rule 2 performs a simpler comparison for two date-only fields and prevents selecting an invalid sequence.

• Both rules trigger whenever the relevant date fields are updated.

28. Add an “Assign to Me” Link to a User Field

This feature lets users quickly assign a task, record, or request to themselves by clicking a simple “Assign to me” link next to a user field. It uses one rule to initialise the function and another to display the clickable link.

Why use it?
Streamlines assigning ownership without needing to manually search for and select your own name in a user field.

Rule 1: Initialise Variables and Create the Assign Function

Run Once: True
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Run Once.
• Add the Step: Execute Custom JS and paste the code below:

  SPApi.ensureInitialized(); var ctx = SPApi.context; var web = SPApi.hostWeb; var customLogic = function() { var self = this; self.assignToMe = function () { setCurrentUser("Person"); showMessage("You have been assigned, don't forget to save the form!", "success"); // saveForm(); // Optional: uncomment to auto-save after assigning }; self.initVariables(); }; window.SFCustomLogic = new customLogic();

Rule 2: Add the “Assign to Me” Link in the Field Label

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: None.
• Add the Step: Execute Custom JS and paste the code below:

  setLabel("Person", 'Person (<a href="javascript:window.SFCustomLogic.assignToMe()">assign to me</a>)');

How it works:

• Rule 1 initialises SharePoint API context and defines the assignToMe function that sets the “Person” field to the current logged-in user and displays a success message.

• Rule 2 dynamically updates the field label to include a clickable assign to me link.

• Clicking the link runs the function from Rule 1, instantly assigning the current user.

29. Count the Number of Linked Items and Completed Items

This setup allows you to automatically count all items in a linked list and the number of completed items, displaying the results in read-only numeric fields on the main form.

Why use it?
Provides a quick overview of progress or status by showing both the total number of linked items and how many have been completed, without manual counting.

Rule 1: Initialise Counting Functions

Run Once: True
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Run Once.
• Add the Step: Execute Custom JS and paste the code below:

  window.countAllLinkedItems = function () { let allItems = _.filter(getValue("8e4d48e5-4e4e-4903-8273-848f52df65b3") || [], function (o) { return !o.sintelForms_isDeleted; }) || []; return allItems.length; } window.countCompletedLinkedItems = function () { let allItems = _.filter(getValue("8e4d48e5-4e4e-4903-8273-848f52df65b3") || [], function (o) { return !o.sintelForms_isDeleted && o.Complete; }) || []; return allItems.length; }
• Step 2: Create Calculated Read-Only Numeric Fields
• Fields:
  Total Items: Set formula to: window.countAllLinkedItems()
  Completed Items: Set formula to: window.countCompletedLinkedItems()

• How it works:
• countAllLinkedItems filters the linked list to exclude deleted items and returns the total count.
• countCompletedLinkedItems filters the linked list to exclude deleted items and only include those marked as complete.

• Both formulas are placed in read-only numeric fields to display the counts dynamically on the main form.

30. Get UserProfile Properties and Populate Fields on the Form

This setup automatically retrieves the selected user’s profile information and populates multiple fields on the form, including name, contact details, department, manager, and profile picture.

Why use it? Reduces manual data entry by automatically filling in all relevant user information when a person is selected in a form field.

Rule 1: Fetch UserProfile Properties

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Check field value for ‘Person’ is ” ” which means empty. 
• Add the Step: Execute Custom JS and paste the code below:

  let user = getValue('Person')[0]; let properties = []; getUserProfile(user, properties).then(data => { setValue('AccountName', data.AccountName); setValue('FirstName', data.FirstName); setValue('LastName', data.LastName); setValue('FullName', data.PreferredName); setValue('WorkPhone', data.WorkPhone); setValue('Department', data.Department); setValue('PersonTitle', data.Title); setValue('SPS-JobTitle', data["SPS-JobTitle"]); setValue('Manager', data.Manager); setValue('PictureURL', data.PictureURL); setValue('UserName', data.UserName); setValue('CellPhone', data.CellPhone); setValue('WorkEmail', data.WorkEmail); setValue('HomePhone', data.HomePhone); setValue('Office', data.Office); setValue('SPS-Location', data["SPS-Location"]); setValue("UserProfileData", JSON.stringify(data)); setValue("PersonFieldData", JSON.stringify(user)); });

How it works:

• getUserProfile fetches all the user’s profile properties from the system.

• Each relevant field is automatically updated on the form using setValue.

• Two hidden fields (UserProfileData and PersonFieldData) store the raw JSON for reference or further automation.

31. Output All UserProfile Data to a Multi-Line Text Field

This setup allows you to store the full user profile JSON in a multi-line text field on the form for debugging, reporting, or further automation.

Why use it?
Captures all available user profile properties in a single field, making it easy to reference or export later.

Rule: Store Full UserProfile JSON

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: none (runs whenever the form loads or the user field changes).
• Add the Step: Execute Custom JS and paste the code below:

  // Assume `data` is the user profile object retrieved from getUserProfile setValue("SomeTextField", JSON.stringify(data));

How it works:

• data is the JSON object returned from getUserProfile.
• JSON.stringify(data) converts the object into a string.
• setValue writes this string into a multi-line text field (SomeTextField).
• This is useful when you want a full dump of user profile information on the form for reference, logging, or advanced logic.

32. Disable Adding New Comments When Form Status is Completed

This setup prevents users from adding new comments once a form’s status is marked as “Completed.”

Why use it? Ensures that completed forms cannot receive further comments, keeping the record clean and preventing accidental updates.

Rule: Disable Comments on Completed Forms

Run Once: False
Conditions: Form status equals “Completed” (only applies when this condition is met)

Steps:

• In the Logic tab, click + Add a Rule.
• Set the Condition: Form status equals “Completed”
• Add the Step: Execute Custom JS and paste the code below:

  document.body.className += ' StatusCompleted';

   

33. Set Relevant Dates Based on Workflow Status

This setup automatically populates date fields when the form status changes, tracking the workflow progress.

Why use it?
Keeps a timestamp for each workflow stage, ensuring you know when each step occurred without manual input.

Rule: Update Dates When Status Changes

Run Once: False
Conditions: None

Steps:

• In the Logic tab, click + Add a Rule.
• Add the Step: Execute Custom JS and paste the code below:

let workflowStatus = getValue("SintelFormsStatus"); let dateDraft = getValue("DateDraft"); let dateES = getValue("DateES"); let dateOPS = getValue("DateOPS"); let dateEHS = getValue("DateEHS"); let dateQA = getValue("DateQA"); let dateComplete = getValue("DateComplete"); // When Draft if (workflowStatus == "Draft" && !dateDraft) { setValue("DateDraft", new Date().toISOString()); } // When With Execution Systems else if (workflowStatus == "With Execution Systems" && !dateES) { setValue("DateES", new Date().toISOString()); } // When With OPS else if (workflowStatus == "With OPS" && !dateOPS) { setValue("DateOPS", new Date().toISOString()); } // When With EHS else if (workflowStatus == "With EHS" && !dateEHS) { setValue("DateEHS", new Date().toISOString()); } // When With QA else if (workflowStatus == "With QA" && !dateQA) { setValue("DateQA", new Date().toISOString()); } // When Completed else if (workflowStatus == "Completed" && !dateComplete) { setValue("DateComplete", new Date().toISOString()); }

 

How it works:

• Checks the current workflow status of the form.
• If the corresponding date field is empty, it sets it to the current date and time using toISOString().
• Ensures each workflow stage is timestamped automatically.