User Manual Selligent Designer en v5.0

8/11/2019 User Manual Selligent Designer en v5.0

1/112

Current release: 11/26/2012

Product Manual

Designer

Selligent

The contents of this manual cover m aterial copyrighted by Selligent.

This manual cannot be reproduced, in part or in whole, or distributed or transferred by means electronic or mechanical,

or hotoco ied, without the rior written consent of a re resentative from Selli ent.


2/112

2 Foreword

1 ForewordCopyright

The contents of this manual cover material copyrighted by Selligent. Selligent reserves all intellectualproperty rights on the manual, which should be treated as confidential information as defined under the

agreed upon software licence/lease terms and conditions.

The use and distribution of this manual is strictly limited to authorized users of the Selligent Interactive

Marketing Software (hereafter the Software) and can only be used for the purpose of using the

Software under the agreed upon software licence/lease terms and conditions. Upon termination of the

right to use the Software, this manual and any copies made must either be returned to Selligent or be

destroyed, at the latest two weeks after the right to use the Software has ended.

With the exception of the first sentence of the previous paragraph, no part of this manual may bereprinted or reproduced or distributed or used in any form or by any electronic, mechanical or other

means, not known or hereafter invented, included photocopying and recording, or in any information

storage or retrieval or distribution system, without the prior permission in writing from Selligent.

Selligent will not be responsible or liable for any accidental or inevitable damage that may result from

unauthorized access or modifications.

User is aware that this manual may contain errors or inaccuracies and that it may be revised without

advance notice. This manual is updated frequently.

Selligent welcomes any recommendations or suggestions regarding the manual, as it helps to continuously

improve the quality of our products and manuals.


3/112

3Table of Contents

2 Table of Contents

1 Foreword ................................................................................................................................................. 2

2 Table of Contents .................................................................................................................................... 3

3 Introduction ............................................................................................................................................. 6

3.1 Introducing the Selligent Interactive Marketing Designer............................................................... 6

3.2 Concepts .......................................................................................................................................... 7

4 SELLIGENT Designer Interface ................................................................................................................. 8

4.1 Navigator Window ........................................................................................................................... 9

4.2 Document Window ........................................................................................................................ 10

4.3 Resource Window .......................................................................................................................... 13

4.3.1 Sensor Window ...................................................................................................................... 13

4.3.1.1 Validate Sensors............................................................................................................. 15

4.3.1.2 Sensor Properties Window ............................................................................................ 16

4.3.2 Perso tab ................................................................................................................................ 19

4.3.2.1 User lists......................................................................................................................... 19

4.3.2.2 Tags ................................................................................................................................ 22

4.3.3 Content tab ............................................................................................................................ 22

4.3.3.1 Sql Container.................................................................................................................. 23

4.3.3.2 Action article container ................................................................................................. 27

4.3.4 Images tab ............................................................................................................................. 35

4.4 Main Design Area........................................................................................................................... 36

5 Designer functionality ........................................................................................................................... 38

5.1 Configuring a new message ........................................................................................................... 38

5.1.1 Message fields ....................................................................................................................... 40

5.1.2 HTML...................................................................................................................................... 46

5.1.3 Attachments .......................................................................................................................... 47

5.1.4 Advanced ............................................................................................................................... 52

5.1.5 Language ................................................................................................................................ 54

5.1.6 Best version ........................................................................................................................... 54

5.2 Testing emails ................................................................................................................................ 56

5.2.1 Content preview .................................................................................................................... 56

5.2.2 Spam check ............................................................................................................................ 58

5.3 Creating text version of mail messages ......................................................................................... 59

5.4 Designing a form ............................................................................................................................ 62

5.4.1 Creating the Form .................................................................................................................. 62

5.4.2 Adding Form Elements .......................................................................................................... 63

5.4.2.1 Insert form elements from the form toolbar or insert menu. ....................................... 64


4/112

4 Table of Contents

5.4.2.2 Insert form elements from the user properties window. .............................................. 65

5.4.3 Configuring Form element properties ................................................................................... 66

5.4.3.1 Radio Button and Check Box.......................................................................................... 66

5.4.3.2 Select List and Drop down Box ...................................................................................... 67

5.4.3.3 Text Field........................................................................................................................ 68

5.4.3.4 Button ............................................................................................................................ 68

5.5 Using content sections................................................................................................................... 69

5.5.1 Creating sections ................................................................................................................... 69

5.5.1.1 From the Design area..................................................................................................... 69

5.5.1.2 From the Document window ......................................................................................... 72

5.5.2 Defining the content .............................................................................................................. 77

5.6 MVT-containers ............................................................................................................................. 78

5.7 Translating messages ..................................................................................................................... 875.7.1 Translation files ..................................................................................................................... 87

5.7.2 Labels ..................................................................................................................................... 91

5.8 Importing files................................................................................................................................ 93

5.8.1 Files tab.................................................................................................................................. 94

5.8.2 Static content......................................................................................................................... 95

5.8.3 Dynamic content.................................................................................................................... 95

5.8.4 Links ....................................................................................................................................... 96

6 Version Control in SELLIGENT Designer ................................................................................................. 976.1 Change Log .................................................................................................................................... 97

6.2 Versions ......................................................................................................................................... 98

6.2.1 Creating a Backup of the Current Message ........................................................................... 99

6.2.2 Restoring a backup .............................................................................................................. 100

6.2.3 Restoring a backup as a copy............................................................................................... 101

7 Social Media in SELLIGENT Designer ................................................................................................... 102

8 SELLIGENT Designer Menus ................................................................................................................. 105

8.1 File Menu ..................................................................................................................................... 105

8.2 Edit Menu .................................................................................................................................... 106

8.3 Insert Menu ................................................................................................................................. 106

8.4 Table Menu .................................................................................................................................. 107

8.5 View Menu................................................................................................................................... 108

8.6 Help Menu ................................................................................................................................... 108

9 SELLIGENT Designer Toolbars .............................................................................................................. 109

9.1 The Document Toolbar ................................................................................................................ 109

9.2 The Edit Toolbar........................................................................................................................... 110

9.3 The HTML Design Toolbar............................................................................................................ 110


5/112

5Table of Contents

9.4 The Insert toolbar ........................................................................................................................ 111

9.5 The View Toolbar ......................................................................................................................... 111

10 Whats New..................................................................................................................................... 112

10.1 4.2 ............................................................................................................................................ 112

10.2 4.3 ............................................................................................................................................ 112

10.3 5.0 ............................................................................................................................................ 112


6/112

6 Introduction

3 Introduction

3.1 Introducing the Selligent Interactive Marketing DesignerSelligent Designer is a full authoring environment where one manages, creates and edits the messages in

a communication process. E-mails, (web or mobile) pages and web forms are supported.

Apart from designing messages, the Designer is capable of importing(HTML/graphical) designs from your

