Platinum Users Manual ENG[1]

8/2/2019 Platinum Users Manual ENG[1]

1/73

PlatinumVersion 03- 2009

Users Manual


2/73

Platinum 4 Manual rev. 03 2009

2

IndexIndex .................................................................................................................................................................. 2

1. INTRODUCTION ............................................................................................................................................. 7

1.1. Who is this manual aimed at? ................................................................................................................ 7

1.2. The Operators ......................................................................................................................................... 7

1.3. Documents and Nodes ........................................................................................................................... 8

2. Dashboard ..................................................................................................................................................... 9

2.1. The information on the Dashboard: ....................................................................................................... 9

2.1.1. Operator Data Block ........................................................................................................................ 9

2.1.2. Recent Modifications Block ............................................................................................................. 9

2.1.3. To Do Block ...................................................................................................................................... 9

3. ARCHIVES ..................................................................................................................................................... 10

3.1. Multimedia ........................................................................................................................................... 10

3.1.1. Creating a new folder .................................................................................................................... 11

3.1.2. Deleting a folder ............................................................................................................................ 11

3.1.3. Loading a file .................................................................................................................................. 12

3.1.4. Deleting a file ................................................................................................................................. 12

3.2. Files ....................................................................................................................................................... 14

3.2.1. Creating a new folder .................................................................................................................... 14

3.2.3. Deleting a folder ............................................................................................................................ 14

3.2.5. Deleting a file ................................................................................................................................. 15

3.3. Models .................................................................................................................................................. 16

3.3.1. Loading a model in the archive...................................................................................................... 16

3.3.2. Downloading a model from the archive ........................................................................................ 16

3.3.3. Deleting a model from the archive ................................................................................................ 16

3.4. Data ...................................................................................................................................................... 17

3.4.1. Downloading a file from the archive ............................................................................................. 17

3.5. Logs ....................................................................................................................................................... 18

3.5.1. Downloading a .log file from the archive ...................................................................................... 18

4. OPERATORS ................................................................................................................................................. 19

4.1. The Groups ........................................................................................................................................... 20

4.1.1. Creating a group ............................................................................................................................ 20

4.1.2. Modifying a group ......................................................................................................................... 20

4.1.3. Deleting a group ............................................................................................................................ 21

4.1.4. Group Properties ........................................................................................................................... 21


3/73


3

4.2. The Operators ....................................................................................................................................... 21

4.2.1. Creating an Operator ..................................................................................................................... 21

4.2.2. Modifying an Operator .................................................................................................................. 21

4.2.3. Removing an Operator .................................................................................................................. 21

4.2.5. Search functions ............................................................................................................................ 22

5. USERS (Site Visitors) .................................................................................................................................... 23

5.1. Creating a new group ........................................................................................................................... 23

5.2. Modifying a group ................................................................................................................................ 23

5.3. Deleting a group ................................................................................................................................... 24

5.4. Creating a new User ............................................................................................................................. 24

5.5. Modifying a User.................................................................................................................................. 24

5.6. Deleting a User ..................................................................................................................................... 24

5.7. User properties ..................................................................................................................................... 25

Information .............................................................................................................................................. 25

Additional fields ....................................................................................................................................... 25

Profile fields ............................................................................................................................................. 25

5.8. Additional Fields ................................................................................................................................... 25

5.9. Importing and Exporting Users ............................................................................................................. 26

5.9.1. Importing a Users list ..................................................................................................................... 26

5.9.2. Exporting a Users list ..................................................................................................................... 26

5.10. Search functions ................................................................................................................................. 26

6. CONFIGURATION ......................................................................................................................................... 27

6.1. Categories ............................................................................................................................................. 27

6.1.1. Creating a new Category ............................................................................................................... 27

6.1.2. Modifying the name of a Category ................................................................................................ 28

6.1.3. Deleting a Category ....................................................................................................................... 28

6.1.4. Creating a sub-category ................................................................................................................. 28

6.1.5. Modifying the name of a sub-category ......................................................................................... 28

6.1.6. Deleting a sub-category ................................................................................................................. 28

6.2. Additional tables ................................................................................................................................... 29

6.2.1. Creating a new Table ..................................................................................................................... 29

6.2.2. Modifying a Table .......................................................................................................................... 29

6.2.3. Deleting a Table ............................................................................................................................. 29

7. CMS .............................................................................................................................................................. 30

7.1. Organisation ......................................................................................................................................... 31


4/73


4

7.2. Staging and Production ........................................................................................................................ 31

7.3. Preview ................................................................................................................................................. 32

7.4. The Tree ................................................................................................................................................ 32

7.4.1. Creation of a Tree (Root Node) ..................................................................................................... 32

7.4.2. Properties of the Tree.................................................................................................................... 32

7.5. The Nodes ............................................................................................................................................. 33

7.5.1. How to create a Node .................................................................................................................... 33

7.5.2. Saving a Node ................................................................................................................................ 33

7.5.3. Publishing a Node .......................................................................................................................... 33

7.5.4. Moving a Node .............................................................................................................................. 34

7.5.5. Copying a Node .............................................................................................................................. 34

7.5.6. Deleting a Node ............................................................................................................................. 34

7.5.7. Node Properties ............................................................................................................................. 34

7.5.8. Legend for the Nodes .................................................................................................................... 36

7.6.Node types............................................................................................................................................. 37

7.6.1. Site Map ......................................................................................................................................... 37

7.6.2. Link ................................................................................................................................................. 37

7.6.3. Form ............................................................................................................................................... 37

7.6.4. News Node .................................................................................................................................... 40

7.6.5. Page ............................................................................................................................................... 41

7.6.6. Logout ............................................................................................................................................ 41

7.6.7. Password Retrieval ........................................................................................................................ 41

7.6.8. User Profile .................................................................................................................................... 41

7.6.9. Login .............................................................................................................................................. 42

7.6.10. Registration ................................................................................................................................. 42

7.6.12. Feed by Category ......................................................................................................................... 42

7.6.13. Search .......................................................................................................................................... 43

7.6.14. Feed ............................................................................................................................................. 43

7.6.15. Calendar ....................................................................................................................................... 43

7.6.16. Documents container .................................................................................................................. 44

7.7. Node Layout ......................................................................................................................................... 45

7.7.1. Adding a graphics component ....................................................................................................... 46

7.7.2. Moving a graphics component ...................................................................................................... 46

7.7.3. Copying a graphics component ..................................................................................................... 46

7.7.4. Deleting a graphics component ..................................................................................................... 46


5/73


5

7.7.5 Publishing a graphics component ................................................................................................... 46

7.7.6. Common tabs description ............................................................................................................. 46

7.7.7. Graphics Components description and associated content tabs .................................................. 47

7.8. Documents Management ..................................................................................................................... 50

7.8.1. Creating a document ..................................................................................................................... 50

