Pergapedia / SSP7
SMTX SupportSMTX Wiki
  • Introduction
  • Pergapedia / SSP7 Admin guide
  • Catalog
    • Typical use cases
      • Usage as Knowledge Catalog
      • Usage as Data Catalog
      • Usage as Service Catalog
    • Catalog Maintenance
      • Templates
        • Create a new template
        • Version management of templates
        • ACL (Access Control Lists)
          • Scopes
          • Add default ACLs
          • Remove All ACLS
          • ACL condition script examples
        • Set translation label for Publication request button
      • Parts (Fields)
        • Field types
        • Calculations
        • Field Validation examples
        • Field Visibility Examples
        • Field Filtering
        • Default value
      • Actors
      • Reusable content
      • Settings
      • General Settings
      • Roles
      • Javascript for Variables in processes
      • Action Forms
        • Add log entries for Action Forms
    • Service Maintenance
      • Services
        • Filter list of services
        • Duplicating services
        • Adding a new service
        • Service Details
          • General settings
          • Service Data
          • Contracts
          • Actors
          • Receivers
          • Targets
          • Support Groups
          • Relations
          • Requests
          • Quality Notes
          • Publication History
          • Documents
          • Log
          • Service Actions
        • Compare versions
        • Quality Notes
        • Service Changed flag
      • Approvals
      • Relations
        • Start service from service
      • Subscriptions
      • Outages
    • Public
    • Service Catalog API
      • Outbound REST API
        • Get Services
        • Get Service Details
      • Inbound SOAP calls
        • Create custom approval
        • Add log to service publish request
        • Add person to service person list
        • Add persongroup to service persongroup list
        • Delete service
        • Mark service publish request as in approval state
        • Process service publish request
        • Publish request set can be cancelled
        • Publish request set show in public
        • Remove person from service person list
        • Remove persongroup from service persongroup list
        • Remove support group from service
        • Update service field
        • Update service language field
        • Update template part datetime value
        • Update template part numeric value
        • Update template part text value
  • Fulfillment Platform
    • Admin Panel
    • General Settings
      • General
      • My Profile
      • Mail Settings
      • Login
      • Forms Setting
      • Workflow
      • Archive
      • Calendar Overview
      • Dashboard
      • Mobile Component
      • Ticketing
      • Webhooks
      • Goto
      • Search options
      • Application URL Settings
      • Address Book Settings
    • Dashboard
    • Categories
    • Topics
    • Forms
      • Fields-tab
      • Field: General Settings
      • Dynamic Value
      • Text (Area) Field
      • Yes : No Field
      • Upload file(s)
      • Date (Time) Field
      • Password Field
      • Read Only Display Field
      • Header
      • Tab
      • Section
      • Repeatable section buttons
      • Subform
      • Static HTML
      • Hidden Field
      • Selection Fields
      • Calculations
    • Processes
      • General Settings
      • Dynamic Field Mapping
      • Process Steps
      • Step Types
      • Logging
    • Datastore
      • Process interaction
      • Manage datastore entries via Webservices - Javascript
    • Tasks
    • Auto Forms
    • Adapters
      • Person Data
      • Web Services
    • Event triggers
    • Roles
    • Rolesets
    • Groups
    • Views
      • View Example 1
      • View example 2
    • Mail Templates
    • Layouts
    • Mail queue
    • Reporting
    • External Apps
    • My Items
    • Translations
    • Bulk Uploads
    • Help page
    • Goto
    • Search
    • Inbound Email
    • Reporting Dashboard
    • Ticketing
      • My Activities
      • Ticketing Views
      • External Integrations
    • Release Manager
    • Content Management Console module
    • SSP Studio
    • Persons & Accounts
    • Pools
  • Release Notes
    • Terms and Conditions
      • December 2024
    • Release 7.21.01
    • Release 7.21.03
    • Release 7.21.04
    • Release 7.21.05
    • Release 7.21.06
    • Release 7.21.07
    • Release 7.21.08
    • Release 7.21.09
    • Release 7.21.10
    • Release 7.21.11
    • Release 7.21.12
    • Release 7.22.02
    • Release 7.22.03
    • Release 7.22.04
    • Release 7.22.05
    • Release 7.22.06
    • Release 7.22.07
    • Release 7.22.08
    • Release 7.22.09
    • Release 7.22.10
    • Release 7.22.12
    • Release 7.23.01
    • Release 7.23.02
    • Release 7.23.03
    • Release 7.23.04
    • Release 7.23.05
    • Release 7.23.07
    • Release 7.23.08
    • Release 7.23.09
    • Release 7.23.10
    • Release 7.23.11
    • Release 7.23.12
    • Release 7.24.02
    • Release 7.24.03
    • Release 7.24.04
    • Release 7.24.05
    • Release 7.24.06
    • Release 7.24.07
    • Release 7.24.08
    • Release 7.24.09
    • Release 7.24.10
    • Release 7.24.11
    • Release 7.24.12
    • Release 7.25.01
    • Release 7.25.02
    • Release 7.25.03
    • Release 7.25.04
    • Release 7.25.05
  • Guides
    • Installation Guide
      • Scheduled Task installation
    • Upgrade Guide
    • LDAP Import
    • Training
      • Exercise : Create a new form
      • Exercise : Create a new Datastore Parameter
      • Exercise : Create a new Process
      • Exercise : Create a new Role
    • SubTopics in Topics
  • Pergapedia platform