standard authoring environments like Adobe (Dreamweaver) and many others. Both imported and

designed messages can be saved as templates, which give you a head start when creating new messages.

The Designer can convert HTMLmessages automatically to text emails in flows, which saves a lot of work.

Messages are organized in a flexible message inventory system that allows structuring work to a

maximum. Personalisation and content sections offer unmatched flexibility to create highly targeted

communication with the least effort.

Based on the available contact information stored in the User lists, messages are enriched with

personalisationfields

In addition it is possible to adapt the content of a message to the preferences of each user. A message canbe composed of different sections, which are either shown or hidden, based on profile information. This

offers extreme flexibility at design time. Outgoing e-mailings are dynamically built based on relevancy for

the target user. Advanced preview functionality allows viewing the resulting messages for all defined

content sections.

SELLIGENT Designer key features:

Authoring of emails, digital pages and forms.

Access to the user profile in order to personalise messages.

Integrate response sensors in messages for reporting reasons.

Efficiently create personalised content with content Sections.

Organize messages in multi-level folders.

Real-time Spam check (multiple checks such as domain checks, Spamassassin,...)

Image library

Create email templates (to use in Express)


7/112

7Introduction

3.2 ConceptsWorking with SELLIGENT Designer requires basic knowledge of Microsoft Windows and basic HTML

knowledge (this only when using templates and automation templates).

Besides, you need to understand some essential elements on which the Designer is based. You must in

other words have an idea of the logic that is used throughout the application. The following concepts are

used within SELLIGENT Designer:

Message: Within SELLIGENT the term message is frequently used. This refers to all communication

elements that can be created with or imported into the Designer. The Designer allows you to create

and store two types of messages: Emails and Pages (crosschannel: mobile, internet ...).

Sensors: SELLIGENT Designer allows you to create sensors that can be inserted in all types of

messages. These sensors are measurable hyperlinks which enables measuring the action taken on

these sensors: click through, submissions of forms etc.

Content Segments/Sections: Content Sections allow breaking up messages in different sections. This

means that one message can contain multiple variants depending on the activated sections of the

message. By using constraints, specific content sections can be shown or hidden. There are many

occasions where this tactic is useful. For instance, when sending a newsletter, you want to supply theinformation that matches the interest of your audience. (E.g. showing the appropriate mobile phone

based on the type of mobile phone you get from user profile)

List Sections: List Sections are not to be confused with content Sections. List sections refer to specific

target groups within the contact list. They allow aiming the flow at those individuals that are most

likely to be interested in your message. These target groups can be attained by using the drill down

environment (part of SELLIGENT Manager) or by using conditions / constraints. For instance, you can

decide to target exclusively male contacts.

Personalisation: Personalisation starts with an individual approach within the message and based

upon information that is available in the contact list. For instance, you can address the recipient -

when known - by his /her first name, address, last purchase date etc. SELLIGENT also allows

personalisation to pre-fill forms with contact profile information.

Filter/constraints: The target users can be refined by adding constraints (additional filters) on the

target list. This allows defining specific sub-lists based on profile information

Coding/functions: All personalisation must be enclosed between tildes e.g. ~NAME~. In that case data

comes from the user list. To use personalisation data that is provided by a form or posted through a

link, the @ sign is used. E.g. @NAME . When using text data, one should use single quotes and not

double quotes (e.g. COUNTRY=BE). To show translations the prefix $ is used.

Note that the quotes created in Word will not work when copied to the Designer. Only straight

quotes are allowed in the Designer. COUNTRY=BE instead of COUNTRY=BE


8/112

8 SELLIGENT Designer Interface

4 SELLIGENT Designer InterfaceThe Designer consists of four windows. You can re-locate the windows on your screen by using drag-and-

drop. To move these windows around, select the top bar of the window and move your mouse (by

keeping the left mouse-click pushed down). You can also close them by clicking on the close button

located at the top right of the window. Use the View menuto make the windows reappear after closing.

The Designer contains following windows:

Main Design Areasituated in the center

Message Navigator on the left top

Document window(Segment Window)

Resource Windowon the right


9/112

9SELLIGENT Designer Interface

4.1 Navigator WindowBy default the window is situated in the top left corner of the Designer.

The Navigator Window gives a hierarchical view of all the messages in the SELLIGENT system. These

messages are visualized in a tree view.

The navigator window facilitates the organization of your messages in logical folders. You can create

multi-level folders like in Windows Explorer. Depending on your user rights, you can view, create, modify,

move or delete folders and messages.

Click the small + andsign in front of the folders, to respectively expand or close folders. In order to open

a message, click the desired message.

The tree view of folders in the Designer is the same as within the Campaigner. Only the content is

different. Deleting a folder in the Designer deletes the corresponding folder in the Campaigner.

The Designer allows the creation of two types of messages. Every message type has a dedicated icon by

which it can be recognised:

: mail message: mail messages are send out by using the e-mail component in the Campaigner

: page: pages can be used for rendering in external websites. They can also be accessed directly by a

target


10/112


11/112


Text Version: When this tab is active messages are displayed in plain text IF available.

Note:

The generation of the text version of a message must be performed from the Edit menu through the

Convert to text option.

However the extraction of the text version from the HTML version does not create the references to

sensors. These sensors must be linked manually to the text version.

Messages are built from content sections. Every message contains at least one content section. In that

case, the content of the message will be identical for all recipients (by default the name will be

Message).Creating multiple sections enables content differences based on conditions.

The HTML version tab page gives an overview of the different sections that are used in your message.

When your message is meant to target the entire contact list, it will contain only one section. If on the

other hand you wish to target different audiences in the same flow, it will contain multiple sections.

Note:

The content Sections can be applied independently to rich content or plain text.

The available options for HTML content and plain text are identical. They are accessible by right-clicking

the selected content section in the Sections Window.

New section: create a new content section. This new section is created within the selected section and a

name must be defined (For more information check out section0.):

Example:

Sections that are created within this Document view represent in general bigger content sections. For instance it is

possible to create a section targeted to men, and a section targeted to women. When a section is selected in the

Document window, only the corresponding content of that section is displayed in the Design area. However, the

Preview view will display the complete message, with all sections.


12/112


Delete: delete the selected section

Up/down: move the selected section up or down

Properties: display the properties for the selected section. The properties dialog is displayed. (More

information can be found in section5.5.1)

Segment name: the name by which the segment/section will be referred to.

Language: defines how the values will be translated and when the segment is visible. (Fields in user lists

can be translated in other languages. These translations are created in the Manager. When the section

contains personalisation fields with a $ sign in front, these fields are translated into the language defined

for the section.) It is possible also to use the language defined for the complete message (option: Use

Message language).

Target selection: define the target audience that will receive this section of the message. A choice can be

made between all recipients and selection. In the latter the constraints are defined in the text field

box.

Note:

Sections that are only visible to a selection of targets are displayed with a small icon in front of it:

Within a section, a sub-section can be created with the same properties and rules as the mother-section.

On the lowest level a section (with the same characteristics as a segment) can be defined.

Note:

The properties of a sub-section are not copied automatically. However when a language is defined

for a upper section , there is no need to redefine the language for the lower section as the filtering is

already applied on the highest level.


13/112


4.3 Resource WindowThe Resource window to the right contains four tabs:

Sensor

Perso

Content

Images

4.3.1 Sensor Window

The Sensor window provides an overview of the available sensors within a selected message.

Sensors are usedto:

Measure a user response. This can be visualized within the SELLIGENT Analytics.

Serve as triggers to initiate new actions.

Now, the following sensor is by default available from the Sensor window, even if no sensors have yet

been defined for the message:

The Web version sensor is added to mail messages to allow users to read the mail mess age in a web

browser in case they are unable to view the mail correctly in their email client. To ensure that this sensor

is only displayed when the mail is viewed in an email client (it is no use showing this sensor if you are

already viewing the mail in a web browser) a condition is to be added to the visualization of the sensor:

SYSTEM.MAIL=1. This implies that the mail is being opened in a mail client and not a web browser.


14/112


A right click anywhere within the Sensor window displays a pop-up menu with the following options:

New sensor: creates a new sensor within the selected message. The Properties window is launched.

Hyperlink to sensors: converts all hyperlinks to sensors.

Remove unused sensors: removes all unused sensors from this message.

Validate Sensors: opens the sensor validation panel.

Overview: gives an overview of all sensors with their type, id, name and url.

Right clicking a sensor gives the following pop-up:

Link sensor: link the selected sensor to a selection in the current message.

Delete: delete the selected sensor.

Test: test the URL attached to the selected sensor.

Find: Find the selected sensor in the current message.

Properties: Open the properties window of the selected sensor.


15/112


4.3.1.1 Validate Sensors

Selecting the Validate sensors option in the contextual menu launches the following window:

From this screen, its possible to validate each sensor included in the message.

Note: This validation process checks each direct URL, ignore blank sensors and also verifies links to

SELLIGENT flows.

To do so, select a user list and a test user by using the corresponding dropdown lists:

Next, click the Validate button to perform the check operation:

Once the process is finished, the validation status are displayed in the table:


16/112


4.3.1.2 Sensor Properties Window

When selecting the Properties option from the contextual menu, the following window is displayed:

This window consists of two tabs:

General

Advanced


17/112


4.3.1.2.1 Sensor Properties Window: General tab

This tab allows configuring the basic information of the sensor.

SELLIGENT has three sensor types:

A redirect to an external URL. In this case, the user clicking the sensor will be taken to a

specific web page.

A redirect to an existing flow. This sends the target to another flow and the option is to be

used in combination with an Input component in that flow. The It is possible to send a

number of parameters at the same time which can be retrieved by the Input component

A redirect at flow level- blank sensor (action will be defined at flow level)

Redirect to an external URL:

Enter the absolute URL (starting with http://). (Note: When entering a web site url, add a /. This ensures

that the system verifies immediately an url. If it is not added, it will search for files and folder names with

that value and next web pages. By adding the / the search is slightly quicker.)

You can also insert references to the user list or external properties (e.g. ~LINK~). Use the browse button

next to the URL field to select the desired user property field.

Redirect to an existing flow:

Via the Selectbutton an input component (see SELLIGENT Campaigner manual) in an already existing flow

can be selected. This allows sending the target to another flow when clicking the sensor. The Parameters

section allows defining a number of parameters that can be retrieved by the Input component and used

further on in the targeted flow.

Reaction at flow level(A blank Sensor):

Choose this option when you do not wish to link the sensor in the Designer. The sensor will need to be

defined later in SELLIGENT Campaigner. This may come in handy when the same sensor is used in multiple

campaigns but behaviour is different depending on the campaign.

After choosing the correct sensor, click on the Finishbutton to apply the changes.


18/112


Tip: The name of the sensor is also used in the reporting.

4.3.1.2.2 Sensor Properties Window: Advanced tab

In this tab, its possible to define specific information that allows performing reporting.

Tagging

The tagging panel is used to add specific tags to the sensor. Those tags can be used by external systems.

(Example of external systems are Xiti, nedstat,..) This allows indicating for instance that a sensor

redirecting to a sports page is tagged as Sport. This tag can be requested as following: PROBE.TAG

Categorisation

This panel allows assigning a category to the sensor. The available categories are defined in the SELLIGENT

Manager tool. (To get more information about Category, consult the SELLIGENT Manager manual). This

Category field is mainly used for the OPTOUT- category which is used in combination with the AB-component. When measuring the best click through rate clicks on sensors with the OPTOUT category are

not taken into account.

Taxonomy

The taxonomy panel provides a list of taxonomy tags used to characterize the sensor. For example, a

sensor which sends the user to a financial website can be tagged with the appropriate tag Financial.

Whenever the user clicks such a sensor his profile is extended with this information. However, before

using taxonomy on sensors, its mandatory to specify first a User list with a taxonomy defined on it. This

means linking a taxonomy list to the user list. It can be easily done in the Message properties panel.

Reporting on taxonomy is available from Analytics.


19/112


4.3.2 Perso tab

The Perso tab, represented by the icon, displays an overview of all available user lists and system

tags. All these entries can be used in a message.

The Perso tab is situated right of the application in the resource window.

4.3.2.1 User lists

User lists contain attributes that can be incorporated as personalization fields in the message.

Personalization can equally be used to pre-fill forms or to create the forms with an immediate link to the

appropriate field name.

Clicking the small + andicons will expand or close the list.

When a contact list is not available, a red cross is marked through the list icon.

Two buttons are available at the top:

Inserts the contact profile attribute

Inserts the translation of the contact profile attribute. The personalisation field is displayed with a $

sign in front of the field name and between two tildes. (The translation of this field is defined in the

SELLIGENT Manager.)

Note: when a translation is inserted in a message, the language must be defined in the message as

well. If no language is defined, only the code related to the field is displayed as SELLIGENT has no

way of knowing which translation to use.


20/112


Now, the main purpose of this window is to insert personalisation fields in the messages. It is also a

valuable feature in relation to forms. Lets explain this: When right clicking an attribute in a list a pop -up

menu appears:

Depending on the properties of the selected attribute, a different number of functions are available.

Insert: The database value of the user attribute is inserted as a personalisation field.

This is typically used in mailings where the opening and closing are adapted

according to the target person. (ex: Dear Mrs. Lupin)

In the message this looks like following:

Insert Translation: The database translation of the user attribute is inserted as a personalisation

field at the cursor location in the current message (ex: Dear Madame Lupin in

case of a French speaking user)

In the message this is displayed as follows:

Insert as Textbox: The user attribute is inserted as a textbox. The maximum length is limited to

length defined for the field in the List This is typically used in forms where the

user viewing the form has to enter some text.

In the message this is displayed as follows:

The @ in front of the field indicates that a value will be retrieved from the

database, if available or that the value entered by the user in the form will be

stored in the database when the form is posted.

Insert as TextArea: The user attribute is inserted as a text area. The @ in front of the field indicates

that a value will be retrieved from the database, if available or that the valueentered by the user in the form will be stored in the database when the form is

posted.


21/112


Insert as Dropdown: The user attribute is inserted as a dropdown box

If an attribute has a list of values associated to it, a + icon appears next to the

attribute in the User list. .

Example:

The Language field has several options attached to it. In this case the Language field can

be added as a dropdown list from which the user can select a value.

So adding the f ield as a dropdown list results in the following:

However right-clicking a field option allows inserting it as a radio or checkbox.

The result is as follows:

Insert as List: The user attribute is inserted as a select list. The result is as follows:

Insert as radio buttons: The user attribute is inserted as a radio list.

Link to selection: The user attribute is linked to the form. This is used when the value of the

selected attribute is to be filled out with a value from the user list. This is the

same as typing ~@Attribute~.

Refresh: Refresh the User attribute

Note:Insertion of user properties can also be done manually.Insert the value of the user attribute: ~USER_PROPERTY~

Insert the translation-value of the user attribute: ~$USER_PROPERTY


22/112


4.3.2.2 Tags

Apart from user properties, SELLIGENT also recognizes system properties. These predefined properties are

useful when the message is generated. The tags with syntax NAME.TAG can also be used for trackers. The

other tags are mostly used in the Designer to hide/show sections in a message.

System field properties are inserted in the same way as user attributes. Position the cursor at the desired

position in the message and select Insert by right-clicking the system attribute or double click the

attribute.

Typically one will find system tags with date information and IDs (flow, mail, list...). Others are:SYSTEM.MAIL: can be used to retrieve how an email is being viewed. When it equals 1 the message is

viewed in a mail client. If it equals 0 the message is viewed in a web browser. This system tag can be used

to show/hide the hyperlink in a message that allows viewing the message in a browser.

DATA_ERROR: When this tag is placed in a message an error message is displayed when an error occurs

during validation. The content of this error message is defined in the Validation of the Data component in

the Campaigner. In there, for every parameter being validated it is possible to define a specific error

message when validation fails.

SYSTEM.TESTMAIL: A tag that can be used to display specific text or section when the message is a test

message. Ex: ~(IF(SYSTEM.TESTMAIL=1, ' [TEST ] ',''))~ the subject of the message.In this exemple the

subject of the message will display TEST in addition to the normal subject line.

SYSTEM.DEBUG: this value is set to 1 if the message is being tested in the preview window.

4.3.3 Content tab

The content tab can be used to insert variable sections and article sections, typically used in Newsletters.

In the Designer, template messages can be created and later on used in SELLIGENT Express.

Most components available from the Content tab are used for Express templates. To find out more about

these templates and components, please check out the corresponding document SELLIGENT_Express.

However, some components are only available for regular e-mails and pages, and are not available for

selection in template emails. These components are explained below: Sql Container and Action Article

container.


23/112


Both components allow displaying dynamic content either in a page or in an email. The container is always

structured in the same way and fed by a list:

1. Header: is shown once, above all the articles

2. Item: this section will contain the actual articles. It will be repeated for each section.

3. Footer: is shown once, below the articles

4. NoMatch or Default: is shown when no articles are found. This will only be used when enable

missing content protection is not checked (see later).

Each of these elements in the container can contain blocks of text and images.

4.3.3.1 Sql Container

An SQL container can be used for SELLIGENT pages and is a mechanism allowing displaying variable

content based on data stored in a datalist.

Note: SQL containers are only available for SELLIGENT pages. They cannot be used in emails or

express templates.

Note: The data list used for the SQL container MUST be linked to a user list. As a result, the

container can only be used for known users.

Whenever a SELLIGENT page is rendered it loads the content (articles) for its SQL containers from the

underlying database. To do so it executes an SQL query (that is defined in the containers configuration)against the data list table. Every row returned by the SQL query is translated into 1 article (the columns

are the article fields).

Every page hit (rendering) reloads the articles from the database; this ensures that the content of an SQL

container always reflects the content of the database at the moment the page is rendered. Therefore SQL

containers should only be used when it is strictly required that a page always displays the latest data.

Important note: articles are only displayed for authenticated users. SQL containers cannot be used

for pages visited by anonymous users.

To add an SQL container to a page:

1. Create a page.

2. Next, activate the Content tab.

3. From the toolbar, select the icon SQL container


24/112


The following dialog is displayed:

4. On the Generaltab, enter the name, alias and description.

The Type field is filled out automatically.

The Content Selection tab defines how and where the SQL container loads the articles. The following

properties are set:


25/112


5. Select the data list from which articles are retrieved. The drop down list provides access to all data

lists defined in the SELLIGENT Manager.

6. The where clause defines a filter that limits the articles loaded from the data list.It is possible to use

posted data or data from the master user profile.

Example:

Use ~FieldName~ to retrieve data from the master user profile.

Use ~@FieldName~ to retrieve a posted value.

7. The field Max article count limits the maximum number of records returned by the query. If no value

is entered or a value over 500 is set, the system limits the maximum number returned to 500.

Note: when the where clause is executed on the data list, records are returned randomly. If there

are more then 500 records corresponding to the where clause, only the 500 first are returned, in a

random way. To influence which records are exactly returned, the Fields section is used.

Technical Note:

The SQL statement is executed on every page hit. To avoid performance problems the where clause must

be as eff icient as possible (indexes) and it should return the smallest possible set of articles.

8. The fields section at the bottom is used to define the fields on which sorting of the articles must be

performed and thus in what order the articles are returned.

Example:

A query on a database that is not using an explicit ORDER BY returns its results in a random order. If the maximum

article count setting limits the articles that are returned by the query it will take the first N articles that are returned

by the query (where N is the value configured in the dialog) and it will disregard the rest. Due to the fact that the

result set of the query is unordered it is impossible to predict what articles will make it into the final set of results.

As is the case for regular article containers as well, sorting fields can be added. Adding these sort fields will order the

articles that are returned by the query before the maximum article count is enforced (i.e. if the records are sorted by


26/112


CREATED_DT (DESC) the most recent records will be returned). This allows you to determine which records are

returned first.

To ensure that the where clause is correctlyentered, a test is provided. Press the button Test SQL to

launch the following dialog:

Through this dialog, the SQL statement can be tested against the database.

A user list and test user must be selected to be able to fill out any user profile fields used in the where

clause.

When the Test button is hit the test result is displayed. At the bottom of the dialog, the articles returned

