Difference between revisions of "Document view tabs"

From 1Archive help
Jump to: navigation, search
(link= "Log")
 
(3 intermediate revisions by the same user not shown)
Line 31: Line 31:
 
<br/>{{note|The '''VIS''' environment has an extra field '''Voucher date'''}}
 
<br/>{{note|The '''VIS''' environment has an extra field '''Voucher date'''}}
  
<br/>
+
==[[image:EventLog.png|link=]] '''"Log"'''==
 +
All events related to the invoice are stored in the logs. Following events could occur:
 +
* '''Import''': when a document is created.
 +
* '''Processing''': a log entry is created for each step during automatic processing (thumbnail creation, annotating, signing, ...).
 +
<br/>{{info|When an error occurs during processing, a log entry of type '''Error''' will be created.}}<br/>
 +
* '''User action''': a log entry is created when a user performs one of the following actions:
 +
** Set ready for download
 +
** Cancel document
 +
 
 +
<br/>{{info|No log entry is added when changes are made in the header fields or accounting lines.}}<br/>
  
==[[image:EventLog.png|link=]] '''"Log"'''==
+
Following information is available:
 +
* '''Step type''': could be one of the following:
 +
** [[image:eventinfo.png|link=]] ''"INFO"'': for regular actions like the creation of a document, routing of a document, thumbnail creation, ... .
 +
** [[image:eventwarning.png|link=]] ''"WARNING"'': for actions that require your attention like booking errors.
 +
** [[image:eventerror.png|link=]] ''"ERROR"'': for severe errors like the failure of signing the document.
 +
* '''Time''': the date and time when the event occurred.
 +
* '''Source''': where the event occurred. Possible values are:
 +
* '''Message''': a more detailed message about what actually happened.
  
 
==[[image:deliverylog.png|link=]] '''"Delivery log"'''==
 
==[[image:deliverylog.png|link=]] '''"Delivery log"'''==
 +
Shows all the log entries regarding the delivery of the invoice.
 +
 +
<br/>{{warning|In use only when delivery of documents are activated.}}
  
 
==[[image:workflow.png|link=]] '''"Log"'''==
 
==[[image:workflow.png|link=]] '''"Log"'''==
 +
Shows an overview of all the workflow steps the document has been through. The grey lines show the workflow status the document was in, the white lines show how it got there.
 +
<br/>
 +
Following info is available:
 +
* '''Activation time''': the date and time when the event was activated.
 +
* '''Activated by''': the user who activated the workflow event.
 +
* '''Step type''': the type of the step. Could be one of the following:
 +
** ''Approval''
 +
** ''Sidestep''
 +
** ''Informative''
 +
* '''Action time''': the date and time when the action ended.
 +
* '''Action user''': the user who initiated the action.
 +
* '''Action''': the action that was initiated on the document.
 +
* '''Flow status''': the workflow status the document was in when the event was initiated.
 +
* '''Line''': if the routing happened for an accounting line, the line will be indicated here.
 +
* '''Roles''': the role to which the document was assigned.
 +
* '''Assigned users''': the user(s) and/or user group(s) who were assigned to the document when the action was activated.
 +
<br/>
 +
An example:<br/>
 +
<br/>[[image:workflow_log.png|link=]]
  
 
==[[image:fixedflow.png|link=]] '''"Flow visualisation"'''==
 
==[[image:fixedflow.png|link=]] '''"Flow visualisation"'''==
Line 46: Line 84:
  
 
<br/>The vertical lines indicate the different workflow statuses the document has been through.
 
<br/>The vertical lines indicate the different workflow statuses the document has been through.
The colors of the beads represent the type of the step taken:
+
The colours of the beads represent the type of the step taken:
 
* '''Green''': an approval/action step.
 
* '''Green''': an approval/action step.
 
* '''Red''': a side-step in the approval flow.
 
* '''Red''': a side-step in the approval flow.
 
* '''Blue''': an informative step in the approval flow.
 
* '''Blue''': an informative step in the approval flow.
  
<br/>A step that isn't active anymore is shown in a lighter color and the round bead changes to a square one.
+
<br/>A step that isn't active anymore is shown in a lighter colour and the round bead changes to a square one.
  
 
<br/>When hovering over a certain step, a pop-up screen with additional information about the current step appears. This screen contains several pieces of information like:
 
<br/>When hovering over a certain step, a pop-up screen with additional information about the current step appears. This screen contains several pieces of information like:
Line 61: Line 99:
  
 
<br/>{{note|When the auto flow was used instead of the manual flow to send a document in the approval flow, the black connecting lines will appear in green.}}
 
<br/>{{note|When the auto flow was used instead of the manual flow to send a document in the approval flow, the black connecting lines will appear in green.}}
 
 
 
 
 
 
 
 
 
 
All invoices have a log which contains all the events related to the invoice. The log is updated with following information:
 
 
* Import: When a document arrives in the archive, a log entry is added.
 