Powered by GitBook
On this page
  • FieldTwo checks if it is equal to FieldOne, if not: show error
  • Compare dates
  • Field cannot contain negative values (-)
  • Make a field required (example is for Document template part)
  • Make 3 fields required (example is for Document template part)

Was this helpful?

  1. Catalog
  2. Catalog Maintenance
  3. Parts (Fields)

Field Validation examples

PreviousCalculationsNextField Visibility Examples

Last updated 1 year ago

Was this helpful?

FieldTwo checks if it is equal to FieldOne, if not: show error

  1. FieldOne: no validation

  2. FieldTwo:

    1. Set validation error via: Javascript

    2. Validation Error:

      1. if (#REPLACE-PARTVALUE-FieldOne||# !== #REPLACE-PARTVALUE-FieldTwo||#) return 'Field one must be equal to field two';

    3. Screenshot

Compare dates

  1. Field ‘DateToCompareTo’ contains the date to compare the other field ‘DateAfterDateToCompareWith. ‘DateToCompareTo’ can be filled form the workflow and set as read-only.

    1. This is the default value to set on ‘today’:

      1. Default value type: NCALC

      2. Default value: FORMAT('{0:yyyyMMdd}', NOW())

  2. DateAfterDateToCompareWith

    1. Set validation error via: Javascript

    2. Validation error:

      1. if (#REPLACE-PARTVALUE-DateAfterDateToCompareWith||# < #REPLACE-PARTVALUE-DateToCompareTo||#) return 'Date must be after date to compare with';

      2. Screenshot:

  3. DateAfterToday checks if the filled in date is in the future.

    1. Set validation error via: NCALC

    2. Validation error;

      1. IIF('#REPLACE-PARTVALUE-DateAfterToday||#' < FORMAT('{0:yyyyMMdd}', NOW()), 'Date must be after today', '')

Field cannot contain negative values (-)

  1. var thenumber = Number(#REPLACE-PARTVALUE-nummer||#);

  2. if (thenumber && thenumber < 0) return "Only positive numbers allowed";

Make a field required (example is for Document template part)

In the example below, 2 fields are required:

var toreturn = { success: true };

var parts = JSON.parse(g_data_string).parts; var category = parts.filter(function (p) { return p.internalname === "Doc_Category"; }).map(function (p) { return p.value; }).join(""); var version = parts.filter(function (p) { return p.internalname === "Doc_Versie"; }).map(function (p) { return p.value; }).join(""); if (!category || !version) { toreturn.success = false; toreturn.errormessages = {};

if (!category && !version) {
    toreturn.errormessage = "'Category' and 'Version' are required";    
} else {
    if (!category) {
        toreturn.errormessage = "'Category' is required";
    } else if (!version) {
        toreturn.errormessage = "'Version' is required";
    }
}
if (!category) {
    toreturn.errormessages.Doc_Category = "A value is required";
}
if (!version) {
    toreturn.errormessages.Doc_Versie = "A value is required";
}

} return toreturn;

Make 3 fields required (example is for Document template part)

var toreturn = { success: true };

var parts = JSON.parse(g_data_string).parts;

var category = parts.filter(function (p) { return p.internalname === "Doc_Category"; }).map(function (p) { return p.value; }).join("");

var version = parts.filter(function (p) { return p.internalname === "Doc_Version"; }).map(function (p) { return p.value; }).join("");

var versiondate = parts.filter(function (p) { return p.internalname === "Doc_Version_date"; }).map(function (p) { return p.value; }).join("");

if (!category || !version || !versiondate) {

toreturn.success = false;

toreturn.errormessages = {};

var missingfields = [];

if (!category) {

missingfields.push("Category");

toreturn.errormessages.Doc_Category = "A value is required";

}

if (!version) {

missingfields.push("Version number");

toreturn.errormessages.Doc_Version = "A value is required";

}

if (!versiondate) {

missingfields.push("Version date");

toreturn.errormessages.Doc_Version_date = "A value is required";

}

toreturn.errormessage = "One or more fields are required: " + missingfields.map(function (fld) { return "'" + fld + "'"; }).join(", ");

}

return toreturn;