by the SQL statement are listed.

When the configuration of the SQL container is finished, press the OK button. The container is now

available from within the Content tab. All fields within the container are loaded automatically. These

fields correspond to the columns of the selected data list.

A right click on a field allows accessing the properties of the field and sett ing it as mandatory:


27/112


When a mandatory field is empty the record is skipped.

A right click on the container provides access to an option that displays the articles:

This is the content of the data list that is configured for the container, the content selection rules are

not applied in this view (i.e. sorting, where clause, maximum record count ).

The container can now be used and placed onto the page. Configuration of the container is done in the

same way as for the other containers:

4.3.3.2 Action article container

An action article container is a mechanism that allows displaying variable content in an email. This

content is retrieved from an action list record. A dedicated field in the action record contains the articles

that must be presented in the container. (Check out the technical note for more details on this action list.)


28/112


!!!Note that action article containers cannot be used in Express templates nor pages. They can only

be used in regular emails.

Whenever an email is sent from an action list it loads the articles for its action containers from a field in

the action list record. Action article containers do not cache their articles for re-use like standard

containers do. The articles are always loaded from the action list item.

Because the action list item is part of the user profile (see note below) theres no real impact on the

performance of the mail agent when using action containers. There is just a look-up of a user profile field

that is already loaded in memory at that time.

Note: when action lists are used in emails to render the content for the action container, the action

list must be linked to the user list selected for the email. This link must be a 1 to many relation.

Technical note:

Before continuing the explanation on how to use action article containers, we need to explain something

about the action listthat is used by the container. The action list contains one record per action. Multiple

actions can be created for each user. Each action record has a dedicated field (longtext) that stores the

articles. These articles can be stored in 2 formats in that field: XML and JSON.

Example: An action list called ActionToTake with a field ARTICLEDESCRIPTION that stores XML.

The following format must be respected:

XML:

Where Parameter Namemust correspond to the name of the action article container (used below when

creating the action article container in the Designer). The reason for this is that it is possible to call

multiple article containers through the PARAMETER tag for one single mail and one single user. The

advantage of this way of working is that data can be delivered combined and stored in one single field in

the database. By using the exact name of the article container, the system knows where to retrieve the

articles.

The article IDs must be unique. If the ID is not set, the article is not loaded. If there are duplicate IDs only

the first one is loaded.


29/112


The Field names are also used later on in the definition of the action article container. So if the XML is

created before the action container, write these down or else take the f ields used in the action container.

The CDATA tags are recommended and used to avoid bad parsing of the XML due to invalid characters.

JSON:[{

"ID" : 1,

"PARAM" : "ACTION_ARTICLES",

"CONTENT" : {

"FIELD1" : "Field 1 data",

"FIELD2" : "Field 2 data"

}

},

{

"ID" : 2,

"PARAM" : "ACTION_ARTICLES",

"CONTENT" : {

"FIELD1" : "Field 1 data",

"FIELD2" : "Field 2 data"

}

}]

The Paramatttribute in the article node is the name of the action article container that will be created

later on.

The ID attributeis mandatory and must be unique within the same article container. If the ID is not set,

the article is not loaded. If duplicate IDs are detected, only the first is loaded, the others are disregarded.The Fieldsrepresent the different elements of the article and can be used as such in the action article

container.

As action articles can only be used for one particular user, it is recommended to limit the number of

articles that is stored in an action record to those only required for a user.

Before the actionlist can be used in a flow, we need to add the possible action codes to this list. These

action codes represent in fact the possible values for the ACTIONCODE field in a record and allows

filtering. Adding these action codes is done through a right click on the action list in the Manager and

selecting Manage action code from the pop-up menu. The list of possible values is added through the

Addbutton.


30/112


In the SELLIGENT Campaigner a list component can be configured to use an action list. This also requires

the selection of 1 or more action codes that are defined on the action list. Whenever the flow sees newrecords in the action list with one of the selected action codes it handles them as defined in the flow (i.e.

send a mail).

Action codes allow multiple campaigns to operate on the same action list without interfering:

Only records in the actionlist that have an ACTIONCODE that matches one of the selected codes in here

are used in the flow.

Now, lets start the creation of the Action article container.

1. First an email needs to be created (or edited) in which an action article container must be used. In the

properties of the email you need to select the user list on which you want to target the campaign and

consequently to which the action list should be linked.


31/112


2. Next, activate the Contenttab on the right of the Designer Canvas.

3. From the toolbar, select the icon representing Action container:

When an action article container is created, the following dialog pops up.

4. On the General tab a name, descriptionand aliasis defined.

!!!!Note that the name used in here for the article container has to be the same as the one used in

the XML or JSON code stored in the action list.

The typefield is filled out automatically based on the selected type of container.

The Contentprotection section is used to indicate if the email can be sent out or not in case content is

missing. (Note that this option is linked to the default line in the container structure .See page 22. The

default line is used to indicate what should be displayed if nothing is available. )

On the Content tab, the following is defined:


32/112


5. First, select the action list that must be used to provide articles for this container. A drop down list is

available.

Note: only action lists linked to the user list defined in the email are listed. If no action lists are

listed, make sure that the email has a linked user list and that the user list has at least one data list

linked to it.

6. Next, select the field in the action list that contains the articles. This field stores the XML or JSON

code.

7. Once the list and field have been selected, it is possible to test the data provided in the article list.

Click the button Test article data. The following dialog pops up:


33/112


There are two ways to test article data:

Enter the ID of a record in the action list table: the system will load the article data from this

record

Enter JSON or XML formatted article data directly in the provided text field

The test checks if the XML or JSON code is correct, if all article IDs are present and valid, if the articles

have parameter names and if there are indeed articles in the record. Within the articles a check is made

for mandatory information and if all fields are present.

When the test passes, the data can be considered as valid

Once the action article container is created it is added to the Content tab.

However, no fields are listed yet within this container. These have to be added manually and correspond

to the fields used in the XML or JSON code describing the different articles.

Example of XML:


34/112


The tags DESCRIPTION and IMAGE are used as fields within the action container.

1. To add fields to the action container, right click the container and select New field.

2. In the dialog, enter the name of the field and indicate if the field is mandatory:

Note that the name of the field must be exactly the same as the tag used in the XML file or the fields

in the Content section of the JSON file.

If the field is set as required and information is missing for that field, an alert is returned, indicating a bad

template..

Once the fields are created, they are available for selection from the action container entry:

It is recommended to create these fields once within the container. This makes it easier to place them

later within the email and avoids typing errors.

The next step is to place the action container in the email and define the content.

As explained earlier, the action container contains four sections: a header, an item section, a footer and a

default line. The articles provided by the action list are added to the item section.


35/112


Of course, similar to all the other container types, you can the necessary fonts, sizes, colors and other

standard formats for an HTML.

4.3.4 Images tab