7.8.2. Saving a document ........................................................................................................................ 51

7.8.3. Publishing a document .................................................................................................................. 51

7.8.4. Copying and Moving a Document ................................................................................................. 51

7.8.5. Deleting a Document ..................................................................................................................... 51

7.8.6 Document Properties ..................................................................................................................... 51

7.9. Advanced HTML editor ......................................................................................................................... 54

8. STATISTICS ................................................................................................................................................... 63

9. COMMENTS ................................................................................................................................................. 65

10. CALENDAR.................................................................................................................................................. 66

10.1. Events Search...................................................................................................................................... 66

10.1.1. Search by Name ........................................................................................................................... 66

10.1.2. Search by Date ............................................................................................................................. 66

10.2. Calendar .............................................................................................................................................. 67

10.2.1. Creating a new calendar .............................................................................................................. 67

10.2.2. Deleting a calendar ...................................................................................................................... 67

10.3. Categories ........................................................................................................................................... 68

10.3.1. Creating a new category .............................................................................................................. 68

10.3.2. Deleting a category ...................................................................................................................... 68

10.4. Events Management ........................................................................................................................... 69

10.4.1. Creating a new event ................................................................................................................... 69

10.4.2. Modifying an event ...................................................................................................................... 70

10.4.3. Deleting an event ........................................................................................................................ 70

11. NEWSLETTER.............................................................................................................................................. 71

11.1. Creating a newsletter ......................................................................................................................... 72

11.2. Modifying a newsletter ...................................................................................................................... 72

11.3. Deleting a newsletter ......................................................................................................................... 72

11.4. Creating an e-mail to be sent as a newsletter .................................................................................... 73


6/73


6


7/73


71. INTRODUCTION

1. INTRODUCTION

Platinum 4 is a CMS (content management system) web-based enterprise level platform created to improve

the management of internet/intranet site content and integrate part of the information system of the

company on the web.

The present manual describes the functions and the characteristics of the new Platinum platform, which

has now reached its 4th version.

1.1. Who is this manual aimed at?

The following manual has been conceived, planned and written for the non-technical operator: it contains

all the information and the instructions necessary to be able to work in autonomy, describing every part of

the platform guiding the operator through its use step by step.

1.2. The Operators

With Platinum 4 it is possible to create, modify and publish content very simply from your own website.

The use of the platform is permitted only by authorised users who between themselves can assume

different roles and powers and who are organised into an editorial staff, a hierarchical scale which in order

is:

Administrators with complete control over Platinum 4

Workflow managers who verify the content edited by the operators and publish it

EnabledOperators who edit the content


8/73


81. INTRODUCTION

The correct use of the platform is essential for a correct and satisfactory working experience, before

carrying out any operation in the portal, therefore it is necessary to wait for the completion of the loading

of the page: which is signalled by an icon located on the top right which shows the loading status of the

various sections.

Once the icon has disappeared it is possible to start working. The loading time depends for the most part

on the power of the computer on which one is working and may range from an instant to a few seconds.

1.3. Documents and Nodes

In Platinum 4 the new concept of NODE has been introduced. For the moment it is sufficient for the reader

to know that the node corresponds to the classic site menu page (see chapter 7.5); a node may contain

documents, web objects or other nodes and on occasion may assume different behaviours: e.g. Page node,documents list node, users node. A document is a web object such as a pdf file, an article, a technical sheet

for example or, more complex objects such as links and lists of images.

(Example of a node tree structure)


9/73


92. Dashboard

2. DashboardTo access the administrative area of the portal you need to be one of the operators or possess the

credentials for access, generally supplied by the administrator; once the login has been correctly executed

the Dashboard will be loaded.

The Dashboard presents a summary of the recent activities carried out: the main data of the online

operator and in the To Do window, if one is a Workflow manager, the modifications made by other

operators which must be authorised.

2.1. The information on the Dashboard:

2.1.1. Operator Data Block

In this box the online operators data is shown

Login:The name by which the operator is identified in Platinum 4.

E-Mail: The operators email address Group: The workgroup to which the operator belongs (for details on the groups, their division and

management see the chapter Operators).

2.1.2. Recent Modifications Block

This window shows the chronology of the recent modifications made by the operators. In this way one has

a record of the activities recently carried out.

For every single operation carried out (modifications, inserts, creation, deletions, etc) the date, the time,

the operator and the operation carried out are memorised.

2.1.3. To Do BlockIf you are a workflow manager the To do window shows the list of the activities (waiting to be validated)

carried out by the enabledoperators: operators who create content which in order to be published must

be validated by the workflow manager.

From here it is possible to see which modifications have been carried out by clicking on the ; button; to

validate them simply click on the button; to reject them click on the button.

In the case of a modification carried out by another workflow manager the other managers will receive a

request for a tick on the modification which involves clicking the button to show it has been seen.


10/73


103. ARCHIVES

3. ARCHIVESThe archives section is the place where it is possible to store images, files, models and other data for the

management of the site. Also present is a logs subsection where the log files created by the platform are

collected.

The user interface is the same for every subsection: on the left is the light grey block entitled Folders with

the archives tree structure organised in folders and sub-folders, while on the right, in the larger block, the

content of the selected folder or sub-folder will be displayed

3.1. Multimedia

In this subsection (Multimedia) all the files to be used in the portal contents will be collected. It is possible

to load any of the following formats: jpeg, gif, png, swf, flv, qt, mov, wmp, wmv, wma, rmp, rm, ra.

Clicking on a folder from the tree on the left the content will be displayed in the block on the right (titledFiles) where the previews in miniature will be displayed, the name, the extension and the size in Kb of the

files. The symbol displays the preview of the multimedia objects, while the symbol allows the

downloading of the file directly onto ones own computer.

If the loaded file is not among those accepted (jpeg, gif, png, swf, flv, qt, mov, wmp, wmv, wma, rmp, rm,

ra) it will not be viewed in preview and it will not be usable in the creation of content.

At the root of the tree structure the folder Media is present from which it is possible to create all the sub-

folders necessary. It is good practice, to maintain the files in order, to organise them by subject or by

section of the portal in which they are utilised.


11/73


3.1.1. Creating a new folder

1. Access the Multimedia su2. Click on the folder in which3. Click on the button on4. A window Create folder5. Insert the name of the new

The tree will be updated with the n

ONCE THE FOLDER HAS BEEN

OPPORTUNE TO PLAN THE OR

3.1.2. Deleting a folder

1. Access the Multimediasection

2. Click on the folder which yo3. Click on the button on4. Confirm the deletion opera

AFTER THE REMOVAL OF THE FOLDER THE

bsection from the Archives section

you want to create a new one

he bottom left

ill appear where you can insert the name

folder and click on the Create button.

wly created folder

CREATED IT IS NO LONGER POSSIBLE TO MODIFY THE NAM

