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

Was this helpful?

  1. Fulfillment Platform
  2. Forms

Section

PreviousTabNextRepeatable section buttons

Last updated 3 years ago

Was this helpful?

Sections are used to only display questions under certain conditions. Within Sections, conditions are defined that decide if the Section is active or not. When Active, all questions defined within the section will be displayed. Fields can individually be to sections.

clip0250
  • Condition X : a Section acts upon the entry of a value in one of the fields defined in the condition. Every time a parent field has a change in value, the condition of the sections is evaluated.

  • Connector: Conditions build up the rule(s) so SSP 7 can decide if the Section needs to be shown or not. A Condition is made out of multiple Conditions, each Condition represents a rule. The Rows work together by using the different states in the Connector ( AND & OR)

  • Field(s) to compare : Select a option to set as the source for the comparison.

Options: Person Field: Any information from the Requestor or the Requested For can be selected. These fields are defined under Admin > Adapters > Person Data.

Form Field: The drop down list shows all questions. By selecting a question, all fields of the parameter become available. The selected column will be used as default answer of the current question.

Main/Sub Form Field: When Subforms are used in a form, use this option to select it, and see the Fields belonging to it. This can be used both when defining the main form, as well as the sub form.

Base Form Field : When a form is used in a process, you might want to use a field from the form that was used to start the process. This is where you can select those fields.

Process Instance Variable: when a form is used in a process, you have access to the Variables that are defined in that process. Select the process and the variables are presented for selection.

Repeatable section index : when using repeated sections, you might want to know the sequence number of that section. use this option to implement it in your form (for example to show the number of entries).

  • Operator: Set the comparison ( =, <, <=, >, >=, different,contains, not contains)

  • Value: the value against which the comparison is made. For DataStore fields, the values from the DataStore are displayed. For text fields, free text can be used as condition.

Section Settings

Section Indent : the value entered in the field 'Indent String' will let the questions inside the Section move to the right. You can for example add spaces in the entry field, to move the questions a few character widths to the right, thus making a distinction with the questions outside of this Section.

Repeatable : check this box to make this section repeatable by the user. Upon checking these options are available:

Translations

The other required input are the Translations, called 'labels' in the screen below:

All Field types can be used in Conditions. Please note that conditions on text fields are only evaluated after the user has removed the cursor from the edited field.

You can include sections within another Section. This goes down to unlimited levels.

Deleting a section will delete all questions and sub-sections below it.

When using Multi-Select fields as condition (like checkboxes), sections will become active if the condition is met, also when more values than defined in the condition are selected.

When a section is copied from the Field list , all question inside it are copied as well.

clip0251
clip0252

- Initial repeats : set the number of initial appearances of this section upon opening the form. If left empty, the value is 1. - Minimum repeats : set the minimum repeats that the user needs to complete. If left empty, the value is 1. - Maximum repeats: set the maximum repeats that the user can complete. If left empty, the value is 1. - Add more repeats increments by: when the user wants to add more repeats, set the number of added sections. If left empty, the value is 1. Do not forget to copy the field type 'Repeatable section buttons' to this repeated section. Otherwise, the user will not have any buttons to add more repeats, or any other option.

clip0224
linked
alert_1818
alert_1818
alert_1818
alert_1818
alert_1818
alert_1818