SoluDyne BASIC

SoluDyne BASIC consists of functionality, like Organization and Employee functionality, that is the basis for all other modules in SoluDyne.

Net Account

Best Practices & Other Governing Elements

01 - Basic

Alarms and Notifcations

B-12380 - Alarms in Workqueue (Lincense, Certification, Requirement)

00 Overview
01 Description


00 Overview

This Best Practice describes the Alarm functionality in SoluDyne.

01 Description
A leader receive License Alarms, Certification Alarms and Requirement Alarrms for his/her employees. Leader must have My Units set in order to have user listed under My Employees.

Application

B-13188 - Application Classes Configuration

Overview

This Best Practice describe how to configure URI links to Customer servers in the SoluDyne System.

The URI links can be specified in an Application register in SoluDyne under Portfolio menu. The links are used for easy access and maintenance of external Applications.  When user click the link in shape popup of an Activity on a FlowChart (or popup of FlowChart on a Sub-Process), a new window appears and the user continues the work in the opened Application.

Application classes are: Application Register, Application Group, Application, Application Interface, Application Service. Application register provides hierarchy of Application objects like:

Application Register
    Application Group
        Application
            Application Service
            Application Service
            Application Interface
            Application Interface
            . . .
        Application
        . . .
    Application Group
        Application Group
        Application
        . . .

Prerequisites

The user has needed access permission to create and modify nodes of Application classes.

Description

Application Register is created under the Portfolio main menu item. Application Register consists of some Application Groups. Application Group could contain other Application Groups (sub-groups) and Applications. Application should contain one or some Application Services and one or more Application Interfaces.

One Application Interface specifies one URI link to be available on FlowChart and/or Activity shape popups. Application Interface allows specifying which Application Services this Application Interface available from. Application Interface can be connected with any Application Service that belongs to the same Application (parent node).

Create a new Application Register:

 

  1. Click on New button on the toolbar.
  2. Select New Register item.
  3. Click on Application Register item in the popup to create a new Application Register.

Create a new Application Group under an Application Register:

 

  1. Expand Portfolio main menu.
  2. Select the created Application Register.
  3. Right click in the tree on the created Application Register and select New Node context menu item.
  4. Select Application Group item to create a new Application Group.
  5. Link Add Application Group under Application Groups grid can also be used to create another Application Group.

Create a new Application under Application Group:

 

  1. Right click in the tree on the created Application Group.
  2. Select New Node context menu item.
  3. Select Application item to create a new Application node.
  4. Link Add Application under Application Groups & Applications grid can also be used to create another Application.

Create a new Application Services under Application node:

 

  1. Right click in the tree on the created Application.
  2. Select New Node context menu item.
  3. Select Application Service item to create a new Application Service.
  4. Link Add Application Service under Application Services grid can also be used to create another Application Service.

Create a new Application Interface under Application:

 

  1. Right click in the tree on the created Application.
  2. Select New Node context menu item.
  3. Select Application Interface item to create a new Application Interface.
  4. Also link Add Application Interface under Application Interfaces grid can be used to create another Application Interface.

 

  1. Specify Title
  2. Select a Type from drop-down list.

The following Type values are available:

  • REST Web Service
  • SOAP Web Service
  • Web Application
  • iOS App
  • Android App
  • Windows Mobile App
  • Desktop Application

 

  1. Specify URI link in URI field.
  2. Select in Services field one or more Application Services which the given Application Interface is bound with.
  3. Save the changes.

Services field is a multiple choice control. It is a set of items representing all Application Services that are children on Application node, which the given Application Interface belongs to.

B-13189 - Start Application from Processes

Overview

This Best Practice describes how to use URI links to Customer servers in the SoluDyne System.

Application data model allows:

  • To visualize how the different applications are used in different processes.
  • To be able to automatically start applications directly from the process when possible.

Applications consists of Application Interfaces and Application Services. Application Interfaces are created for documenting enterprise application architecture and provide possibility to start applications directly from the process. Application Services makes it possible to group Application Interfaces and make them available from processes in the System.

The URI links are configured in Application Interfaces in Application Registers in the SoluDyne System. See B-13188 - Application Classes Configuration for details. These links can be associated with Processes: FlowChart and Activity nodes via association with Application Services in Application Registers. After that, URI links will become available on popups of corresponding shapes on Charts of parent nodes. When user clicks the link in popup, it opens URI and the user continues the work in the external Application.

The URI links are specified in Application Interface nodes in URI field. Application Interface is Connected with one or some Application Services using Services field. Vise versa, Application Service is connected with some Application Interfaces, i.e. with the Application Interfaces having the given Application Service selected in their Services field.

One or some Application Service can be associated with a Process (FlowChart or Activity) using Application Services field. When an Application Service is associated with FlowChart or Activity, URI links assigned in all Application Interfaces, connected to given Application Service, become available in the corresponding shape's popup. The link assigned for each Application Interface of the Application Service is shown separately with Title of the Application Interface as displayed text and content of URI field as referred link.

Prerequisites

  • Sub-Process node contains child FlowChart node.
  • This FlowChart node has child Activity node.
  • The user has needed access permission to modify FlowChart and Activity nodes.
  • Application Register is configured in accordance with B-13188 - Application Classes Configuration.

02 Description

 

  1. In the Sub-Process node: Open the child FlowChart.

 

  1. Go to page 2 Flow Chart with Roles.
  2. Click Add Application Services link under Application Services grid to open Select Application Service window.

 

  1. Select an Application Service to be connected.
  2. Verify that the selected Application Service is shown in the grid.
  3. Close the window.

 

  1. Verify that the selected Application Service is shown in the Application Services grid on Flowchart form.

 

  1. In the parent Sub-Process node of the given FlowChart node: Move mouse cursor over shape of the FlowChart to show popup.
  2. In the popup, in the area shown content of associated Application Service: Click on the link of Application Interfaces.

Note, popup content is updated with the latest information only when all nodes involved in popup content are published.

 

  1. Verify that the Web site assigned to the Application Interface opens in a new window / tab.

 

  1. Open the Activity node under the FlowChart.

 

  1. Go to page 1 Activity.
  2. Click Add Application Services under Application Services grid and select Application Services in the Select Application Service window. 

 

  1. In the parent FlowChart node of the given Activity node: Verify that Application icon is shown near Activity shape.
  2. Move mouse cursor over shape of the Activity to show popup.
  3. In the popup: Click on the link of Application Interfaces and verify that referred Web Site is open in a new window / tab.

Note, popup content is updated with the latest information only when all nodes involved in popup content are published.

B-13373 - Rename File When Opened in Another Application

Overview

This Best Practice describe how to rename File node correctly when its attached file is opened in an external application.

See B-12190 - Add and Edit Files for details on how to attach files to nodes in SoluDyne System.

Prerequisites

1. SoluDyne Web  server is configured to use Network Share for files.

2. File node has an attached file. External application associated with this file type locks the file on open. An example of such file type is PDF.

Description

 

  1. Open File node with attached file.
  2. Click Edit button to open the attached file in an external application associated with given file type.

 

  1. Close the external application to release the file.

 

  1. Specify a new name for the File node.
  2. Click Save button to save the changes.

B-13374 - Rename File When Content is Changed in Another Application

Overview

This Best Practice describe how to rename File node correctly when its attached file is modified in an external application.

See B-12190 - Add and Edit Files for details on how to attach files to nodes in SoluDyne System.

Prerequisites

1. SoluDyne Web  server is configured to use WebDAV. For details see:

  • B-12893 - IIS7.5 and WebDAV
  • B-13176 - WebDAV with Standard or AD FS Authentication

Additional information on IIS.NET Installation and Configurering WebDAV

2. File node has an attached file. External application associated with this file type supports WebDAV.

Description

 

  1. Open File node with attached file.
  2. Click Edit button to modify the attached file in an external application associated with given file type.

 

  1. Perform desired changes.
  2. Click Save button.
  3. Close the external application to release the file.

 

  1. Specify a new name for the File node.
  2. Click Save button.

 

  1. After the page is saved, click Edit button to continue the changes in the file.

FAQ

B-10580 - FAQ - Frequently Asked Questions

0.00 Definisjoner
1.00 Beskrivelse
2.00 FAQ-prosessen
2.01 Forutsetning for FAQ register
3.00 Opprette ny FAQ
3.01 Felter tilgjengelig på FAQ-skjema
4.00 Evaluere FAQ
5.00 Forespørsel etter mer informasjon
6.00 Endelig kvittering
7.00 Publiserte FAQs
8.00 Avslåtte FAQs


0.00 Definisjoner

FAQ - Ofte stilte spørsmål

1.00 Beskrivelse

FAQ brukes for å registrere informasjon om saker der medlemmer av organisasjonen rapporterer de samme spørsmålene flere ganger. De rapporterte spørsmål og tilhørende svar vil gjøre det lettere å gjenbruke eksisterende informasjon og metoder for å løse utfordringer.
 

2.00 FAQ-prosessen

Et forslag til en FAQ kan registreres av alle typer brukere logget på SoluDyne.

Når feltene i FAQ skjemaet er fylt ut, signert og lagret, blir FAQ sendt til evaluering.
I evalueringssteget vil den Ansvarlig evaluere om den foreslåtte FAQen skal publiseres eller bli forkastet. 
Hvis mer informasjon er nødvendig for å kunne beslutte om FAQen skal beholdes, vil den foreslåtte FAQ bli sendt tilbake til innrapportør med en forespørsel om mer informasjon. Innrapportør skal fylle ut mer informasjon på FAQen, og signere denne ut.
FAQ vil etter innrapportørs signatur havne hos ansvarlig igjen.
Den ansvarlige kan publisere eller avslå en foreslått FAQ ved å velge enten publiser eller avslå og signere ut evalueringsskjemaet.Innrapportør får da en endelig kvittering som viser hva utfallet av evalueringen av FAQ ble.


    
  
Figur 1 - FAQ flytskjema. Illustrasjon av flyten og stegene i FAQ-prosessen.

 

2.01 Forutsetning for FAQ register

1. FAQ Register - ID definert i System > SoluDyne Administrasjon > FAQRegisterUID
2. Stilling/-er som skal være ansvarlig for å evaluere FAQer må være knyttet opp i System> SoluDyne WorkFlow Register> 0 - - - FAQ - Frequently Asked Questions - - 24 > Responsible


3.00 Opprette ny FAQ
1. Opprett en ny FAQ ved å klikke på ny-knappen på SoluDyne verktøylinje.     
2. Velge Nytt arbeidsflyt element på menyen og deretter FAQ.
3. Sørg for å fylle ut info i alle de obligatoriske feltene og inkludere så mye informasjon som mulig på alle andre felt. Skjemaet har mindre sannsynlighet for å bli sendt tilbake til innrapportør om feltene inneholder tilstrekkelig informasjon.


3.01 Felter tilgjengelig på FAQ-skjema

Fyll ut alle obligatoriske felter på FAQ skjemaet først.
 
Fyll deretter ut felter som gjelder for FAQ det jobbes med.


Følgende felter er tilgjengelige:

Nr. : Blir generert automatisk som et sekvensielt nummer med prefikset FAQ.
Tittel: En kort beskrivelse av hva FAQ handler om. Vanligvis ville dette være det området som spørsmålene gjelder for.
Forfatter: Brukernavnet til den ansatte som opprettet FAQ.
Emne: Beskrivelse av hva FAQ handler om. Dette vil vanligvis være i form av et kort spørsmål.
Sammendrag: Dette feltet kan brukes dersom det er nødvendig å foreta en oppsummering av emnet. Feltet brukes hvis FAQ-emne er langt eller komplisert og trenger en kort beskrivelse.
Område: De områdene der FAQ er gjelder.
Lokasjon: Fysisk lokasjon hvor FAQ er opplevd.
Gruppe: Hvis aktuelt; hvilket team eller gruppe har opplevd FAQ.
Innrapportør: Brukes hvis innrapportør i SoluDyne systemet er en annen en dem som opprinnelig opplevde grunnlag for FAQ. Hvis FAQ ikke ble opplevd av personen som skapte den i SoluDyne systemet, er det viktig å registrere hvem som faktisk har opplevd grunnlag for FAQ.
ATA: Gjelder bare luftfart. Registrer ATA.
Beskrivelse: Saken er tatt opp i dette feltet. Tekst, bilder og filmsnutter kan legges til for å bedre forklare grunnlaget for FAQ.
Referanser tekst: Ekstra referanser kan bli lagt til som tekst til dette feltet.
Referanser lenker: Andre referanser i SoluDyne kan knyttes til dette feltet.
Referanser filer: Tilleggsfiler kan lastes opp til dette feltet.
Signatur: Dette feltet må signeres når skjemaet er ferdig utfylt. Skjemaet ligger i forfatterens arbeidskø helt til forfatteren signerer ut skjemaet.


Når alle feltene er fylt ut og at skjemaet er signert for, sendes FAQ til neste trinn i prosessen.


4.00 Evaluere FAQ 

Brukere med rollen ansvarlig i FAQ-prosess vil motta FAQ i arbeidskø for evaluering.
 
Fyll i feltet Evalueringskommentar og angi om FAQ skal publiseres eller ikke. Hvis publisert blir valgt, vil FAQ ende opp i FAQ drilldown for publiserte FAQer. Hvis avvist, vil FAQ ende opp i drilldown for avslåtte FAQer.


For å bli sendt videre til neste steg- og endelig kvittering, signer skjema for FAQ.  Dersom ytterligere informasjon er nødvendig før evalueringen er utført, velg Krever mer info i felt Evaluer.
 

5.00 Forespørsel etter mer informasjon

Innrapportøren vil enten motta en forespørsel for mer informasjon eller en kvittering. Dersom brukeren mottar forespørsel for ytterligere informasjon, kan dette legges ved i kommentarfeltet. Den foreslåtte FAQ kan deretter returneres til den ansvarlige for evaluering ved å signere og lagre skjema.
 

6.00 Endelig kvittering

Endelig kvittering mottas av innrapportør i SoluDyne arbeidskø. Utvid arbeidskøen og åpne skjemaet ved å klikke på en node under FAQ - Ofte stilte spørsmål. Les skjema og signer det ut med underskrift og deretter trykke lagre eller enter.


7.00 Publiserte FAQs

Publisert FAQ er en drilldown som viser FAQer som ble ansett som relevant, og dermed akseptert. Den publiserte FAQ drilldownen er portalen/grensesnittet for å kunne bla i FAQer for ordinære brukere. Ved å bruke drilldown-filteret, kan det søkes etter ulike emner i FAQ.

   
Figur 2 - FAQ har egen knapp på SoluDyne meny. Herunder ligger blant annet F-5 Publiserte FAQ.


8.00 Avslåtte FAQs 

Avslåtte FAQ er en drilldown som viser de spørsmål/FAQ som ikke ble akseptert og publisert. Dette registeret kan brukes til å gjennomgå tidligere avviste FAQ.
 


 

Favorites

B-10561 - Use of Favorite button in SoluDyne

00 Overview
01 Description

02 Example
02.01 Create favorite to a work process 
02.02 Retrieve link to a work process
02.03 Add shape from work process in Microsoft Word


00 Overview

This Best Practice describes the use of the favorite button in SoluDyne. See figure 1.

01 Description

Using the favorite button in SoluDyne enables the User to perform the following:

  • Add favorite under my favorites in Internet Explorer to for example a work process or a Best Practice.
  • Retrieve links to for example a work process or a Best Practice that for instance can be sent by e-mail or used in a Microsoft Word document.
  • Add shape of work process in for example a Microsoft Word Document.

02 Example 

02.01 Create favorite to a work process

  1. Navigate to the work process.
  2. Click on the Favorite button on SoluDyne Toolbar. 
  3. Click  'Add to favorites'. See figure 2.
  4. A new window will appear. The user can change the name of the favorite, and location.  See figure 3.
  5. Click add to save changes.
  6. New favorite will be available under the favorite button in Internet Explorer. See figure 4.  

02.02 Retrieve link to a work process and send it by e-mail

  1. Navigate to the work process. 
  2. Click on the Favorite button on SoluDyne Toolbar.
  3. Click on  'Copy link to clipboard'. See figure 5.
  4. Create new e-mail. 
  5. Paste the link and choose subject. See figure 6.
  6. The receiver of the e-mail can click on the link to open the work process.