GANISATION OF THE FOLDERS BEFORE STARTING THE UPL

subsection from the Archives

u want to eliminate

the bottom left

ion.

REE WILL BE UPDATED AUTOMATICALLY

113. ARCHIVES

E, THEREFORE IT IS

AD OF THE IMAGES.


12/73


WHEN DELETING A FOLDER,

AS ALL THE IMAGES PRESE

3.1.3. Loading a file

1. Access the Multimedia su2. Click on the folder in which3. Click on the button in t4. The window for the loading

Click on the button to choose

If the loaded file is an image, once

settings the system will load the im

the following formats:

small (100x100 pixel) medium (400x300 pixel) large (800x600 pixel)

Additionally it is possible to ma

ticking the little box which corresp

you want to resize the image

maintaining its proportions it is su

the voice In proportion checked.

Once the dimensions have been de

to save, otherwise, click on the

3.1.4. Deleting a file

1. Access the Multimedia su

ALL THE SUB-FOLDERS CONNECTED TO IT WILL AUTOMAT

NT WITHIN AND IT WILL NO LONGER BE POSSIBLE T

bsection in the Archives section

you want to insert images

he Files window

of the file will appear:

hich file to load browsing through the folders of

the loading is completed you can configure th

age with the original dimensions; or alternativ

ually insert the desired size

onds to the Manual voice. If

to a fixed width or height

fficient to leave the box with

cided on, click on the icon

button to cancel the operation.

bsection in the Archives section

123. ARCHIVES

ICALLY BE DELETED, AS WELL

RETRIEVE THIS CONTENT.

your own computer

dimensions; as default

ly you can choose from


13/73


2. Select the folder where the3. Click on the preview of the4. Click on the button loc

As for the folders, for the

ask for the operators confi

IT IS POSSIBLE TO DELETE IM

THEREFORE ADVISED TO TAKE

file is located

ile which you intend to delete

ted in the big window.

iles and any other content which you intend t

mation

AGES WHICH HAVE ALREADY BEEN ASSOCIATED TO CO

GREAT CARE WITH WHICH FILES ARE TO BE DELETED.

133. ARCHIVES

delete, the system will

TENT USERS CAN USE, IT IS


14/73


3.2. Files

In this subsection of the Archives it

multimedia archives the files archiv

block on the left with a light grey c

on the right.

3.2.1. Creating a new folder

1. Access the Files subsectio2. Click on the folder in which3. Click on the button on4. A window Create folder5. Click on Create

PLEASE BE CAREFUL WITH T

NAME, AND IF PRESENT THEY

NO LONGER BE POSSIBLE TO

NEWLY CREATED FOLDER AN

3.2.3. Deleting a folder

1. Access the Files subsectio2. Click on the folder which yo3. Click on the button on4. Confirm the operation of d

After the deletion of the fol

automatically.

is possible to load any type of file to attach insi

es are organised in folders with a tree structure

olour; the content of every folder is however vi

n in the Archives section

you want to create the new sub-folder

he bottom left

ill appear for the insertion of the name of the n

E NAMES GIVEN TO THE FOLDERS, THE SYSTEM DOES NOT

WILL BE SUBSTITUED BY THE DASH -.ONCE THE FOLDER

ODIFY ITS NAME, IT IS ALWAYS POSSIBLE IN THE CASE OF

RECREATE IT.


u want to delete

the bottom left

letion.

der the tree will update

143. ARCHIVES

e web pages. As for the

, visible in the Folders

sible in the Files block

w folder

ALLOW SPACES IN THE

HAS BEEN CREATED IT WILL

AN ERROR, TO DELETE THE


15/73


WHEN DELETING A FOLDER,

AS ALL THE FILES PRESENT A

3.2.4. Adding a file1. Access the Files subsectio2. Click on the folder into whi3. Click on the button in t4. The window will appear for

5. Clicking on the buttonown computer.

6. Once the file to be loaded hto finish.

Each file is represented by an icon

in Kb. It is always possible to downl

3.2.5. Deleting a file

1.

Access the Files subsectio2. Select the folder in which t3. Click on the icon of the file4. Click on the button loc5. Confirm the deletion by clic

ALL THE SUB-FOLDERS CONNECTED TO IT WILL AUTOMATI

D IT WILL NO LONGER BE POSSIBLE TO RETRIEVE THIS CO


h you want to insert the new file

he Files window

the upload of the file:

ou can choose which file to load browsing thro

as been chosen click on the Upload button an

hich identifies its type (doc, pdf, excel etc), wit

ad the selected file clicking on the button.

n in the Archives sectione file is located

hich you want to delete

ted in the Files window

king on the Remove icon of the advisory wind

153. ARCHIVES

CALLY BE DELETED, AS WELL

TENT.

ugh the folders of ones

d wait for the operation

h the name and the size

w.


16/73


163. ARCHIVES

3.3. Models

A model is actually a model of a document, the use of which allows the acceleration and simplification of

content insertion using a predefined layout, a classic example of the use of this tool is the insertion of

product cards, identical in structure and composition but with different content from time to time.

The models archive serves as a container for all the document models to be used in the portal. This archive

is organised in a single folder which contains all the documents. The document models must be in .html or

.htm format.

3.3.1. Loading a model in the archive

1. Access the Models subsection in the Archives section2. Click on the Models folder3. Click on the button4. Click on the button and select the file to be uploaded5.

Once the model has been chosen click on the upload button and wait for completion.

3.3.2. Downloading a model from the archive

1. Access the Models subsection in the Archives section.2. Click on the Models folder3. Click on the button corresponding to the document you want to download

3.3.3. Deleting a model from the archive

1. Access the Models subsection in the Archives section.2. Click on the Models folder and select the document to be deleted3. Click on the button and confirm the removal clicking on the Remove button


17/73


173. ARCHIVES

3.4. Data

This archive gathers the data generated by the portal by using the forms (specifically created modules for

the gathering of data), it has, therefore, a consultation function and verification function that information

gathering is functioning correctly.

During the creation of the forms it is actually possible to specify the name of the file in which to save the

collected data, this data will be automatically memorised by the system in this folder.

The files can be downloaded and read with the software Microsoft Excel or similar products.

In this archive it is not possible to create sub-folders in that these will be generated automatically by

Platinum. The files present may only be downloaded.

3.4.1. Downloading a file from the archive1. Access the Data subsection in the Archives section.2. Click on the desired folder3. Click on the button associated with the file you want to download

Depending on the settings of browser you are using, it will be possible to save and/or open the file

in order to view it.


18/73


183. ARCHIVES

3.5. Logs

The logs section, like the data section, also has predominantly the function of consultation and verification

of the correct functioning of the portal.

In this section the log files created by the system are gathered, regarding access to the portal and the

searches carried out on the portals internal search engine.