In the images-tab, you can manage all the images

that are uploaded in SELLIGENT. Drag images or

files from Windows Explorer to this tab to upload,

drag images from the Images tab to WindowsExplorer to download images.

Right clicking an image displays a pop-up menu.

To insert an image in your page or mail, right click

the image and choose Insert image.

To insert a link or sensor to a file located in the

images-folders, right click the file and choose

Insert as link or insert as sensor.

A toolbar is available:

Use the buttons to navigate the tree view of images or create new folders.

When an image is highlighted in the list, the hour glass allows previewing the image.

Note:To be able to create folders within the Images tab, the user must have the necessary NTFS rights on

the Image folder. The images folder should also be physically created first and configured in the

SELLIGENT Manager. Contact your administrator if you have issues with the Images folder.


36/112


4.4 Main Design AreaThe Main Design Area is the most important section of the application. It displays the message you are

currently designing.

The main design area consists of three tabs:

The Source tab: used to create/view the code behind the Design like standard HTML editors. It is

possible to switch from design to the source mode or vice versa. This is especially helpful for designers

with HTML knowledge. It will allow them to make adjustments to a message that was built in design

mode or to check the results of a message created in HTML. The existing message will automatically

adapt to HTML or design view when clicking on the tabs.

The Design tab: In the design mode, you can build message as if you were working in a standard

authoring environment. The WYSIWYG principle (What You See Is What You Get) applies in this editing

mode. The design mode equally supports form building using the form toolbar or insert menu. This

enables you to insert form tags, checkboxes, radio buttons, text fields and drop down boxes without

the need of HTML knowledge.

The Preview tab: In the preview mode, you can test messages with prefilled values and sections for

different test-users. This allows you to check if the constraints and values you entered are correct. It

also allows you to check your spam score with a real-time link to spam assassin.

Note:

Do not define custom head or body tags in the source mode of the main design area. If you wish to

apply or tags, see the html properties tab in the properties function accessible via

the file menu.


37/112


General options are accessible by right clicking the Main Design Area

Following general options are available:

Undo: Undo the last modification.

Redo: Redo the last modification.

Cut: Cut the selection and place it on the clipboard

Copy: Copy the selection and place it on the clipboard

Paste: Paste the selection of the clipboard into the message

New sensor: Link a new sensor to the selection

Hyperlink: Insert a hyperlink for the current selection. A dialog box appears to define the

hyperlink

Unlink: A previously defined hyperlink on the selection is removed

Insert/Section: Insert a new section or image at the current cursor location in the message (see

section0.).

Insert/Form: Insert a new Form at the current cursor location in the message (see section0).

Insert/Image: Insert a new Image at the current cursor location in the message.

Table: Insert Table, Add Row(s)/Column(s), delete Row(s)/Column(s), merge cells and split

cells.

Properties: Open the properties window of the selected message (see section5.1).


38/112

38 Designer functionality

5 Designer functionalityThis chapter explains the major functionalities available in the Designer.

5.1 Configuring a new message

Mails and pages are created and configured within the Designer. The properties of both types are more orless the same.

To create a new message, right click the folder of choice in the navigator and select New e-mail/New page

from the pop-up menu:

A new message has been added but must yet be configured:

These properties are accessible through a right click on the message and selecting the Properties option

from the pop-up menu.

Note:

Always rename a new added message immediately.


39/112

39Designer functionality

Following tabs are available (all tabs are available for the mail message but not for the page):

Message Fields(mail message only)

Html

Attachments(mail message only)

Advanced

Language

Best version


40/112


41/112


When a user list is selected, an additional option is available: setting a pickup priority:

This option allows defining what emails should be picked up and sent first. The selection is based on a

numeric or date field in the selected user list:

The values for the selected field are sorted either ascending or descending and the order of the targets in

the list is automatically adapted based on the selected pickup priority.

Brand: select a Brand that will be used to broadcast this email. Example: a customer has 1 Selligent

installation but has different product lines that do their communications independently. For each one of

these product lines a brand can be created. This brand is then used in the mails sent out.

Technical note

A Brand is a maildomain. A maildomain contains settings regarding DKIM-signing, mailqueues and

available From addresses. These brands are defined in the Manager. When a Brand is selected a pick list

of available mail addresses is available from the Mail From field. A brand is used to avoid that the mail

sent out is considered as spam. Without a valid from address this will most likely be the case.

It is therefore always recommended to define and use brands when sending out emails.

When a brand is selected and mailqueues are configured, a drop down field allows selecting the

mailqueue to use:


42/112


43/112


From this dialog you can either return to the previous window and allow only one single brand to be used

(Simple button) or start configuring the dynamic mail domains (Edit button). Click the Edit button to start

the configuration on the following page.

In here, multiple mail domains can be defined. To add a new one, press the Add button. Another dialog is

launched with more or less the same fields as displayed on the Message fieldspage, explained earlier.


44/112


In this dialog you are able to select a mail domain, define the header properties but most important set a

condition:

Use the Condition field to enter a constraint. An icon indicates if the constraint is valid( ) or not( ).

Note: It is possible to configure one mail domain without a condition. This is the default one used

when none of the other conditions are met. This specific mail domain is not displayed in the list with

the others, but at the bottom.

When multiple domains are defined, it is possible to change the order in which they are listed by using the

Up and Down buttons to the right.


45/112


Each condition is checked, starting with the first one in the list. If the condition is met, the indicated mail

domain is used. If not, the next condition is checked. If none of the conditions are met, the default mail

domain is applied.

When the configuration of multiple mail domains is finished, the result looks like following on the

Message fields tab:


46/112


5.1.2 HTML

It allows the designer of the message to use special HTML attributes that normally appear in the

and tag. In the HTML source of the message it is only possible to define the content of the body-

tag.

The Header section can - amongst others - be used to:

Define CSS


47/112


Enter Meta tags

Use scripting

Enter the header attributes in the same manner as you would in a HTML editor.

The buttons at the right are used to create constraints or use elements from the User list and tags list.

Example:

The above example shows that a different title is displayed in the header based on a constraint on the gender of the

user. When a constraint is defined the header section displays multiple options available: click here to edit.

The Body Attributes section enables you to define custom body attributes for the message. For instance,

you can set the bgcolor=grey (background colour).

Tip:

For mails, place the subject between -tags in the HTML-tab. That way, the subject of the mail

is shown in the browser-title-bar when a user looks at the html-version of the mail in the browser.

Doc-type: This defines the rules that are to be respected by a browser when converting the html code of a

