OPALE - 10.0 - Utilisation - Formats de fichier/en

Différence entre versions

De MappingDoc
(Page créée avec « Opened in '''OPALE Server''', a Format is a '''Designer''' project which was generated and imported on the production server. A format can be composed of several sequences. »)
 
(18 révisions intermédiaires par le même utilisateur non affichées)
Ligne 11 : Ligne 11 :
  
  
−
The name project is used as the template is designed in '''Designer'''. Once generated in the production server, we refer to it as a format and a sequence number.  
+
The name project is used as the template is designed in '''Designer'''. Once generated in the production server, we refer to it as a format with a sequence number.  
  
  
Ligne 27 : Ligne 27 :
 
These two first parameters are required.   
 
These two first parameters are required.   
  
−
Other parameters can be configured in the Properties window (Tick the box Properties in the Display Menu) :  
+
Other parameters can be configured in the Properties window (Tick the box Properties in the Display Menu):  
  
 
[[File:Projet.PNG|500px|center|sans_cadre]]
 
[[File:Projet.PNG|500px|center|sans_cadre]]
Ligne 35 : Ligne 35 :
 
# Comment: additional information.  
 
# Comment: additional information.  
 
# Shared folder: generation path of the project (also defined in Preferences).  
 
# Shared folder: generation path of the project (also defined in Preferences).  
−
# Mode: corresponds to the data type to format: SPLF (text) or XML.  
+
# Mode: corresponds to the type of data to format: SPLF (text) or XML.  
 
# Code Page: opens a non-Unicode spooled file with an XPS template by specifying the code page of the file in the project properties. This option is only accessible in SPLF mode.  
 
# Code Page: opens a non-Unicode spooled file with an XPS template by specifying the code page of the file in the project properties. This option is only accessible in SPLF mode.  
 
# Designing language: defines the languages in which the template is designed, using a drop-down menu.  
 
# Designing language: defines the languages in which the template is designed, using a drop-down menu.  
Ligne 41 : Ligne 41 :
 
# Page size (standard ISO formats, or customized format) and margins.  
 
# Page size (standard ISO formats, or customized format) and margins.  
 
# Simplex/Duplex project (flip the page on the long or the short edge)  
 
# Simplex/Duplex project (flip the page on the long or the short edge)  
−
# Page break: default setting of the aplication as it processes data one page at a time and adds a page break once the data of a page has been completely processed. If the break is deactivated, the data of the following page will be placed after that of the page processed.
+
# Page break: default setting of the application as it processes data one page at a time and adds a page break once the data of a page has been completely processed. If the break is deactivated, the data of the following page will be placed after that of the page processed.
−
# Position: if the page break is deactivated, this option lets you specify where to place the data of th following page: on the right of the page being currently processed (horizontal position shift) or underneath (vertical shift). This option is only available in XPS.
+
# Position: if the page break is deactivated, this option lets you specify where to place the data of the following page: on the right of the page being currently processed (horizontal position shift) or underneath (vertical shift). This option is only available in XPS.
  
  
Ligne 49 : Ligne 49 :
 
Opened in '''OPALE Server''', a Format is a '''Designer''' project which was generated and imported on the production server. A format can be composed of several sequences.  
 
Opened in '''OPALE Server''', a Format is a '''Designer''' project which was generated and imported on the production server. A format can be composed of several sequences.  
  
−
Chaque séquence est conditionnée pour s’exécuter sur les différentes pages d’un fichier de données (spool ou XML).  
+
Every sequence is conditioned to run on different pages of a data file (spooled file or XML file).  
  
−
Voici un exemple pour mieux comprendre l’intérêt d’avoir plusieurs séquences pour un même projet :  
+
Here is an example to better understand the benefit of having several sequences for one project:  
  
−
Soit une facture de 3 pages :  
+
On an invoice with 3 pages:  
−
* La première page contient l’adresse du destinataire, l’adresse de l’expéditeur ainsi que le début du tableau facture (Type de page 1)   
+
* The first page includes the recipient's address, the sender's address as well as the start of the invoice table (Page type 1)   
−
* La dernière page contient le total de la facture (Type de page 2)   
+
* The last page includes the price to pay (Page type 2)   
−
* Toutes les autres pages contiennent le corps de la facture (Type de page 3)  
+
* All the other pages contain the body of the invoice (Page type 3)  
  
  
−
Traiter ce spool avec un même format est difficile car les mises en forme sont différentes suivant les types de page. Trois formats vont donc être créés, un pour chaque type de page. Ces trois formats porteront le même nom car ils définissent à eux trois '''LE''' modèle de document "Facture" mais ils auront un numéro de séquence différent :  
+
Processing the spooled file with the same format is difficult since formatting can differ depending on the page type. Three formats will then be created, one for each page type. These three formats will have the same name because the three together make '''THE''' document "invoice" template, however they will have different sequence numbers:  
−
* Séquence 00010 s’exécutant sur le type de page 1   
+
* Sequence 00010 runs on page type 1   
−
* Séquence 00020 s’exécutant sur le type de page 2.   
+
* Sequence 00020 runs on page type 2.   
−
* Séquence 00030 s’exécutant sur le type de page 3.  
+
* Sequence 00030 runs on page type 3.  
  
  
−
Lors de l’exécution du format Facture sur un fichier de données, un «''' MERGE '''» de ces trois séquences sera effectué afin de traiter le spool intégralement.  
+
When running the invoice format on a data file, a "'''MERGE'''" of these sequences is carried out to process the spooled file entirely.  
  
  
−
'''Ressources :'''
+
'''Resources:'''
  