The structure of the archive is as always organised by a tree of folders; the operator cannot however

modify this structure or create log files to upload to the various folders, but can only download the existing

files; as in the other sections of the archive the files are shown by icons with the associated name of the file

and the size in Kb.

3.5.1. Downloading a .log file from the archive

1. Access the Logs subsection in the Archives section.2. Click on the desired folder in which the .log file you want to download is located3. Click on the button associated with the file you want to download

Depending on the settings of the browser you are using it will be possible to save and/or open the file in

order to view it.


19/73


194. OPERATORS

4. OPERATORSThe operators are users assigned to the creation and management of portal content. In Platinum the

concept of an editing staff is present, or rather a hierarchical ladder which guarantees the complete control

of the information published. At the apex of this hierarchy the administrators group of operators is found,

who have total control of the platform, under the administrators are the workflow managers, who have

the task of verifying and validating the content created by junior workers: the enabledoperators, who, for

each individual node are authorised to create content.

The Operators section is used for the management (creation, modification and removal) of the operators

and groups of operators. For each operator you can handle the permissions and privileges (reading, writing,

modifying and accesses) independently of the group they are part of.

If the permissions for every single operator are not defined, they will be inherited from the group to which

they belong; it is also possible to assign permissions and privileges to the groups:

- Administrators:They possess the right to write on all the portal content, and they have permission to publish it.

They can in this way create, modify and delete any object on the portal. They can also designate

which operators will be workflow managers for each node of the structure and which other

operators will be enabled or not for modifications.

- Workflow Managers:They have the task of managing the nodes assigned to them and they possess all the rights of

writing and publishing. They also have the responsibility of validating any document modified,created or deleted by the other qualified operators and they are effectively responsible for what

will be displayed on the site. In addition they have the possibility to enable the operators to write in

the nodes for which they are responsible.

- Enabled Operators:These are the operators assigned by the administrators or the workflow managers to the creation,

modification and cancellation of content within a node, but who do not have the possibility to

publish the content.

Every one of their modifications is reported to the workflow managers of the nodes they have

worked on, and these are found in the TO DO window of the DASHBOARD section along with the


20/73


204. OPERATORS

complete list of changes carried out by the operators, with the possibility of validating the work

done and publishing what results.

The window for managing Operators is subdivided into three blocks: the block on the left Groups,

shows the list of all the operators groups present; the central block Operators, shows the list of the

operators associated with the selected group (clicking on the various group names the content of thewindow will change); the block on the right Operator properties permits the viewing of the properties of

the selected operators. If you have the right to do so, from the right-hand block you can intervene and

modify the settings.

4.1. The Groups

4.1.1. Creating a group

1. Access the Operators section2. Click on the button in the Groups block on the left3. In the window which appears it will be possible to define all the relative properties for the new

group

4. Once you have completed management of the properties click on the button to save, or on thebutton to cancel.

4.1.2. Modifying a group

1. Access the Operators section2. Click on the button corresponding to the group which you intend to modify3. The window of the properties relative to the selected group will appear, in which, through the

various tabs, it is possible to modify role, permissions and characteristics

4. Once you have completed management of the properties click on the button to save, or on thebutton to cancel.


21/73


214. OPERATORS

4.1.3. Deleting a group

1. Access the Operators section2. Click on the group you want to delete3. Click on the button in the Groups block on the left4. Confirm the operation.

4.1.4. Group Properties

General Data

Name: The name that you want to give the group is inserted here

Additional Data

For the creation and definition of additional specific fields

Access to the CMS properties

Access Control: an option to give the power to the group operators

to give other operators access or not to the nodesEnabled Operators: an option to give the group members the

possibility to decide who will be the enabled operators for the

management of the nodes

Workflow Managers: an option to give the members of the group the possibility to decide who will be the

node workflow managers

4.2. The Operators

4.2.1. Creating an Operator

1. Access the Operators section2. Click on the group to which you want to add an operator3. Click on the button in the central block Operators4. In the window which opens it will be possible to configure all the properties of the operator,

independently of the group to which he belongs. If no modifications are made, the operator will

have the properties of the group to which he belongs.

5. Once finished with the properties management click on the button to save, or on thebutton to cancel.

4.2.2. Modifying an Operator

1. Access the Operators section2. Click on the group to which the operator belongs3. Click on the name of the operator4. In the block on the right Operator properties it is possible to modify the operators properties5. Once the modifications have been completed to save click on the button.

4.2.3. Removing an Operator

1. Access the Operators section2. Click on the group to which the operator belongs3. Click on the name of the operator4. Click on the button in the central Operators block5. Confirm the removal.


22/73


224. OPERATORS

4.2.4. Operator properties

General Data

Username: The access name to the portal, inserted at the

creation of the operator after which it is no longer possible to

change it.

Password: the secret word for the identification of the operator

Name and Surname: Name and surname of the operator

Email: the operators email

Group: the operators group

State: Set on enabled allows the operator to carry out the login, if

it is set on not enabled it will not allow the operator to access the

contents management.

Language: The language of the back-end.

Type of Editor: From here it is possible to change the HTML editor type used by the operator..

Applications

Applications: A list of the applications of Platinum, those checked are those usable by the operator.

Enabled Nodes: From here it is possible to set the list of nodes usable by the operator, if the node type is

not enabled it will not be possible for the operator to use it on the creation of content.

EnabledGraphics components and documents: As for the nodes, the graphics components and the

documents can also be enabled.

4.2.5. Search functions

If the portal contains many operators, it may be difficult to identify a specific one; for this reason, Platinum

possesses an integrated function to search for operators.

If you want to search for an operator, insert the name in the appropriate text box situated in the upper part

of the Operators window and click on the button if you want to search for the operator in the

selected group, or on the button if you want to search for the operator among all the operators

present.


23/73


235. USERS (Site Visitors)

5. USERS (Site Visitors)With Platinum 4 the areas of the portal with restricted access can be managed; in the users section it is

possible to manage and to administer the users who can access these areas.

The users section is divided into three main blocks. The left-hand window presents the portals groups list,the central window shows the list of users contained in the selected group, whereas, once a user has been

selected, the window on the right describes all his/her properties, with the relative credentials and rights of

access.

5.1. Creating a new group

1. Access the Users section2. Click on the button in the left-hand groups block3. In the window which appears insert the name you want to give the new group4. Click on Advanced data if you want to insert additional information (see inserting additional

fields)5. Click on the button to save or on the button to cancel.

5.2. Modifying a group

1. Access the Users section2. Click on the button corresponding to the role you intend to modify3. The window used for the creation of the group will appear; then modify the properties which

require changing

4. Click on the button to save or on the button to cancel.


24/73


5.3. Deleting a group

1. Access the Users section2. Click on the group which yo3. Click on the button in t4. Confirm the operation of el