message to the actual message on the screen. (For more information check out:

http://www.w3schools.com/tags/tag_doctype.asp )

5.1.3 Attachments

The attachment tab gives a review of all the attachments that should accompany the message.Attachment can be added to, modified and deleted from the message.
http://www.w3schools.com/tags/tag_doctype.asphttp://www.w3schools.com/tags/tag_doctype.asphttp://www.w3schools.com/tags/tag_doctype.asp


48/112


To add: Click on the Addbutton. Three options are provided:

File

Contact

Appointment

To modify: Select the attachment and then click on the Modify

button.

To delete: Select the attachment and then click on the Delete button.


49/112


50/112


51/112


Appointment:

In case of an appointment, the following dialog pops up to define the details of the appointment.

The email received by the target will look as follows:

A button allows accepting the appointment.


52/112


5.1.4 Advanced

The advanced tab is only available for mail messages. Images can be included as an attachment in a mail

and the character set to be used can be defined in here.

Following options can be defined:

Embed images: When this option is flagged the images are stored within the message. In general it is not

recommended to embed the images. It could be used for instance in secure environments where the end-

user does not have access to the internet and cannot download the images as a consequence.

Use unicode processing: This option is only available for Unicode Database installations. When available,

it is recommended to check the option.

Define a character set: When no character set is defined, the default character set of the mail program is

used.

It is possible to select more than 1 character set and put constraints on them. ( Example: if the country of

the user is France, use a different character set than if the country of the user is Bulgary)

Tip: For European mails, select Define a character set. Then scroll down in the list to the bottom,

and check Western European (ISO) [ISO-8859-1]. That way, special characters like in French will

always be shown correctly.

Include List-Unsubscribe: when this option is flagged, automatically a link/sensor is created and can be

added to the mail allowing the user to unsubscribe. (This is only used when the mail client supports the

list-unsubscribe standard. More information can be found on www.list-unsubscribe.com). The

corresponding sensor is 9.

By using the option, the recipient will see an opt-out button, instead of a spam button. (Clicking a spam

button is always bad for reputation.) By clicking the opt-out button, a signal is sent to the tool and the

opt-out value is set to 9.

It is recommended to leave the option checked, even if a custom opt-out button is provided. A

custom opt-out will allow taking the user to an opt-out flow.
http://www.list-unsubscribe.com/http://www.list-unsubscribe.com/http://www.list-unsubscribe.com/


53/112


Note that used in an email message the sensor still needs to be configured.

Categorisation: Its possible to define a specific category for the selected message. (To get more

information about Category, consult the SELLIGENT Manager Manual). When a message is categorized

reporting is available on that


54/112


55/112


Automatically select a winner at a specific date and time.

Automatically select a winner after a certain time has elapsed since the start of the test.

The winner is selected when a specific amount of clicks is reached.

It is possible to select multiple options but the one that is completed first is used to determine the winner.

Additionally, it is possible to ensure that there is a significant difference between the winner and the

runner up. The statistical significance allows setting that percentage.


56/112


57/112


The content of the page or mail should contain information on the selected test user:

The Email header as well should be updated with contextual information on the selected test user.

Note that in the text version of the message, the value displayed for sensors is #PREVIEW. This is

because sensors need to be in the context of a flow to be able to create corresponding URL.


58/112


5.2.2 Spam check

With Spam check it is possible to find out if an email message is likely to be considered as spam. The email

body is scanned and a spam score is provided at the end. The higher the score, more likely the email will

be perceived as spam. A spam check can be executed when clicking on the top menu on start analysis:

The following screen appears:

When a spam score is returned, click on show details to see a detailed explanation. A check i s done in

real-time with Spamassassin among others. Some of the explanations given refer to the codes in the

Spamassassin wiki:

Go tohttp://wiki.apache.org/spamassassin/FindPage to get a detailed explanation on the issue.

Use the information provided in this spam check tool to optimize the email message and try again.
http://wiki.apache.org/spamassassin/FindPagehttp://wiki.apache.org/spamassassin/FindPagehttp://wiki.apache.org/spamassassin/FindPagehttp://wiki.apache.org/spamassassin/FindPage


59/112


5.3 Creating text version of mail messagesThe e-mail client of recipients determines whether the recipient will receive the e-mails in rich content

format or pure text format. To be sure that the recipient receives a non-blank mail it is important to

create both formats.

With SELLIGENT you can automatically convert rich content to plain text. After the conversion, you can

manually enhance the plain text mail by editing the text.

To start the text conversion, carry out the following tasks:

1. Select the HTML message

2. Use the Edit Menu to convert to plain text and choose the Extract Text Contentoption.


60/112


3. Use the Document Window in order to view the converted plain text. Click on Text version-tab to

view the message in plain text mode.

4. Edit the layout after the conversion by restructuring paragraphs and phrases and add sensors

manually.

5. After you have edited the text, save the changes:

6. Click on the Preview tab to view the final text message:

All personalisation fields are correctly filled out with the information on the selected test user.


61/112


However, hyperlinks are removed from the text version and need to be re-assigned:

Example:

The original HTML message looks as following:

When the text version is created, the result is this:

The personalisation fields remain correctly displayed but the hyperlinks have been removed. These hyperlinks need to

be linked manually to the sensors. To do so, select the text for which a hyperlink must be created. Next, in the Sensor

window on the right select the sensor, right click and choose Link sensor:

When the hyperlink is created, the syntax ~PROBE()~ is used.

Note: All the HTML-tags are stripped from the text version with an exception of the ... . This tag will be parsed and interpreted by SELLIGENT before sending the

e-mail.


62/112


5.4 Designing a formThe Designer allows inserting forms in a page or mail without the knowledge of HTML or the need to

understand integration protocols. These forms can be made available to a target user either in a mail

message or through a page.

The data entered by the target user in a form can be used to store information in the database, to trigger

an event, If the target user is already known fields in a form can also be prefilled with information

already stored in the database.

When designing a form you need to execute the following steps:

Add a form tag to a message.

Place the form fields within the form. Select carefully the type of form element you want to add:

input text, radio button, drop down list...

Make sure that the data entered in the form can be stored at submit (the @ syntaxis to be used)

Provide a Submit button and define its behaviour

To store the information entered in a form it should be used in combination with a Data component

in the Campaigner.

5.4.1 Creating the Form

Before any data-interaction can happen the GUI components needs to be placed in a Form.

1. A design form can be inserted via the -icon in the Quick-start menu or via a right-click (Insert >

Insert Form) on a white area of the Main Design Area.

A dialog will appear to handle the automatic form processing.

2. Assign a name to the form

3. Choose the right form processing:

Create a new sensor: this is the most common way to process a form, which will send the form

output to the new sensor. This sensor is automatically created and linked to the Submit action of

the form.


63/112


The form will be processed by an external system: The form output will not be processed by

SELLIGENT but by an external system. Enter the absolute URL where the form has to be sent. This

URL has always following structure: http://www.selligent.com/request.html

4. Click OK.

The yellow form tags will appear on the main design area.

All form elements should be entered between the tags.

5.4.2 Adding Form Elements

Once the form has been created form elements can be inserted in two ways:

Insert form elements from the form toolbaror insert menu. In this case the form element is not

automatically linked to a user property

Insert form elements from the user properties window. While doing this, there is a direct link

between the form element and a user property allowing dynamic retrieval of the corresponding

value from the database or storing a value when submitting the form.


64/112


5.4.2.1 Insert form elements from the form toolbar or insert menu.

1. Put your cursor between the form tags in the current page.

2. In the toolbar click the element that must be added to the form. The form element is added

automatically at the position of the cursor:

The form tags will not be prefilled or linked to user properties by default. It is just an empty field.

3. If the element must be linked to a user property, select the form element.

4. Next, right click the user property in the User properties window and choose Link to Selection.

.


65/112


66/112


5.4.3 Configuring Form element properties

The properties of a form element depend on the type. These properties are by default set when form

elements are inserted directly from the user properties window.

Form element properties can be defined in two ways:

Right-click the form element and select properties.

Click the Form Properties button in the form toolbar.

A popup window will appear with the properties of the selected form element.

5.4.3.1 Radio Button and Check Box

Aside from one field, the properties for both radio button and check box are identical. Therefore, we will

discuss them simultaneously.

1. Open the properties on a checkbox or radio button

2. Enter a suitable name for the field. If the element status should be read only, check the

corresponding box.

The field typeis applied automatically when the check box or radio button was inserted.

3. Define the value: this can be done in the usual way (1, 0, checked ). This value will be stored in the

list.

4. Select the stateof the field. With the last selection, it is possible to apply a condition to the checked

state. Use constraint commands (=, , AND, OR ) to formulate the condition.

Example:

Display the check box by default as ticked if the value in the database for the OPTOUT field is 1.

CHECKPROP(@OPTOUT,1)

5. Click OK.


67/112


5.4.3.2 Select List and Drop down Box

The properties dialog is identical for both these form elements.

1. Open the properties of the list or drop down box

2. Enter the field name.

3. Enter the number of visible rows.

When more than one row is visible, the multi-select box becomes available. This box allows the user to

select more than one entry in the list or drop-down box.

4. Select the Field in the Prefill Options section:

Field: if the inserted field is an already existing list-field, it can be selected. If the field is blank the

next option (Prefill with field definition) will be greyed out.

Prefill with field definition: Prefill the option list with the predefined values for the optionlist set

on this field (defined in the SELLIGENT Manager)

Prefill using a customized option List: Enter the value and the caption of the customized option

list. (The caption is displayed in the form, the value is stored)

5. Click OK


68/112


5.4.3.3 Text Field

Define text field properties

1. Enter the field name. If the element should be read only, check the corresponding box.

2. The field typeis applied automatically when the text field was created and cannot be altered.

3. Define a valuewhen you want to pre-fill the text field with information that exists in the contact list.

Use the browse button to select the appropriate user property.

4. Click OK

Tip:

Add a DATA_ERROR system property from the User Properties window to the form. Adding thistag to the form page allows displaying error messages when the form is being validated. The content

of these messages is defined in the Campaigner, on the validation tab of the Data component. These

messages are automatically displayed.

5.4.3.4 Button

A Submit button allows sending the information in the form to either a sensor or an external page.

The behavior of the Submit button is defined inthe properties of the form.


69/112


Technical note:

To use an image for submitting the form (instead of the standard Submit button) execute the following

steps:

1. Insert the image in the form

2. Edit the source code: replace


70/112


2. Click the Insertsection icon or right click and select Insert/sectionfrom the pop-up menu The section is

added:

3. Right-click the new section and select properties. A popup window appears to define the section

properties.

Visibility: Use this option to limit the current section to only a specified number of users

1. Check the option if you want to set a constraint for the users that should see the section. The textbox

is enabled. (example: limit this section only to men)

2. Press the [] button to access the Constraint Editor:


71/112


72/112


6. If this section must also be visible to users with a different language than the selected one, flag the

corresponding option.

7. Next, it is possible to link the current section to another section within the same page. This is an

option that is used when creating templates with dynamic sections. (An article container on which a

filter is placed)

8. Check the option and access the drop down list. All sections in the current message are listed.

8. On the Style tab you can enter a custom style or predefined css-class for the section. By default, a

section is included as a .

The DIV option must be unchecked in case the current section must be in-line with the surrounding

sections. (Example: There are several sections but only one will be used to complete the above text in a

message. This section must be in-line with the above text and therefore the DIV option must be

unflagged)

The Apply style field will allow to apply a predefined style . However although the option is already

visible it is not available yet.

The last option allows entering manually the style that must be applied.

Ex: Margin:0px; font-size:12px; font-weight:bold;

5.5.1.2 From the Document window

When no sections have been created yet from the Document window only the following is displayed:

This indicates that only one section exists at this point. This section has not yet been named.

Note: it is possible that this one section contains several smaller sections created in the Design area.


73/112


Example:

Above is an example of a message with only one section in the Document window in which already two smaller

sections have been created in the Design are. The large section takes up the complete design area.

1. To create a new section, right click the Message and select New section:

A new section is added.


74/112


Note: as you can see from the above screen, this new section is added just underneath Section.

Because smaller sections were already created within the Design area (see previous screen), those

are considered as being part of a first bigger Section in the document window. The New section is

the second section in this case and as you can see no smaller sections exist at this point.

2. Define a name and the properties for this new section by right clicking the section and selecting

Properties from the pop-up menu:

3. Select a specific language for this section or use the language defined for the message.

4. Select the target for this section in the message. Either all recipients can be selected or a selection of

recipients, based on a constraint.

Example: As this section is dedicated to France, a filter can be placed on the Targets, addressing only

targets in France.

5. When the section is configured, it is displayed as following in the Document window:


75/112


Example:

As this second section is targeted to France, name the first section indicating that the target is the Netherlands.

As you can see, this first section contains already two smaller sections.

6. To create smaller sections within the section France, select first this section and go then to the design

area, which is at this point still empty.

7. Right click within the design area and select Insert section from the pop-up menu:


76/112


The section is added:

Enter some text to distinguish this section from the sections created in the Netherlands section.

When a preview is made of this message for a Dutch user it will look like following:

A preview for a French user looks like following:


77/112


5.5.2 Defining the content

Within the sections of a message content must be placed. This content can be simple text, an image, a

form page.

1. To insert images, sections or forms in an existing section, select first this section (a dotted border must

be displayed around the selected section):

2. Next, right click within the selected section. A pop-up menu is displayed.

Three options are available:

Insert section: a new section can be created within an existing section. (This new section does

not copy the properties of the mother section)

Insert Form: creates a form within the selected section. Form tags are added. (For more

information on creating forms please check out section5.4)

Insert image: inserts an image in the selected section. Browse for the location of the image

and select it. When images are selec

Documents

User Manual Selligent Designer en v5.0