You are able to create additional criteria to further customize your front page or list layouts. Two database tables are used for this purpose, namely BacoDiscussions and DocumentCorporateTags tables.
To create or edit a front page or list layout, function right 282 – Maintain layouts is required. By default, users with the Documents administrator and Web administrator roles have this function right.
For more details on what you can do with function rights or levels, go to System/Setup/Security/Function rights, select the required module, and then click on the relevant ID. To find out the functions you can perform with a particular role, go to System/Setup/Security/Roles, type in the description, click Refresh, and then click the required link under the Role column.
There are no applicable buttons.
The BacoDiscussions table is used to specify the document properties while the DocumentCorporateTags table is used the corporate tags attached to the documents. Within the tables, the different database fields can be utilized to customize the layouts.
The fields that can be used for customization include:
Field
Description
Assortment
The ID of the assortment.
Body
The text found in the body or attachment.
Category
The category of the document.
Class_02_1
The assortment version (from).
Class_02_2
The assortment version (to).
Company
The company’s division ID that is related to the document.
CreatedBy
The ID of the document creator.
CreatedByFullName
The full name of the creator.
CreatedDate
The date the document was created.
Document
The contents of the attached document in binary form.
ExpiryDate
The date the document is expected to be deleted.
Filename
The filename of the attached document.
GroupID
The ID of the document’s main category.
HID
The ID of the document in numbers. This is used by the user to identify a document.
HumResID
The ID of the user that is linked to the document.
IsMailMerge
This identifies whether it is a mail merge-based document.
IsTemplate
This identifies whether it is a document layout template.
ItemCode
The item code that is linked to the document.
JobLevel
The security level of the document.
LanguageID
The language ID of the document.
ModifiedBy
The ID of the person who last modified the document.
ModifiedDate
The date the document was last modified.
NewsType
The type the document was published as. The following is used to represent the different types:
ParentID
The HID of the main document, if the document is in reply to a main document.
ProjectNr
The project code that the document is linked to.
Status
The status of the document. The following is used to represent the different statuses:
SubCategory
The subcategory of the document.
Subject
The subject of the document.
Type
The ID of the document’s type.
Version
The version of the document.
The ID of the user who created the document.
The date and time the document was created.
Division
The division code of the user.
DocumentID
The ID of the document that the corporate tag is attached to.
DocVersion
The version of the document that has corporate tag(s) attached.
ID
The ID of the corporate tag.
Tag
The title of the tag that is attached to the document.
TagID
The ID of the tag that are attached to the documents.
Note: The DocumentCorporateTags table is used in Standard mode only. For more information, see Product Update 240: Streamlining Document Structure with Document Types.
To effectively execute the criteria, SQL operators can be used. These are divided into two types of operators, namely logical and comparison operators.
Logical operators are used to test for the truth of some conditions. These include:
Operator
Meaning
ALL
TRUE if all of a set of comparisons are TRUE.
AND
TRUE if both Boolean expressions are TRUE.
ANY
TRUE if any one of a set of comparisons is TRUE.
BETWEEN
TRUE if the operand is within a range.
EXISTS
TRUE if a subquery contains any row.
IN
TRUE if the operand is equal to one of a list of expressions.
LIKE
TRUE if the operand matches a pattern.
NOT
Reverses the value of any other Boolean operator.
OR
TRUE if either Boolean expression is TRUE.
SOME
TRUE if some of a set of comparisons are TRUE.
Comparison operators are used to compare whether the results of two statements, usually a value, are the same. These include:
= (Equals)
Equal to
> (Greater Than)
Greater than
< (Less Than)
Less than
>= (Greater Than or Equal To)
Greater than or equal to
<= (Less Than or Equal To)
Less than or equal to
<> (Not Equal To)
Not equal to
!= (Not Equal To)
!< (Not Less Than)
Not less than
!> (Not Greater Than)
Not greater than
The following table lists possible examples and their expected results when using criteria to create front page or list layouts:
Example
Expected result
bd.CreatedDate > '01/01/2004' AND bd.NewsType = '1'
Lists documents created after 1 January, 2004 and appeared on the front page.
bd.JobLevel > '12' AND bg.UseHumResID = 2
Lists documents with security level higher than 12 and where resource ID is mandatory.
bd.JobLevel < '2' AND bd.Company IN ('063','065')
Lists documents with security level less than 2 and associated with divisions 063 or 065.
bd.LanguageID = 'NL' AND bd.Assortment IN (1, 6, 12, 16)
Lists documents written in Dutch and is related to assortments 1, 6, 12 or 16.
bd.HumResID BETWEEN 001 AND 050 AND bd.Assortment IS NOT NULL
Lists documents written by users with IDs between 001 and 050 and also where the assortment is specified.