WHEN A GROUP IS ELIMINAT

5.4. Creating a new User

1. Access the Users section2. Click on the button in t3. In the window which app

Information, Advanced d

4. Click on the button to5.5. Modifying a User

1. Access the Users section2. Click on the group in which3. Click on the button cor4. The window used for the c

you want to change

5. Click on the button to

5.6. Deleting a User

1. Access the Users section2. Click on the role where the3. Click on the user you want4. Click on the button in t

u intend to eliminate

e left hand Groups block

imination.

D ALL THE USERS WHO BELONG TO IT WILL ALSO BE ELIMI

he central Users block

ears insert the users data and the relative

ata and Profile (also see inserting additional

ave or on the to cancel.

the user you intend to modify is present

esponding to the user you intend to modify

reation of the user will appear and thus you ca

ave or on the button to cancel.

user to be deleted is present

o delete

he central Users block and confirm the deleti


NATED!

properties via the tabs

ields)

n modify the properties

n.


25/73



5.7. User properties

General Data

Login: The access name for the portal, inserted during creation

of the user and after which it will no longer be possible to

change.

Password: the secret word for the identification of the user

Name and surname: User name and surname

Email: The users email address

State:

Enabled the active user on the site

Not Enabled the user to whom access to the site has been

blocked

In Waiting is the status (set by Platinum) for those users who,

have carried out registration, but have not yet confirmed it via

emailGroups Set the group to which the user belongs.

Information

In this window two important pieces of user data are displayed, the last access and the last time the user

changed the password.

Additional fields

In this window additional fields relative to the user will be displayed.

Profile fields

In this window the additional user profile fields will be displayed

5.8. Additional Fields

For every group and user it is possible to specify some additional fields. To insert these new fields click on

the button in the blue Users management bar and proceed to the insertion.

Advanced fields: these are fields used to define useful properties in the phase of integration of Platinum

with other external systems (management etc)

Profile Fields: These are additional fields which the user may be requested to compile during registration to

the site, as for example the address, the town of residence etc.

Group Fields: These have the same function as the additional fields only that they are applied to the groups

instead of to the users.


26/73


5.9. Importing and Exporti

When you have many users to inser

function for importing or exporting

on the role affiliation. Platinum imp

To find out the charact

first add a couple of us

.csv file with the necess

users you want to load

5.9.1. Importing a Users list

1. Access the Users section2. Click on the button in t3. In the window which appea4. A window will open where5. Select from the drop-down6. If you want to force the i

import

7. Click on the upload butto

5.9.2. Exporting a Users list

1. Access the Users section2. Click on the button in t3. In the window which appe

group you intend to export

4. Click on the button pre5. A window will appear wher

5.10. Search functions

The system possesses an integrate

insert the name in the appropriate

the button if you want to sear

you want to search for the user in a

g Users

t or in the eventuality you want to make a back

the users list is present with the relative propert

orts and exports users lists in csv format (comm

ristics with which the .csv file must be created

rs manually to Platinum and carry out the exp

ry characteristics to be read correctly, to which

o Platinum.

he blue Users Management bar

rs click on the button

ou can search for the file to be loaded

menu Group the group in which you want to sporting of the file based on the settings give

n and wait for completion of the loading.

he blue Users Management bar

ars select in the drop-down menu Group the

sent in the same window

you can select the folder in which you want to

function to search for users, if you want to s

text box located in the upper part of the Use

ch for the user in the currently selected group,

ll the existing groups.


p of the users, the

ies, subdivided based

separated values).

for the import of users,

rt. You will then have a

you just have to add the

ave the users listn check the box Force

list of the users of the

save the file.

arch for a specific user,

s window and click on

or on the button if


27/73


276. CONFIGURATION

6. CONFIGURATIONIn this section you can create subject types (categories) and manually load data from external sources

(Additional tables).

6.1. Categories

In this sub-section it is possible to create categories to tag or rather categorize the documents into

groups. This operation allows the viewing of the published documents according to certain parameters

(categories). For example 6 news type documents can be viewed in the front-end of the site with the

following criteria: two documents from the news category, two documents from the Events category

and two documents from the highlights category.

The section is subdivided into three hierarchical blocks: the Roots-list block, the Categories list block

and the Sub-categories list block. The roots list block is generated by Platinum which displays the list of

the homes.

6.1.1. Creating a new Category

1. Access the Categories subsection of the Configuration section2. Click on the root in which you want to add a category3. Click on the button in the central Categories list block4. Insert the new category name via the window which will appear


28/73


5. Confirm by clicking on the 6.1.2. Modifying the name of a C

1. Access the Categories sub2. Click on the root to which t3.

Click on the button cor4. Insert the new name in the

5. Confirm by clicking on the

6.1.3. Deleting a Category

1. Access the Categories sub2. Click on the root to which t3. Click on the category you w4. Click on the button in t

DELETING A CATEGORY AUTO

6.1.4. Creating a sub-category

1. Access the Categories sub2. Click on the root in which y3. Click on the category in whi4. Click on the button in t5. Insert the new name of the6. Confirm by clicking on the

6.1.5. Modifying the name of a s

1. Access the Categories sub2. Click on the root to which t3. Click on the category to whi4. Click on the button cor5. Insert the new name in the6. Click on the OK button to

6.1.6. Deleting a sub-category

1. Access the Categories sub2. Click on the root to which t3. Click on the category to whi4. Click on the sub-category y5. Click on the button of t

In the CMS section it will be possibl

Create button, to cancel the operation click on

ategory

section of the Configuration section

e category belongs

esponding to the category you want to modifywindow which appears

Create button, to cancel the operation click on


e category belongs

ant to delete

he central Categories list block and confirm th

MATICALLY ELIMINATES ALL THE SUB-CATEGORIES CONNE


u want to add a sub-category

ch you want to add the sub-category

he right-hand Sub-categories list block

sub-category in the windowCreate button, to cancel the operation click on

b-category


e sub-category belongs

ch the sub-category belongs

esponding to the sub-category which you want

window which appears

confirm or the Cancel button to cancel the op


e sub-category belongs

ch the sub-category belongs

u want to eliminate

he right-hand Sub-categories list block and co

to tag a document by selecting one or more ca

286. CONFIGURATION

the Cancel button.

the Cancel button.

e deletion.

CTED TO IT

the Cancel button.

o modify.

eration.ition

firm the elimination.

egories.


29/73


296. CONFIGURATION

6.2. Additional tables

In this sub-section it is possible to upload tables of data from csv files. Once the table has been created in

csv format using appropriate programmes (eg. Excel) it is possible to import them in order to then reuse

them in the portal documents. The section presents two blocks: in the Tables block the List of the Tables

already uploaded is present, while in the right-hand block the content of the selected table will appear.

6.2.1. Creating a new Table

