Communication with the lists in the Worklite Docs Electronic Document Management document card at Sharepoint 2013
As we all know the banal truth, Electronic Document Management is the movement and storage of documents within a company. In addition to the system itself, the core, so to speak - the heart of the SED, is the document card (in fact, the central node of the document's interrelations with functionality and workflows, in accordance with which the document carries out its movement).
Workflows are a separate thing. Today, we’ll look at the document card, which is absent in Sharepoint in a convenient form, but of course it is the cornerstone for any decent EDS.
A document card is a kind of synthesis of the functionality necessary for convenient document management, its subsequent storage and quick access to attributes.
In simplified, customized form, it looks like a set of blocks, each of which performs its task. And in principle - in their performance, at first glance, they usually do not differ much from each other among different developers. Another question is what kind of subcutaneous functionality and potentialities they have.
')
An example of a fully customized document card — in which it is present — is such a wonderful thing as “linking with lists:
Larger image - available here.
And here - see the entire Electronic Workflow Document Worklite Docs
If you pay attention to the block "additional fields", then you can see there the fields that are specific to this particular card for a specific type of document. In each type of document, the right block of the card has unique fields that are assigned only for documents of a particular library - let's say “Contracts”.
The necessary fields are implemented, categorically quickly:
1. A required list is created with the required elements - let's say 'counterparties', in which all the necessary values ​​for this list are specified (name, address, contact, full name, etc.). Well, in general, the lawyer knows better.
2. Since, in this solution, the SED for Sharepoint 2013, the most wonderful thing is the functionality of the “Communication with lists”, then the counterparty field is entered in the right block indicating the list created and the ability to search through it or select a control.
3. In the card, an additional functional field "Counterparties" appears, which is now an integral attribute and with which you can bind specific counterparties in this document.
4. You can make any number of different fields and links with any lists - it depends only on the needs within the type (library) of the document.
The whole operation takes a few minutes. I wrote longer than this is done :)
Workflows are a separate thing. Today, we’ll look at the document card, which is absent in Sharepoint in a convenient form, but of course it is the cornerstone for any decent EDS.
A document card is a kind of synthesis of the functionality necessary for convenient document management, its subsequent storage and quick access to attributes.
In simplified, customized form, it looks like a set of blocks, each of which performs its task. And in principle - in their performance, at first glance, they usually do not differ much from each other among different developers. Another question is what kind of subcutaneous functionality and potentialities they have.
')
An example of a fully customized document card — in which it is present — is such a wonderful thing as “linking with lists:
Larger image - available here.
And here - see the entire Electronic Workflow Document Worklite Docs
If you pay attention to the block "additional fields", then you can see there the fields that are specific to this particular card for a specific type of document. In each type of document, the right block of the card has unique fields that are assigned only for documents of a particular library - let's say “Contracts”.
The necessary fields are implemented, categorically quickly:
1. A required list is created with the required elements - let's say 'counterparties', in which all the necessary values ​​for this list are specified (name, address, contact, full name, etc.). Well, in general, the lawyer knows better.
2. Since, in this solution, the SED for Sharepoint 2013, the most wonderful thing is the functionality of the “Communication with lists”, then the counterparty field is entered in the right block indicating the list created and the ability to search through it or select a control.
3. In the card, an additional functional field "Counterparties" appears, which is now an integral attribute and with which you can bind specific counterparties in this document.
4. You can make any number of different fields and links with any lists - it depends only on the needs within the type (library) of the document.
The whole operation takes a few minutes. I wrote longer than this is done :)
Source: https://habr.com/ru/post/194304/
All Articles