Parameters

Description of the function:

Set generation parameters

Steps:

1. Click on the  button

2. Set the parameters and click on ok.

Standard:

• Tree menu width: allows to modify the tree menu width of the generated site 
   

• Use frame to present item paths in the item hierarchy: define if an item path (in the item hierarchy) will be generated at the top of pages as show in the picture below.
  Notes:
  - the item path is generated in a separated frame, so if user scroll down, the item path will remain at the top
  - the change of this parameter only apply to the new created items and not the existing one
  
   

• Item path frame size in %: The default path frame high can also be configured (can be set to 0, if you want to remove the feature and that some item have been generated with 'Use frame to present item paths in the item hierarchy'=yes)
   

• Include page header image: define if a page header image will be included in the page header to identify the page kind. Note that the image can be changed using Modify item and that change only apply to generated items.  
   

• Generate site in 2 language: define if the site is bilingual or monolingual.
  Notes:
  - If bilingual each dual directory will contain one overview.htm page in the first language and one overviewL2.htm in the second language.
  - The name of a item in the second language can be set using Modify item , and attributes in the second languages can be set using Edit Attributes.
   

• Language 1, Language 2: define the language 1 and the language 2 in selecting the ISO 639-1 language code.
  
  Code and translation are predefined for English (EN) and French (FR). If you want to add other languages read the following:
  
  1. Close Process Builder
  
  2. Add the language code: open the project file (*.pbp) with notepad and change the Available languages line
      AvailableLanguages=EN,FR,<new ISO 639-1 language code>
  
  3. Open process Builder and change language 1 and/or language 2

  4. Edit the translation file
   

• Edit translation file: allows to change the translation of a given word or sentence or to add a new translation for a new language
  
  Format of the opened file is the following:
  
  S -> { SentenceTranslation }
  SentenceTranslation -> DefaultTranslation { Translation in language i }
  DefaultTranslation -> <Sentence code>'='<Sentence in default language> <carriage return>
  Translation in language i -> <Sentence code>_<language code i>'='<Sentence in language i> <carriage return>

  For instance:
  ReadingActivities=Reading activities:
  ReadingActivities_EN=Reading activities:
  ReadingActivities_FR=Activités l'utilisant:
  ReadingActivities_<language code>=<translation>
   

• Charset: define the charset you want to use depending of your language
  - iso-8859-1 (the default) for US and western European (English, French, German, Italian, Spanish, Swedish, Dutch, Finnish, Irish, Norvegian, ...)
  - iso-8859-2 for Hungarian, Czech, Romanian, ...
  - iso-8859-5 for Russian, Bulgarian, ...
  - iso-8859-6 for Arabic
  - iso-8859-7 for Greek
  ....
  
  Notes:
  - only iso-8859-1 has been tested
  - bilingual site with 2 charsets are not supported (trad.ini is code in ascii and not UTF8 nor Unicode)
   

• Edit style sheets: allows to edit the generated site style sheets - for instance to change the font size and color.
  To know more about style sheets, consult the W3C website.
   

• Site Name, Site name L2: allows to change the process repository name in first and second language

• Template in 2 languages: define if the table referencing templates should contains columns for 1 or 2 languages.

  Define if the table referencing templates should contains column for one or 2 languages. Example follow:

• Use alternative links to template/procedures if available:
  Templates and procedures/guides can be stored in 2 different locations. For instance embedded in the site or located in a SharePoint site or PDM tool.
  This parameter allows to switch between the 2 locations and to generate the process repository website for a given location.
  
  Note: storing the templates and procedures/guides in the site allows to generate a standalone site that can for instance be used from a DVD.
  
  The following strategy is used for the generation:
  - if "use alternative links" is checked -> get alternative links if exist, if not get standard links
   if "use alternative links" is unchecked ->  get standard links
   

• Item with no domain appears in item overview of all domains:
  Define if items (work product, procedure/guideline) not depending of a domain (that have no domain as a parent) will appear or not in the work product overview, template access and procedure group.
  If yes, it means items with no domain are relevant for all domains.
   
• Element order in the activity page:

• Generate shortcut button in activity page:
  Define if link buttons will be generated in the activity schema

• Use treeview for hierarchical steps:
  Define if hierarchical steps are generated using a foldable treeview
  
   
• View children work products in work product overview:
  Define if work products that are child of other work product in the item hierarchy will appear or not in the work product overview pages.

• Show <X> column in work product overview:
  Define if attributes <X> of work products will appears as a column in the work product overview pages.

• For generic role or acting role group, generate activity links related to children roles:
   Acting role group or generic role is a role attribute. The attribute semantic is the following:
  * Acting role group: the role is in fact a group of roles - adding the group means adding all members of the group.
  * Generic role: factorize the behavior of a set of roles. If the generic role is added in an activity, it means that all derived roles participates.
  
  If a generic role or acting role group is linked to an activity <Y>, the parameter defines if children role pages will reference the activity <Y> (as activity in which the role is involved).
  
   
• Generate WBS number in process overview:
  Define if Process overview work breakdown structure will contain bullets or numbering.
   

Configure for each process class for which a popup is generated on its hyperlink, the content of the popup.