1. Access the Additional tables subsection of the Configuration section2. Click on the button3. In the window New group which appears insert the name of the new table4. Click on the button to upload the .csv file from your own computer5. Click on the button to save or on the button to cancel the operation.

6.2.2. Modifying a Table

1. Access the Additional tables subsection of the Configuration section2. Click on the button corresponding to the table which you want to modify3. In the Table Detail window which will appear, insert the new name of the table or leave the

existing one

4. Click on the button to upload the new .csv file from your own computer5. Click on the button to save or on the button to cancel the operation.

6.2.3. Deleting a Table

1. Access the Additional tables subsection of the Configuration section2.

Click on the name of the table present in the List which you want to delete

3. Click on the button and confirm the operation of deletion.


30/73


307. CMS

7. CMSThe CMS section is dedicated to content managment, from here it is possible to create, modify and cancel

every piece of portal content. The content is organised in nodes or folders, which correspond to the portal

sections. Such nodes can contain other sub-nodes, documents and graphics components.

The navigable tree structure renders content management extremely fast and immediate.

The users who have access to this section are identified as operators subdivided into 3 different levels

based on their authorisation.

Administrator The administrator is the chief manager of the portal, his/her job is tomanage the operators appointed to the creation and publication of content,

identifying the workflow managers. He/She possesses the right to write and

publish all portal content.

Workflow Manager The Workflow manager, appointed by the administrator, is the manager of

the contents in the node which he is responsible for. He is the only operator

who can publish the modifications made. He can enable the other operators

to modify the content of the nodes which he manages. He has the right to

write and publish within his own nodes.

Enabled Operator The enabled operator is the operator assigned by the Workflow manager to

the modification of content inside a node; every modification and deletion

carried out has to be approved by the workflow mangers in order to be

published. He has the right to write within the node.


31/73


317. CMS

7.1. Organisation

Inside the CMS section you find the blue Contents Management bar, on the left the light grey Nodes

creation block, in the centre the site structure, which summarises via a navigable tree all the nodes in the

portal which have already been created.

In the right-hand block you find the Properties of the Page through which you can set all the properties of

the node, this will be explained in detail later. From the same block it is also possible to insert the node

contents, such as graphics components and documents

(example of root node with sub-nodes)

7.2. Staging and Production

In Platinum 4 the mode STAGING has been introduced; this mode allows theoperator to work on the creation of nodes and content which will only be

visible in Preview in the back-end of Platinum but will not be published or

visible on the site (front-end) until the moment the operator makes the modification public by publishing it.

Through the drop-down menu Mode it is possible to go from Staging to Production with a click and

thereby always keep the state of progress of the work under monitoring. In a reality structured by editing

the staging mode allows the managers to view the content created by the operators before authorising itspublication.


32/73


IN THE PRODUCTION MODE

THE STAGING MODE

7.3. Preview

To view the content inserted in the

the button which is found on t

bar on the bottom right.

7.4. The Tree

Below the operation for the creatio

carried out when the structure has

7.4.1. Creation of a Tree (RootTo start the insertion of the cont

clicking on the drop-down menu

the name of the new tree and the g

At this point it is also possible to c

option the new tree will have the st

One of the classic uses of this functi

sites.

The root node correspon

enter a portal using the

7.4.2. Properties of the Tree

Once the new tree has been creat

button will appear on the bottom r

the page, the description, specify th

links are planned.

IT IS NOT POSSIBLE TO ADD OR MODIFY CONTENT.TO DO

staging mode but not yet published, first you n

he bottom right and then click on the butt

n of a new structure (tree) is explained; these op

already been pre-configured (the more common

ode)nts you first need to create a new tree,

ree and selecting New tree. Then insert

raphics features (layout) of the node.

oose to copy an entire tree; selecting this

ructure and contents of the copied tree.

on is in the management of multi-language

ds to the more familiar HOME, the page which y

rl without specifying the page, for example ww

ed, clicking on the root node the definition of

ight (see fig. 7). Among the properties it is possi

e language, the header and the footer text and

327. CMS

THIS YOU HAVE TO WORK IN

ed to save it clicking on

n present on the same

erations are not to be

situation).

u reach when you

.omnys.it

the tree properties

ble to insert the Title of

pecify where additional


33/73


337. CMS

7.5. The Nodes

In Platinum 4 various types of Node are present, as explained further on. In the toolbar on the left Nodes

creation is the list of the nodes to be created and from the right-hand Page Properties block it is possible

to manage all the characteristics of the created node, from the properties to the content (see fig. 7)

7.5.1. How to create a Node

The simple procedure of node creation is the same for all types, once the node which you want to create

has been identified from the Nodes Creation toolbar just drag it (drag and drop) on the tree in the

desired position until a red line appears which indicates the location, as can be seen in the following figure

Once the left key of the mouse has been released a window will appear

where the name of the node and the desired layout (graphics aspect)

can be inserted. Leaving the option Inherited the node will inherit

the layout from the parent node connected to it on an upper level, in

our example the parent node is HOME.

If your installation of Platinum has the staging mode activated, any operation you carry out on the content

will have an effect only in the staging area and not in that of production;

therefore the node just created will be orange in colour. The colour orange

indicates that the created node is not present in published or a

modification has been made to its properties or to its content since the last

time that it was sent to be published. The green colour is used to indicate that the node and the content

present in Production are aligned and updated to those present in Staging where you are working.

7.5.2. Saving a Node

To save the node you have just created and in general to save any content which has just been inserted you

need to click on the button.

7.5.3. Publishing a Node

The publication procedure for the node which will be explained here is the same for the publication of all

the portal content. Once the content to be published has been selected simply click on the button on

the bottom right, once this has been done the content will automatically change from an orange to green


34/73


colour. To publish entire portions

the bottom right. On clicking, a wi

voice Sub-nodes allows publicati

where you find yourself.

The content to be publis

in green has already bee

7.5.4. Moving a Node

Drag the chosen node to the new

symbol next to the parent nod

which appears select the Move no

7.5.5. Copying a Node

Drag the chosen node in the new pmove yourself with the cursor on th

node and wait for the automatic op

window which appears select the

operation click on the cancel butt

7.5.6. Deleting a Node

To delete a node and in general all

area with the wastebasket symbol

action. If your installation of Platinu

will have an effect only on the stagibeen confirmed the object will bec

deleted but whose deletion has not

contents.

To make the deletio

THE PUBLICATION OF DELETI

7.5.7. Node Properties

The properties of the page block

and in general of all the inserted c

voices: General parameters, Con

to the node, Workflow Managers

f the content tree with just one click simply cli

ndow will appear which will ask you the actio

n to be extended to all the sub-nodes present

ed must be orange in colour, as explained in th

published.

osition. To access any sub-nodes, move yoursel

e and wait for the automatic opening of the s

de button. To annul the operation click on the

sition. To access any sub-nodes,e symbol next to the parent