* Processing: A log entry will be added for each step during automatic processing, like thumbnail creation, annotating, signing, routing of the document. <br/>When an error occurs during processing, a log entry of type “Error” will also be added.
 
* User action: When a user performs following actions:
 
** Set ready for download.
 
** Cancel document.
 
* No log is added when changes are made in the header or line fields at moment of saving.
 

Latest revision as of 13:47, 28 September 2016

1 Images.png "Images"


If the document has several attachments, you can browse through them by using the arrow buttons in the bottom right of the image screen.

  • BlockFirst.png "First attachment": go to the first attachment of the list.
  • BlockPrevious.png "Previous attachment": go to the previous attachment of the list.
  • BlockLast.png "Last attachment": go to the last attachment of the list.
  • BlockNext.png "Next attachment": go to the next attachment of the list.

Use the Adobe Acrobat specific features to navigate inside the document.


At the bottom left of the image screen you have following buttons available:

  • Documentlink.png "Share document": allows you to send the document attachment to another person.

Note.png Note that this person does not need to be registered in 1Archive.

Note.png This button gives you a link to the document, you have to copy paste it to send it to someone else.
Share document.png

  • Save.png "Download": allows you to download the image of the attachment.
  • Outgoing.png "Detach": allows you to open the document attachment in a seperate screen. This will facilitate the input of data.

Note.png To leave the detached document, just close the newly created screen.


There are some extra buttons available after booking the invoice in the accountancy package:

  • Signature.png "Signature": allows you to download the signature of the image.
  • Key.png "Public key": allows you to download the public key of the image.
  • Validate.png "Validate": allows you to check if the current image has been modified since it has been archived.
  • Annotating information on top of the invoice image:
    • the name of the accountant.
    • the period in which the invoice was booked.
    • the ID of the document inside 1Archive.
    • the voucher number of the document.

Note.png For VIS the field period is the bookyear and the journal.

Note.png The VIS environment has an extra field Voucher date

2 EventLog.png "Log"

All events related to the invoice are stored in the logs. Following events could occur:

  • Import: when a document is created.
  • Processing: a log entry is created for each step during automatic processing (thumbnail creation, annotating, signing, ...).

Info.png When an error occurs during processing, a log entry of type Error will be created.

  • User action: a log entry is created when a user performs one of the following actions:
    • Set ready for download
    • Cancel document

Info.png No log entry is added when changes are made in the header fields or accounting lines.

Following information is available:

  • Step type: could be one of the following:
    • Eventinfo.png "INFO": for regular actions like the creation of a document, routing of a document, thumbnail creation, ... .
    • Eventwarning.png "WARNING": for actions that require your attention like booking errors.
    • Eventerror.png "ERROR": for severe errors like the failure of signing the document.
  • Time: the date and time when the event occurred.
  • Source: where the event occurred. Possible values are:
  • Message: a more detailed message about what actually happened.

3 Deliverylog.png "Delivery log"

Shows all the log entries regarding the delivery of the invoice.


Warning.png In use only when delivery of documents are activated.

4 Workflow.png "Log"

Shows an overview of all the workflow steps the document has been through. The grey lines show the workflow status the document was in, the white lines show how it got there.
Following info is available:

  • Activation time: the date and time when the event was activated.
  • Activated by: the user who activated the workflow event.
  • Step type: the type of the step. Could be one of the following:
    • Approval
    • Sidestep
    • Informative
  • Action time: the date and time when the action ended.
  • Action user: the user who initiated the action.
  • Action: the action that was initiated on the document.
  • Flow status: the workflow status the document was in when the event was initiated.
  • Line: if the routing happened for an accounting line, the line will be indicated here.
  • Roles: the role to which the document was assigned.
  • Assigned users: the user(s) and/or user group(s) who were assigned to the document when the action was activated.


An example:

Workflow log.png

5 Fixedflow.png "Flow visualisation"


Flow visualisation.png

The flow visualisation shows the path a document followed in the workflow. It clearly shows which users saw the document and which actions were executed on it.


The vertical lines indicate the different workflow statuses the document has been through. The colours of the beads represent the type of the step taken:

  • Green: an approval/action step.
  • Red: a side-step in the approval flow.
  • Blue: an informative step in the approval flow.


A step that isn't active anymore is shown in a lighter colour and the round bead changes to a square one.


When hovering over a certain step, a pop-up screen with additional information about the current step appears. This screen contains several pieces of information like:

  • the time it was received
  • what action was executed.


An example:
Flow visualisation detail.png


Note.png When the auto flow was used instead of the manual flow to send a document in the approval flow, the black connecting lines will appear in green.