About d.velop smart invoice
Open Documentation Menu
Interactions with d.3
d.velop smart invoice uses d.3 to store invoices, invoice attachments and workflow logs, among other things. d.3 is accessed via a source system, which is independent of the repository’s specific category and property structure. For d.velop smart invoice to function properly, there is a small minimum set of categories and properties that must be created and assigned.
Category: Rechnungen/Invoices
Company number
Company name
Workflow participants
Created on (system property)
Category: Workflow logs
Doc ID workflow
You can use the Workflow document ID property in the Workflow logs category to establish the connection between the invoice and the log.
Beyond this minimal set of fields, you are free to choose the repository structure.
In order for d.velop smart invoice to connect to a repository, you need to enter an API key. The user associated with the API key must have read and write permissions in all repositories for the categories used. In particular, you must grant the user the Change attribute in release right.
Deactivating the synchronization of guest users in SharePoint
You want to deactivate the synchronization of external users such as guests (e-mail addresses with #EXT#) in SharePoint. This then stops newly created guest users from being synchronized and sets existing guest users as inactive.
This is how it works
In the d.velop smart invoice administration area, go to User/Groups.
Under Interval (Minutes), activate the relevant checkbox to stop the synchronization of guest users.
Save the synchronization settings. The changes are applied during the next synchronization process.
Setting up assignments
To use a repository with d.velop smart invoice, you need to assign the sources smart invoice - invoice and smart invoice - protocol to the corresponding categories and properties in your d.3 repository.
Suppose that your d.3 repository contains the categories Incoming invoices and Workflow logs.
This is how it works
Click the Mappings tile.
Create a new assignment.
Select smart invoice - invoice as the source.
Select Incoming invoices as the category.
Assign the d.velop smart invoice property d.3ecm - creation date to the system property Created on.
Assign the required d.velop smart invoice properties to the category properties. You must assign at least the properties Company number, Workflow participants and Company name.
Save the assignment.
Create a new assignment.
Select smart invoice - protocol as the source.
Select Workflow logs as the category.
Assign the required d.velop smart invoice properties to the category properties. You must assign at least the Workflow doc ID property.
Save the assignment.
Navigate to the d.velop smart invoice administration interface.
Select Repositories to switch to the overview of d.3 repositories.
You should see the repository in the list. If the repository and the assignments are set up correctly, a check mark icon appears in the Status column.
The d.3 repository is now ready for use.
Granting permissions for invoice documents
Each user needs repository read permissions for the invoices they process in d.velop smart invoice. The multi-value property Workflow participants is used for this purpose. d.velop smart invoice populates this field with a list of all users and groups to whom the invoice is assigned throughout the workflow. In the repository, you need to set up an appropriate permission profile that allows these users and groups read access for the invoice documents.
Setting up a permission profile for d.ecs identity provider support
The section below applies only to the on-premises installation version.
If you are using d.3 with support for d.ecs identity provider enabled, you can use the @D3IDPUSER and @D3IDPGROUP macros to grant read permissions for the invoice documents to the worfklow participants. Unless there are reasons to the contrary, d.ecs identity provider support is usually preferrable to LDAP support.
Suppose you are using a document type with the name Incoming invoices.
This is how it works
Open the d.3 administration and switch to editing mode.
Open d.3 restriction set manager.
Create a new restriction set to restrict documents by users and groups. Name the restriction set Workflow participants.
Create a new set assignment of the type No mapping.
Enter the two values @D3IDPUSER and @D3IDPGROUP as filters in two separate lines.
Save the set assignment.
Create a new document class for the document type Incoming invoices.
Enter the value @D3SET(Workflow participants) in the Workflow participants field.
Name the document class Workflow participants incoming invoices.
Save the document class.
Create a new permission profile named smart invoice user.
Add the document class Workflow participants incoming invoices.
Create read permissions for this document class.
Save the permission profile.
Setting up a permission profile for LDAP support
The section below applies only to the on-premises installation version.
If you are using d.3 with LDAP support enabled, you can use a combination of the macros @D3GROUP and @D3USER_OPTFIELD_NN to grant read permissions for the invoice documents to workflow participants.
You can use the @D3GROUP macro to give a user rights to any invoices assigned to a group to which they belong during the workflow. Please note that d.velop smart invoice uses the groups from d.ecs identity provider, which are usually groups from connected external user management systems, such as Microsoft Active Directory. For the permissions to be correctly assigned via @D3GROUP, each user group that is relevant for d.velop smart invoice must have exactly the same name in d.3. Additionally, you must use d.3’s LDAP support function to ensure that the users belonging to a group in the connected LDAP system are also assigned to the corresponding group in d.3. Details can be found in the administration manual for d.3.
You can use the @D3USER_OPTFIELD_NN macro to grant a user rights to any invoices assigned to them directly during the workflow, i.e. not via a group. To do this, you have to enter the login name of the d.3 user in an optional field in the LDAP support function. Note that the optional field must match the name used by d.ecs identity provider. If you are using Microsoft Active Directory, you can use the sAMAccountName field.
Suppose you are using a document type named Incoming invoices and you have copied the user's login name to Optional field 1. For the document type, there is a multi-value field named Workflow participants to which you have assigned the d.velop smart invoice field Workflow participants.
This is how it works
Open the d.3 administration and switch to editing mode.
Open d.3 restriction set manager.
Create a new restriction set to restrict documents by users and groups. Name the restriction set Workflow participants.
Create a new set assignment of the type No mapping.
Enter the two values @D3USER_OPTFIELD_01 and @D3GROUP as filters in two separate lines.
Save the set assignment.
Create a new document class for the document type Incoming invoices.
Enter the value @D3SET(Workflow participants) in the Workflow participants field.
Name the document class Workflow participants incoming invoices.
Save the document class.
Create a new permission profile named smart invoice user.
Add the document class Workflow participants incoming invoices to the new permission profile.
Grant read permissions for the document class.
Save the permission profile.
Use the LDAP support function to assign the permission profile to all users participating in the workflow.
Defining a delegate during absences
If you report yourself as absent in d.velop documents and define a delegate, your delegate can access your task list.
Your delegate can only view tasks that have been personally addressed to you. Your delegate cannot view any tasks that were sent to you as part of a group membership. As soon as your delegate opens a task, d.velop smart invoice adds the delegate to the workflow participants.
To ensure that your delegate can also see the document attachments for the tasks, your delegate must have an appropriate permission profile in d.velop documents.
Note
In d.velop documents, permission problems may occur in rare cases due to the configuration of the permission profiles. That means the delegate is not immediately authorized to view the attached invoice document when opening a task.
This can happen when permission profiles are used to grant the permissions for invoice documents based on the list of workflow participants. In such cases, the invoice document was loaded more quickly than the delegate could be added to the list of workflow participants. Closing the task and opening it again after a short time rectifies the problem with the permission.