ening of the sub-tree. In the

opy node button. To annul the

on.

he portal contents just drag the element to be d

n the bottom left. A window will ask you to con

m has the staging activated, any operation you

ng area and not in that of production; thereforeme red in colour. The red colour indicates the it

yet been published. In this case it is still possibl

n definitive click on the button on the bott

N WILL MAKE THE CONTENTS IRRETRIEVABLE.

on the right allows the configuration of all the

ntent. The block is composed of a drop-down

tent configuration, Meta data for search engi

and Info and Versions..

347. CMS

k on the button on

to be performed. The

starting from the node

previous point; content

f with the cursor on the

ub-tree. In the window

cancel button

eleted in the dark grey

irm the requested

erform on the content

once the operation hasems which have been

to retrieve the

m right.

properties of the node

enu with the following

nes, Control of access


35/73


357. CMS

General Parameters

Name of the node on-line: In this voice the name you have chosen for

the node is inserted.

Name of the URL: This voice, which is automatically compiled by

Platinum, displays the name which will appear in the address bar when

you are navigating in a given node. It is possible to modify it, please

note that the words must be separated by a -.

Page title: You can insert the title of the page here.

Graphics engine: You can select the graphics engine to apply to the

node here.

On-Line: The on-line function allows you to decide if the published

content is accessible or not. It is possible to set an interval of dates for

the publication. This function is typically used for the publication of

events which have a precise duration.

Visible in the menu: With this option it is possible to make the nodevisible or invisible in the navigation menu.

Images: These are the additional images which can be added to the

content; ask your administrator how to use them.

Content Configuration

Content of the page: Here you can configure the predefined content of the node, according to the type of

node created, this could be a document, a link etc. The different types of node will be dealt with later in

this manual.

Jump to the first sub-node: Ticking this box the content present in the first existing sub-node will be

displayed.

Meta Data for search engines

META Description: This is the description of the site, usually used in

operations of web marketing for an efficient indexing of the site on the

part of search engines.

META Keywords: These are the key words of the site, usually used in

operations of web marketing for an efficient indexing of the site on the part of search engines.

Control of access to the Node

This tab allows you to configure the access rights for users to the individual nodes. 4 options exist from

which to choose from:

Inherited: the rights are inherited from the parent node

Public: Access to the node is open to anybody

Every logged-in user: The node is accessible to all the users who have

logged in to the portal.

Enabled Groups: Only the users belonging to the group or groups selected will be able to view the content

of the node.

Enable HTTPS: If you want the content of the node to be viewed by the user in secure mode (SSL), it is

possible to impose that this content will be supplied via HTTPS, if a cryptation certificate has been installed

in the server. From the node properties window just select the voice Enable HTTPS and that content will besupplied in encrypted form.


36/73


367. CMS

Operators qualified to modify the node

As suggested by the title, in this section the operators who have the rights to be able to elaborate the

contents inside the node are indicated; these are selected by the portal administrators.

It is possible to spread the authorisation to all the sub-nodes of the node by enabling Propagate to the

sub-nodes

Info and Versions

In this voice, all the previous versions of the node are displayed

chronologically. Clicking on the button a window will appear

where the properties of the node in the previous version are displayed,

to restore a previous version of the node click on the relevant key.

Node Layout

The description of this voice is explained in detail in chapter 7.7.

7.5.8. Legend for the Nodes

A node may assume different status, here is a list with descriptions:

Green node: node published on-line Transparent node: node off-line Orange node: node modified, awaiting approval Red node: node deleted, awaiting approval Nodo with a lock: node with restricted access

Node with little ghost: node not visible in the on-line navigation menu


37/73


377. CMS

7.6.Node types

In Platinum 4 many types of node exist, each one specifically designed for a particular function, what has

been explained up to now regarding node properties stands for every type of node except for the voice

Contents configuration which varies from type to type. The following explanation therefore refers only to

the configuration of the contents.

The node types are subdivided into 4 categories, Standard, Users, Advanced and Personalised, as you can

see in the nodes toolbar "Nodes creation".

7.6.1. Site Map

The standard node Site Map is a node designed to automatically display the map of the site, once

created the node is already functioning without any additional configuration, it is possible to specify

the level of depth of the tree displayed via the voice Contents Configuration.

7.6.2. Link

With this standard node you can create a link to other content on the portal or to an externalsource on the internet.

To create a link to other content in the portal select the voice Internal address, a pop-up will appear

where you can navigate the tree of portal contents, once you have found the desired content select it by

doing a double click with the left button on the mouse.

To insert an external link just write the address in the empty space, for example: http://www.omnys.com/

7.6.3. Form

A form allows you to present to the user, the site navigator, a series of fields which can be compiled

by the user himself and then sent to the site administrator. The most common use of this node is

the information request, the registration request or the contact us.

The Form node provided by Platinum 4 allows the gathering of data on-line which can be sent to a

destination email address, normally an addressee within the company, who can then view it. In addition it

also allows you to gather data on file, in CSV format(comma separated values), downloadable from the

Archives (in Data).

Before moving on to the description of the procedure for inserting and configuring a form it is necessary to

draw attention to the following concepts:

The form field names The sequencing of the form fields The use of webpage writing programmes

Field names

Every field on the form has two names:

1. The title of the field: which appears on-line - Title 2. A single identifying voice name: Name - (it does not appear on-line, but is reported in the mails

and in the .CSV files)

In this way the site administrator who receives the mail will see the single identifying voice of each field

with the associated text inserted by the user in that particular field. For example:

Name = Gino


38/73


387. CMS

Surname = Rossi

Street = Via Roma, 35