02.03 Add shape of work process in Microsoft Word.

  1. Navigate to the work process.
  2. Click on the Favorite button on SoluDyne Toolbar. 
  3. Click on 'Copy flowchart to clipboard'. See figure 7. 
  4. Open Microsoft Word 
  5. Paste the work process. See figure 8.





    Figure 1 - Favorite Button.




    Figure 2 - Create favourite to a work process.  



      
    Figure 3 - Change name and location.

         
    Figure 4 - Favorite button in Internet Explorer.



      
    Figure 5 - Copy link to clipboard



     
    Figure 6 - Paste the link in an e-mail and choose subject.


     
    Figure 7 - Copy Flowchart to clipboard.


     
    Figure 8 - Paste Work process in Microsoft Word.

    File

    B-12190 - Add and Edit Files

    Overview

    This Best Practice describes how to add and edit file attachments in SoluDyne.

    Several ways of attaching files to nodes are supported by SoluDyne: it can be done via File List field, via Floating Toolbar or by drag & drop. Inserting files via Floating Toolbar is useful when they are put directly into HTML Editor fields (for example, when pictures are added). When the files are added by drag & drop, behavior of the system depends on the target node where the file is dropped: for some of them, new child nodes are created (like File nodes being created under Section nodes); for others, the files are simply added to the file list.

    Data nodes must be put to checked out state before the files can be attached to them. Workflow node do not require checkout for attaching files.

    The attached files can be edited via the File List field. Depending on server configuration, access to the files being edited is provided either via a shared network folder or via the WebDAV protocol.

    Data nodes must be put to checked out state before the files attached to them can be modified, and the changes to attached files are visible only to the change owners until the nodes are published. Workflow nodes do not require checkout for modification of files attached to them, and the changes being done can be viewed by others immediately after save - only opening or refresh of the corresponding pages in browser is required.

    Hyperlinks to attached files can be copied from the File List field by standard 'Copy shortcut' browser action. An URL created in this way looks like 'file/<id>/filename.ext', and it always points to the latest revision of the file attachment. Hyperlinks pointing to latest revisions of files are preferable because they always show the files in their actual states. However, it is also possible to create a hyperlink pointing to permanent revision of file which always refers to the same content: in order to do it, one should change the 'file/' part in URL to 'file-permanent/'.

    The attached files can be deleted from the system by means of delete button in File List field.

    Data nodes must be put to checked out state before the attached files can be deleted from them. Workflow nodes do not require checkout for deleting attached files.

    Description
    Files can be attached to any node in SoluDyne which has the File List field or HTML Editor field.

     

    1. Navigate to the target node which form contains a File List field and use Add files button on the File List Field to open the Select File Dialog.
    2. In the Select File Dialog, specify the file(s) to be uploaded.
    3. Press Upload button to attach files to the Node and close.

    1. Observe file is added to File List.
    2. Put the text cursor into the HTML Editor Field.
    3. Click on the Insert File button on the Floating Toolbar.

    1. Click on the added file in Select File Dialog to choose it (preview of the chosen file will be shown).
    2. Insert button can be used to insert chosen file into HTML Editor Field.

     

    1. Expand the desired node in the Treeview.
    2. Open the folder containing the file to be attached in Windows Explorer.
    3. Drag the file from the folder into the target Section node.

     

    1. Confirm the drop of file.
    2. File will be added to the system by creating a new child node under the target node or attaching to the target node, depending on the kind of target node.

       

    1. Navigate to the target Node which Form contains a File List field.
    2. Click on Edit file button in the row of File List to open the file in default application associated with it.
    3. Copy the hyperlink from the row of File List, for example, by means of the Copy shortcut option in browser context menu to use it afterwards.
    4. Click on 'Delete' button in the row of File List to remove the file.



    1. If the SoluDyne Server is accessed through the Internet, the URL of the SoluDyne Server has to be a trusted site. To set trusted sites, perform the following steps.
    2. Open Internet Options in Microsoft Internet Explorer. Navigate to the Security tab and select Trusted sites.
    3. Click the Sites Button to open Trusted sites dialog.
    4. The option Require server verification (https://) for all sites in this zone, must be unchecked.
    5. Fill in web-site url and press Add button.
    6. Click on the Close button and close Trusted sites dialog.
    7. Click on the OK button and close Internet Options dialog and restart Microsoft Internet Explorer to apply changes.

    B-12335 - Dynamic Content in Microsoft Word document files

    00 Oversikt
    01 Beskrivelse
    02 Eksempel
    02.01 Oppdatere innhold i mal
    02.02 Legge til flettefelt Microsoft Word dokument
    02.03 GUID Sti-uttrykk
    02.03.01 Ofte brukte GUID-uttrykk
    02.03.02 Sti-uttrykk
    02.03.03 Spesifisere nåværende node
    02.03.04 Spesifisere overstående node
    2.03.05 Spesifisere rot-node
    02.03.06 Hvordan GUID Sti-uttrykk fungerer
    02.04 Filformat
    02.05 Benytte dokumentet som mal
    02.06 Legge til flettefelt i bunntekst og topptekst

    00 Oversikt

    Denne Beste Praksis beskriver bruken av Dynamisk Innhold i SoluDyne - Innhold som oppdateres da data-kilden oppdateres.

    01 Beskrivelse

    Skjemafelter i Microsoft Word dokumenter kan kobles mot SoluDyne. Dette innebærer at skjemafeltene oppdateres automatisk når en bruker åpner dokumentet for redigering.

    Eksemplene under viser hvordan flettefelt kan legges til i Office 2010 dokumenter som allerede er lastet opp til SoluDyne, hvordan man kan lokalisere riktig GUID (Globalt unike IDer som benyttes for å velge hvilken informasjon som skal hentes) og hvordan man kan lage en mal av dokumentet i SoluDyne.

    Se også ytterligere informasjon om maler (templates) på B-12205 - Maler og B-12222 - Flytskjema mal og Modelleringsstandard.

    02 Eksempel

    02.01 Oppdatere innhold i mal

    Feltverdier oppdateres automatisk da dokumentet åpnes for redigering ved bruk av 'Edit File' knappen i SoluDyne.

     
    Figur 1 - Redigering av fil fra filnode.

    02.02 Legge til flettefelt Microsoft Word dokument

    Dynamisk innhold legges til i Word ved bruk av Microsoft Words flettefelt. For å legge til et flettefelt på valgt lokasjon i dokumentet ekspander 'Quick Parts' menyen under 'Insert' fanen og velg 'Field...' som vist under.

       
    Figur 2 - Valg av Field... fra verktøylinjen.

    Dette vil vise Felt-vinduet.

       
    Figur 3 - Felt-vinduet med MergeField valgt og GUID-uttrykket 'current:file_name' fylt inn i 'Field name' feltet.

    I Field names listen; scroll ned og velg MergeField, som vist over. Fyll ønsket GUID-uttrykk inn i 'Field name' feltet. Klikk OK for å sette flettefeltet inn i dokumentet. Frem til dokumentet på nytt åpnes for redigering fra SoluDyne vil GUID-uttrykket fra 'Field name' feltet vises i stedet for verdiene fra SoluDyne.

    Se under for komplett liste over tilgjengelig GUID-uttrykk og ofte brukte GUID-uttrykk.

     
    Figur 4 - Insatte felt som viser GUID-uttrykk.

     
    Figur 5 - De samme feltene etter at dokumentet er blitt åpnet for redigering.

    02.03 GUID Sti-uttrykk

    GUID Sti-uttrykk brukes for å identifisere hvillket felt som skal settes inn i dokumentet. Uttrykket består av to deler; stien og IDen separert av et kolon. For eksempel har uttrykket 'parent:title' stien 'parent' og IDen 'title'.

    En liste over IDer assosiert med filer kan finnes ved å navigere til SoluDyne Ekspanderende Meny > System > GUID Detaljoversikt > Håndbøker & Manualer > Fil som vist i figur 6. Disse kan brukes i kombinasjon men stien 'current' for å hente informasjon fra den valgte filnoden.

     
    Figur 6 - Eksempel GUID oversikt.


    02.03.01 Ofte brukte GUID-uttrykk

    GUID Tittel Forklaring Eksempel
    current:approved_by Godkjent av Hvem som har godkjent dokumentet. Nordmann - Ola - OLA
    current:signature_date Dato Godkjent Dato for godkjenningen 05.02.2014
    current:controlled_by Kontrollert av Hvem som har kontrollert dokumentet. Nordmann - Ola - OLA
    current:published_author Publisert av Hvem som har publisert dokumentet Nordmann - Ola - OLA
    current:published_date Dato publisert Dato for publiseringen 05.02.2014
    current:rev_author Rev. forfatter Hvem som har forfattet dokumentet Nordmann - Ola - OLA 
    current:rev_date Rev. dato Dato for revisjon 05.02.2014
    current:revision Revisjon Versjonsnummer 0.1
    current:tree_path Sti Stien til filen i SoluDyne Manual/Seksjon/Rapport
    current:file_name Navn Tittel på filen Rapport
    current:id Id Fil id F-10052
    current_description Description Beskrivelsesfelt på fil klasse node. Denne filen omhandler...
    current:file_type Type Typen fil DOCX
    Tabell 1 - Oversikt og forklaring av vanlig brukte fil-GUIDer.

    02.03.02 Sti-uttrykk

    Sti-uttrykk består av null eller flere elementer separert av en skråstrek '/' som spesifiserer lokasjonen relativt til nåværende node. For øyeblikket er det støtte for tre elementer; current, parent og root.

    02.03.03 Spesifisere nåværende node

    Sti-uttrykket 'current' spesifiserer nåværende node i sti-evalueringen. For eksempel identifiserer 'current'  den originale noden, mens stien 'parent/current/' vil ende opp på overstående node, altså 'parent'. 'current' uttykket er valgfritt, og kan om ønskelig ekskluderes helt fra evalueringen. Altså har 'current' samme effekt som et helt tomt uttrykk.

    02.03.04 Spesifisere overstående node

    Sti-uttrykket 'parent' spesifiserer den overstående noden, et nivå opp i treet. For eksempel vil sti-uttrykket 'parent' identifisere den umiddelbart overstående noden, mens uttrykket 'parent/parent' identifiserer noden to nivåer opp i treet.

    02.03.05 Spesifisere rot-node

    'root' elementet spesifiserer rot-noden i det nåværende treet. Bruk av 'root' elementet vil resette inneværende sti-evaluering til rot-noden. For eksempel er evalueringen av uttrykkene 'root' og 'parent/root/parent/parent/root' identiske.

    02.03.06 Hvordan GUID Sti-uttrykk fungerer

    GUID Sti-uttrykkene evalueres relativt til inneværende node. Først evalueres stien, så benyttes stien for å lokalisere noden som innehar den påkrevde verdien. Når hele stien er evaluert kobles GUIDen mot feltet for den lokaliserte noden.

    02.04 Filformat

    Microsoft Word filer må lagres som .doc eller .docx om de skal benyttes som maler.

    02.05 Benytte dokumentet som mal

    Naviger til filnoden som skal benyttes som mal. Sørg for at den står i redigeringsmodus. Fra SoluDyne verktøylinjen, velg Info > Properties. Under mal-fanen, huk av Bruk som Mal. For å begrense bruken av malen til spesifikke klasser, huk av for ønskede Malklasser under. Slik som f.eks Seksjon. Trykk Save.

    Aktiveres mal for Seksjon vil bruker få opp ett valg om å bruke mal når bruker høyreklikker på en seksjon i systemet.

     
    Figur 7 - Bruk dokumentet som mal.

    02.06 Legge til flettefelt i bunntekst og topptekst

    Flettefelt fungerer ikke korrekt da de brukes direkte i toppteksten eller bunnteksten av et dokument, siden Word resetter feltene da de printes eller lagres til PDF eller åpnes for printing. Denne seksjonen forklarer hvordan flettefelt kan legges til i topptekst og bunntekst i et dokument. 

    Først, sett inn et felt i dokumentet som forklart over. Dette feltet kan ikke befinne seg i toppteksten eller bunnteksten.

     
    Figur 8 - Felt satt inn i dokumentet.

    Marker flettefeltet i teksten og velg bokmerke under Sett inn fanen. Dette vil vise Bokmerke vinduet.

     
    Figur 9 - Sett inn nytt bokmerke.

    Skriv inn navnet på det nye bokmerket og klikk Legg til. Dette vil opprette det nye bokmerket. Lukk bokmerke-vinduet.

     
    Figur 10 - Definere et nytt bokmerke.

    Høyreklikk i toppen eller bunnen av dokumentet for å redigere topptekst og bunntekst.

    Velg Rediger Topptekst

     
    Figur 11 - Aktivere topptekst og bunntekst.

      
    Figur 12 - Redigere toppteksten.

    I toppteksten, Velg Quick Parts > Field, under Inser fanen. I felt vinduet, velg Ref under Felt navn.

       
    Figur 13 - Feltvinduet som viser Ref og bokmerker.

    Velg bokmerket definert tidligere, under felt egenskaper.

      
    Figur 14 - Velg title bokmerket.

    Klikk OK for å sette inn det nye feltet på valgt sted i teksten.

      
    Figur 15 - Det nyopprettede feltet.

    Referansefeltet i hovedteksten må skjules, med mindre det er ønskelig at den er synlig. For å gjøre dette, legges feltet til i en Tekstboks, og tekstboksen skjules.Metoden for å opprette flettefelt og bokmerker er fortsatt den samme.

      
    Figur 16 - Legge til flettefelt i tekstboksen.

    Skjul tekstboksen ved å høyreklikke og velge  'Formater figur...'.
    Sett Fill til No Fill og Line til No Line.

     
    Figur 17 - Sett farge til No Fill og Line til No Line.

    Med tekstboksen markert, velg Tegneverktøy fanen, som vist i figur 18.

    Sett høyde og bredde til 0.

      
    Figur 18 - Sett høyde og bredde til 0 i Word 2010

    Å lokalisere tekstboksen senere kan være vanskelig.

    For å lokalisere den i Word 2010 kan følgende metode benyttes.

    I høyre ende av Hjem fanen, klikk Velg.. > Valgrute...

    Velg tekstboksen i listen under.

     
    Figur 19 - Velg > Valgrute..


    Figur 20 - Velg tekstboksen i listen.

    Når tekstboksen er lokalisert kan størrelsen endres for å gjøre oppdateringer lettere. husk å endre størrelsen til 0 igjen når ferdig.

      
    Figur 21 - Endre størrelsen på tekstboks.

    B-12947 - How to work with File renditions

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes how to work with File renditions in SoluDyne.

    01 Description

    It is possible to add renditions to a File in SoluDyne. A rendition is considered to be a copy of the main file saved in another format. It is possible to open quickly a file in the needed format by clicking on the corresponding extension in "Available formats".

    02 Example

    How to work with renditions on a File node:

    1. Open a File node with an attached file for edit.
    2. Click on the "Upload" button in the Files list.
    3. In the opened dialog select one or more files which are supposed to be renditions of the file already attached to the node and upload them.
    4. The renditions appear in the Files list under the main file.
    5. Formats of the main file and all its renditions are listed as links in the "Available formats" field.
    6. Click on a link in "Available formats" for opening the file in the needed format.

     
    Figure 1. The main file attached to a File node.


    Figure 2. A File rendition.

     
    Figure 3. Available formats.

    Gadgets

    B-10560 - Using SoluDyne Gadgets

    00 Overview
    01 Description
    02.01 SoluDyne Gadget

    02.02 SoluDyne Gadget Panel
    02.03 SoluDyne Gadget Selector Popup
    02.04 SoluDyne Gadget Windows
    02.05 Resize SoluDyne Gadget


    00 Overview

    This Best Practice describes the SoluDyne Gadget functionality in SoluDyne.

    01 Description

    The SoluDyne Gadget Panel is shown on the right side of SoluDyne and acts as a holder for SoluDyne Gadget Windows. The SoluDyne Gadget Panel can be shown in two modes: Normal View or Minimized View. In Normal View the SoluDyne Gadget Panel contains SoluDyne Gadget Windows. These windows contain SoluDyne Gadgets.

    When the SoluDyne Gadget Panel is minimized, only icons of Gadget windows are shown. When clicking on one of the icons in Minimized View, the selected Gadget Window is shown to the left of the icon as a popup.

    02 SoluDyne Gadget

    02.01 SoluDyne Gadget Panel

     
    Figure 1. SoluDyne Gadget Panel. Normal view


    Figure 2. SoluDyne Gadget Panel. Minimized view.

    02.02 SoluDyne Gadget Selector Popup

    The SoluDyne Gadget Selector is used to select what Gadgets are visible on the SoluDyne Gadget Panel. The user opens the SoluDyne Gadget Selector by clicking on the SoluDyne Gadget Selector button.
    The SoluDyne Gadget Selector button is placed in the upper right corner of the SoluDyne Gadget Panel. The SoluDyne Gadget Selector Button opens the SoluDyne Gadget Selector Popup, where the user can select SoluDyne Gadgets.

    The SoluDyne Gadget Selector Popup shows a list of available SoluDyne Gadgets, where the user can check those, that should be visible on the SoluDyne Gadget Panel. Each item in the list consists of a checkbox, SoluDyne Gadget Icon and the SoluDyne Gadget Title.

    Gadget can have child nodes. These child nodes can also be chosen to be shown as separate Gadgets. This means that for example the child nodes shown in the Workqueue gadget could be possible to show as separate gadgets in addition to the original Workqueue gadget.

     
    Figure 3. Gadget Selector Button opens the SoluDyne Gadget Selector Popup. Items are shown as a tree. Child nodes can be shown as separate Gadgets

    02.03 SoluDyne Gadget Windows

    SoluDyne Gadget Windows are used to hold SoluDyne Gadgets inside the SoluDyne Gadget Panel. A SoluDyne Gadget Window is made up to two parts: a Title Bar and a Content Panel. The Title Bar shows the title of the SoluDyne Gadgets inside it and buttons to control the SoluDyne Gadget Window. The Content Panel displays the active SoluDyne Gadget.

    The Title Bar contains a tab for each SoluDyne Gadget it contains. Each tab can be either active or inactive. Only one tab can be active at a time. The Content Panel displays the SoluDyne Gadget associated with the Active tab. Clicking on an inactive tab makes that tab the active tab.

    The 'Minimize' and 'Restore' buttons are used to toggle the visibility of the SoluDyne Gadget. When clicking the 'Minimize' button, the SoluDyne Gadget is hidden and the button changes to the 'Restore' icon. Clicking 'Restore' displays the SoluDyne Gadget, and the button changes to the 'Minimize' icon.

    The Close button is used to close the SoluDyne Gadget Window with a SoluDyne Gadget. The Refresh button is used to reload the content of the SoluDyne Gadget.


    Figure 4. Minimize, Restore, Refresh and Close buttons on Title Bars of SoluDyne Gadget Windows

    SoluDyne Gadget Windows can be combined so that one SoluDyne Gadget Window contains multiple SoluDyne Gadgets. SoluDyne Gadget Windows are combined by dragging the Tab from one SoluDyne Gadget Window onto the Title Bar of another SoluDyne Gadget Window. If the last tab of a SoluDyne Gadget Window is dragged onto another SoluDyne Gadget Window, the SoluDyne Gadget Window will be closed.

     
    Figure 5. The User clicks and drags to move My Favorites to the same window as Workqueue

     
    Figure 6. The User has moved My Favorites to share the same window as Workqueue

     
    Figure 7. The User clicks and drags to move My Favorites in between the windows for Workqueue and Workgroup Links

     
    Figure 8. User has then manually restored the windows to their original position on the panel

    02.05 Resize SoluDyne Gadget

    The SoluDyne Gadget Window can be resized differently based on wether it is displayed pinned to the SoluDyne Gadget Panel or as a popup. When pinned to the SoluDyne Gadget Panel, the SoluDyne Gadget Window can only be resized vertically, either by using the resize button placed at the bottom right of the window, or by using the bottom border of the window; see Figure 1. When the SoluDyne Gadget Window is opened as a popup, it can be resized using its bottom and left borders; see Figure 2.

    HTML and Text Editor

    B-10486 - Undo Functionality

    00 Oversikt
    01 Beskrivelse
    02 Eksempel
    02.01 Angrefunksjon - Oppdater i HTML-felt
    02.02 Angrefunksjon - Oppdater ved bruk av treet
    02.03 Angrefunksjon - Oppdater i nettleser


    00 Oversikt

    Angrefunksjonaliteten i SoluDyne.

    01 Beskrivelse


    Angrefunksjonaliteten i SoluDyne gjør det mulig å tilbakestille utførte handlinger. Tilbakestilling kan kun utføres før lagring/publisering. Funksjonalitet for å tilbakestille kan kun benyttes når verktøylinjen er aktiv. Verktøylinjen er kun aktiv i HTML felt. Beskrivelsesfelt er HTML felt.

    Oppdatere ved bruk av treet benyttes for å tilbakestille handling i edit-modus, dette gjøres ved å klikke på gjeldende plassering i treet eller i stien hvor en befinner seg, f.eks. i et flytskjema. Alternativt ved å høyreklikke i nettleser og velge "Oppdater", dette fører til at alle handlinger som har vært utført før bruker har lagret eller publisert blir tilbakestilt.

    02 Eksempel

    Nedenfor er illustrerte eksempler for å tilbakestille handlinger.

    02.01 Angrefunksjon - Oppdater i HTML-felt

    Metode for å tilbakestille en utført handling i HTML- / beskrivelsesfelt er illustrert i Figur 1. Ved å klikke på angrepil vil innskrevet tekst tilbakestilles.     

         
    Figur 1. Oppdater i HTML-felt

    02.02 Angrefunksjon - Oppdater ved bruk av treet

    Metode for å tilbakestille en utført handling ved å re-åpne f.eks. flytskjema fra treet i den utvidede menyen til venstre i skjermbildet. Endringer blir ikke lagret. Se Figur 2.

             
    Figur 2. Oppdater ved bruk av treet

    02.03 Angrefunksjon - Oppdater i nettleser

    Metode for å tilbakestille en utført handling ved å høyreklikke i flytskjema for deretter å velge "Oppdater". Se Figur 3.

            
    Figur 3. Oppdater i nettleser

    B-11805 - Creating Customized List Numbering

    Overview

    Customized list numbering is done using a two-column table with no borders. The first column is used for holding the numbering, while the second column is for the item. Each step is described below.

    Steps

    1. Insert a new table with two columns.
    2. Add a new row for each item.
    3. Fill in numbering for each row in the first column, and content into the second column.
    4. Hide the column borders by right-clicking inside the table and select Border On/Off.

    Example

       
       

    Step 1 - New table inserted.

    3.5 Baseline - A formally approved version of a configuration item, regardless of media, formally designated and fixed at aspecific time during the configuration item’s life cycle. [ISO/IEC12207:1995, definition 3.5]
    3.11 Life Cycle Model - A framework containing the processes, activities, and tasks involved in the development, operation, andmaintenance of a software product, spanning the life of the system from the definition of its requirements to the termination of its use. [ISO/IEC12207:1995, definition 3.11]
    3.22 Release - A particular version of a configuration item that is made available for a specific purpose. [ISO/IEC12207:1995, definition 3.22]

    Step 2 and 3 - Added rows and filled in numbering and content. 

    3.5 Baseline - A formally approved version of a configuration item, regardless of media, formally designated and fixed at aspecific time during the configuration item’s life cycle. [ISO/IEC12207:1995, definition 3.5]
    3.11 Life Cycle Model - A framework containing the processes, activities, and tasks involved in the development, operation, andmaintenance of a software product, spanning the life of the system from the definition of its requirements to the termination of its use. [ISO/IEC12207:1995, definition 3.11]
    3.22 Release - A particular version of a configuration item that is made available for a specific purpose. [ISO/IEC12207:1995, definition 3.22]

    Step 4 - After hiding the borders.

    B-12246 - Workaround for Undo changes in SoluDyne

    00 Overview
    01 Description



    00 Overview

    This Best Practice describes the Reset/Undo Changes functionality in SoluDyne. 


    01 Description

    Reset functions in SoluDyne makes it possible to go back /reset a performed action. The functions are only accplicable for resetting of an action before it has been saved/published.


    Reset function 01 
     
    By clicking regret /Undo the performed action is reset.  See figure 1. 

    Reset function 02

    An alternative method for resetting a performed action is to re-open the flowchart from the tree in the expanding menu to the left on the screen. Changes will not be saved. See figure 2.  

    Reset function 03

    An alternative method for resetting a performed action is to right click in the flowchart and choose update. See figure 3.

    Reset function 04

    An alternative method for resetting a performed action is to click on Form Selector in the toolbar and choose the same form on more time. Choose cancel. See figure 4.

     
    Figure 1 - Regret function 01.

     

    Figure 2 - Regret function 02.

     

    Figure 3 - Regret function 03.

     

    Figure 4 - Regret function 04.

    B-12375 - Resize and Insert Images into SoluDyne

    00 Overview
    01 Description
    02 Example

    00 Overview
    This Best Practice describes how to Resize and Insert images into SoluDyne.

    01 Description
    When printing on A4 it is a requirement that the width of the image should not be larger than 720 pixels. To scale the images in order to meet
    this requirement, perform one of the following options:

    1. Resize the image by adjusting the number of pixels in MS Paint or similar. It is recommended that unnecessary margins are cut off before resizing the image.
      The image will thus get a better resolution.
    2. Resize the image when inserting it into SoluDyne:
      1. Press the button Insert File in SoluDyne, see Example 1.
      2. Find the image and press the button Upload, see Example 2.
      3. Scale the image by entering the desired percentage size and press the button Insert, see Example 3.
      4. The image will then be displayed in SoluDyne, see Example 4.

    02 Example

     

    Example 1

      
      
    Example 2

     
     
    Example 3

      
     
    Example 4

    B-12394 - Uploading Images

    Overview
    Images may be added in any HTML Editor Field

    Prerequisites
    User should have enough permissions to edit Node where images to be inserted. Node should be in Edit Mode.

    Description

     

    1. Put a cursor into HTML Editor field where image will be inserted.
    2. Click Insert Image Button on a Floating Toolbar.

      

    1.  In shown Select File Dialog press Add files button.

     

    1. In  shown Select file Dialog click on Browse button to specify what image file to be uploaded.
    2. If more than one file is needed, it may be done by clicking on Browse button in several rows. Each file to be selected in a separate row.
    3. After all files selected, press Upload button for uploading files to the system.

     

    1. Click on image to be inserted.
    2. Select desired size.
    3. Set Insert link only if hyperlink is desired instead of image itself.
    4. Click Insert button.

     

    1. Make sure image is inserted.

     

    1. All images added in any HTML Editor fields on a particular node are uploaded as files to the system and shown in References - Files grid. Don't delete it from there as images will be lost otherwise.

    B-12418 - Clean HTML

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes the Clean HTML functionality in SoluDyne. 

    01 Description

    Clean HTML in SoluDyne is used for removing unnecessary formatting (HTML) when copying text from external sources such as Microsoft Word. By running Clean HTML font type and font size will change to SoluDyne standard font type and size.

    Clean HTML is available, by right-clicking, in all description (editor) fields where SoluDyne Floating Toolbar is active.

    02 Example

    Text has been copied from Microsoft Word:

    1. Right-click, anywhere in the description field, and choose Clean HTML. See figure 1
    2. Save Best Practice

     
    Figure 1. Before Clean HTML

     
    Figure 2. After Clean HTML

    History

    B-12198 - History

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes the History functionality in SoluDyne.

    01 Description

    Through History users can view nodes (requirements, best practice, activities, QIRs etc.) accessed the last 10 days. History is available under General in SoluDyne Expanding Menu.

    02 Example



    1. Open SoluDyne Expanding Menu and select General.
    2. Click on History.
    3. Select date.  

     

    TIP! Use Show Filter to search for a specific node!

    Home Page

    10 - Presentation of SoluDyne Homepage

    B-12426 - APOS Main Page

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes the Main Page functionality in SoluDyne.

    01 Description

    When logging into the SoluDyne system, the first page viewed is the SoluDyne Main Page. This view is used to navigate further into the system.


    02 Example

    Log into SoluDyne to view the Main Page.

       

    1. Main Processes.
      1. Gives an overview of available Main Processes.
    2. News.
      1. Recent News on top, older articles further down.
    3. Toolbar.
      1. Hold mouse over different button to view help text. 
    4. Workqueue.
    5. Shortcuts.
    6. Links.
    7. Gadget selector.
      1. Click on this button to select/deselect other gadgets

    B-11971 - Menu


    Figure 1. Menu shown on the Home Page.

     

        
    Figure 2. The content of the Menu is set by adding and updating Web Pages.

    Linking

    B-11780 - Linking nodes

    Overview
    This Best Practice describes how to create links between nodes.

    Description
    Links can be created between Nodes using Link button on the Floating Toolbar. Links allows to created references between different Nodes in the system.

     

    1. Navigate to the editable Node and press Link button on SoluDyne Floating Toolbar.
    2. Navigate to the desired Node in the Select Links dialog window using TreeView and click the Node to link.
    3. Observe selected Node appeared in the list under the TreeView within Select Links dialog window.
    4. Close Select Links dialog window.

     

    1. Check that the desired node is linked up under References - Links.

    B-11799 - Linking Activities and Comment.

    Overview

    The purpose is to have one place to store the master document on as well as be able to write in the same master document from different activities. Thereby different persons can have their own activitiy while working on the Master document on Plan.


    1.Link Comment to an Activity.

    1. When standing on an Activity, create a Comment.
    2. Click on the Comment icon to open the Comment.
    3. Click on Add links or click on the link icon on the toolbar white,
    4. Search and find the correct Activity to be linked.  The Comment will then include the linked Activity in the Activity grid. See image. below.

       

       

    2.Link and show linked Comments on an Activity.

    1. When standing on an activity; Click on Add links on an Activity to link a Comment from another Activity in the dialog box.
    2. Search and find the correct Comment on an Activity linked. Click on the comment. The Activity will then includes the linked Comment in the Comments grid. See image.

       

            
    Figure 1. An Activity displays the linked Comments.


    B-11802 - Linking from SoluDyne

    Prerequisites:
    Users must have access to SoluDyne to be able to make use of the link.

    Description:
    The following steps should be performed for linking from SoluDyne to other applications:

    1. Navigate to the correct node in SoluDyne.
    2. Click the Favorites button on SoluDyne Toolbar
    3. Chose Copy link to clipboard
    4. Open the source where the link should be and click Paste

    Figure 1. Copy link to a node from SoluDyne.

    B-11803 - Linking from internet to SoluDyne

    00 Description
    01 Navigate to node
    02 Change URL, setting Link Text
    03 Save and publish

    00 Description
    This Best Practice shows how to use hyperlinks in SoluDyne.

    01. Navigate to node
    Navigate to node and HTML field where hyperlink shall be inserted.

    02. Change URL, setting Link Text
    Set the node in Edit mode and paste in the hyperlink in the HTML field. Right click on the link to get options:


    Figure 01. Right click to get options. 

    Set URL will allow user to change the url.


    Figure 02. Set URL...

    Set Link Text will allow the user to customize the text that is displayed, instead of the URL.

    Figure 03.Setting Technical information as link text instead of http://demo/soludyne/.....

    Set Tooltip Text wil allow the user to set information text that shows when a user is holding the mouse over the link.


    Figure 4. Set Tooltip Text as guide text on URL.

    Example of use - Tooltip:
     
    Figure 5. Example of Tooltip text

    03 Save and publish
    Press Enter for changes to take effect. Save and publish node.

    B-12951 - Best Practice for Adding Link to Link Register

    Overview

    This Best Practice describes the Link Register functionality in SoluDyne.

    A Link node can be created under Link Register located under General menu. Link node shows content of a page referred by specified HTML address.

    Prerequisites
    User must have access permissions to create and modify Link Register and Link nodes.

    Description

     

    1. Navigate to the Link Register node and click on it. 

     

    The node will appear in a new menu. Right click on Link Register.

    1. Select New Node
    2. Select Link.

      

    1. A new Link has been created. 

     

    1. Type in the address of a link in the HTML Link field.
    2. Type in the correct Link Name.
    3. Click Go button to display content of linked site.
    4. Publish.

     

    1. The content of linked page is shown, node is published.
    2. Click Open button to show the page in separate tab.

     

    1. The page has been opened in separate tab.

    B-12952 - Best Practice for Changing Existing Link

    Overview

    This Best Practice describes how to change an existing Link in Link Register.

    All links specified in Link nodes located under Links Register can be changed.

    Prerequisites
    User must have access permissions to modify Link nodes.

    Description

     

    1. Navigate to the existing link and select edit.

     
     

    1. Type in the new link in the HTML Link field.
    2. Type in the correct Link Name.
    3. Click save, and double check the information written in the different fields.
    4. Publish the new link.


    1. Type in clearcache.aspx after server-name in the address-field, and hit enter on the keyboard.

    B-12970 - Link Register

    00 Oversikt
    01 Beskrivelse
    02 Eksempel

    00 Oversikt

    Denne Beste praksisen beskriver link register funksjonaliteten i SoluDyne.

    01 Beskrivelse

    For å opprette et Link Register i SoluDyne må klassene Link Register (Klasse ID: 650) og Link (Klasse ID: 651) må være aktivert. Klassene aktiveres i Systemtilgangskontrollen.

    Når aktivert opprettes nytt Link Register fra Ny knappen og legges under Generelt i SoluDyne Ekpanderende Meny.

    02 Eksempel

    N/A

    B-13026 - Open nodes/links in SoluDyne

    00 Overview
    01 Description
    02 Example


    00 Overview
    This Best Practice describes how to open registers, nodes and links in SoluDyne.

    01 Description
    Registers, nodes and links in SoluDyne can be opened in existing web browser window, in a new tab or in a new web browser window.

    By right-click on a register/node in SoluDyne, one can choose to open the register/node in current web browser window or in a new window. 

    By right-click a link in SoluDyne, one can choose to open the link in a new browser window or a new tab. This dialogbox is browser specific.

    02 Example

     

    Figure 1. Options in Internet Explorer for opening a link in a new tab or a new window.

    Location

    B-12352 - Create Location Register and Location Area Register

    Incomplete - See Norwegian version

    00 Overview
    01 Description

    02 Example
    02.01 Create Location Register
    02.02 Create Location
    02.03 Create Location Area Register
    02.04 Create Location Area

    02.05 Set Location for Governing Element


    This Best Practice describes how to use the Location and Location Area Register in SoluDyne.

    01 Description

    The example explains how to create a Location Register, Location Area Register, Location and Location Area and how to assign locations to Governing Elements.

    Basic SoluDyne knowledge and user access rights to create and edit Location Register, Location Area Register, Location, Location Area and governing elements are required.

    02 Example

    02.01 Create Location Register
    From SoluDyne Toolbar select New > New Register > 3115 Location Register. Set a name and an ID and press Publish.
     

    02.02 Create Location
    Naviger til og velg det nyopprettede registeret i SoluDyne Ekspanderende Meny under Organisasjon. Høyreklikk på registeret i trevisningen og velg New Node > 3117 Lokasjon.
    Gi lokasjonen en id og en tittel og trykk Publish.

    02.03 Opprette lokasjonsområderegister
    Fra verktøylinjen velg New > New Register > 3120 Lokasjonsområderegister. Gi registeret en id og en tittel og trykk Publish.
     

    02.04 Opprette lokasjonsområde
    Naviger til og velg det nyopprettede registeret i SoluDyne Ekspanderende Meny. Høyreklikk på registeret i trevisningen og velg New Node > 3121 Lokasjonsområde.
     

    Gi lokasjonsområdet en id og en tittel. Trykk Add Links for å legge lokasjoner til lokasjonsområdet, ekspander lokasjonsregisteret, velg ønskede lokasjoner, lukk sprettopp-vinduet og trykk Publish.
     

    02.05 Knytte styringselement opp mot lokasjon
    For å knytte et styringselement opp mot en lokasjon, sett elementet i redigeringsmodus, ekspander lokasjonsregisteret opprettet i 02.01 og huk av ønskede lokasjoner eller lokasjonsområder. Trykk Publish.
     
     

    News

    B-12203 - News and Broadcasts

    Innhold

    0.00   Definitions

    1.00   General Description 
    2.00   Create News
    2.01   Write news content
    2.02   Choose status
    2.03   Send out article
    2.04   Read news article
    2.05   Read and sign for broadcast.
    3.00   Read and sign for received news

    0.00   Definitions
    N/A

    1.00  
    General Description  
    Publication of news and information bulletins is used to inform users of SoluDyne about important events. These can be published on the homepage or be sent out to each user`s work queue.  

    2.00   Create News
    News can be found in the expanding menu:
    A. Right click on the top node.
    B. Choose news.

    2.01   Write news content
    Form for writing news.

    A form is shown on the right side of the screen: 
    Specify the news by filling out the following fields:

    A. Title
    B. Author
    C. Date
    D. Summary
    E. News
    F. Links
    G. Attachments

    2.02   Choose status
     By marking the news as Current the news will appear on the Homepage.

    By marking off Historic the news will appear at the bottom of the Homepage after the current News.

    Outdated news will be added to the newsarchive, but will not appear on the homepage. 

    2.03   Send out article
    If Broadcast is chosen, the news will be sent out to users work queue.

    2.04   Read news article
    Click on message in the work queue. Available broadcasts is shown in the menu under the title Message.

    2.05   Read and sign for broadcast.
    News can be opened in the work queue, and read. 

    3.00   Read and sign for received news
    By clicking on the news message in the work queue, the news message can be read and signed for. By signing it, the news message disappears from the work queue.

    Notification and Subscription

    Notifications

    B-12200 - Revision Notification

    00 Overview
    01 Description
    01.01 Turn off Revision Notifications
    02 Example



    00 Overview

    This Best Practice describes the Revision Notification functionality in SoluDyne.

    01 Description

    Revision Notifications are automatically generated when a user checks in a document. Revision messages are put in the Workqueue of affected users. To remove Notification from Workqueue, user must sign the Notification out.

    Classes where revision notifications are sent out:

    1. Requirement
    2. Best Practice
    3. Local Practice
    4. Procedure
    5. Flowchart with Roles
    6. Activity

    Recipients: Users or employees are the Recipients of notifications, but the connection is usually indirect through Job Function and Role. Employees are associated with one or more Job Functions, which in turn can be connected to one or more roles.

    Owner/Responsible: Revision notifications are sent to the Owner and Responsible of the checked-in node. Both Responsible and Owner can be set to either an Employee or a Job Function. If a Job Function is selected, all associated Employees receive the notification message.

    Distribution Package: Revision notifications are sent to the Responsible of any distribution package containing the changed node. As with the Owner or Responsible on the node, the Responsible of a distribution package can be both an Employee and a Job Function.

    Flowchart with Roles: When a Flowchart goes through a Major Revision a notification message is sent to all Employees connected to one of the Roles on the Flowchart.

    Activities: When an activity is changed all Employees connected to the Role that the activity belongs to, receive a notification message in their Workqueue.

    Role Attachments: Changes to governing documentation also causes notification messages to be sent to Employees that are connected indirectly through Roles.

    The following two rules apply:

    any member of a Role will receive a notification when

      1.  Any descendant of any associated activity is changed.
      2. A linked node to a descendant of the activity, or a descendant of the linked node, changes.

    01.01 Turn off Revision Notifications

    By default Revision Notifications is turned on. Revision Notifications can be turned off by setting the Revision Notification class under System Access Control to not active (uncheck the checkbox) and clicking button 'Update Permissions' on the bottom of the page.

    Se B-11692 - System Access Control for more information on rights management in SoluDyne.

     

    02 Example

    New Revision Notifications are inserted into the user Workqueue.

      

    Workqueue containing Revision Notifications.

    1. Click on title Revision Notification, to reveal any outstanding Revision Notifications.

       

    1. Revision Notification section expanded, showing unsigned notifications. Click on a notification to open Revision Notification Form.

       

    1. The Revision Notification Form, showing the changed document inside a frame.
    2. After reading the notification, type in signature in Signature field. Hit Enter on keyboard or click save.

       

    1. The notification has now been signed out from the Workqueue. In this example there is now one less Revision Notification in the user's Workqueue.

    B-13303 - Configuration of Notifications for Notification Service

    Overview
    SoluDyne Notification Service is used for informing users about items in their workqueues via email. Notifications can be configured in SoluDyne Administration. WorkQueue Notification Steps and WorkQueue Notification Rules are used for this purpose. 

    Prerequisites
    The user is a member of the Admin group in SoluDyne.

    Description

    1. Log into SoluDyne and open the Expanding Menu.

       

    1. Click on System in the Expanding Menu.
    2. Select SoluDyne Administration.
    3. Open the Workqueue Notification tab in the right frame.
    4. Add a new Workqueue Notification Step by clicking on the corresponding link below the grid.
    5. A new row will appear in the Notification Workqueue Steps grid. Click on its icon for opening the newly created Step for further configuration.
    6. The Rebuild Notification Queue button is to be pressed when the Notification Service is installed for the first time. Do not click on it without a need.

     

    1. Select the Config Class that requires notification in Class.
    2. Save the form.
    3. Select a step from the Step dropdown list for a Workflow class or "N/A" for a class which is not a Workflow. Save the form.
    4. Add a WorkQueue Notification Rule by clicking on the corresponding link below the grid.

     

     A WorkQueue Notification Rule is used for setting notification parameters. It has the following fields:

    1. When - type of an event on which notification starts. Possible values are:
      - Arrived: notification starts immediately after an item appears in the user's workqueue
      - After: notification starts after some number of time intervals elapse
    2. Value - number of time intervals which should elapse before notification starts. This setting has sense only when "After" is selected in When
    3. Units - type of the time interval number of which is set in Value. This setting has sense only when "After" is selected in When. Possible values are:
      - Hours
      - Days
      - Weeks
      - Months
    4. Repeat - type of the time interval used in Recur Every. Possible values are
      - Never
      - Hourly
      - Daily
      - Weekly
      - Monthly
    5. Recur Every - number of times to repeat notification.
    6. Ends - type of an event on which notifications starts. Possible values are:
      - Never: notification never ends. It will be always repeated on the configured schedule.
      - After: notification ends after some number of time intervals
    7. Value - number of time intervals which should elapse before notification ends. This setting has sense only when "After" is selected in Ends
    8. Units - type of the time interval number of which is set in Value. This setting has sense only when "After" is selected in Ends. Possible values are:
      - Times
      - Hours
      - Days
      - Weeks
      - Months
    9. Recipients - a list of email addresses separated with ";" which notification is to be sent to. Leave this field blank if it is needed to send notification to all the users who get the item in the workqueues.

      

     It is a sample Rule which
       - sends notifications to all the users who get a Broadcast item in the workqueue immediately after the item arrives
       - repeats notifications every 3 hours
       - stops notifications after 10 days 

     

     It is a sample Rule that:
       - Starts sending notifications to em1234@soludyne.com about all the Broadcasts when 5 hours have passed since they arrive into the workqueues.
       - Repeats notifications every 2 days.
       - Never stops sending Notifications.

    Subscription

    B-12201 - Subscriptions

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes the My Subscriptions functionality in SoluDyne.

    01 Description

    In some occasions it can be useful to keep track of when a node or document is revised. Subscriptions allow users to be notified when a Process has been revised. The My Subscriptions list shows all nodes the User subscribes to. The My Subscription list can be found under General in the Expanding Menu.

    02 Example
     
     

    1. Open the Expanding Menu by clicking on it.

     
     
    The expanding menu has been opened.

    1. Click on General.

     
     

    1. Click on My Subscriptions.
    2. Click on Add links to add new Subscriptions.

     
     
    Navigate to a node to subscribe to. In this example:

    1. Click on Process.
    2. Click on a Main Process.

     
     

    1. Click on a Sub Process.
    2. Click on a Flowchart.

     

     

    1. After clicking once on the node to be linked, a link appears under Name. The Process has been added in the list of Subscriptions.
    2. It is possible to delete link if incorrect by clicking on delete button.
    3. Close the Dialog window when finished.

       
     

    1. The Subscription list shows all nodes the User subscribes to, in this example including the new Subscription 02 - Plan and Prepare Work Permit.
    2. It is possible to delete link if incorrect by clicking on delete button.

    The node subscribed to will now appear in the workqueue when there is a new revision.

    To remove a notification from the Workqueue, the notification for the subscribed node must be signed by the user. Open the node by clicking it in the Workqueue. A page containing the actual contents of the node, and a signature field will then be opened. Type the password in the signature field and click the Save button.

    Organization

    B-12144 - Category field on Job Function

    The different Job Function Category field lookup values have the following effect:

    Manager The Job Function is shown on top of the selected Organization Chart, as Project Manager in figure 1.  Furthermore selecting Manager will give the users that have this Job Function Manager permissions for the users that has the Job Functions in that specific Organization Unit.
    Staff The Job Function is shown to the left and right of the vertical line linking the Manager Job Function / Organization Unit shape to the bottom Employee Job Function / Organization Unit shapes in the Organization Chart, as Planner in figure 1.  
    Employee The Job Function is shown in the bottom rows of the Organization Chart. 
    Not Holding a Position The Job Function is not shown in the Organization Chart.

     

    Figure 1. Sample Organization Chart

    B-12145 - Employee and Job Function Connection

    00 Description
    01 Link from Employee to Job Function
    02 Link from Job Function to Employee
    03 Delete link

    00 Description
    This Best Practice shows the functionality of linking between employees and Job Functions.

    01 Link from Employee to Job Function

    The link between an employee and a Job Function can be created in the following manner when the node is in editing mode:

      
      

    1. Select add links or the link-button on the toolbar.
       

    02 Link from Job Function to an employee


      

    1. Select Add links, or the link-button on the toolbar.

     

    03 Delete link
    The link between and employee and a Job Function can be deleted by the following manners:

    a) Selecting the delete-button in the node it is being linked from.
    b) O
    pening the node by clicking on the link-button in the toolbar and deleting it.


    a) Selecting the delete-button in the node it is being linked from.


      
    b) O
    pening the node by clicking on the link-button in the toolbar and deleting it.

      

    B-12188 - View Process Ownership

    Overview

    The Process Ownership tab on Job Function can be used in order to view processes where Job Function is either Owner and/or Responsible.

    Prerequisites

    1. Job Functions must be set as Owner/Responsible for relevant Workflows.

    Description

      

    1. Klick on Organization in the SoluDyne Expanding Menu.
    2. Klick on relevant organization, e.g. Strat Corp.
    3. Navigate to and click on the job function, e.g. Operations - Coordinator.

      

    1. Klick on the Process Ownership Tab.

      

    1. The job function Operations - Coordinator is Responsible for the process 01 - Evaluate need for Work Permit. The job function is not Owner of any processes.

    B-12217 - Creating Organizations, Org. Units and Job Functions

    00 Overview
    01
    Prerequisites
    02 Description
    03 Example




    00 Overview
    This Best Practice describes the creation of an organization chart with organization units and job functions.


    01 Prerequisites
    Create or use existing Job Function Type Register. A new Job Function Type Register can be created by clicking the New button and chosing Job Function Type Register.

    • The Job Function Type is the title that is shown in the Organization chart

    • Job Functions can be used across several Organizations and Organization Units.

     

    02 Description
    Organization, organization unit, job functions can be created and set up in SoluDyne.

    03 Example


       

    1. Create an Organization by clicking the New button on SoluDyne Toolbar.
    2. Click new Register 
    3. Click new organization.


     

    1. Click OK.


     

    1. Navigate to page 2.


     

    1. Type Org. name.
    2. Fyll inn type. Fill out type
    3. Publish.


     

    1. Navigate to the created organization which exists under Organization in the expanding menu.
    2. Select new node.
    3. Select Organization Unit.


     

    1. Navigate to page 2


     

    1. Enter name.
    2. Enter type.
    3. Publish.


     

    1. Navigate to the created organization unit.
    2. Select new node.
    3. Click on Job Function.


      

    1. Enter Job Function Code 
    2. Enter Type
    3. Enter Category.
    4. Enter Title.
    5. Publish.
    • ''Stillingskode'' Shows the Organization
    • Type shows ''stillingstype''
    • Kategori viser posisjonen til stillingen. Category shows the position of the job function.




      

    1. Navigate to an employee.
    2. Enter the correct job function for the employee by using the tree. This can also be done by using Add Links.

     


      

    1. Publish. 

    B-12743 - Temporary Organization

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes how to use the temporary Organizations, Organization Units and Job Function in Org. Charts in SoluDyne.

    01 Description

    An Organization, Organization Unit or Job Function can be made temporary by selecting a predefined type for the corresponding shape in the Organization Chart.
     
    The shape types are:
    • "Shape Type8 White Temporary" for Organization
    • "Shape Type9 White Temporary" for Organization Unit
    • "Shape Type10 White Temporary" for Job Function

    02 Example

    How to make an Organization temporary:

    1. Open the Organization Chart for edit.
    2. Select the Organization shape in the Chart.
    3. Select "Shape Type8 White Temporary" in the Type field of the Properties window.
    4. Save the data. 

      
    Figure 1. A temporary Organization.

    B-12745 - Multiple Organization Chart Levels

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes how to enable multiple levels in Organization Charts in SoluDyne.

    01 Description

    It is possible to have expanded charts for Organizations and Organization Units.
    The default level  to which charts are expanded is controlled via the "Org Chart: Expanded Levels" system setting.
    Possible values are:
    • 0 (charts are not expanded)
    • any number from the 1 - 999 range. For example, "2" will result in showing 2 additional levels in an Organization Chart.

    It is also possible to specify an individual expansion level for an Organization or Organization Unit. It will override the value of the system setting. It is necessary to clear "Expanded Levels" field for a Chart to make it inherit the default value from the system setting (see Figure 1).

    A Chart with a large number of Organization Units and Job Functions may result in overlapping the Horizontal holder with shapes. Such a situation can be avoided by setting minimal distance between the top border of the chart and the topmost shape. It is specified in the "Org Chart: Vertical offset of the topmost shape" system setting (see Figure 2).

    02 Example

    How to set the expansion level for an Organization:

    1. Ensure that the "Org Chart: Expanded Levels" system setting is enabled.
    2. Open an Organization for editing
    3. Navigate to the Organization Chart.
    4. Click on an empty place in the Chart. The Chart properties will be displayed in the Properties window. 
    5. Set "Expanded Levels" to the needed value.
    6. Save the Organization.

      
    Figure 1. Specifying individual "Expanded Levels
    " setting for an Organization.

      
    Figure 2. Vertical offset of the topmost shape in an Organization Chart.

    B-13306 - Customization of Organization Unit Title on Organization Charts

    Overview
    This Best Practice describes how to customize Organization Unit title on Organization Charts in SoluDyne.

    Prerequisites
    User must have Administrator privileges to change SoluDyne System Settings.

    Description
    By default Organization Unit Manager Job Function is displayed as a Title for Organization Unit on Organization Chart. There are several System Settings to change the Title. All SoluDyne System Settings are described in 06.19 - SoluDyne System Parameters

    • PublishedShapeTitle. Default value is SHAPE. In case of TREE value the Tree Title of Organization Unit is shown on Organization Chart in Published mode. In case of SHAPE value the value depends on Org Chart: Organization Unit Name parameter.
    • EditableShapeTitle. Default value is SHAPE. In case of TREE value the Tree Title of Organization Unit is shown on Organization Chart in Edit mode. In case of SHAPE value the value depends on Org Chart: Organization Unit Name parameter.
    • Org Chart: Organization Unit Name. Default value is Manager. In case of Name value Organization Unit Title is displayed. In case of Manager value the Manager Job Function Title is shown. In case of several Manger Job functions only one is shown which is the first after alphabetical sorting. Note! This parameter is used only if SHAPETITLE parameter for Organization Unit Class is not overridden.

      

    1. Login in SoluDyne and open Expanding Menu. 
    2. Click on System. 
    3. Click on SoluDyne Administration.
    4. Open System Configuration Form.

      

    1. Find Org Chart: Organization Unit Name parameter in Grid. If there is no such parameter create a new one. Change the value to Name in case of Organization Unit Title should be displayed on Organization Charts.
    2. Make sure there is no parameters PublishedShapeTitle and EditableShapeTitle or there values are SHAPE.
    3. Click on Save button.
    4. Clear Server Cache to apply new parameters values.
    5. Log off and Log in again.

    Personnel

    B-11700 - Create New Employee User

    Overview
    Employee users are added as child nodes below an Employee Register or Employee Group directly from the tree. Group membership, password and status is controlled by administrators on the Access Administration tab.

    Prerequisites

    1. Must be logged in as a user that has permission to add new employees, and has access to the Access Administration form.
    2. There must already exist and existing Employee Register. See B-13211 - Example - Creating a new Employee Register.
    3. The current user must have permission to login as another user.
    4. Login validation must be set to Standard Login or NTLM to be able to log in as newly created user.

    Description

    Create new employee under Personell Register:

    1. Navigate to Personnel - Employee register e.g. Strat Corp.
    2. Right click and select New Node and Employee.
    3. Enter employee no, first name, surname, user name (Windows user name), email and any other available information in Employee Information tab. If, Employee No is not available then use user name. See figure 1.
    4. Select Job Function if Job Functions has been added to the organization chart.
    5. Open Access Administration tab and select user group and set a password. See figure 2.
    6. Save and publish.

     
    Figure 1 - Employee Information

    1. Click on the Employee Information tab to open the form.
    2. Verify that the Employee No field is mandatory.
    3. Fill in Employee No, First Name, Surname and User Name.
    4. Click Save on the toolbar.


     
    Figure 2. Access Administration

    1. Click on Access Administration tab.
    2. Verify that User Name is the same as entered in step 6.
    3. Verify that Status is set to Active.
    4. Select User Group.
    5. Change the password of the user according to B-98765 Change user Password.

    B-11794 - Image on Employee

    00 Overview
    This Best Practice describes how to modify an Employee's image in SoluDyne.

    01 Example

     

    1. Select Personnel in the Expanding Menu.
    2. Select an Employee Register under Personnel.
    3. Select an Employee. 

     

    1. Go to the Employee Information form and switch it into the Edit mode if it is published.

     

    1. The neutral image is displayed for an Employee if Gender is not selected.

     

    For selecting the default male image:

    1. Select Male in Gender.
    2. Save the form.
    3. The default male image will be displayed.

     

    For selecting the default female image:

    1. Select Female in Gender.
    2. Save the form.
    3. The default female image will be displayed.

     

    1. For adding a file with a custom image scroll down to the bottom and click on Add files.

     

    1. Click Browse.
    2. Select a file with image.
    3. Upload the file to SoluDyne.

     

    For specifying a custom image from a file:

    1. Select Image as picture source.
    2. Select the needed file in the drop-down list.
    3. Save the form.
    4. The selected custom image will be displayed.

     

    For deleting the current custom image and returning the default one:

    1. Select the empty value from the drop-down list.
    2. Save the form.
    3. The default image corresponding to the Employee's gender will be displayed.

     

    For specifying a custom image from a URI:

    1. Select URI as picture source.
    2. Type a URI in the source field.
    3. Save the form.
    4. The selected custom image will be displayed.

     

    For deleting the current custom image and returning the default one:

    1. Clear the URI source.
    2. Save the form.
    3. The default image corresponding to the Employee's gender will be displayed.

     

    For refreshing the current user image in the Workqueue gadget:

    1. Show the Gadget Panel by clicking on the arrow button in the top-right corner.
    2. Open the Gadget settings.
    3. Select Workqueue in the list of available gadgets.

     

    1. Expand the Gadget panel.

     

    1. Refresh the content of the Workqueue gadget by clicking on the Refresh button.
    2. The up-to-date image for the currently logged user will be displayed.

    B-12124 - Employee Forms

    00 Overview
    01 Description

    00 Overview

    This Best Practice describes how to fill in Employee Forms in SoluDyne. Also it explains what additional Print Reports are available when operating with Employees.

    01 Description

    SoluDyne Employee Forms contain all Information, related to some particular Employee. By default any SoluDyne User is able to see following Forms in Read Only Mode:

    • CV Form - represents Employee CV related Information. See B-12125 - Filling in the CV about how to fill in Employee CV. See B-12126 - Printing of CV about how to print Employee CV.

    Employee himself also see following extra Forms:

    • Employee Information - contains Generic Employee Information
    • Development Plan & Goal (Read-Only) - shows Employee Development Goal and Goal Contract Info
    • Competence (Read-Only) - shows all info about Employee Competences
    • Certifications (Read-Only) - shows all info about Employee Certifications
    • Licenses (Read-Only) - shows all info about Employee Licenses
    • Stamps (Read-Only) - shows all info about Employee Stamps
    • Courses (Read-Only) - shows all info about Employee Courses
    • GAP (Read-Only) - shows difference between current Employee Competences and the Competences, required from him by associated Job Function(s)
    • Password - allows User to change his/her Password, used for SoluDyne System. See B-12158 - Filling in Password  about how Employee can change a Password
    • Employees also have writeable access to standard CV Form

    Employee Manager are able to see following extra Forms:

    • Development Plan & Goal - contains Employee Development Goal and Goal Contract Info. See B-12151 - Filling in Employee Development Plan & Goal about how to fill in Employee Development Plan & Goal
    • Competence - contains all info about Employee Competences. See B-12152 - Filling in Competence about how to fill in Employee Competences 
    • Certifications - contains all info about Employee Certifications. See B-12127 - Apply for Approval & Authorization about how to manage Employee Certifications
    • Licenses - contains all info about Employee Licenses. See B-12153 - Filling in Licenses about how to fill in Employee Licenses
    • Stamps - contains all info about Employee Stamps. See B-12154 - Filling in Stamps about how to fill in Employee Stamps
    • Courses (Read-Only) - shows all info about Employee Courses.
    • GAP (Read-Only) - shows difference between current Employee Competences and the Competences, required from him by associated Job Function(s)
    • Employee Managers also have writeable access to standard CV Form

    Users of HR User Group are able to see following extra Forms:

    • Employee Information - contains Generic Employee Information
    • Development Plan & Goal - contains Employee Development Goal and Goal Contract Info. See B-12151 - Filling in Employee Development Plan & Goal about how to fill in Employee Development Plan & Goal
    • Competence - contains all info about Employee Competences. See B-12152 - Filling in Competence about how to fill in Employee Competences
    • Certifications - contains all info about Employee Certifications. See B-12127 - Apply for Approval & Authorization about how to manage Employee Certifications
    • Licenses - contains all info about Employee Licenses. See B-12153 - Filling in Licenses about how to fill in Employee Licenses
    • Stamps - contains all info about Employee Stamps. See B-12154 - Filling in Stamps about how to fill in Employee Stamps
    • Courses - contains all info about Employee Courses. See B-12155 - Managing Employee Courses about how to manage Employee Courses
    • GAP - shows difference between current Employee Competences and the Competences, required from him by associated Job Function(s)
    • Users of HR User Group also have writeable access to standard CV Form

    Users of Competence Admin User Group are able to see following extra Forms:

    • Employee (Read Only) - represents Generic Employee Information
    • Competence - contains all info about Employee Competences. See B-12152 - Filling in Competence about how to fill in Employee Competences
    • Certifications - contains all info about Employee Certifications. See B-12127 - Apply for Approval & Authorization about how to manage Employee Certifications
    • Licenses - contains all info about Employee Licenses. See B-12153 - Filling in Licenses about how to fill in Employee Licenses
    • Stamps - contains all info about Employee Stamps. See B-12154 - Filling in Stamps about how to fill in Employee Stamps
    • Courses - contains all info about Employee Courses. See B-12155 - Managing Employee Courses about how to manage Employee Courses
    • GAP - shows difference between current Employee Competences and the Competences, required from him by associated Job Function(s)

    Users of Quality User Group are able to see following extra Forms:

    • Employee (Read Only) - represents Generic Employee Information
    • Competence - contains all info about Employee Competences. See B-12152 - Filling in Competence about how to fill in Employee Competences
    • Certifications - contains all info about Employee Certifications. See B-12127 - Apply for Approval & Authorization about how to manage Employee Certifications
    • Licenses - contains all info about Employee Licenses. See B-12153 - Filling in Licenses about how to fill in Employee Licenses
    • Stamps - contains all info about Employee Stamps. See B-12154 - Filling in Stamps about how to fill in Employee Stamps
    • GAP - shows difference between current Employee Competences and the Competences, required from him by associated Job Function(s)
    • Employee Settings - allows to specify Employee Operator and to associate him/her with the Organization(s). See B-12156 - Filling in Employee Settings about how to manage Employee Settings

    Users of Admin User Group are able to see following extra Forms:

    • Employee Information - contains Generic Employee Information
    • Development Plan & Goal - contains Employee Development Goal and Goal Contract Info. See B-12151 - Filling in Employee Development Plan & Goal about how to fill in Employee Development Plan & Goal
    • Competence - contains all info about Employee Competences. See B-12152 - Filling in Competence about how to fill in Employee Competences
    • Certifications - contains all info about Employee Certifications. See B-12127 - Apply for Approval & Authorization about how to manage Employee Certifications
    • Licenses - contains all info about Employee Licenses. See B-12153 - Filling in Licenses about how to fill in Employee Licenses
    • Stamps - contains all info about Employee Stamps. See B-12154 - Filling in Stamps about how to fill in Employee Stamps
    • Courses - contains all info about Employee Courses. See B-12155 - Managing Employee Courses about how to manage Employee Courses
    • GAP -  shows difference between current Employee Competences and the Competences, required from him by associated Job Function(s)
    • Employee Settings - allows to specify Employee Operator and to associate him/her with the Organization(s). See B-12156 - Filling in Employee Settings about how to manage Employee Settings
    • Users of Admin User Group also have writeable access to standard CV Form

    When any of Employees Form are opened additional Print Reports are available in Print Menu, accessible via Print Button on Main Toolbar:

    • Course History - provides Course History Information related to selected Employee. See B-12159 - Printing Employee Course History about how to print Employee Course History
    • Employee Summary - provides Employee Summary Information. See B-12160 - Printing Employee Summary about how to print Employee Summary Information
    • Certification Report - Provides Detail Report regarding selected Employee Certifications. See B-12161 - Printing Employee Certification Report about how to print Employee Certification Report

    B-12125 - Filling in the CV

    Definitions
    Best Practice
    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how to fill in CV in SoluDyne.

    01 Description

    CV Form contains following fields to be filled in:

    • Education - grid field where Education related Information (Period, Place, Type and Description) to be documented
    • Work Experience - grid field where Work Experience (Period, Place, Type and Description) to be documented
    • Language - grid field where Language skills (Period, Language, Language Skill) to be documented
    • Course - grid field where passed Courses Information (Start, End, Course, Description) to be documented
    • Projects - grid field where Projects Information where this Employee participated in (Period, Place, Description) to be documented
    • Skills - free form text field where additional Skills to be documented
    • Other - free form text field where any Additional Information, related to this Employee to be documented
    • Attachments - grid field where any External Files related to this Employee may be attached
    • References - grid field where this Employee Reference Contacts Information (Last Name, First Name, Organization, Job Function, Mobile, E-Mail) to be documented

    02 Sample Session

     
    Fig.1:
    Employee CV Form

    B-12126 - Printing of CV

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how to print CV in SoluDyne.

    01 Description

    In order to print some Employee CV it is necessary to open required CV and to press Print This Form Item in Print Menu available under Print Button on Main Toolbar. CV may be previewed and layout adjusted if necessary in Print Preview Dialog before it is printed.

    02 Sample Session

     
    Figure 1 -
     Print This Form Item in Print Menu available under Print Button on Main Toolbar

     
    Figure 2 - Printed CV (Print Preview Dialog)

    B-12150 - Filling in Employee Information

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes how Authorized Users can fill in Employee Summary Info.

    01 Description

    Following User Types are authorized to fill in Employee Summary Info in SoluDyne:

    • Employees themselves
    • Members of HR User Group
    • Members of Admin User Group

    All of them can fill in Employee Summary Info on Summary Info tab. This form contains following fields to be filled in:

    • Employee Image - image field where Employee Photo to be added/changed
    • Employee No - text field where Employee No to be changed
    • First Name - text field where Employee First Name to be documented
    • Surname - text field where Employee Surname to be documented
    • User Name - text field where Unique User Name to be changed
    • Short Name - text field where Employee Short Name to be documented
    • Date of Birth - calendar field where Employee Date of Birth to be documented
    • Place of Birth - calendar field where Employee Place of Birth to be documented
    • Gender - selector field where Employee Gender to be documented
    • Employed Since - calendar field where Date when Employee was hired to be documented
    • Employment Type - lookup field where Employee Employment Type to be documented
    • Business Address - text field where Employee Business Address to be documented
    • City (Business) - text field where City part of Employee Business Address to be documented
    • Postal Code (Business) - text field where Post Code part of Employee Business Address to be documented
    • Country (Business) - text field where Country part of Employee Business Address to be documented
    • Job Function - lookup field where Main Employee Job Function to be documented
    • Cost Center - text field where Employee Cost Center to be documented
    • Location - lookup field where Main Employee Location to be documented
    • Phone Business - text field where Employee Business Phone to be documented
    • Mobile - text field where Employee Business Phone to be documented
    • Fax No - text field where Employee Fax No to be documented
    • E-Mail - text field where Employee E-Mail to be documented
    • Web - text field where Employee Web to be documented
    • Phone Private - text field where Employee Private Phone to be documented
    • Home Address - text field where Employee Home Address to be documented
    • City (Home) - text field where City part of Employee Home Address to be documented
    • Postal Code (Home) - text field where Postal Code part of Employee Home Address to be documented
    • Country (Home) - text field where Country part of Employee Home Address to be documented
    • Job Functions - grid field where additional Employee Job Functions can be edited
    • Comments - text field where any additional comments, related to selected Employee, may be documented
    • Links - grid field where any information in SoluDyne System, related to selected Employee, may be linked
    • Attachments - grid field where any external documents, related to selected Employee, may be attached

     
    02 Example

     
    Figure. 1 Employee Information Form

    B-12151 - Filling in Employee Development Plan & Goal

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how Authorized Users can fill in Employee Development Plan & Goal

    01 Description

    Following User Types are authorized to fill in Employee Development Plan & Goal in SoluDyne:

    • Managers
    • Members of HR User Group

    All of them can fill in Employee Development Plan & Goal on Development Plan & Goal tab. This form contains following fields to be filled in:

    • Development Plan - grid field where Employee Development Plans to be added 
    • Attachments - grid field where Employee Goals to be added

    02 Sample Session

     
    Fig.1: Employee Development Plan & Goal Form

    B-12152 - Filling in Competence

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how Authorized Users can manage Employee Competences

    01 Description

    Following User Types are authorized to manage Employee Competences in SoluDyne:

    • Managers
    • Members of HR User Group
    • Members of Competence Admin User Group
    • Members of Quality User Group
    • Members of Admin User Group

    All of them can manage Employee Competences on Competences tab. This form contains following fields to be filled in:

    • Show All Competences - flag field, specifying if all Competences available in the System will be shown in Competences grid (when checked on) or only currently specified for selected Employee (when checked off)
    • Show Certifications - flag field, specifying if Certifications will be shown in Competences grid (when checked on) or only Competences (when checked off)
    • Competences - grid field where Competence Levels to be selected

    02 Sample Session

      
    Fig.1: Competence Form

    B-12153 - Filling in Licenses

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how Authorized Users can document Employee Licenses

    01 Description

    Following User Types are authorized to document Employee Licenses in SoluDyne:

    • Managers
    • Members of HR User Group
    • Members of Competence Admin User Group
    • Members of Quality User Group
    • Members of Admin User Group

    All of them can document Employee Licenses on Licenses tab. This form contains following fields to be filled in:

    • Licenses - grid field where Licenses to be documented

    02 Sample Session

     
    Fig.1: Licenses Form

    B-12154 - Filling in Stamps

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how Authorized Users can document Employee Stamps

    01 Description

    Following User Types are authorized to document Employee Stamps in SoluDyne:

    • Managers
    • Members of HR User Group
    • Members of Competence Admin User Group
    • Members of Quality User Group
    • Members of Admin User Group

    All of them can document Employee Stamps on Stamps tab. This form contains following fields to be filled in:

    • Stamps - grid field where Stamps to be documented

    02 Sample Session

     
    Fig.1: Stamps Form

    B-12155 - Managing Employee Courses

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how Authorized Users can manage Employee Courses

    01 Description

    Following User Types are authorized to manage Employee Courses in SoluDyne:

    • Members of HR User Group
    • Members of Competence Admin User Group
    • Members of Admin User Group

    All of them can manage Employee Courses on Courses tab. This form contains following fields to be filled in:

    • Course Comments - text field where any Courses related additional info may be added
    • Requested Courses - grid field where Employee Requested Courses to be added

    02 Sample Session

     
    Fig.1: Employee Courses Form

    B-12157 - Access Administration

    Overview
    This Best Practice describes how Authorized Users can manage Employee System Access.

    Prerequisites
    Following User Types are authorized to manage Employee System Access in SoluDyne:

    • Members of Admin User Group.

    All of them can manage Employee System Access on Access Administration tab. This form contains following fields to be filled in:

    • User Name - text field where User Name may be changed.
    • User Group - lookup field where User Group for selected Employee may be specified.
    • Status - lookup field where User may be activated/deactivated temporary or permanently.

    Description

     

    1. In order to edit Employee System Access open Access Administration tab of Employee node.
    2. User name should be filled in and saved before any other changes are done.
    3. When User name on new or existing Employee is inputted and saved Change Password button becomes available on a form. Change Password dialog is shown when it is pressed.

     

    1. New password may be inputted into Enter new password text field.

     

    1.  New password to be inputted twice in order to avoid any typos.

     

    1. When both text fields contain the same password Change Password button becomes available.
    2. Password change is completed after Change Password button is pressed and Change Password dialog is closed.

    B-12158 - Filling in Password

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes how users can manage their System Password.

    01 Description

    All User Types are authorized to manage their System Password on Password tab. This can be done on the Access Administration-tab. 

    02 Example


      

    1. Select Change Password.

      

    1. Type in the new password and select 'Change Password'.

      

    The password is now changed.

    B-12159 - Printing Employee Course History

    00 Overview
    01 Description

    02 Sample Session

    00 Overview

    This Best Practice describes how to print Employee Course History in SoluDyne.

    01 Description

    In order to print some Employee Course History it is necessary to open this Employee Node and to press Course History Item in Print Menu available under Print Button on Main Toolbar. Course History may be previewed and layout adjusted if necessary in Print Preview Dialog before it is printed.

    02 Sample Session

     
    Fig.1: Course History Item in Print Menu available under Print Button on Main Toolbar

     
    Fig.2: Printed Course History (Print Preview Dialog)

    B-12160 - Printing Employee Summary

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how to print Employee Summary in SoluDyne.

    01 Description

    In order to print some Employee Summary it is necessary to open this Employee Node and to press Employee Summary Item in Print Menu available under Print Button on Main Toolbar. Employee Summary may be previewed and layout adjusted if necessary in Print Preview Dialog before it is printed.

    02 Sample Session

     
    Fig.1:
     Employee Summary Item in Print Menu available under Print Button on Main Toolbar

     
    Fig.2: Employee Summary (Print Preview Dialog)

    B-12161 - Printing Employee Certification Report

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes how to print Employee Certification Report in SoluDyne.

    01 Description

    In order to print some Employee Certification Report it is necessary to open this Employee Node and to press Certification Report Item in Print Menu available under Print Button on Main Toolbar. Employee Certification Report may be previewed and layout adjusted if necessary in Print Preview Dialog before it is printed.

    02 Sample Session

     
    Fig.1:
    Employee Certification Report Item in Print Menu available under Print Button on Main Toolbar

     
    Fig.2: Employee Certification Report (Print Preview Dialog)

    B-12302 - When a user is inactive/employee quits - Checklist

    Overview

    This Best Practice describes actions to consider when users/employees (hereby called user) are no longer active in SoluDyne. These actions are important to perform in order to ensure that no nodes remain in the inactive user's work queue.

    Prerequisites

    Access to the following reports/drilldowns:

    • DP101 - Request for Service / Overview - Activity
    • D120 Active Comments / Change Requests
    • Report: Status QIRs
    • Drilldown D113 Owner
    • Drilldown D114 Responsible

    Description

    A report/drilldown should be created on the items below to get an overview of all nodes which are located in the inactive user's workqueue. The nodes should be moved to an active user. 

     Item  Description   Link to Best Practice 
     Activities  Check which activities that are assigned to the user. This is done by creating a drilldown. Note: It is possible that activities are assigned to the user on a later stage, and therefore are forwarded to the user in the future.   B-13383 - Overview of Activities assigned to a user
     QIR  Check which QIRs that are present in the user's work queue. This is done by creating a drilldown.  B-13386 - Overview of QIR's assigned to a user

     Comment/Change

     Check which Comment / Change requests that are present in the user's work queue. This is done by creating a drilldown.  B-13384 - Overview of Comments / Change requests assigned to a user
     Owner  Check which documents that have the user (not role) as owner. This is done by creating a drilldown.  B-13381 - Find all documents where the user is the Owner
     Responsible  Check which documents that have the user (not role) as responsible. This is done by creating a drilldown.   B-13382 - Find all documents where the user is the Responsible

    If an employee quits, and there is no replacement for the position, the position can be set to Not hold a position in order to hide the position in the organizational chart, and move Owner/Responsible nodes to new position/employee for this position.

    B-13064 - Creating a Employee Register

    Best Practice
    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes how to add a Employee Register in SoluDyne.

    01  Description

    The employee register is used to store the organizations employee records. It is created by adding a new register.

    02 Example

      

    1. Click the New button.
    2. Select New Register.
    3. Select Employee Register.

    NOTE: Use the scroll bar to the right to scroll down if required.

     

      

    1. Click OK

     

    1. Fill in the required fields on the form.
    2. Save or publish.

    Required Fields:

    • Title - Short descriptive name

     

     

    1. Example of the new, published employee register.

    Planning

    B-12300 - Planning & Control - Activity

    00 Overview
    00.01 References

    01 Description
    01.01 User rights

    02 Example

    00 Overview


    This Best Practice describes the use of Activity functionality in SoluDyne. Activities are used in f.ex. QIS, MARK and Planning & Control.

    00.01 References

    For additional information, also see linked Best Practices under References - Links below.

    01 Description

    A set of actions designed to achieve a particular result. Activities are usually defined as part of Processes or Plans, and are documented in Procedures.

    Point

    Requirements

    Number

    Description

    1 Layout
    1.1 Font:
    Arial

    Use Clean HTML to remove HTML tags.
    2. SoluDyne Activity Process Fields
    2.1  Parent: 
    According to parent. Set automatically.
    2.2  Type: 
    According to Plan Type. Lookup Field. Mastervalues can be overruled according to B-11775 - Custom Lookup Values
    2.3

    Reference No: 
    Date and time

    2.4  Contact: 
    Refereance name. Value from Personell-, Customer- and Supplier register.
    2.5 Priority
    Set the correct priority; Low, medium, High and Max 8 hrs. Lookup Field. Mastervalues can be overruled according to B-11775 - Custom Lookup Values
    2.6 Progress
    2.6.1 Set the Progress to 0-25% when registered the first time. Lookup Field. Mastervalues can be overruled according to B-11775 - Custom Lookup Values
    2.6.2 Set to 25%-75% when starting work.
    2.6.3 Set to 75%-99% when signing for control.
    2.6.4 Set to 100% when signing for Approval.
    2.7 Planned Start
    Write the scheduled Start Date of the Activity.
    2.8 Planned End
    Write the scheduled End Date of the Activity.
    2.9 Actual Start Date
    Write the date the work on the Activity started.
    2.10 Actual End Date
    Write the date the Activity was completed.
    2.11 Est hours
    Estimated hours for performance of the Activity.
    2.12  Actual Hrs
    Shows actual hours registered on Activity. 
    2.13  Description of Time Deviation
    Description of time deviation. 
    2.14  Invoiceable? 
    Radio button
     

    Workflow: Set according to desired process. Steps Perform Change and Control are mandatory.

    • Originator - set automatically.
    • Evaluate or Classify
    • Analyze / Investigate
    • Review
    • Perform Change
    • Control
    • Approve
    • Verification
    • Delivery
    • Prepare Invoice - Shown if On Activity is clicked On. Mandatory.
    • Invoice - Shown if On Activity is clicked On. Mandatory.
    • Approve Invoice - Shown if On Activity is clicked On. Mandatory.
    • Follow up 
    2.15  Step: Show current step 
    3.  Activity Description 
    3.1  Phase:
    According to the phase the Activity is on. Lookup Field. Mastervalues can be overruled according to B-11775 - Custom Lookup Values
    3.2  ID
    According to standard Activity ID.  
    3.3  Title
    According to standard Activity. 
    3.4  Description:
    Give a description of the Activity. 
    3.5  Activity Summary
    Give a bried summary/Status.  
    4.  Activity Buttons 
    4.1  Activity 
    Show added or linked activities.
    4.2  Cost
    Show added Estimated Time and Material 
    4.3  Risk 
    Show added Risk Analysis
    4.4  Audit
    Show added Audit item 
    4.5 Comment
    When working on a Activity, the performance is documented by using the different Types below Comment.
    Publish the Comments.

    Types: See examples below. Lookup Field. Mastervalues can be overruled according to B-11775 - Custom Lookup Values

    4.5.1

    Change Log
    Choose the template for Change Log and fill out according to Requirements.

    4.5.2 Requirement
    Choose the template for Requirement and fill out according to requirements.
    4.5.3 Solution
    When finishing step 2 Perform Change, fill in a Solution in the Activity, and sign the Activity to Control.
    4.5.4 Deployment
    Description of deployment.
    4.5.5 Form
    When selecting a SoluDyne Template, the Type Form will be set automatically.
    4.5.6 Approve
    When the Activity is under approval, this field shall be filled out.
    4.5.7 Specification
    Choose the template for Specification and fill out according to requirements.
    4.5.8 Test Case
    Choose the template for Test Case and fill out according to requirements.
    4.5.9 Control
    When the Activity is under control, this field shall be filled out.

    Note! Set N/A in Control if no Controller is needed.
    4.5.10 Information
    All general information regarding work on Activity shall be documented in this field.
    4.6

    Communication
    Field used for logging e-mail and Telephone communications. Lookup Field. Mastervalues can be overruled according to B-11775 - Custom Lookup Values

    4.7 TimeSheet Button: 
    Log number of hours used on Activity.
    17 Add Links:
    Link all referenced documents to the Activity.
    18  Add Files:
    Add all relevant files

    01.01 User Rights

    To change user rights on activities, the following rights must be configured:

    Module Class   Type  Title 
    Workflows  903  Config Class  Activity 
    Workflows  903  Config Form  Activity 
    Workflows  903  Config Form  Action Activity 
     

    02 Example

     

    Figure 1. Example of Activity form.

    02.01 Activity - Workflow

    Example on default workflow for activity process.

    • The Pre-defined process 06.01 Evaluate, Classify and Investigate handles the following steps: Evaluate, Classify and Investigate.
    • The Pre-defined process 06.02 Perform Change handles the following steps: Perform Change, Control, Approve and Verification.
    • The Pre-defined process 06.03 Invoice handles the following steps: Prepare Invoice, Invoice and Approve Invoice

    Pre-defined process - Definition:

    A pre-defined process is a flowchart element. It is a separate, stand-alone process that is linked into another process.

    By placing a pre-defined process into a flowchart, one process is linked to another, existing process. 

     

    Figure 2. Workflow for Activity process with Pre-defined processes.

     

    Figure 3. Workflow for Evaluate, Classify and Investigate.

     

    Figure 4. Workflow for Perform Change.

     

    Figure 5. Workflow for Invoice.

    B-13029 - DP100 Request for Service / Overview - Plan

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes the DP100 Request for Service Overview - Plan functionality in SoluDyne.

    01 Description

    DP100 Request for Service Overview - Plan is a drilldown report that shows a list of plans registered in the system based on filtered criterias.

    Filteroptions:

    • Customer
    • Order
    • Step
    • Plan No
    • Plan Title
    • Priority
    • Progress
    • Performer
    • Start From/Start To
    • End From / End To

    Values in the filter and Drilldown report are from values set on the plans.

    02 Example

    Navigate to the Planning on SoluDyne Expanding Menu.

    1. Click on DP100 Request for Service Overview - Plan
    2. Add values in filter and press Filter button
    3. Click on required Filter result
    4. The result will show in the drilldown report in the window to the right

    B-13041 - Timesheet on Activity

    00 Oversikt
    01 Beskrivelse

    02 Eksempel

    00 Oversikt

    Denne Beste praksisen beskriver funksjonalitet for timeføring på aktiviteter i SoluDyne.

    Bruk av aktiviteter generelt er beskrevet i B-12300 - Bruk av Aktivitet

    01 Beskrivelse

    Det er mulig å bruke Timeliste-knappen på aktiviteter til å dokumentere og føre timer for arbeid brukt på aktiviteten. Standardvisning når en står i aktiviteten er inneværende uke, din egen timeliste og aktivitetens nåværende steg. Start dato, ansatt, steg og kalendervisning kan endres for å føre nye timer.

    02 Eksempel

    1. Klikk på Timeliste knappen.
    2. Start dato kan endres ved å åpne kalender og velge ny dato.
    3. Ansatt kan endres ved å søke eller navigere i treet.
    4. Det er mulig å endre hvilket aktivitetsteg en ønsker å føre timer på.
    5. Det er mulig å endre kalendervisning.
    6. Lagre etter timeføring.

    Standardvisningen viser inneværende uke, aktivitetetens nåværende steg og innlogget broker. Timelisten viser timer ført av bruker på steget som vises i 3). Timer ført av andre brukere/på andre steg vil kun vises ved å endre verdier i disse to feltene, eller bruke  tilgjengelige rapporter under Planlegging.

     

    Figur 1. Timeliste skjema for aktiviteter.

    B-13071 - Cost on Activity

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describe the functionality for Cost on Activity in SoluDyne.

    General use of activies is described in B-12300 - Planning & Control - Activity

    01 Description

    Pre-requisite: Before start using Cost on Activity, Product and Prices must be configured. For more information, see; B-12989 - Booking System Products

    It is possible to use the Cost-button on activities for documenting estimated time and material and actual time and material.

    02 Example

    1. Click the Cost-button.
    2. Add Estimate Time and Material.
      1. Set id, title, comment, items and amount.
      2. Publish node.
    3. Add Actual Time and Material.
      1. Set id, title, comment, items and amount.
      2. Publish node.

      

    Figure 1. Cost-button on Activity.

    B-13092 - DP101 Request for Service / Overview - Activity

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes the DP101 Request for Service Overview - Activity functionality in SoluDyne.

    01 Description

    DP101 Request for Service Overview - Activity is a drilldown report that shows a list of activities registered in the system based on filtered criterias.

    Filteroptions:

    • Customer
    • Order
    • Plan 
    • Step
    • Activity ID
    • Activity No
    • Activity Title
    • Priority
    • Progress
    • Performer
    • Start From/Start To
    • End From / End To

    Values in the filter and Drilldown report are from values set on the activities.

    02 Example

    Navigate to the Planning on SoluDyne Expanding Menu.

    1. Click on DP101 Request for Service Overview - Activity
    2. Add values in filter and press Filter button
    3. Click on required Filter result
    4. The result will show in the drilldown report in the window to the right

    B-13093 - DP102 Request for Service / Overview - Linked Activity

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes the DP102 Request for Service Overview - Linked Activity functionality in SoluDyne.

    01 Description

    DP102 Request for Service Overview - Linked Activity is a drilldown report that shows a list of activities registered in the system based on filtered criterias.

    The drilldown show activities that are linked to plans.

    Filteroptions:

    • Customer
    • Order
    • Plan 
    • Step
    • Activity ID
    • Activity No
    • Activity Title
    • Priority
    • Progress
    • Performer
    • Start From/Start To
    • End From / End To

    Values in the filter and Drilldown report are from values set on the activities.

    02 Example

    Navigate to the Planning on SoluDyne Expanding Menu.

    1. Click on DP102 Request for Service Overview - Linked Activity
    2. Add values in filter and press Filter button
    3. Click on required Filter result
    4. The result will show in the drilldown report in the window to the right

    Portfolio

    B-12236 - Information System Portfolio Modelling

    00 Oversikt
    01 Beskrivelse

    02 Eksempel

    00 Oversikt

    Denne Beste Praksisen beskriver hvordan man modellere informasjonssystem elementer i SoluDyne.  Dette kan gjøres som en del av APOS eller som en del av Application Portfolio Management. 

    01 Beskrivelse

    Gjør følgende steg for å opprette et Portfolioregister og modellere i dette:

    1. Lag et Portfolioregister.
      1. Klikk på ny knappen på SoluDyne knapperad.
      2. Velg New Register.
      3. Velg 1201 Portfolioregister.
      4. Systemet oppretter et nytt Portfolioregister
      5. Fyll ut Tittel, Eier og Saksbehandler
      6. Trykk på hjemknappen for å vise det nye registeret i Ekspanderende meny.
      7. Naviger til det nye registeret ved å gå under Portefølje knappen på Ekspanderende meny.
    2. Legg til en Portfoliogruppe.
      1. Velg et Portfolioregister.
      2. Høyre musklikk og klikk på New Node.  Velg 1221 Portfoliogruppe.
      3. Systemet legger til en ny Portfoliogruppe.
      4. Naviger til side 2 og fyll tittelfeltet på Portofoliogruppe skjemaet.
    3. Naviger til side 1 og begynn og modellere på Application Landscape Diagrammet.
    4. Etter som man har modellert kan man fylle ut skjemaet for hver modellert element.  Dette kan gjøres ved;
      1. Navigere i treet og klikke på det ønskede element for å åpne skjema og fylle inn.
      2. Høyre muse-klikke på tittelen til elementet og velge åpne i nytt vindu eller åpne i ny fane for å åpne skjema og fylle inn.
      3. Publisere diagrammet og klikke på elementene for åpne dem en etter en.
    5. Hvis det er brukt feil symbol, så kan dette endres ved å klikke på elementet i diagrammet og velge et annet symbol fra Type feltet i Properties boksen på høyre side.

    02 Eksempel

       

    Figur 1 Portfolioregister

      

    Figur 2 Portfoliogruppe

      

    Figur 3 Application Landscape diagram

      

    Figur 4 Eksempel på et nettverksdiagram

    B-12850 - Creating a Portfolio Register

    00 Overview
    01 Description

    02 Example

    00 Overview

    This Best Practice describes how establish a Portfolio Register in SoluDyne.

    01 Description

    The Portfolio Register is used to store information landscapes, applications and it system elements. Life Cycle information about the elements is stored in the Portfolio Register.

    02 Example

      

    1. Select the "New" button on the SoluDyne toolbar.
    2. Select "New Register".
    3. Scroll down and select "Portfolio Register".

     

    1. Fill-in the title.
    2. Add the Owner and Responsible.
    3. Add a description if required.
    4. Publish

     

    1. The Portfolio Register will be located under "Portfolio" in the SoluDyne Expanding Menu.

    Preferences

    B-12709 - Setting up user preferences

    00 Overview
    01 Description
    02 Example

    00 Overview

    This best practice describes how to find the change user preferences in the preference-window.

    01 Description

    In the Preferences window, the following actions can be done:

    • Choose to view requirements and best practice where only you are the owner, manager or by location.
    • Changing toolbar. 
    • Choosing which language to appear first on the nodes the user opens

    02 Example


      

    1. Click on information button on the SoluDyne menu.
    2. Click on preferences.


      

    Click on the save button after selecting the desired preferences.

    Properties

    B-10487 - Workflow Steps and Change Performer

    00 Overview
    01 Description

    02 Sample Session

    00 Overview

    This Best Practice describes the workflow steps functionality in SoluDyne.

    01 Description

    Performer on Workflow Item can be changed from Workflow Steps under Properties when standing on a 'QIR', '0197 Comment / Change' or any other Workflow Item.  

    02 Sample Session 

    Locate for instance the QIR, either using Search or any of the Report available

    1. Click on Info button on SoluDyne Toolbar and choose Properties
    2. Open Workflow Steps tab
    3. Choose Step and change Performer and then Save

    Note! Depending on the current user right setup. This task can usually only be performed by an Administrator.

     
    Figure 1. Workflow Steps

    B-12425 - Set Expiration Date

    00 Oversikt
    01 Beskrivelse

    02 Eksempel

    00 Oversikt

    Denne beste praksisen beskriver Forfallsdato funksjonaliteten i SoluDyne.

    01 Beskrivelse

    Forfallsdato kan settes på alle noder f.eks Flytskjema, Krav og Beste Praksis i SoluDyne. SoluDyne vil sende ut et varsel til arbeidskøen til Eier og Saksbehandler for den aktuelle noden samme dag som forfallsdato er satt.

    Mottaker av varsel kan åpne den aktuelle noden og sette ny forfallsdato. Varsel vil da forsvinne fra arbeidskøen.

    Forfallsdato settes på Egenskaper og Generelt under I-knappen på SoluDyne Verktøylinje.

    02 Eksempel

    Sette forfallsdato på flytskjema: '03 - Perform Audits':

    1. Åpne flytskjema '03 - Perform Audits'
    2. Klikk Edit
    3. Klikk på I-knapp på SoluDyne Verktøylinje
    4. Velg Egenskaper
    5. Velg Generelt
    6. Sett Forfallsdato. Se figur 1
    7. Klikk Save
    8. Lukk Egenskaper
    9. Klikk Publish på SoluDyne Flytende Verktøylinje

    Varsel vil nå bli sendt ut til arbeidskøen til 'Quality Processes - Owner' og 'Quality Processes - Responsible' den 30. mai 2014.

     
    Figur 1. Sett Forfallsdato.

    Recycle Bin

    B-12108 - Restore Deleted Nodes from Recycle Bin

    00 Overview
    01 Description
    02 Sample Session

    00 Overview

    This Best Practice describes the Recycle Bin functionality in SoluDyne.

    01 Description

    A deleted node can be restored from the Recycle Bin. Nodes in SoluDyne can be deleted if the user has sufficient rights. When a node is deleted, it will be moved from its original location into the Recycle Bin. It is not possible to delete a node that has been put into the recycle bin. This ensures that a node can never be permanently deleted or removed.

    Recycle Bin is accessible for administrators under SoluDyne Expanding Menu and General.

    02 Sample Session

    Restore deleted manual from Recycle Bin:

    1. Open Recycle Bin. See figure 1
    2. Click on Show Filter
    3. Fill in Date From and Date To 
    4. Click on Filter
    5. Click on Manual
    6. Choose the correct manual (if more than one manual has been deleted within given time frame)
    7. Click on Restore at the bottom of the form. See figure 2

     
    Figure 1. Open Recycle Bin

     
    Figure 2. Restore node

    Revision History

    B-12210 - Revision History

    Revision Control ensures that all changes are trackable in SoluDyne and is accessed through the SoluDyne Toolbar.

    01 Open Revision History

    Open the revision history by navigating to the node, click on the I-button on the SoluDyne toolbar and select Show Revision History. See figure 1.

     
    Figure 1 - Open Revision History dialog window.

    02 The Revision History Dialog Window

    The revision history lists all revisions on the current node. Each revision lists the following:

    1. Link to the revision
    2. Title of the revision
    3. Date and time of revision
    4. Revision number
    5. Revision author

    Each revision also contains a link to a difference, showing the changes performed in that revision. See figure 2.

     
    Figure 2 - Revision history

    To open a particular revision, click on the icon in the left margin. This will open a new window or tab showing that particular version.

    03 Track Changes

    To see changes, click on the Track Changes link on the right side. This will open a new window or tab showing the changes done in that revision. Any changes are marked in red or blue. Content marked as red is content that has been removed and blue marks content that has been added. See figure 3.

     
    Figure 3 - Showing differences between two revisions

    04 Node Status

    The current status of the node is available on the Status tab. This form contains the following information:

    1. Title - the current title of the node.
    2. State - the current state of the node.
    3. Rev Author - If the state is not Published, this contains the name of the user who has locked the node.
    4. Next Revision - The revision number that will be given to the next revision.
    5. Locked Date - The date the author locked the node for editing.

     
    Figure 3 - Node status

    Revision and Change Management

    B-12283 - Minor Change: Publish without Owner Approval

    Overview

    This Best Practice describes the Approval functionality in SoluDyne.
    Minor Change: Includes all changes that do not require Approval from the Owner. A Minor Change can be correcting spelling, layout or small changes to the content without changing the meaning of the content.

    Prerequisites

    Requires that Show Publish Dialog is selected for at least one Class. See B-12285 - Change Management: System Admin Setup for more details.

    Description

     

    1. Click on the Publish Button.

     

    1. Fill in Comment Field outlining changes made.
    2. Select Minor Revision.
    3. If users shall be informed of the change or trained before the Node is published, check off the Requires Implementation Checkbox. Note! Checkbox is disabled for changes when Implementation is mandatory or is not used.
    4. If signature is required, fill in the Signature Field with the correct password. Note! Only available if signature is mandatory. In this case, the button Publish changes will be greyed out until the User has written his or her signature. 
    5. Click on the Publish Changes Button. Note! The text changes into Send for Approval, Send to Implementation, Publish Changes when approval or implementation should be performed before publish.
    6. The system will publish the node or send it to Implementation. Note! In case of required Signature and invalid password was typed in the Publish Dialog appears again after reload.

    B-12284 - Major Change: Publish with Owner Approval

    Overview

    This Best Practice describes the Approval functionality in SoluDyne.
    Major Change: Includes all changes that must be approved by the Owner before publishing. A Major Change is change in meaning of the content.

    Prerequisites
    Requires that Approval and Implementation is set to either Optional or Required and that Show Publish Dialog is selected. See B-12285 - Change Management: System Admin Setup for more details.

    Description

     

    1. Click on the Publish button when all changes are completed. 

     

    1. Fill in Comment Field outlining changes made on Publish Dialog.
    2. Select Major Revision.
    3. If Owner Approval is not mandatory, check off in the Requires Approval Checkbox. Note! Checkbox is disabled for changes when Approval is mandatory or is not used.
    4. If users shall be informed of the change or trained before the Node is published, check off the Requires Implementation Checkbox. Note! Checkbox is disabled for changes when Implementation is mandatory or is not used.
    5. If signature is required, fill in the Signature Field with the correct password. Note! Only available if signature is mandatory. In this case, the button Publish changes will be greyed out until the User has written his or her signature.
    6. Click on the button that reads Send to Approval. Note! The text changes into Send for Approval, Send to Implementation, Publish Changes when approval or implementation should be performed before publish.
    7. The system sends the node for Owner Approval. Note! In case of required Signature and invalid password was typed in the Publish Dialog appears again after reload. 

    B-12285 - Change Management: System Admin Setup

    Overview

    In SoluDyne the Change Management Functionality can be configured to suit the customer's needs. It is possible to independently configure approval, implementation and publish dialog.

    The revision settings are set per Class and consist of four settings as described in the sections below.

    Approval

    Sets the approval level:

    1. Not in use - no Approval is required before changes are published.
    2. Optional - the user can choose to send the change for approval or not.
      NOTE: Requires that the Show Publish Dialog is option is selected.
    3. Required - node will be sent to Approve before changes are published.

    Implementation

    Sets the implementation level:

    1. Not in use - no Implementation is required before changes are published.
    2. Optional - the user can select to send the change for implementation or not.
      NOTE: Requires that the Show Publish Dialog is option is selected.
    3. Required - node will be sent to Implement before changes are published.

    Show Publish Dialog

    When show Publish Dialog is checked, the publish dialog is shown to the user when they click on the publish button. In the Publish Dialog the user will be able to fill in an optional revision comment. This comment will become part of the revision and will show in the revision history.

    Requires Signature

    When Requires Signature is checked the user is required to sign the change with their password before being able to publish.

    NOTE: This setting will only have effect when the Show Publish Dialog flag is checked.

    Prerequisities

    1. Must be logged in as Administrator.

    Description

    System Wide Revision Settings:

     
      

    1. Open the SoluDyne Expanding Menu and click on System.
    2. Click on SoluDyne Administration.
    3. Click on the Revision Settings Tab.

     
     

    1. Set the revision settings as required.  Note! There is a possibility to set up settings per Module which is have differ from Class color, as an example Handbooks & Manuals. Show Publish Dialog and Require Signature Module checkboxes are selected if all Classes in the Module have appropriate setting. Approval and Implementation level Modules selectors should be used only for changing settings and do not show any cumulative value.  
    2. Click on Save. 
    3. Log out and log in to apply changes.

    B-12296 - Approve Change

    Overview

    This Best Practice describes the Approval functionality in SoluDyne.

    Users can Edit content in the system. For major changes, approval by Owner may be required or necessary. Approval is performed by Node's Owner, and implementation is performed by the change author.  

    Prerequisites

    •  Approval should be enabled in revision settings for at least one Class using B-12285 - Change Management: System Admin Setup
    •  User must be an Owner of the Node with required Approval

    Description


     

    1. Login in SoluDyne and open Expanding Menu.
    2. Click on General.
    3. Click on Workqueue.
    4. Click on Approve Change.
    5. Click on Node to Approve.

     

    1. There are Node's Path, Revision Author and Revision Date on the top of the Approve Change Form.
    2. Show changes done by looking at the information frame in the Approve Change Form. 

     

    1. Read revision comment from the author.
    2. All previous Approved NOT OK comments are shown before Revision Comment.
    3. Fill in Approval Comment.
    4. Approve Yes or No.  
    5. Fill in Signature.
    6. Click on Save button or press Enter on keyboard. 
    7. There are several ways in case of Approved OK:
      1. Publish if there is no Implementation required.
      2. Appear in Author's Workqueue for Implement.
    8. In case of Approved NOT OK the Node appears in Author's Workqueue in Approved NOT OK list.

    B-13268 - Revision Field

    Overview
    This Best Practice describes the Revision Field functionality in SoluDyne.

    Revision Field is read-only Field displayed on some Forms and contains current revision number or the next revision number:

    • In case of there is no Publish operations performed on Node Revision value is 0.1
    • In case on Node was created in scope of 0197 Comment / Change process revision number is 1.0
    • In case of Node is Published and the visible Form is read-only the latest Revision number is displayed
    • In case of Node is in Edit mode the next revision number is displayed
      • In case of Minor change the number will be increased after point delimiter. For example initial revision was 0.10, after Minor change it will be 0.11.  B-12283 - Minor Change: Publish without Owner Approval
      • In case of Major change the number will be increased before point delimiter and 0 will be after point delimiter. For example initial revision was 0.10, after Major change it will be 1.0. Note! Changes performed in scope of 0197 Comment/Change process are Major. B-12284 - Major Change: Publish with Owner Approval

    Prerequisites
    N/A

    Description

     

    1. Revision number is displayed with revision Date for Published Node.

     

    1. The next revision number is displayed without date in Edit mode.

    B-13287 - Reject a Comment/change

    Overview
    This Best Practice describes how to reject an incoming Comment/Change.

    Prerequisites

    1. The Comment/Change should be on Step A-3 Evaluate Comment / Request Change - Responsible or A-4 On Hold, as described in B-12195 - Comment/Change - Responsible.
    2. The user should be responsible for the current Comment/Change Step.

    Description

     

    1. Open the Workqueue. 
    2. Click on 0197 Comment/Change.
    3. Click on the requested Comment/Change to reject.

     

    1. Ensure that the opened form is on step A-3 Evaluate Comment / Request Change - Responsible. In case the Comment/Change is on step A-4 On Hold go to the next step.
    2. Describe reason for rejection in the Comment Responsible Field.
    3. Tick off for Reject in the Evaluation Field.
    4. Fill in the Signature Field.
    5. Click on Save button on Toolbar or press Enter to send the form to the next step.

       

    1. Ensure that the opened Form is on step A-4 On Hold.
    2. Fill in the Suggested Change Field.
    3. Tick off for Reject in the Send for Processing Field.
    4. Fill in the Signature Field.
    5. Click on Save button on Toolbar or press Enter to send the form to the next step.

       

    1. The Originator of the change request will receive a A-3b Receipt after Reject is performed.
    2. The comment from Responsible is displayed in Suggested Change / Corrective Action Responsible.
    3. Reject is displayed in Status Field.
    4. Fill in Signature Field to remove this item from Workqueue.
    5. Click on the Save button on Toolbar or press Enter to send the Comment/Change out of the workqueue.

     

    1. All information regarding the status on 0197 Comment / Change is available in D123 All Comments / Change Request Drilldown. To open it click on Expanding menu.
    2. Click on Process.
    3. Click on D123 All Comments / Change Request.
    4. Click on Show Filter link to display filter and fill in the table using known data.
    5. All completed 0197 Comment/Change are available on 0197 Comment / Change Step. Click on step label to show all detail in grid.
    6. Comment / Change is on A-3b Receipt Step until the Originator has signed this Step. Click on step label to show all detail in grid.
    7. Grid with details is displayed in D123 ALL COMMENTS / CHANGE REQUEST grid.

    B-13292 - Approve of several Nodes

    Overview
    This Best Practice describes the Approval functionality in SoluDyne in case of several Nodes should be quickly Approved.

    In case of only one Node should be Approved check B-12296 - Approve Change

    Prerequisites

    • Approval should be enabled in revision settings for at least one Class using B-12285 - Change Management: System Admin Setup
    • User must be an Owner of the Nodes with required Approval
    • Class Approve changes Dashboard should be Active

    Description

     

    1. Log in into SoluDyne and Open Expanding Menu. 
    2. Click on General. 
    3. Click on Approve changes Dashboard.
    4. Approve Changes Form appears.
    5. All Nodes required Approval are displayed in the Grid.

     

    1. Click on required action for each Node.
      1. In progress value is default. Approve will not be performed for this option.
      2. Approved. The Node will be Approved OK
      3. Not Approved. The Node will return to Author to continue editing. 
    2. Click on Save button to perform all selected operations. 

    B-13293 - Implement Change

    Overview
    This Best Practice describes the Approval functionality in SoluDyne.

    Implement functionality can be used in case of several situations. For example:

    • Users shall be informed of the change 
    • Users shall be trained before the Node is published
    • Publish shell be performed later
    • File renditions should be added before the Node is Published, for example PDF file with the same content should be added.

    Prerequisites

    1. Requires that Implementation is optional or required for at least one Class. See B-12285 - Change Management: System Admin Setup for more details.
    2. At least one Node is send to Implement.

    Description

     

    1. Login in SoluDyne and open Expanding Menu. 
    2. Click on General. 
    3. Click on Workqueue.
    4. Click on Implement Changes in Workqueue.
    5. Click on Node to Approve.

     

    1. Implement Changes Form is opened. 
    2. Information regarding current Node status is displayed:
      1. Node's path.
      2. Revision Author.
      3. Approver name if Approve was performed.
      4. Revision Number.
      5. Revision date.
      6. Approved date if Approve was performed.
    3. The latest Node's content is displayed in the information frame in the Implement Change Form.

     

    1. Click on Open Node button in case of full Form required. Note! Node is in read-only view, only upload renditions is available for File Nodes.
    2. Fill in Signature Field with the correct password.
    3. Click on Save button to Implement Node. Node will be Published and the new content will be visible for all Users. Note! In case invalid password was typed in the Form will be reloaded.

    Search

    B-12337 - Search Functionality

    Overview

    The search functionality can be used to search content in SoluDyne and allows filtering based on where the Nodes are found, for example by searching only Handbooks & Manuals. It is also possible to limit search to titles only.

    The search functionality is not "case sensitive". This is Best Practice in order to reduce errors caused by use of uppercase and/or lowercase letters among the users. It is possible to use the star * in combination with space when performing a search.

    A search for SAT will generate hits for all words with the letter sequence SAT.
    A search for * DOCUMENTATION * will generate hits where the letters DOCUMENTATION are standing alone, e.g. "Requirement for Documentation".
    A search for * DOCUMENTATION* will generate hits for words starting with the letters DOCUMENTATION and where additional letters follow, e.g. "Establish Documentation-Plan".
    A search for *DOCUMENTATION * will generate hits for words ending on DOCUMENTATION, e.g. "Test-Documentation".

    Note that the hit may also apply for the content in e.g. a Requirement.

    Prerequisities

    1. N/A

    Description

     

    1. Click on the Search-icon.
    2. Click on Search all.

      

    1. Type the relevant search word in the Enter Value field, e.g. Risk.
    2. Tick off Search in Titles Only in case of searching only in Node's Titles.
    3. Tick off required Modules or tick off the last one Check all to search anywhere in SoluDyne.
    4. Click on the Search button.
    5. Hits are available below Search Results.

    B-12434 - Search for a Work Process

    Overview

    This Best Practice describes the how to Search for a Work Process in SoluDyne.

    Description

    Search for Work Process using Search button on SoluDyne Toolbar.

    Example

      

    1. Click on the Search button.

    2. Select Search All from the menu as shown.

      

    1. Enter the Search Value: Plan and Prepare.
    2. Check off as shown, Search in Titles Only.
    3. Check off the Process check box in Modules.
    4. Click the Search button.

      

    1. Click on the process searched for.


      

    1. After clicking on the process, the new page shown is the Search result.

    B-12435 - Search for a Requirement

    Overview

    This Best Practice describes the how to search for a Requirement in SoluDyne. 

    Description

    Use search functionality to search for Requirements.

    Example

     

    1. Click on Search Button on Toolbar.
    2. Click on Search all.



     

    1. Enter Search value. Type in text.
    2. Check off the Handbooks and Manuals check box in Modules.
    3. Click the Search button.

     

    1. Click on the Search result. In this example K-14860.

     
     

    1. Figure showing Search result K-14860. 

    Sectioning

    B-11801 - Show Sectioned Document on Section node

    To have a sectioned document show as default on a Section the following steps must be done:

    1. Put the Section in Edit mode.
    2. Hide the Table of Content form by clicking on the open eye on the floating toolbar.

       
      Figure 1a - Click on the eye to hide the form.

       
      Figure 1b - The eye is closed to show that the form is hidden when published.
    3. Open the Section form and create the sectioned document. This can be done manually by using Insert Section or Insert section list from the context menu. See also note 1 below. 

        
      Figure 2 - Example of sectioned document.
    4. Publish the Section when completed.

        
      Figure 3 - The final result when published. Note that only the Section form is visible.

    When users open the Section from the tree they will now see the sectioned document instead of the Table of Content.

    NOTES:

    1. It is recommended that the auto-generate sectioning is activated to ensure that the sectioned view is always updated with new governing elements.

       
      Figure 4 - Right-click inside the HTML Editor and click on Auto Generate Sectioning to toggle this auto-generate sectioning functionality.
    2. The actions described in this Best Practice needs to be repeated for all levels where the sectioned document is to be shown.

    B-12202 - Sectioning

    00.00  Definitions
    01.00  General Description
    02.00  Inserting Sections
    0
    3.00  Section Header
    04.00  Expand and Collapse Sections
    05.00  Changing the Order of Sections
    06.00  Section Appearance in the Tree
    07.00  Drag-and-Drop from Section to Tree
    08.00  Drag-and-Drop from Tree to Section
    09.00  Section in Section
    10.00  Publishing Sections
    11.00  New Empty Section
    12.00  Editing Sections
    13.00  Automatic Sectioning
    14.00  Re-Using Sections
    15.00  Setting a Section to Be Visible at All Time
    16.00  Filtering of Sections

    0.00  Definitions
    Sectioning: The process of dividing/organizing a document into Sections.  
    Section: A window to information that exists on a document in the system.
    Child: A node that belongs to another node.
    Parent: A node that owns other nodes.
    Edit/Publish: Changing the state of a document/node. When a document/node is in the editable state, it can be modified.

    It is not possible to do any modifications to a document/node that is in published state.

    1.00  General Description
    A section can be thought of as a window to information that exists on a different document/node somewhere else within the system.
    Sectioning makes it possible to divide/organize a document into Subsections. The order of the sections can be changed by dragging up and down within the containing document.

    Note: Please note that bilinguality together with Sectioning is currently not supported in SoluDyne.

    2.00  Inserting Sections
    Open the Document that needs sectioning. The document/node can be a Section, a Requirement, a Best Practice or any other SoluDyne document/node, that has been configured to support sectioning.

     
    Figure 1 - Text in HTML-fields can easily be sectioned by highlighting the part of the text that is to become a section.

      
    Figure 2 - Right click the marked text and select Insert Section -> new and the type of section to create from the popup-menu.

    A new node containing the selected text is created and a section referencing this, is inserted at the current position. Type a name for it in the field to the right; it will be assigned a name by default based on the section type. If required, the User can also type in an ID for the new section. This can be done in the second text-field in the section header.

      
    Figure 3 - ID and name for the Section is typed in.

    Save the section by clicking the Save button. Please note that each section must be published separately.
    Selecting Insert section -> Child will let the User insert a section referring to one of the child-nodes of the current node in the tree.

      
    Figure 4 - Inserting a Child Section.

    3.00  Section Header


    Figure 5 - Inserting ID and name for the Section Header.

    Icon for dragging the section up and down; reordering of sections.
    Icon to expand/collapse the content of a section.
    Type of section. This icon will be the same as the one found for this section in the tree.
    If the section is a link to a node found somewhere else in the tree, a small arrow in the lower left corner of the icon will show to indicate this.    
    Identificator of the underlaying document/node.
    Name of the section.

    4.00  Expand and Collapse Sections  
    Sections are normally shown in a collapsed state. This means that to be able to see the contents of a section, it must first be expanded. Clicking the plus sign in the section header expands the section:

      
    Figure 6 - The plus and minus signs will expand and collapse the Sections.

    To collapse the section again, simply click the minus sign.

    The Expand All and Collapse All icons on the top of the field works as shortcuts for expanding or collapsing all sections in a field in a single operation.

    5.00  Changing the Order of Sections
    The order of sections within a document can be arranged by dragging the section icon found in the left margin. Click and hold down the mouse button while moving the section either up or down,
    and release button when the section is in the appropriate position.

      
    Figure 7 - A marker line indicating the new position of the section will be visible while dragging.

    6.00 Section Appearance in the Tree
    Sections will appear as individual nodes in the Tree. The document/node they were created within, will be their parent node.

     
    Figure 8 - Sections accessed from a Tree.

    7.00  Drag-and-Drop from Section to Tree.
    The User can drag sections that have been published onto the tree in the Expanding Menu. This allows users to move a node/section, create links to a node/section or append documents as sections to other nodes. To drag a section onto the tree, click on the icon in the section header and drag it over the tree without releasing the mouse button. When the mouse is over a node in the tree, the cursor will change to indicate that the selected section can be dropped onto it. When the mouse is released, a popup will appear, allowing the user to select what action to take. 

    Move here - Selecting Move here will move the underlying node; not the section, to the given location; it will become a child of the node it was dropped on to.

    Create link - The Create link selection is used to create a link from the node the section was dropped on, to the underlying node. Please note that links will not be visible until the linked node has been published.

    Append section - Choosing Append section will not be applicable for all nodes; not all classes have a section enabled HTML Editor Field. When it appears it can be used to append the section to the end of the section enabled HTML Editor Field.

     
    Figure 9 - Move here, Create link and Append section can be selected by right clicking a Section.

    8.00  Drag-and-Drop from Tree to Section

    Nodes in the tree can be dragged into an HTML Editor Field by right-clicking the wanted node in the tree, holding the button while dragging, and releasing it when over the HTML Editor Field where the node is to be inserted.

      
    Figure 10 - Left-click the Insert as Section option, and a new section will be created based on the node dragged in.

     
    Figure 11 - The new Section is inserted.

    9.00  Section in Section
    If you want to section your docment/node further, follow the same procedure as for creating the top document.  Select the text to be inserted into the section, right click and click on the type of section you want to create.

     
    Figure 12 - Multiple Sections are inserted.

    10.00  Publishing Sections
    Each and every section reference has a document/node that needs to be published separately. 

    11.00  New Empty Section
    To create a new empty section, right click on the position in the text where you want to insert the new empty section.  Click on the section type and a new empty section is created 

    12.00  Editing Sections
    Editing of sections follows the same procedure as for any HTML Editor field, which can be edited with formatted text, images and film. The editing and formatting is controlled by using the SoluDyne Floating Toolbar in the floating toolbar at the bottom, or by right clicking in the SoluDyne HTML Editor Field. 

    13.00  Automatic Sectioning
    Automatic Sectioning can be used to automatically generate Sections in an HTML Editor Field from the child nodes of the document. To turn on Automatic Sectioning, select the Auto Generate Sectioning from the pop-up window.

     
    Figure 13 - Auto Generate Sectioning can be selected from the pop-up menu.

    The first level of child nodes will now turn up as individual sections within the Editor Field.

     
    Figure 14 - When Automatic Sectioning has been activated, it will automatically insert any child node as a section into the HTML Editor Field. 

    It is not possible to perform any manual editing on the HTML Editor Field as long as Automatic Sectioning is turned on. To deactivate Automatic Sectioning, click the Auto Generate Sectioning item again.

     
    Figure 15 - Auto Generate Sectioning is deactivated.

    14.00  Re-Using Sections:  Using this feature is not recommended, because it is easy to make mistakes and thereby not getting the expected result!
    Once you have created a section you can use the same section in other documents/nodes.  To re-use/link to an existing section, highlight the section you want to re-use by clicking on the section, and then pressing CTRL+A. 
     
      
    Figure 16 - Copy the section by pressing CTRL+C.  Go to the node item/document where you want the linked section to appear and paste the section by pressing CTRL+V, or right-click and select Paste. 


      
    Figure 17 - Changes made to the section, will appear in all the linked sections.

    15.00  Setting a Section to Be Visible at All Time
    By right clicking on the Section, the User can choose to make the content of a section to be visible at all time. It will not be possible to collapse or expand a section that has this status. 

      
    Figure 18 - The User can also choose to hide the title/header of a section that has been set to be Always Visible. 

      
    Figure 19 - Checking the Hide title option, hides the title/header of a section. 

    16.00  Filtering of Sections
    Filtering of sections can be used to prevent a section e.g. Requirement, Local Practice or Best Practice from being visible in a tree or section containing the node. This is especially useful if there exists two or more copies of a tree/register/manual, that contain different Local Practices. By using filters, depending on its use, the visibility for the end-user of a Local Practice can be turned on and off.

    In the following example, a Local Practice is linked up with two Processes within the System.

       
    Figure 20 - By highlighting the second checkbox, the User can hide the Local Practice from the Second Process.

     
    Figure 21 - The Section that has been filtered out, will not be visible when viewing the published document.

    If however the document containing the filtered section, is in the editable state, the section will show. This section can not be edited as a result of the filtering.

     
    Figure 22 - In the editable state, the section will show.

    System Filter

    B-12719 - System Filter Functionality

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes the System Filter functionality in SoluDyne.

    01 Description

    The System Filter provides convenient navigation in SoluDyne. When the System Filter is active, the nodes which do not comply with the specified criteria are grayed. Usually it helps to focus on processes or documentation which is needed now, keeping the overall structure visible as well.

    The System Filter is based on Multiple Choice fields being set for the nodes. For each supported field on the node, there is a corresponding field on Filter form. When the System Filter is active and all its handled fields have intersections with corresponding fields on a node, the node is shown as usual, otherwise the node is grayed.

    Currently, there are three fields being supported by the System Filter. They are: Process Group, Business Area and Location. All of them can be specified for the node via Properties dialog; usually, Location can also be specified directly on the node's form.

    The fields which are handled by the System Filter can be configured via the SystemFilterOptions in System Configuration available under SoluDyne Administration. The format of the setting is:

      <Field ID 1>|<View Name 1>|<View Column Name 1>;...;<Field ID N>|<View Name N>|<View Column Name N>

    The full string enabling all three supported fields is:

    14340002|WSTREEVIEW_PROCESSGROUPS|PROCESSGROUPID;14340003|WSTREEVIEW_LOCATIONS|LOCATIONID;14340005|WSTREEVIEW_BUSINESSAREA|BUSINESSAREAID

    02 Example

    Consider the following scenario.

    The System Filter is configured to support Process Groups and Locations with the following SystemFilterOptions setting:

    14340002|WSTREEVIEW_PROCESSGROUPS|PROCESSGROUPID;14340003|WSTREEVIEW_LOCATIONS|LOCATIONID

    There are three nodes on a Process with the following settings.

    Node Locations Process Groups
    Flowchart 1 - Stavanger, 3 - Bergen Internal Processes
    01 - Activity  1 - Stavanger, 2 - Oslo External Processes
    W-509 - Subprocess 2 - Oslo, 3 - Bergen, 4 - Trondheim External Processes

    In this case, various System Filter selections give the following results.

    Selection 1 Result 1


    Selection 2  Result 2 


    Selection 3 Result 3

    Templates

    B-12205 - Templates

    Overview

    Templates with default values are used when it is identified that the same entries tend to be entered on some or all the fields on a form. Using default values on forms, saves the user from filling inn the same values each time. A template with default values can be created from the system templates. Such templates can be created for all system templates in SoluDyne.

    System templates are created in Sections in a Template Register in Handbooks & Manuals. The system templates are then made into own templates with standard values. These templates can be opened via SoluDyne Expanding Menu or via the New button directly on a form.

    Prerequisities

    1. Must be logged in as a user that has permission to create and edit new registers with child nodes.

    Description

    Creating a new Template Register:

     

    1. Click on the New-button on the SoluDyne Toolbar.
    2. Click on New Register.
    3. Click on Manual.

     

    1. Click on the arrow to go to page 2.

     

    1. Fill in a title, e.g. Templates.
    2. Fill in Owner and Responsible.
    3. Click Publish.

    Structuring Sections in the Template Register:

     

    1. Click on the Templates Register in Handbooks & Manuals.
    2. Right click on the Templates Register in the Tree.
    3. Click on New Node.
    4. Click on Section.

     

    1. In the Section node, fill in Id and a title, e.g. 01 - Operations.
    2. Click in Publish.

    Creating system templates in Sections:

      

    1. Right click on the Section in the Template Register, e.g. 01- Operations.
    2. Click on New Node.
    3. Click on the applicable system template, e.g. Procedure.

      

    1. In the Procedure form, fill in the values which shall be standard values, e.g. Id, Title, Content, Owner, Responsible and Location.
    2. Click on Save.

    Changing the system template to template with default values:

      

    1. Click on the I-button on the SoluDyne Toolbar.
    2. Click on Properties.

     

    1. In the Properties window, click on the Template tab.
    2. Check the checkbox Use as Template.
    3. Click on Save.
    4. Close the Properties window.

    Opening a Template via SoluDyne Expaning Menu:

     

    1. Click on Governing Elements in the SoluDyne Expanding Menu.
    2. Right click on the relevant Section, e.g. 08 - Governing Procedure.
    3. Click on New Node.
    4. Click on the Template Procedure - PR - Procedure Title.

    Opening a Template via New Node directly on a form:

     

    1. In a form, click on the New-button.
    2. Click on New Child Node.
    3. Click on the Template Procedure - PR - Procedure Title.

    The default values can be changed when filling in the Template. 

    B-12222 - Flowchart Template / Modelling Standard

    00 Overview
    01 Prerequisites
    02 Description

    03 Modelling Standard
    04 Example



    00 Overview

    This Best Practice describes how to create a flowchart template in SoluDyne.

    01 Prerequisites

    Familiar with template and modelling functionality in SoluDyne.

    02 Description

    By creating a flowchart template with a defined modelling standard such as placement of Horizontal Holder or first Functional Band will simplify the creation of new flowcharts. In addition to flowchart templates, templates can be used for all the usual classes in SoluDyne. Such as Checklist, Best Practice, Requirement, Comment and many more.

    03 Modelling Standard

    Item Name Description
    1 Horizontal Holder Set Left and Top to 1. Leave Height and Width as is. Height will auto-resize when all four Functional Bands has been added. See figure 1
    2 1st Functional Band Set Top to 60. Set Role Type to Originator and Text to for instance User. See figure 2
    3 2nd - 4th Functional Band Specify Role Types: Responsible, Controller and Approver. See figure 3
    4 Activities Configure activities according to figure 4.
    5 Purpose & Scope Purpose:

    To ensure that <Flowchart> is performed in accordance with regulations, requirements and standards.

    Scope:

    This process describes the main activities and minimum requirements for <Flowchart>, specifically:

    • <activity> 
    • <activity> 
    • ...

     
    Figure 1. Horizontal Holder

     
    Figure 2. 1st Functional Band

     
    Figure 3. 2nd - 4th Functional Band

     
    Figure 4. Flowchart complete with activities

    04 Example

    Create new flowchart template:

    1. Create new flowchart
    2. Move flowchart to manual called Templates (for easy administration of all templates) using Drag & Drop. See figure 5
    3. Add Shapes and configure according to 03 Modelling Standard:
      1. Horizontal Holder
      2. Four Role Bands
      3. Set Role Types and Text
      4. Add activities
      5. Navigate to page 2 of flowchart and add Purpose & Scope
    4. Set flowchart as template
    5. Publish flowchart

     
    Figure 5. Manual: Templates

    TreeView

    B-12206 - Drag and Drop

    0.00   Definitions
    1.00   General Description

    0.00   Definitions

    N/A

    1.00   General Description

    An easy way to perform Drag-and-Drop operations on documents and nodes is to use the SoluDyne TreeView Drag-and-Drop Tool. Clicking a main module in the Expanding Menu will cause the toolbar to show up.


    Figure 1 – The Drag-and-Drop button

    When clicking the icon in the upper right corner, the Drag-and-Drop window will be opened.


    Figure 2 – The Drag-and-Drop window

    The tool allows the User to navigate all the way down to the details of a specific document in one part of the window, while having access to all other parts of the SoluDyne system in the other half. Right-clicking a node in the Treeview Drag-and-Drop Tool, and then clicking the Open menu entry will load the details of any document in the tree.

     
    Figure 3 – A document is opened from the tree on one side.

    The left part of the window now contains the details of a specific document, while the right part still have the tree easy accessible for further navigation or Drag-and-Drop into the loaded document.

     
    Figure 4 – The split view with document and tree.  

    By right-clicking on a tree node in the right frame, dragging it over to the details in the left-frame while holding the button, and then releasing the button, a popup-menu will show up, letting the User choose to create a link or a section to the node dragged in.


    Figure 5 – A Popup window for Link or Section is visible in the middle of the screen. 

    Choosing the Insert as section menu option will create a new section referring to the node dragged in.


    Figure 6 – Creating a new section referring to the node dragged in.

    Dragging can also be done in the other direction, e.g. dragging from the detailed document-view to the tree. The procedure for doing this is the same as for dragging from tree to detailed view.

    To switch between tree- and detail-view in one of the frames in the SoluDyne Treeview Drag-and-Drop tool, simply click the Tree or Detail buttons on the top. 


    Figure 7 - The buttons for alternating between tree and detail view.  

    Clicking the Tree button while the detailed view is active will bring up the tree again. Clicking the Detail button will show the details of the currently loaded document; if any.


    Figure 8 – The tree is visible on both sides. 

    B-12452 - Drag and Drop Node

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes the Drag and Drop functionality in SoluDyne.

    01 Description

    An easy way to perform Drag-and-Drop operations on documents and nodes is to use the SoluDyne TreeView Drag-and-Drop Tool. Clicking a main module in the Expanding Menu will cause the toolbar to show up.

    02 Example

      

    1. Open Expanding Menu by clicking on bar in top left corner. 

     

    1. Click on a title in the Expanding Menu, to open the submenu.

     

    1. Click on a node in the menu to open Expanding Menu Submenu.

     

    1. Click on button for Drag and Drop.

     

    1./2. The Drag and Drop Dialog Window shows two identical trees, seperated by a vertical line. It is possible to drag nodes back and forth between these two trees. 

     

    1. Open tree on right hand side by clicking on down icon.

     

    1. Choose where in the system node shall be moved to from field.

     

    1. Click on plus icon to find node to be moved.
    2. Click on plus icon to find place node shall be moved to.

     

    1. Click and drag node to be moved->
    2. Drop node over placement in tree it is to be moved to.

     

    1. Node has now been moved to new placement in tree.

    B-13294 - Sort order in Register Tree

    Overview
    This Best Practice describes the sort order in SoluDyne Register Tree.

    All Classes in SoluDyne has optional Id and Title Fields. The most part of data is organized into Registers and can be displayed in Tree. Tree Title for Node is combined from Id and Title Fields with devider.

    To simplify search in Tree Nodes are sorted.

    By default Nodes are sorted by Tree Title. There is a way to customize sorting by creating TREESORT parameter on Register Class. 

    The Rules for the sorting for Manual and Main Process Trees are:

    1. Requirements sorted by Id and Tree Title if any.
    2. Best Practices sorted by Id and Tree Title if any.
    3. Roles sorted by Id and Tree Title if any.
    4. All other Nodes sorted by Id and Tree Title.

    Note. As letters and numbers are allowed in Id and Title Fields, so Id 10 will be located before Id 2. In case of numbers is used as Id use 02 instead of 2 for correct sort order.

    Prerequisites
    N/A

    Description

        

    1. Login into Soludyne and open Expanding Menu. 
    2. Click any available Module. Handbooks & Manuals can be used as an example.
    3. Click on any Register Node.
    4. Tree will appear on a right side. Click on plus to expand level. On each Tree level Nodes are sorted by Class, after that by Id and after that by Title.
    5. Title in Tree is combined by Id and Title with - sign as divider.  

    Work Queue

    B-12454 - Workqueue

    00 Overview
    01 Description
    02 Example

    00 Overview

    This Best Practice describes the Workqueue functionality in SoluDyne.

    01 Description

    The SoluDyne Workqueue gives access to all tasks and notifications routed to the user. The Workqueue has two levels and can be expanded by clicking on the first level.

    • The first level shows what type of information/class the Workqueue item belongs to, e.g. Plan, Activity, Broadcast or Revision Notification.
    • The second level shows the actual Workqueue Items for each class type.


    02 Example

      

    1. Click on any Workqueue class.

     

    1. Workqueue class expands, showing items in queue.

    Working Copies

    B-10557 - Working Copies and Node Permissions

    0.00   Definitions
    1.00   General Description
    2.00   Question
    3.00   Answer
    4.00   Sample Session

    0.00 Definitions

    N/A

    1.00 General Description

    Working Copies are used when working with Processes and Governing Elements which is not completed.  Working Copies can be set with restricted access to other users.
    Employees can also be allowed access to Working Copies. Such Access can be restricted to specific Sections through Process Owner and Responsible, i.e. Employees identified as such may work on own Section without access or edit rights on additional Sections.
    When completed the Node can be implemented to the system.

    2.00   Question

    How to use Working Copies?

    3.00   Answer

    Create Manual, i.e. called "Working Copies".
    Create Section under Manual.  Set Owner and Responsible and Node Permissions as desired.
    Move desired nodes to the Manual using the Drag and Drop Tool or create new nodes.
    Now work can be perfomed on the nodes with restricted access to other users as desired. 

    Note! In order to be able to create new Sub Processes and Flowchart, and Sub Process must be created under an existing Main Process and moved to "Working Copies" under Drag and Drop Tool.

    4.00   Sample Session

    1. Create Manual, i.e. called "Working Copies".
    2. Create Section under Manual. Set Owner and Responsible as desired.

     
    Figure 1 - Working Copies Manual

    3. Access the Properties window under the given Section, and set Node Permissions.

     
    Figure 2 - Properties window, Node Permissions.

    4. Move desired nodes to the Manual using the Drag and Drop Tool or create new nodes.

     
    Figure 3 - Moving a Sub Process using the Drag and Drop Tool.

    5. Perfom work on given Node, and use Drag and Drop tool to move nodes to permanent location.











    Save