−
Pour tracer la liste des formats utilisant une ressource en particulier (une police, un fond de page ou un composant).
+
List all formats using a particular resource (a font, an overlay or a component).
  
−
MAPLNK est le fichier qui relie l’ensemble des ressources et les formats disponibles sur '''OPALE Server'''.
+
MAPLNK is the file which links together all resources and formats available on '''OPALE Server'''.
  
−
Sur IBM i :<code> DSPPFM FILE(MAPLNK)</code>
+
On IBM i:<code> DSPPFM FILE(MAPLNK)</code>

Version actuelle datée du 24 juillet 2019 à 13:43

Autres langues :
English • ‎français

Project/Format:

A Designer project is made up of an overlay (static part of the template) and a data file (variable part or dynamic part of the template). A project has a specific format name and sequence number which make it unique within the production Server.

A project is composed of three files (or five files when it is a double-sided project) :

  • A .mpw file which contains the simplex of the overlay (another one can contain the duplex side of the overlay).
  • A .mpi file which contains the data formatting (template) on the simplex side (another file can possibly contain the data formatting for the duplex side of the project).
  • A .mpp file identifies the project and merges the .mpw and .mpi file(s).
  • Project associations are files with *.MPA extensions


The name project is used as the template is designed in Designer. Once generated in the production server, we refer to it as a format with a sequence number.


Creating a project:

To create a new project, select New, then Project, in the File Menu.

The designing view then displays the project as a blank page with default configuration (portrait, A4, simplex mode).

First, fill in the project properties:

  • Name of the format: identifies the format with 10 characters maximum.
  • Sequence number: identifies the sequence numerically with 5 characters maximum.


These two first parameters are required.

Other parameters can be configured in the Properties window (Tick the box Properties in the Display Menu):

Projet.PNG


  1. Description: user information with 25 characters maximum.
  2. Comment: additional information.
  3. Shared folder: generation path of the project (also defined in Preferences).
  4. Mode: corresponds to the type of data to format: SPLF (text) or XML.
  5. Code Page: opens a non-Unicode spooled file with an XPS template by specifying the code page of the file in the project properties. This option is only accessible in SPLF mode.
  6. Designing language: defines the languages in which the template is designed, using a drop-down menu.
  7. Orientation: Portrait or Landscape, for the simplex and the duplex.
  8. Page size (standard ISO formats, or customized format) and margins.
  9. Simplex/Duplex project (flip the page on the long or the short edge)
  10. Page break: default setting of the application as it processes data one page at a time and adds a page break once the data of a page has been completely processed. If the break is deactivated, the data of the following page will be placed after that of the page processed.
  11. Position: if the page break is deactivated, this option lets you specify where to place the data of the following page: on the right of the page being currently processed (horizontal position shift) or underneath (vertical shift). This option is only available in XPS.


Format:

Opened in OPALE Server, a Format is a Designer project which was generated and imported on the production server. A format can be composed of several sequences.

Every sequence is conditioned to run on different pages of a data file (spooled file or XML file).

Here is an example to better understand the benefit of having several sequences for one project:

On an invoice with 3 pages:

  • The first page includes the recipient's address, the sender's address as well as the start of the invoice table (Page type 1)
  • The last page includes the price to pay (Page type 2)
  • All the other pages contain the body of the invoice (Page type 3)


Processing the spooled file with the same format is difficult since formatting can differ depending on the page type. Three formats will then be created, one for each page type. These three formats will have the same name because the three together make THE document "invoice" template, however they will have different sequence numbers:

  • Sequence 00010 runs on page type 1
  • Sequence 00020 runs on page type 2.
  • Sequence 00030 runs on page type 3.


When running the invoice format on a data file, a "MERGE" of these sequences is carried out to process the spooled file entirely.


Resources:

List all formats using a particular resource (a font, an overlay or a component).

MAPLNK is the file which links together all resources and formats available on OPALE Server.

On IBM i: DSPPFM FILE(MAPLNK)

Récupérée de « https://docs.mappingsuite.com/w/index.php?title=OPALE:10.0:Utilisation:_Formats_de_fichier/en&oldid=19034 »
  • Powered by MediaWiki