Telephone = [empty.

The first word (Name, Surname, ...) is the name of the field which the site administrator has chosen, while

the following text, after the "equals" symbol, is the text inserted by the user. It is essential to underline thatthe field names cannot contain spaces or special characters such as the symbols (%, &, $, ...) or accented

letters. Additionally they cannot start with a number, or contain the minus - character, or the underscore

_ character

Incorrect examples: 1Name, Name%, Name Surname, Name-Surname,Name_Surname

Correct examples: Name, Street, Name1, Name2, NameSurname

Sequencing of the fields

Because of a limit in browser technology (Internet Explorer, Mozilla, Firefox, ), the values collected by the

form do not keep the order in which they are found in the HTML code and therefore the email sent to thesite administrator can contain the list of fields in a different order every time.

To make up for this limit, it is possible to place a numerical prefix in the form _nn_ in front of the field

names, where nn must be a double digit number. The sending system, identifying these prefixes, will

sequence the fields according to the values nn in increasing order.

For example, if you want to construct a form which collects name, surname and email and will deliver them

in the same order, field names can be assigned as follows: _01_Name, _02_Surname, _03_Email.

The numeration does not necessarily have to be sequential and the presence of duplicate numbers does

not create any problems. The numerical prefixes will be removed by the delivery system and therefore willnot appear in the email or in the .CSV file of collected data.

The use of WEB pages programmes

You can use programmes for the realisation of Web pages (for example FrontPage, Dreamweaver, ) to

generate the forms. It is important that the HTML code produced is cleaned of its tags , ,

, , all the block. Additionally the tags, (if inserted by the programme)

must be eliminated which are then restored correctly by the module itself.

The possibility of inserting JavaScript code into the tag is allowed and

to carry out specific checks on the fields of the form. Once copied and stripped of the HTMLcode, it is possible to refine the form via the Form node editor itself.

Creation of a Form

The Form node has a HTML editor integrated in it for designing the form in a visual way. To proceed with

the personalisation of the form, once the new node has been inserted move to the voice Contents

configuration in the properties, from here you can configure every desired detail of the form.

Data page

The html code which designs the form is inserted here, if you already possess the code it is sufficient to

insert it in the empty space or the Form can be created using the editor, which also allows the setting of

various parameters on the fields for the automatic checking of the validity of the same. Examples of

parameters are the maximum length, the obligations, if it must contain numbers, etc.


39/73


397. CMS

As well as these, the following parameters are present:

Name This is the name of the field. It must not contain spaces and it is the name with which

the data inserted by the user in that field will be labelled.

Title This is a brief description which is used as a label of the field for error messages.

Required Indicates that the field must be completed by the user. If it is a field of text at least onecharacter must be introduced, if it is a checkbox it must be checked, if it is a series of

radio-buttons at least one must be checked. For a select, a different voice from the first

must be selected, as the first is considered a false voice or default.

Email Type Usable only for text fields, indicates that the content must be a valid email address

which will be formally verified.

Numerical Type Indicates that the content of the field must be a numerical value (even with a comma).

In the module a button of the type "submit" must always be present which the user will use to confirm the

sending of the data. The button is inserted using the appropriate button in the editor toolbar.

Invalid data message (Obligatory)

Here you specify the error message which appears when a portal user tries to submit the form but has not

compiled all the fields correctly.

Addressees E-mail (Obligatory)

The email of the person in charge of receiving the information/requests compiled in the form goes here.

Email subject (Obligatory)

The subject of the mail which the system will send to the recipient specified in the previous voice goes here

Name of the CSV file

In this field you can specify the name of the CSV file where the data compiled by the users will be

memorised, leaving the field empty will result in no CSV file being created.

Note: order the names of the fields which appear in the form if you are using a .CSV file in which to

memorise the collected data.

Thank you page Closing text (Obligatory)

Every time a user compiles the form correctly the system will direct him to a portal Thank you page, in this

field you can design this page with the html editor or, if you already have the html code, insert it in theempty space.

Specific Recipient

In some cases you can give the user the possibility to choose the recipient of the form. In the classic

example of feedback for a tourist resort, the addressee could be the management or entertainment

rather than catering. In these cases compile the list of specific addressees inserting mail and identifying

label. To insert the list in the form use the signpost i{list}. The addressee, inserted in the page data, will

receive the mail addressed to specific addressees in copy.


40/73


407. CMS

Receipt sent to the users email

The Form node also foresees the possibility of setting a confirmation of receipt email of the form on the

part of the portal, once this option has been activated you can specify the subject of the email which the

user will receive and also design the mail content the html editor.

Once the html editor has been opened you can use the signpost function to create a mail with genericcontent which will however be completed by the system with the user data who has compiled the form.

Below is an example of the generic mail which will be completed correctly by the system with the data of

user Mario Rossi.

Dear{user.name} {user.surname}

we thank you for having contacted us, we will see to it that you receive as prompt a reply as possible.

It will automatically become

DearMario Rossi

we thank you for having contacted us, we will see to it that you receive as prompt a reply as possible

Error Page

Here you can specify the text which will appear to the portal user in the eventuality the system does not

successfully conclude the sending of the data to the addressee, for example the text could suggest to the

user to retry the insertion and in the case of a negative outcome suggest an email or a telephone number

where the defective functioning can be reported

7.6.4. News Node

The node news, as easily understood from the name, is a node specially programmed for the

publication of many news articles in the same page. Once the documents have been inserted insidethe node, as we will explain later on in the section of the manual devoted to the creation of documents, it is

possible to choose how these documents will be viewed by the end user.

The number of news items per page:

From here you can set how many news stories will be displayed in the page, if there are more stories than

foreseen in the page, a menu for navigating between the pages will be automatically created.

Show the news from the sub-nodes:

Selecting this option the documents present inside the node and inside the sub-nodes will be displayed.

Show the description:

When a new document is created it is possible to insert a description of the content in a special field. If this

field is compiled and if this function is selected, the node will show the title of the document as well as the

description associated with it.

Show the date:

This voice, if selected, will make the publication date of an individual document visible to the portal users.

Show the icon:

As for the description, every document can be matched to an icon, if this icon is present in the document

and if this function is selected, the chosen icon will be displayed beside the document title.


41/73


417. CMS

Order by:

This function allows you to decide the order in which the news must be shown, you can order by

publication date, by position inside the node, or by Title, i.e. alphabetical order.

7.6.5. Page

Use the page node when you want to create a html page, to set the content go to the ContentsManagement window and use the advanced html editor for the creation, it is possible to directly

insert the html code in the Page content space. If you want the content of the first sub-node to be

displayed just select the voice jump to the first sub-node.

For a detailed explanation on the use of the HTML editor please refer to chapter 7.9.

7.6.6. Logout

With the logout node you set the message which will appear to the user once logout (exit) from a reserved

area has been carried out.

You can create the message with the advanced HTML editor, creating an exit web page for the successfuldisconnection.

7.6.7. Password Retrieval

With this node you can create a module for the sending of a password forgotten by the user who

then requests it.

In the Contents configuration the following fields are present:

Data request page: to construct the page (through theeditor) in which the persons user name will be requested

in order to be able to send via email his/her ownpassword. The system will send the email to the address

chosen by the user during registration.

Final Page: page for the message reporting the successfulsending of the email containing the access password; this

page can also be modified with the help of the editor.

Error message: to manage the situation when it is not possible to send the email with thepassword; this field can also be modified as desired via the platform editor

Subject of e-mail : insert in this field the text which will appear in the email subject bar sent by thesystem

Text email: field which can be structured with the editor, to create the text which will appear in thee-mail

7.6.8. User Profile

With this node a page is created, available to the users, for updating their own profile data, set:

Data modification page: where you create the webpage for the insertion and sending of new data

Final message: where you create the page confirmingthat the data has been sent


42/73


427. CMS

7.6.9. Login

The login node is used to realise the pages through which authenticated users access the website;

you can, as for the other nodes, use the advanced HTML editor.

Login page: Page for