We have developed a demo app based on edoc automate to show you, through various views, an example of how an app is structured around key actions: establishing a connection to the repository and performing common tasks such as searching for invoices, importing them, saving them, viewing invoice details, and editing an invoice.
You can import the d.velop DMS Demo app (d.velop_dms_demo-v<version_number>.eax) into edoc automate as a separate demo app. After importing the demo app, you can explore the basic functions for interacting with documents in a d.velop documents repository at your own pace.
The demo app serves as a template app that demonstrates how to use the d.velop DMS integration through an example covering all actions. The demo app also provides various explanations within the software context, so that the background and intended use are explained in context, making it easier for you to find detailed information.
Of course, you can use the actions in the demo app as a sort of blueprint for your own DMS integrations with an edoc automate app.
Prerequisites for this example scenario
-
You have already created an app and know the basic functions of edoc automate.
-
You are familiar with the basics of d.velop documents and the DMSApp API.
-
You received the demo app named d.velop DMS Demo from your edoc contact.
In this article, we provide only a brief overview of the basics of the d.velop DMS Demo app.
Basic information about the demo app
The demo app focuses on the sample category AutomateRechnung (automateInvoice) (document type in d.velop documents). In the demo app, we show you how to import, search for, view, and edit documents. The AutomateRechnung category also contains default fields and fields for multiple properties.
The demo app illustrates the typical lifecycle of a document in the DMS system (d.velop documents repository).
Things to know
Each demo view has been annotated, and the IDs, GUIDs, actions, and fields used have been documented in detail so that you can use the content as a template for your own app.
Technical requirements for the demo app
To make the most of the demo app, you need to ensure the following:
-
A configured dms data source with the d.velop documents connector already exists in edoc automate.
-
You have all the information about the DMS server, the repository ID, and the API key.
-
You have write access to a d.velop repository containing the sample category AutomateRechnung (AutomateInvoice). The demo app uses all of the category’s metadata to ensure that the demo app functions properly. Alternatively, you can use your own category. If you use your own category, you must adjust the data in the demo app accordingly.
Overview of the individual views and their purposes
The views in the demo app offer the following functionality and generally include additional explanations with details:
-
View Start: On the demo app's home page, you'll find general explanations of the demo app's structure, including key concepts, an overview of the constants used, and links to the demo views.
-
View Repository Setup: Shows how repositories, categories, and properties including GUIDs are retrieved in real time from the connected d.velop documents repository.
-
View Rechnung suchen (Search for invoice): Displays the search for an ECM document using document properties. Wildcard filters and the Zahlungsart (Payment method) property as a multi-select field have also been implemented in this view.
-
View Rechnung anlegen (Create invoice): Shows how a document is uploaded to the DMS system, and which properties including fields with multiple properties in the AutomateRechnung category the users can fill out.
-
View Rechnung Details (Invoice details): Displays the detailed view with all properties of an ECM document and the associated file.
-
View Rechnung bearbeiten (Edit invoice): Shows how to update existing document properties. In addition, the view provides tips on working with property fields for value lists.
Contact your edoc representative to try out the demo app for free.