Records Management controls important information that needs to be retained over time. It's used in highly regulated environments, for managing governmental information or personnel records, or where information might be audited.
Fully integrated into Alfresco Content Services, Records Management makes it easy to work with files and have them declared as records at the right time, without changing the way you work.
What you do in Records Management will vary hugely depending on your role, and how your company is organized. This guide is split into two sections, one for Records Managers, and one for Records Management users. You might find that these guides don't exactly match what you do in your day-to-day job, but even if they don't you should find them useful in getting started, and in understanding the basic concepts of Records Management and how the processes fit together.
When you have added all required metadata to a record you can mark the record as complete. This makes it an active part of the File Plan, and subject to the rules of the retention schedule it is associated with.
It then goes through various time and event based steps such as cut off and retention, until it is eventually transferred elsewhere, or destroyed, according to its retention schedule.
The background configuration of the site should be managed by your Records Management administrator in the RM Admin Tools.
This leaves you to get on with managing the site organization, devising and ensuring the implementation of retention and disposal schedules, and enabling appropriate access to information.
In this guide you'll see how to get started with the basics immediately.
The New Record Category dialog box displays.
Metadata field | Description |
---|---|
Name* | The name for the record category. |
Title* | The title for the record category. |
Description | A description of the record category. |
Record Category ID* | A unique identifier for the record category is generated automatically. You can change this now, but you can't edit it once the category has been created. |
Vital Record Indicator | Defines whether records in this category have a review process. The Vital Record
Indicator is applied to all record folders within that category. You can change this
at folder level. Users with Records Manager permissions receive a notification email when vital records are due for review. |
Period | The time period for the review cycle. Reviews are recurring based on the period
you select. The review period is required when the Vital Record
Indicator option is selected. Note: The "Quarter" option splits the year into 4 sets of 3 months, beginning
with Jan/Feb/March. "Financial Quarter" is the same but based on the start date of
your system-configured financial year.
The review period is displayed on
the details page for folders and records in the category. |
Expression | Enter a number as the Expression to accompany the
Period type. If you enter “Week” and “3”, this would mean a
review cycle of 3 weeks. If you select a Period that doesn't require an Expression then this field isn't available. |
The new category displays in the File Plan.
The category details page displays and if the category already has a retention schedule then you'll see the schedule summary and steps.
Field | Description |
---|---|
Retention Authority | The authority that states how the record should be retained and disposed, for example Sarbanes-Oxley Act (SOX) or Corporate procedures. |
Retention Instructions | A summary of the retention schedule. This information is not actively used but this text is displayed in the record category summary in the File Plan, and is important from a legal perspective. |
Applied to | Record Folder: the retention schedule is applied to
folders and all operations occur at the folder level. With this setting, you cannot
manage records as individual units. If you cut off the folder, all records will be
cut off. Record: the retention schedule is applied to records and all operations occur at the record level. |
The category details page now displays a summary of the new or updated retention schedule.
The category details page displays showing the retention schedule summary.
The Edit Retention Schedule page displays.
Option | Description |
---|---|
Cut off | This is the first step in a retention schedule. Once a record is cut off this triggers the records retention period. You can't add records to a folder that's been cut off. |
Retain | This is an alternative first step that is a 'placeholder' step which delays the next retention step until after a selected time period or event. |
Transfer | Records are transferred from one location to another. This can be applicable to both electronic and non-electronic records, and will be used, for example, when transferring records from an organization to an archive. |
Accession | An advanced form of transfer usually involving the specific legal and physical transfer of records between organizations. |
Destroy | Electronic records are removed from the Records Management system and destroyed, and non-electronic records must be destroyed. |
Option | Description |
---|---|
After a period of | Select the time period after which the step action will take place. Note: If you
select XML Duration from the Period Type drop down list you can specify a time interval
using XML syntax.
The syntax should take the form of: P = Period (required) nY = Number of years nM = Number of months nD = Number of days T = Start time of a time section (required if specifying hours, minutes, or seconds) nH = Number of hours nM = Number of minutes nS = Number of seconds For example, 'P2M10D' represents two months and ten days. Created Date = The date when the file or record is first added to Alfresco. Retention Action = The date when the last retention action took place. Don't select this for the first step in the schedule. The "Quarter" option splits the year into 4 sets of 3 months, beginning with Jan/Feb/March. "Financial Quarter" is the same but based on the start of your system-configured financial year. See Customizing the end of the financial year [37]. |
When event happens | Select the event after which the step action will take place. Most events must be completed manually in the record details page, or you can use rules to automatically complete these events. The Obsolete, Superseded, and Related Record Transferred To Inactive Storage events are automatically completed when relevant relationships are set up between records [38]. |
The date selected here is displayed as the Retention as of date in the details page for records or folders, depending on which the retention applies to. If you select an event then this field will display None, and you should complete the event on the details page.
For example, the following would customize your system to start the financial year in October.
<bean id="period.end.of.financial.month" class="org.alfresco.repo.dictionary.types.period.EndOfFinancialMonth" > <property name="startDayOfMonth"> <value>1</value> </property> <property name="startMonth"> <value>10</value> </property> </bean> <bean id="period.end.of.financial.quarter" class="org.alfresco.repo.dictionary.types.period.EndOfFinancialQuarter" > <property name="startDayOfMonth"> <value>1</value> </property> <property name="startMonth"> <value>12</value> </property> </bean> <bean id="period.end.of.financial.year" class="org.alfresco.repo.dictionary.types.period.EndOfFinancialYear" > <property name="startDayOfMonth"> <value>1</value> </property> <property name="startMonth"> <value>9</value> </property> </bean>
The New Record Folder dialog box displays.
Metadata field | Description |
---|---|
Name* | The name for the record folder. |
Title* | The title for the record folder. |
Description | A description of the record folder. |
Record Folder ID* | A unique identifier for the record folder is generated automatically. You can change this now, but you can't edit it once the folder has been created. |
Location | If relevant specify the physical location of the records contained within this folder. |
Supplemental Marking List | If available, select any suitable properties from the list. Entries on this list are set up by your Alfresco administrator and are only available if you have been given the required permission. |
Vital Record Indicator | Defines whether records in this folder have a review process. The Vital Record
Indicator is applied to all records within the folder. You can change this at record
level. Note: If you don't select this option and the category the folder is in has a
Vital Record Indicator set, then the category setting will be applied to the folder
once it is created.
If you do select this option it will override any Vital Record Indicator set in the category. Users with Records Manager permissions receive a notification email when vital records are due for review. |
Period | The time period for the review cycle. Reviews are recurring based on the period
you select. The Review Period is required when the Vital Record
Indicator check box is selected. Note: The "Quarter" option splits the year into 4 sets of 3 months,
beginning with Jan/Feb/March. "Financial Quarter" is the same but based on the
start date of your system-configured financial year. See Customizing the end of the financial year [37].
The review period is displayed on the
details page for records in the folder. |
Expression | Enter a number as the Expression to accompany the
Period type. If you enter “Week” and “3”, this would mean a
review cycle of 3 weeks. If you select a Period that doesn't require an Expression then this field isn't available. |
The new folder is now shown in the File Plan.
The Manage Permissions page opens with the name of the selected folder or category displayed. Any users and groups that currently have permissions assigned are also displayed. You can change existing user permissions or Remove them entirely.
All users, groups, and roles matching the search are displayed.
Read and File allows users to work with content, whereas users with Read Only permission can only view content.
The permissions you've set are now applied to the folder or category you selected and any folders or categories it contains. You can change these as needed on a folder or category basis.
Your Records Manager will have organized the site and set up retention and retention schedules, leaving you to get on with managing and processing the site records.
In this guide you'll see how to get started with the basics immediately.
The file is added to the Unfiled Records area, in the explorer panel of your Records
Management site. It's still visible in its original site, identified by the icon, but is locked and
with a limited set of actions available.
A file that has been declared as a record can be deleted. The records remain in the File Plan.
All unfiled records are displayed.
The Add Record Metadata option is only available in DoD 5015.2-STD compliant Records Management sites.
The available record types are displayed.
Record type | Description |
---|---|
Web Record | A web page. |
Scanned Record | A file that is scanned into the Records Management system. |
PDF Record | A PDF file. |
Digital Photograph Record | A photographic image file. |
Some record metadata is mandatory. Before you can complete a record, you must edit the metadata to complete the mandatory fields.
The Edit Metadata page displays. The metadata fields you see on this page depend on the file type, and whether or not record types have been associated with the file. The metadata is divided into sections, with additional sections dependant on if a record type has been associated with the item.
If your Records Management system is DoD 5015.2-STD compliant then every file includes the DOD5015 Record section, which is a default set of basic metadata fields. The default record metadata fields are:
Record | |
---|---|
Publication date* | The date that the record is published. Select the date from the calendar selection box. |
Originator* | The person or department in the originating organization. |
Originating Organization* | The organization that created the record. |
Media Type | The general media type such as audio, video, or document. |
Format | The format in which the record is stored, such as electronic or physical file. |
Date received | The date that the record was received from the originator. |
Addressee | The email address of the originating organization to be used for correspondence. |
Other Addressee | The secondary recipients of the message (CC). |
Location | The physical location of the record, generally only applicable to non-electronic records. |
Supplemental Marking List | Any additional properties applicable to the record. This list is defined by
the Alfresco administrator in the List of Values in the
RM Admin Tools. This is available in both standard and DoD 5015.2-STD compliant File Plans. |
You can't save this page until you complete any required fields.
If a record has mandatory metadata that hasn't been completed then a message lets you know that required metadata is missing.
If you apply an action to a folder then it will also be applied to all records within the folder.
Action | Select this to... |
---|---|
Cut off | Cuts off the record/folder and triggers the retention period. Records can't be added to a folder that's been cut off. |
End Retention | Ends the retention period for the record/folder. |
Transfer | Transfers the record/folder to the previously specified location. An audit trail and
metadata is retained. By default transferred records/folders are temporarily held in the Transfers area of the File Plan until you hover over them and click Complete Transfer. |
Accession | Transfers the record/folder to the previously specified location. An audit trail and
metadata is retained. This usually involves the specific legal and physical transfer of records between organizations. By default accessioned records/folders are temporarily held in the Transfers area of the File Plan until you hover over them and click Complete Transfer. |
Destroy | Removes the record/folder content from the Records Management system. If the
Maintain record metadata after destroy option is selected in the
retention schedule, then a visual representation of the record, an audit trail, and
metadata is retained in the File Plan. If the record was declared from a file in an Alfresco site then the file is also removed. |
Icons next to the record/folder indicate their current stage in the schedule.
Access a Records Management site just as you would any other Alfresco site, from the My Sites dashlet or the Sites menu.
Instead of storing your files in a document library as you do in a "regular" Alfresco site, in a Records Management site you file your records in the File Plan. And you can't edit the content of records; once they're in the File Plan record content is considered to be final.
You file records by adding them from your computer to the File Plan, or if you're in another Alfresco site you can declare a file as a record and it will be added to the Records Management site. Once files are added to the File Plan you can edit their metadata (properties) but you can't edit their actual content.
If you're new to Alfresco then take a look at Using Alfresco [53] to help you get started.
When you have added all required metadata to a record you can mark the record as complete. This makes it an active part of the File Plan, and subject to the rules of the retention schedule it is associated with.
It then goes through various time and event based steps such as cut off and retention, until it is eventually transferred elsewhere, or destroyed, according to its retention schedule.
The top level of the File Plan is created when you create a Records Management site. This is like an empty virtual filing cabinet - you then add drawers (categories), folders, and records to it.
Remember that it's far more versatile than a physical filing cabinet, but the following rules are enforced when working with the File Plan structure:
The structure of the File Plan will generally reflect different parts of your organization and can be made up of the following elements:
You can create a File Plan structure from scratch or load the Records Management test data [60] to use as a starting point. This gives you a sample File Plan that you can rework to meet your needs.
You can also automate the File Plan by applying rules to categories and folders [61]. This means that records can be moved automatically through the record lifecycle, without you having to do any of the work.
The records list takes up most of the File Plan main page. You can filter the records list and navigate the File Plan using the explorer panel down the left side of the page.
The explorer panel has the following sections:
The location path above the content list shows your current position in the File Plan
hierarchy. Each location path item is a link so you can easily return to any part of the
current navigation path. Click to display the contents of the folder one level higher.
Use the sort menu to change the criteria used to sort the File Plan contents. You can toggle between ascending and descending sort order.
When you create a container (category or folder) the system records the date of creation and the user who created it. This information is recorded in the object's metadata. Metadata can be thought of as a set of properties, and are where all key information about an item, folder, or category is stored. Record categories carry the most metadata as they hold the retention instructions for the whole category.
The following rules are enforced when working with the File Plan structure:
The Customize Dashboard page displays the current layout and configuration of your dashboard.
The Import Data Set dashlet is added to the site dashboard.
A sample File Plan and associated data is imported to your Returns Management site. You can explore and edit the File Plan as you would with a plan you created from scratch.
The New Record Category dialog box displays.
Metadata field | Description |
---|---|
Name* | The name for the record category. |
Title* | The title for the record category. |
Description | A description of the record category. |
Record Category ID* | A unique identifier for the record category is generated automatically. You can change this now, but you can't edit it once the category has been created. |
Vital Record Indicator | Defines whether records in this category have a review process. The Vital Record
Indicator is applied to all record folders within that category. You can change this
at folder level. Users with Records Manager permissions receive a notification email when vital records are due for review. |
Period | The time period for the review cycle. Reviews are recurring based on the period
you select. The review period is required when the Vital Record
Indicator option is selected. Note: The "Quarter" option splits the year into 4 sets of 3 months, beginning
with Jan/Feb/March. "Financial Quarter" is the same but based on the start date of
your system-configured financial year.
The review period is displayed on
the details page for folders and records in the category. |
Expression | Enter a number as the Expression to accompany the
Period type. If you enter “Week” and “3”, this would mean a
review cycle of 3 weeks. If you select a Period that doesn't require an Expression then this field isn't available. |
The new category displays in the File Plan.
The New Record Folder dialog box displays.
Metadata field | Description |
---|---|
Name* | The name for the record folder. |
Title* | The title for the record folder. |
Description | A description of the record folder. |
Record Folder ID* | A unique identifier for the record folder is generated automatically. You can change this now, but you can't edit it once the folder has been created. |
Location | If relevant specify the physical location of the records contained within this folder. |
Supplemental Marking List | If available, select any suitable properties from the list. Entries on this list are set up by your Alfresco administrator and are only available if you have been given the required permission. |
Vital Record Indicator | Defines whether records in this folder have a review process. The Vital Record
Indicator is applied to all records within the folder. You can change this at record
level. Note: If you don't select this option and the category the folder is in has a
Vital Record Indicator set, then the category setting will be applied to the folder
once it is created.
If you do select this option it will override any Vital Record Indicator set in the category. Users with Records Manager permissions receive a notification email when vital records are due for review. |
Period | The time period for the review cycle. Reviews are recurring based on the period
you select. The Review Period is required when the Vital Record
Indicator check box is selected. Note: The "Quarter" option splits the year into 4 sets of 3 months,
beginning with Jan/Feb/March. "Financial Quarter" is the same but based on the
start date of your system-configured financial year. See Customizing the end of the financial year [37].
The review period is displayed on the
details page for records in the folder. |
Expression | Enter a number as the Expression to accompany the
Period type. If you enter “Week” and “3”, this would mean a
review cycle of 3 weeks. If you select a Period that doesn't require an Expression then this field isn't available. |
The new folder is now shown in the File Plan.
A retention schedule is attached to a record category, and once a file has been completed as a record it's subject to the rules of the retention schedule that's attached to the category it's in.
A retention schedule contains one or more steps that define a particular action to be carried out. These actions can be carried out after a period of time, after certain events, or a combination of the two.
The steps that can make up a retention schedule are:
Option | Description |
---|---|
Cut off | This is the first step in a retention schedule. Once a record is cut off this triggers the records retention period. You can't add records to a folder that's been cut off. |
Retain | This is an alternative first step that is a 'placeholder' step which delays the next retention step until after a selected time period or event. |
Transfer | Records are transferred from one location to another. This can be applicable to both electronic and non-electronic records, and will be used, for example, when transferring records from an organization to an archive. |
Accession | An advanced form of transfer usually involving the specific legal and physical transfer of records between organizations. |
Destroy | Electronic records are removed from the Records Management system and destroyed, and non-electronic records must be destroyed. |
Retention steps can be manually completed once they are considered eligible (the time period has passed and/or the events have been completed), though the retain and cut off steps can be completed automatically by a system process that is run daily. All other retention steps must be completed manually, or by setting up a rule to complete them automatically. If a retention step is complete, then additional options are available for folders or records, dependant on whether the retention schedule is set to folder or record level, see Actioning retention steps [47].
Records that are associated with this schedule will be cut off after one month in the File Plan. They will then be retained in the File Plan for two years or until they're no longer needed, whichever comes first. At that point they will then be destroyed.
The category details page displays and if the category already has a retention schedule then you'll see the schedule summary and steps.
Field | Description |
---|---|
Retention Authority | The authority that states how the record should be retained and disposed, for example Sarbanes-Oxley Act (SOX) or Corporate procedures. |
Retention Instructions | A summary of the retention schedule. This information is not actively used but this text is displayed in the record category summary in the File Plan, and is important from a legal perspective. |
Applied to | Record Folder: the retention schedule is applied to
folders and all operations occur at the folder level. With this setting, you cannot
manage records as individual units. If you cut off the folder, all records will be
cut off. Record: the retention schedule is applied to records and all operations occur at the record level. |
The category details page now displays a summary of the new or updated retention schedule.
The category details page displays showing the retention schedule summary.
The Edit Retention Schedule page displays.
Option | Description |
---|---|
Cut off | This is the first step in a retention schedule. Once a record is cut off this triggers the records retention period. You can't add records to a folder that's been cut off. |
Retain | This is an alternative first step that is a 'placeholder' step which delays the next retention step until after a selected time period or event. |
Transfer | Records are transferred from one location to another. This can be applicable to both electronic and non-electronic records, and will be used, for example, when transferring records from an organization to an archive. |
Accession | An advanced form of transfer usually involving the specific legal and physical transfer of records between organizations. |
Destroy | Electronic records are removed from the Records Management system and destroyed, and non-electronic records must be destroyed. |
Option | Description |
---|---|
After a period of | Select the time period after which the step action will take place. Note: If you
select XML Duration from the Period Type drop down list you can specify a time interval
using XML syntax.
The syntax should take the form of: P = Period (required) nY = Number of years nM = Number of months nD = Number of days T = Start time of a time section (required if specifying hours, minutes, or seconds) nH = Number of hours nM = Number of minutes nS = Number of seconds For example, 'P2M10D' represents two months and ten days. Created Date = The date when the file or record is first added to Alfresco. Retention Action = The date when the last retention action took place. Don't select this for the first step in the schedule. The "Quarter" option splits the year into 4 sets of 3 months, beginning with Jan/Feb/March. "Financial Quarter" is the same but based on the start of your system-configured financial year. See Customizing the end of the financial year [37]. |
When event happens | Select the event after which the step action will take place. Most events must be completed manually in the record details page, or you can use rules to automatically complete these events. The Obsolete, Superseded, and Related Record Transferred To Inactive Storage events are automatically completed when relevant relationships are set up between records [38]. |
The date selected here is displayed as the Retention as of date in the details page for records or folders, depending on which the retention applies to. If you select an event then this field will display None, and you should complete the event on the details page.
The category details page displays and if the category already has a retention schedule then you'll see the schedule summary and steps.
By managing your user permissions you can create restricted areas of the File Plan that are only available to selected users. For an area that all users should have access to, you need to make sure that all users have been given permission to see it.
The Manage Permissions page opens with the name of the selected folder or category displayed. Any users and groups that currently have permissions assigned are also displayed. You can change existing user permissions or Remove them entirely.
All users, groups, and roles matching the search are displayed.
Read and File allows users to work with content, whereas users with Read Only permission can only view content.
The permissions you've set are now applied to the folder or category you selected and any folders or categories it contains. You can change these as needed on a folder or category basis.
Your Alfresco administrator can also set up your system so that emails to specified addresses are captured and stored as records
A record is not considered to be complete until all the required metadata has been added to it. You select Edit Metadata to complete required metadata.
In DoD 5015.2-STD compliant Records Management sites you can also select to Add Record Metadata and associate the file with a record type, so that when you edit metadata there is type-specific metadata to add.
Once that's done you can select to Complete Record and it will be subject to the retention rules that apply to the folder you've placed it in.
Only the Name and Title are required, but you should enter enough information so that the record will be recognized by other users.
A new record is created and displays in the File Plan as an incomplete record. You need to make sure any required metadata is added before you can set records to complete.
All unfiled records are displayed.
The Add Record Metadata option is only available in DoD 5015.2-STD compliant Records Management sites.
The available record types are displayed.
Record type | Description |
---|---|
Web Record | A web page. |
Scanned Record | A file that is scanned into the Records Management system. |
PDF Record | A PDF file. |
Digital Photograph Record | A photographic image file. |
Some record metadata is mandatory. Before you can complete a record, you must edit the metadata to complete the mandatory fields.
The Edit Metadata page displays. The metadata fields you see on this page depend on the file type, and whether or not record types have been associated with the file. The metadata is divided into sections, with additional sections dependant on if a record type has been associated with the item.
If your Records Management system is DoD 5015.2-STD compliant then every file includes the DOD5015 Record section, which is a default set of basic metadata fields. The default record metadata fields are:
Record | |
---|---|
Publication date* | The date that the record is published. Select the date from the calendar selection box. |
Originator* | The person or department in the originating organization. |
Originating Organization* | The organization that created the record. |
Media Type | The general media type such as audio, video, or document. |
Format | The format in which the record is stored, such as electronic or physical file. |
Date received | The date that the record was received from the originator. |
Addressee | The email address of the originating organization to be used for correspondence. |
Other Addressee | The secondary recipients of the message (CC). |
Location | The physical location of the record, generally only applicable to non-electronic records. |
Supplemental Marking List | Any additional properties applicable to the record. This list is defined by
the Alfresco administrator in the List of Values in the
RM Admin Tools. This is available in both standard and DoD 5015.2-STD compliant File Plans. |
You can't save this page until you complete any required fields.
A task will be assigned to the selected user and will show in their My Tasks dashlet. Once they mark the task as done the information they provide will be shown in a task assigned to the user who requested the information. Access the information through your My Tasks dashlet and click Task Done to close the information request.
If a record has mandatory metadata that hasn't been completed then a message lets you know that required metadata is missing.
In many cases you might want to create records from files that already exist in Alfresco, rather than creating a record from scratch.
With Alfresco Records Management you can declare files in non-Records Management site as
records. When you create an "easy access record", a record of the file is added to the Records
Management site. The file is still visible in its original site, identified by the icon, but
is locked and with a limited set of actions available.
This means that most users never need to think about records, file plans, or retention schedules. They just declare the file as a record, and the rest is handled by the Records Administrator and any rules that they've set up.
When a record is created from a file it's added to the Unfiled Records area of the Records Management site. A Records Manager then has numerous options for Filing an unfiled record [43] and Managing unfiled records [70]
A file declared as a record is added to the Unfiled Records area, in the explorer panel of the Records Management site.
It's still
visible in its original site as an easy access record, identified by the icon, but
is locked and with a limited set of actions available.
The version of a file declared as a
record is added to the Unfiled Records area, in the explorer panel of the Records Management
site, and is identified there as a version record by the icon.
It's still available in its original site, with a full set of actions available.
Each time a new major or minor version of the file is created, the version is declared as a
record and added to the Unfiled Records area, in the explorer panel of the Records Management
site. It's identified there as a version record by the icon.
It's still
available in its original site, with a full set of actions available, identified by the
major versions icon or the
all versions
icon.
And as with standard Alfresco functionality you need to have the required permissions before you can do anything with files.
You can see version details of records created from versions in the file preview screen on the Records Management site. When records are created from versions of the same file, a relationship between the records is automatically created.
You can also classify a file [71] and declare it as a record at a later date, and it will keep any classifications applied.
See Classification rules and tips [78] for more on classifying content.
You can autoclassify by by adding instructions, manually apply classifications and security marks, or both.
You can classify using both Security Classification and Security Groups. You'll only see the classification options that you have security clearance for.
To autoclassify:
All the topics you've selected will have their instructions applied to the item you're classifying.
To manually add classifications and security marks:
Downgrade Schedule
Set a schedule for when the item will be downgraded, for example, from Top Secret to Secret. You can enter a specific date for the downgrade to take place, an event that means a downgrade should be considered, and instructions on how to carry out the downgrade. All of these are optional, but once you've entered a downgrade date, event, or both, you're required to enter instructions.
Declassification Schedule
Set a schedule for when the file will be declassified. These means when its classification level will be set to Unclassified. You can enter a specific date for the declassification to take place, an event that means declassification should be considered, and exemptions for when declassification shouldn't take place. All of these are optional.
See How security controls work [79] for more details.
The item now displays its classification level, and can only be seen by those with the required security clearance.
The classification reason and classification-related properties can be seen in the Properties when you preview the file.
If you delete a classified file then it's permanently deleted and isn't available in your Trashcan. If you delete a classified folder then all of its content is permanently deleted, even items that haven't been directly classified themselves.
The file is added to the Unfiled Records area, in the explorer panel of your Records
Management site. It's still visible in its original site, identified by the icon, but is locked and
with a limited set of actions available.
A file that has been declared as a record can be deleted. The records remain in the File Plan.
The file is added to the Unfiled Records folder, in the explorer panel of your
Records Management site, and is identified there as a version record by the icon. The file is still
available in its original site, with a full set of actions available.
If you delete or destroy a record that was declared from a version, then that version is marked as deleted and can't be accessed. Other versions of the file remain unaffected.
The Set Auto-Declare Options screen opens with the default setting of Never.
Each time a new major version of the file
is created, the version is declared as a record and added to the Unfiled Records
area, in the explorer panel of your Records Management site. It's identified there
as a version record by the icon. In its originating site it'll
display the
icon, and the
icon next to each recorded version in the Version History
section of the file preview screen.
Each time a new major or minor
version of the file is created, the version is declared as a record and added to the
Unfiled Records area, in the explorer panel of your Records Management site. It's
identified there as a version record by the icon. In its
originating site it'll display the
icon, and the
icon next to each recorded version in the Version History
section of the file preview screen.
You can change the settings whenever you need to, but any records already created will be unaltered.
Files that have been declared as records can be moved to anywhere in their current site, but cannot be moved to a different site.
The file is moved to it's new location in the site. The record of the file in the Records Management site is unaffected.
This can help to avoid any confusion with site members trying to work with files that have been declared as records.
Once hidden, the record created from the file is available as usual in the Records Management site, but in its originating site it's no longer available in the document library.The record's now hidden from the Document Library. Once a record has been hidden it can't be unhidden. If a record is rejected from the Records Management site then it will become visible again with a warning that it's been rejected.
Action | Select this to... |
---|---|
View Details | View the record category details page, where you can see the metadata and a full list of actions. |
Edit Metadata | Edit the record category metadata. |
Manage Permissions | Set the user and group access for the category. |
Copy to | Create a copy of the category in another location in the File Plan. |
Move to | Move the category to another location in the File Plan. |
Delete | Delete the category from the File Plan. |
View Audit Log | View the auditing information for the category. The Audit Log displays the activity information and has options to export and file as a record. |
Manage rules | Create and edit rules so that category content is managed automatically. |
The details page displays. On this page, you can see the metadata, the retention schedule, and the available actions in the Actions list.
If no retention schedule has been set for the record category, you create it here. If a retention schedule exists, you can edit it.
Where a retention schedule exists, click View Description in the Retention Steps section to display the description for a particular step.
The Edit Metadata page displays.
A confirmation dialog box displays.
The record category is removed from the Records Management system.
Action | Select this to... |
---|---|
View Details | View the record folder details page, where you can see the metadata and a full list of actions. |
Edit Metadata | Edit the record folder metadata. |
Close Folder | Close the folder. A closed record folder cannot accept records for filing. When you close the folder, this action toggles to the Re-open Folder action. |
Edit Retention Date | If a folder is subject to a folder level retention schedule, you can review the retention date for the next step in the retention schedule that applies to the folder. |
Review All | Mark all vital records in a folder as having been reviewed. |
Add to Hold | Hold the folder. You can view on hold folders in the Holds area on the explorer panel. When you hold the folder, this action toggles to the Remove from Hold action. |
Copy to | Create a copy of the folder in another location in the File Plan. |
Move to | Move the folder to another location in the File Plan. |
Manage Permissions | Set the user and group access for the folder. |
Delete | Delete the folder from the File Plan. |
View Audit Log | View the auditing information for the folder. The Audit Log displays the activity information in a new window and has options to export or file this information as a record. |
Manage rules | Create and edit rules so that folder content is managed automatically. |
The details page displays. On this page, you can see the metadata and the available actions in the Actions list.
The Edit Metadata page displays.
The record details page is displayed. All incomplete events for the current schedule step are displayed.
The Edit Retention Date dialog box displays. The current retention date is highlighted.
A message displays confirming that the retention date is updated. This overrules any review dates set in the retention schedule.
If you apply an action to a folder then it will also be applied to all records within the folder.
Action | Select this to... |
---|---|
Cut off | Cuts off the record/folder and triggers the retention period. Records can't be added to a folder that's been cut off. |
End Retention | Ends the retention period for the record/folder. |
Transfer | Transfers the record/folder to the previously specified location. An audit trail and
metadata is retained. By default transferred records/folders are temporarily held in the Transfers area of the File Plan until you hover over them and click Complete Transfer. |
Accession | Transfers the record/folder to the previously specified location. An audit trail and
metadata is retained. This usually involves the specific legal and physical transfer of records between organizations. By default accessioned records/folders are temporarily held in the Transfers area of the File Plan until you hover over them and click Complete Transfer. |
Destroy | Removes the record/folder content from the Records Management system. If the
Maintain record metadata after destroy option is selected in the
retention schedule, then a visual representation of the record, an audit trail, and
metadata is retained in the File Plan. If the record was declared from a file in an Alfresco site then the file is also removed. |
Icons next to the record/folder indicate their current stage in the schedule.
The Add to Hold screen displays.
A message displays confirming that the folder is on hold, and the folder now
displays the icon.
A message displays confirming that the folder is closed.
A confirmation dialog box displays.
The record folder is removed from the Records Management system.
Action | Select this to... |
---|---|
Download | Download the file to your computer. |
Edit Metadata | Edit the metadata for the record. |
Complete Record | Declare the file as a record. All required metadata fields must be complete. When you declare the file as a record, this action toggles to the Reopen Record action. |
Reviewed | Marks a vital record as reviewed. |
Reopen Record | Revert the item back to an incomplete record. |
Add Record Metadata | Associate an undeclared record with one or more record types. This option is only available in DoD 5015.2-STD compliant Records Management sites. |
Add to Hold | Hold the record. You can view on hold records in the Holds area on the explorer panel. When you hold the record, this action toggles to the Remove from Hold action. |
Copy to | Create a copy of the record in another location in the File Plan. |
Move to | Move the record to another location in the File Plan. |
File to | File an unfiled record to the File Plan. |
Link to | File a record in multiple locations in the File Plan and create a link. This gives the appearance of duplicating the record in another location, though actually there is just one record stored in multiple folders. Changes made to the record in one location will be reflected in the other locations. |
Unlink Record | Available for records that have been linked from another record, you can unlink the record. This will remove it from the folder it was linked to. |
Delete | Delete the record from the File Plan. |
View Audit Log | View the auditing information for this record. The Audit Log displays the activity information in a new window and has options to export or file this information as a record. |
Reject | Reject an unfiled record. If you select to reject a record then you need to enter a reason for the rejection. This reason be viewed when looking at the file the record was created from in it's originating site. |
Request Information | Request further information about a record from other users. This is only available for incomplete records. |
Manage Permissions | Use the Manage Permissions option to control user permissions for records. |
Add Relationship | Add a relationship between records such as a cross-reference or obsoleted by. |
When a record has been completed not all of these actions will be available.
When
the record is on hold (identified by the icon), a limited set of actions is
available.
Vital records display the icon.
The record details page displays. On this page, you can see the record details and the available actions in the Actions list.
A link is created in the destination folder. All copies of the record display the
icon.
However, if you select Obsoleted by/Obsoletes or Superseded by/Supersedes, then any outstanding retention schedule obsoleted or superseded events will be automatically completed.
The selected record is shown in the New Relationship screen.
You can repeat these steps to add relationships to multiple other records. You can see details of any relationships when you click on a record to preview it, and relationships can be added and deleted here if you have the correct permissions.
When records are created from versions of the same file, a relationship between the records is automatically created.
A message displays saying that the record has been successfully reviewed. The review date is displayed in the record audit log.
Unfiled records can have been declared as records from a non-Records Management site, from within the Unfiled Records area, or could be reports generated from within the File Plan. Filing an unfiled record [43] describes how records in the Unfiled Records area are processed.
You don't have to use this area as a flat structure, you can configure it to your own requirements.
You can create a full folder hierarchy within the Unfiled Records area and use rules [61] to automate the processing of unfiled records.
You can use the Manage Permissions option to control which users can file and reject unfiled records.
There are also many of the usual options available, including the options to copy and move records and folders within the Unfiled Records area. If you select to Reject a record then you need to enter a reason for the rejection. This reason can be viewed when looking at the file the record was created from in its originating site.
The record details page is displayed. All incomplete events for the current schedule step are displayed.
The Edit Review Date dialog box displays. The current review date is highlighted.
A message displays confirming that the review date is updated. This overrules any review dates set at folder or category level.
The Edit Retention Date dialog box displays. The current retention date is highlighted.
A message displays confirming that the retention date is updated. This overrules any review dates set in the retention schedule, even if you update the retention schedule.
If you apply an action to a folder then it will also be applied to all records within the folder.
Action | Select this to... |
---|---|
Cut off | Cuts off the record/folder and triggers the retention period. Records can't be added to a folder that's been cut off. |
End Retention | Ends the retention period for the record/folder. |
Transfer | Transfers the record/folder to the previously specified location. An audit trail and
metadata is retained. By default transferred records/folders are temporarily held in the Transfers area of the File Plan until you hover over them and click Complete Transfer. |
Accession | Transfers the record/folder to the previously specified location. An audit trail and
metadata is retained. This usually involves the specific legal and physical transfer of records between organizations. By default accessioned records/folders are temporarily held in the Transfers area of the File Plan until you hover over them and click Complete Transfer. |
Destroy | Removes the record/folder content from the Records Management system. If the
Maintain record metadata after destroy option is selected in the
retention schedule, then a visual representation of the record, an audit trail, and
metadata is retained in the File Plan. If the record was declared from a file in an Alfresco site then the file is also removed. |
Icons next to the record/folder indicate their current stage in the schedule.
The Add to Hold screen displays.
A message displays confirming that the record is on hold, and the record now
displays the icon.
The record is now marked as an incomplete record in the file plan and is not subject to the rules of the retention schedule. You can set it to complete again whenever needed.
A confirmation dialog box displays.
The record is removed from the Records Management system. If the record was declared from a file in an Alfresco site then the file is also removed.
You can create as many different holds as you want, which are represented as folders in the Holds area.
In the Holds area there's a New Hold option which you use to set up your different hold types. Once you have a list of different holds you can put records [103] and record folders [92] on as many of the different holds as required.
You can also add records to a hold direct from the Records Search [106].
When you add a folder to a hold, all records within the folder are also added to the hold. They'll stay on hold until removed from the hold or the hold is deleted.
You can use the Manage Permissions option to control which users can view, create, edit, and delete holds. Users who don't have read permission for a specific hold will not receive any indication that records it contains are in that hold.
A new hold is now available for putting records on. You put records on hold by hovering over them in the File Plan and selecting the Add to Hold option.
This can be useful if you want to quickly build your File Plan, or parts of it, based on a File Plan that already exists on an Alfresco system.
You can move entire blocks of content – record categories, record folders, records, metadata, and retention schedules – within a File Plan or to another File Plan.
Files are imported and exported using the Alfresco Content Package (ACP) format. You can also choose to import and export the content as a zip file. Exported files contain all structural information including record categories, folders, and retention schedules, so they make for seamless building of a File Plan in another Alfresco system.
Depending on your browser, you are either prompted to specify a destination or the file is automatically downloaded to a default location.
Depending on your browser, you are either prompted to specify a destination or the file is automatically downloaded to a default location.
The Records Management content is extracted from the uploaded file with it's original structure maintained.
Rules dictate how content entering, leaving, or currently residing in a category or folder is managed.
There are three parts to a content rule:
The events that can trigger a rule are:
Here are some examples of how you can use rules to automate repetitive tasks:
Use rules to manage your File Plan content automatically. There are two ways to define rules: create your own rules or link to rules already created for a different category or folder.
If you create rules for a category, depending on the rule settings, they can apply to folders and categories created in the category, records placed in folders in the category, or both.
Here are 3 examples of conditions that you could apply to trigger a rule:
When you've selected an action you might need to select further options, for example if you select to reject items click Reject to specify a reason.
There are also extensive autocomplete options [117].
If you select Execute script then scripts are only available if they've been set up by your Alfresco administrator in Repository > Data Dictionary > Records Management > Records Management Scripts.
Records will be put into the File Plan based on each individual record property value.
So for example you could set a path of /category/{node.rma:location}. When the rule is run records with a Location property of US would be put in /category/US, and records with a Location property of France would be put in /category/France.
By default autocomplete options are based on the first two letters you type, and only five options for each type of suggestion are offered at a time. Type more letters to narrow down the displayed options.
Select the site then select a folder. Check the rules listed to make sure you're linking to the correct folder.
You can create many rules to form a full set of rules, and then apply multiple rules to categories and folders.
When you select the Manage Rules action for a category/folder with defined rules, the Rules page is split into two.
The left side of the page lists the rules that make up the rule set. If the category/folder inherits rules from a parent category/folder, those rules appear here too. The rules run in the order they're listed. Inherited rules are always run first.
A check mark to the left of the rule means it's active.
Selecting an individual rule in this list displays its details on the right side of the page.
On the New Rule page you can add a new rule to a set of rules in exactly the same way as the first time you created a rule, see creating a rule [124].
If a category/folder has inherited rules these are displayed on the left side of the page.
Any inherited rules are turned off for the category/folder and Don't Inherit Rules is shown. You can click Don't Inherit Rules to turn inherited rules back on for the category/folder.
If you might want to use the rule again, consider disabling it instead. Edit the rule to do that.
When you select the Manage Rules action for a category or folder with linked rules, the Rules page shows the name and path of the category/folder whose rule set is being referenced.
Changes to the rule set have to be done in the category/folder where the rules were originally defined. It's easy to get to the Rules page for the source category/folder: just click View Rule Set.
You can only select locations you have permission to access.
This breaks the link to the original rule set and links you to the new one.
The link between the current category/folder and the linked rules is now broken.
You can either do a basic search, just searching for a term as you would in a search engine, or you can use the advanced search functionality. There's lots of options available for you to set really specific searches that you can use again and again. See Advanced search options [127] for more details on getting the most out of the search tool.
The Search page displays.
Search criteria | Description |
---|---|
Search by | Select from the options available what you want to search for. When you select an option it's added to the field below where you can then enter your search criteria. For example if you select Retention Schedule > Retention Action Name, the field name retentionActionName: is added and you can then type a retention action name, such as retentionActionName:cutoff. Don't insert a space between the colon and the search term. You can select multiple criteria. |
Search Date | Select a date to search on or even multiple dates, see searching for date ranges [136]. |
The search results display in a table on the Results tab.
Title | Field name | Description |
---|---|---|
Keywords (text and name) | keywords | Used to search for the name, title, description fields, and text. This field is tokenized. |
Identifier | identifier | The unique identifier for the record. The system generates this identifier. |
Name | name | The name of the record. This is populated with the name of the file that was uploaded. |
Title | title | The title of the record. This is populated with the name of the file that was uploaded. Change the value to show the title of the record. |
Description | description | A short description of the record. |
Creator | creator | The person(s) who created this record. |
Created | created | The date that this record was created. |
Modifier | modifier | The last user to make any modifications to this record. |
Modified | modified | The time that the last modification occurred. |
Author | author | The name of the document author(s). |
Originator | originator | The person or department in the Originating Organization. |
Date Filed | dateFiled | The date that the record was filed. |
Publication Date | publicationDate | The date that the record is published. Select the date from the calendar selection box. |
Review Date | reviewDate | The date that this record is due for review. |
Originating Organization | originatingOrganization | This is who created the document/record in the first place. Often this will be the organization running the software, but in some cases might be an external organization. |
Media Type | mediaType | The type of the media. |
Format | format | The media on which the record is stored. |
Date Received | dateReceived | The date that the record was received from the originator. |
Location | location | The physical location of the record. This is mainly applicable to non-electronic records. |
Addressee | address | The address of the originating organization to be used for correspondence. |
Other Addressee | otherAddress | The CC list from an email. |
Supplemental Marking List | markings | This list is defined in the RM List of Values tool in the RM Admin Tools. |
Retention Events | dispositionEvents | User defined retention events. |
Retention Action Name | dispositionActionName | The name of the retention action. The values can be Accession, Destroy, Retain, Transfer, and Cutoff. |
Retention Action As of Date | dispositionActionAsOf | The date that the retention action occurred. |
Retention Events Eligible | dispositionEventsEligible | Specifies whether this record has any eligible events. The values can be true or false. |
Retention Period | dispositionPeriod | The period of time to which the retention action is set. The values can be day, fymonthend, fyquarterend, fyyearend, monthend, quarterend, yearend, immediately, month, none, notset, quarter, week, or year. |
Has Retention Schedule | dispositionSchedule | Specifies whether this record is under a retention schedule. The value can be true or false. |
Retention Instructions | dispositionInstructions | The text summary of the retention steps. |
Retention Authority | dispositionAuthority | The legislation relevant to the retention instructions, in particular, relating to the disposal of the record. For example, GRS 2 Item 7. |
Hold Reason | holdReason | The reason that the record is in the Hold area. |
Vital Record Review Period | vitalRecordReviewPeriod | The review period set for a vital record. The values can be day, fymonthend, fyquarterend, fyyearend, monthend, quarterend, yearend, immediately, month, none, notset, quarter, week, year. |
Record type | Special type name | Description |
---|---|---|
Scanned records | dod:scannedFormat | Image Format |
Scanned records | dod:scannedFormatVersion | Image Format Version |
Scanned records | dod:resolutionX | Image Resolution X |
Scanned records | dod:resolutionY | Image Resolution Y |
Scanned records | dod:scannedBitDepth | Scanned Bit Depth |
PDF records | dod:producingApplication | Producing Application |
PDF records | dod:producingApplicationVersion | Producing Application Version |
PDF records | dod:pdfVersion | PDF version |
PDF records | dod:creatingApplication | Creating application |
PDF records | dod:documentSecuritySettings | Document security settings |
Digital photograph records | dod:caption | Caption |
Digital photograph records | dod:photographer | Photographer |
Digital photograph records | dod:copyright | Copyright |
Digital photograph records | dod:bitDepth | Bit Depth |
Digital photograph records | dod:imageSizeX | Image Size X |
Digital photograph records | dod:imageSizeY | Image Size Y |
Digital photograph records | dod:imageSource | Image Source |
Digital photograph records | dod:compression | Compression setting |
Digital photograph records | dod:iccIcmProfile | ICC/ICM profile |
Digital photograph records | dod:exifInformation | EXIF information |
Web records | dod:webFileName | Web file name |
Web records | dod:captureMethod | Method of capture |
Web records | dod:contentManagementSystem | Content management System |
Web records | dod:webPlatform | Web platform |
Web records | dod:webSiteName | Web site name |
Web records | dod:webSiteURL | Web site URL |
Web records | dod:captureDate | Date of capture |
Web records | dod:contact | Capture contact |
The Critera tab is auto-filled with the saved search options. You can change these if you want.
The search results display in a table on the Results tab.
The search you save will be available for all site members.
Depending on your browser you are prompted to open or save the file.
The Critera tab is displayed so you can check that this is the search you want to delete.
The Add to Hold screen displays.
A message displays confirming that the record or folder is on hold.
Full text searches can be very simple, using a text string, or you can do more complex searches with multiple matches, tokens, phrases, wildcards, ranges, and grouping. The search syntax follows the format:
<field-name>:<search-value>
Alfresco Records Management has a large number of fields to search against, see Search field options [140] and Search record type field options [141]. The search query requires that you enter the internal name of these fields in the text box. The Search by menu list assists you when entering the fields.
To search for phrases, wrap the value string in "quotes". You can also use the wildcard matching characters, question mark (?) for a single character, and asterisk (*) for zero or more characters to apply to any text value.
To find a simple text string in any record name, title, description, or content, enter the following in the Query Text box:
keywords:healthcareThe keywords field is a special field name that allows you to match against the name, title, description, and content of a record.
The basic syntax for matching against a field in search queries is the syntax format of the keywords field, then the colon (:), followed by the value to match against.
keywords:health*
keywords:healthcare keywords:hospital
keywords:healthcare AND keywords:hospital
(KEYWORDS:healthcare AND KEYWORDS:hospital) AND NOT KEYWORDS:clinic
originator:"John Smith"
originator:"John Smith*"
You can also escape embedded quotes in a phrase using back slash \.
=part
This search will match "part" but will not match other terms that contain "part", such as "partners".
"2009-09-10"
[MIN TO "2010-01-10"]
Use the MIN special token to denote the minimum possible date that can be represented by the system.
Use the MAX and NOW special tokens to indicate the maximum possible date and the current date, respectively.
dateFiled:NOW
ASPECT:"dod:digitalPhotographRecord"
Special fields | Description |
---|---|
dod:scannedRecord | Search for all scanned records. |
dod:pdfRecord | Search for all PDF records. |
dod:webRecord | Search for all web page records. |
location:””
ISNULL:"cm:description"
ISNOTNULL:"cm:title"
Whenever a record is transferred, added to a hold, accessioned or destroyed, you have the option to file a report. The report contains details of the item, the retention authority, what the retention step was, when it was performed, who by, and any location changes. The report is filed as a record.
The audit log contains the entire history of an object since the point it was added to the File Plan, and can be useful for finding out about specific events that have occurred during an objects life cycle, and any users that have been involved.
Every entry in the audit log is timestamped and where metadata has been changed, the original values and changed values are recorded.
When viewing an audit log you can also select to export it or to file it as a record.
The audit log displays.
See Supported Platforms [160] for information about prerequisites and requirements.
alfresco-rm-enterprise-repo-2.6.x.amp | Contains Records Management functionality that's applied to an existing Alfresco installation. |
alfresco-rm-enterprise-share-2.6.x.amp | Contains Records Management functionality that's applied to an existing Alfresco Share installation. |
Deleting these directories forces Tomcat to read the edited WAR files when Alfresco is restarted.
java -jar bin\alfresco-mmt.jar install amps\alfresco-rm-enterprise-repo-2.6.x.amp tomcat\webapps\alfresco.war
java -jar bin\alfresco-mmt.jar install amps_share\alfresco-rm-enterprise-share-2.6.x.amp tomcat\webapps\share.war
java -jar bin\alfresco-mmt.jar list tomcat\webapps\alfresco.warand
java -jar bin\alfresco-mmt.jar list tomcat\webapps\share.war
http://<your-server-name>:<port number>/share
At this point, the Records Management module is installed. Next, create a Records Management site.
Records Management (RM) consists of two AMP files, which are applied during installation. One of the AMP files, representing the core RM functionality, is applied to the Alfresco WAR file, and the other, representing the RM Share UI component is applied to the Share WAR file. Both of the AMP files need to be removed in order to uninstall RM. Use the Module Management Tool (MMT) to do this. For more information on the tool, see Module Management Tool (MMT) [164]
java -jar bin\alfresco-mmt.jar uninstall <ModuleId> <WARFileLocation>
java -jar bin\alfresco-mmt.jar list tomcat\webapps\alfresco.war
This shows the core RM component:
Module 'alfresco-rm-enterprise-repo' installed in 'tomcat\webapps\alfresco.war' - Title: Records Management - Version: 2.6 - Install Date: Mon November 6 12:04:49 BST 2017 - Description: Alfresco Record Management Extension
You'll need the Module ID, alfresco-rm-enterprise-repo, to uninstall the AMP file.
java -jar bin\alfresco-mmt.jar list tomcat\webapps\share.war
This shows the Share RM component:
Module 'alfresco-rm-enterprise-share' installed in 'tomcat\webapps\share.war' - Title: Alfresco Record Management Share Extension - Version: 2.6 - Install Date: Mon November 6 12:05:24 BST 2017 - Description: Alfresco Record Management Share Extension
You'll need the Module ID, alfresco-rm-enterprise-share, to uninstall the AMP file.
java -jar bin\alfresco-mmt.jar uninstall alfresco-rm-enterprise-repo tomcat\webapps\alfresco.war
java -jar bin\alfresco-mmt.jar uninstall alfresco-rm-enterprise-share tomcat\webapps\share.war
java -jar bin\alfresco-mmt.jar list tomcat\webapps\alfresco.warand
java -jar bin\alfresco-mmt.jar list tomcat\webapps\share.war
Deleting these directories forces Tomcat to read the edited WAR files when Alfresco is restarted.
The Name, URL Name and Description will be completed for you automatically. You can edit the Description if needed. The URL name is used as part of the site URL.
Settings for Records Management are listed in the <configRoot>/classes/alfresco/module/org_alfresco_module_rm/alfresco-global.properties file. For example:
rm.ghosting.enabled=true rm.notification.role=RecordsManager imap.server.attachments.extraction.enabled=false audit.enabled=true audit.rm.enabled=true audit.rm.runas=admin cache.writersSharedCache.maxItems=10000 cache.writersSharedCache.cluster.type=fully-distributed rm.rule.runasadmin=true rm.autocompletesuggestion.minfragmentsize=2 rm.autocompletesuggestion.maxsuggestions.path=5 rm.autocompletesuggestion.maxsuggestions.node=5 rm.autocompletesuggestion.maxsuggestions.date=5 rm.autocompletesuggestion.nodeParameterSuggester.aspectsAndTypes=rma:record,cm:content rm.dispositionlifecycletrigger.cronexpression=0 0/5 * * * ?
Any setting that is false by default, is not shown in the alfresco-global.properties.
Setting | Meaning |
---|---|
audit.enabled | Enable/disable auditing. Default is true. |
audit.rm.enabled | Enable/disable Records Management auditing. Default is true. |
audit.rm.runas | Set the user that the audit log runs under. Default is system.
Alfresco doesn't audit events triggered by the system; for example, cron jobs. Set
this value to admin for these jobs if you want them to be captured
in the audit log. Alternatively, create a user, provide the correct permissions and configure the jobs to run as that user. |
audit.rm.viewLog.maxSize=100 | The log can be viewed from Share or directly via the Audit log web script. By default the log does not exceed 100 entries. If the maximum size of the log is not configured in the alfresco-global-properties file then it will default to 100. If you include the size parameter in the request it will only be applied if it is less than or equal to the maximum size allowed, or it will be ignored. |
cache.writersSharedCache.cluster.type | Extended permission service cache: type of cluster used. Default is fully-distributed. |
cache.writersSharedCache.maxItems | Extended permission service cache: maximum number of items (node references) that are stored in the writer caches. Default is 10000. |
imap.server.attachments.extraction.enabled | Enable/disable IMAP server attachments. Default is false. |
rm.autocompletesuggestion.maxsuggestions.date | Auto-complete suggestions: maximum number of date suggestions to provide. Default is 5. |
rm.autocompletesuggestion.maxsuggestions.node | Auto-complete suggestions: maximum number of node suggestions to provide. Default is 5. |
rm.autocompletesuggestion.maxsuggestions.path | Auto-complete suggestions: maximum number of path suggestions to provide. Default is 5. |
rm.autocompletesuggestion.minfragmentsize |
Auto-complete suggestions: Minimum size of fragment to trigger a search. Default is 2. |
rm.autocompletesuggestion.nodeParameterSuggester.aspectsAndTypes |
Auto-complete suggestions: Comma-separated list of types and aspects used by the node parameter autocomplete suggester. Default is rma:record,cm:content. |
rm.content.cleaner | This setting is used in conjunction with
rm.content.cleansing.enabled=true. Default is
contentCleanser.522022M. When content is sent for deletion, it is cleansed using the default 5220.22-M algorithm. The content is then destroyed, and the node is deleted (if ghosting is not enabled). If you add a custom content cleaner bean, this can be specified using this property. |
rm.content.cleansing.enabled | Set whether content can be deleted immediately (data cleansing). This applies
to deleted (destroyed) classified records and classified documents. The default setting of false allows deleted (destroyed) files to be restored (from the Trashcan if they are documents, or by using a recovery tool, if they are records). This approach is only effective for installations with a single magnetic disk. In other situations, such as RAID or SSD, hardware techniques or process ensure that the content is non-recoverable. |
rm.dispositionlifecycletrigger.cronexpression |
Disposition lifecycle trigger cron job expression. Default is 0 0/5 * * * ?. |
rm.ghosting.enabled | Enable/disable ghosting of records, when a record is deleted. Default is true. |
rm.notification.role |
Specify which role receives notifications; for example, when notifications when vital records are due for review. Default is RecordsManager. A background job executes by default every 15 minutes to search for vital records that are due for review, and sends a notification. The template for the email notification is editable, and is stored in the Records Management section of the Data Dictionary. |
rm.record.contributors.group.enabled |
Set which groups can perform Records Management actions; for example, Declare as Record. Default is false. If this is set to true, only members of the RECORD_CONTRIBUTORS group can perform these actions. |
rm.rule.runasadmin | Require admin rights/ normal rights to run rules. Default is true. |
version.store.enableAutoVersionOnTypeChange | Set whether a version is automatically created when the type of a document is changed. Default is false. |
When your Alfresco Content Services installation is upgraded, you can apply the new AMP files for Alfresco Records Management.
For more information about upgrading, see Upgrading Alfresco [167].
You can start the Alfresco server at this point to verify that the upgrade was successful.
Follow the instructions in Applying the Records Management AMP files [168].
When you upgrade from a previous version of Records Management to the Alfresco Records Management install, any existing Records Management data is preserved (it is 'patched' in the same way as updated data in the server). The File Plan structures will appear as they did in 1.0 and the previous Records Management site is migrated. Therefore, you do not need to create the Records Management site again.
From Records Management 2.0 onwards you cannot create a record series; instead you create a record category with no retention schedule. The record series is retained as a deprecated model construct to be used when migrating existing record series from a 1.0 installation. This means that any previously created record series will appear and behave as record categories in 2.2, but will be of the deprecated type record series (directly extended from record category). If any custom data was defined for record series in 1.0, this will still appear in the Records Management site, but only for the migrated record series.
Note also that any pre-configured saved searches from your previous version are not available after an upgrade.
If you upgrade from a pre-2.3.0.8 version of Records Management, then an additional webscript needs to be run so that easy access records (previously known as in-place records) created in pre-2.3.0.8 sites are shown in the search results of users without Records Management permissions.
2016-09-16 13:46:44,409 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processing – BEGIN [ output cut ] 2016-09-16 13:46:47,131 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processing record file149 (2016-1474021730514).txt - BEGIN 2016-09-16 13:46:47,150 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processing record file149 (2016-1474021730514).txt - END 2016-09-16 13:46:47,152 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processing record file150 (2016-1474021731516).txt - BEGIN 2016-09-16 13:46:47,174 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processing record file150 (2016-1474021731516).txt - END 2016-09-16 13:46:47,238 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processing - END 2016-09-16 13:46:47,238 INFO [org.alfresco.repo.web.scripts.roles.DynamicAuthoritiesGet] [http-apr-8080-exec-6] Processed first 100 records.
The user who created the Records Management site is automatically made a member of the Records Management Administrator group. Other users can access different areas of the RM Admin Tools depending on the capabilities given to the role that they're in.
The RM Admin Tools opens on the Audit page, with various tools available on the left side of the page. Click a tool to manage that part of your site.
It displays auditing information collected from the system to show whether business rules are being followed, and to ensure that any unauthorized activity can be identified and traced. This tool is especially important for systems that deal with classified information.
The Audit tool maintains a complete trace of all the actions on every record and cannot be altered. The information that is captured and stored includes:
The Audit tool displays by default when you access the RM Admin Tools.
Filter action |
---|
By default only the first 20 log entries are displayed. Use this option to select the number of displayed entries. |
Select from and to dates for actions to include in the audit. |
Click Specify and search for then select a user you want to audit, then click Add. |
Select an event type to audit. You can only select one event type. |
The type of action that is recorded in the audit log includes:
If you have an audit running then you can stop it and restart it later.
A dialog box prompts you to confirm the action.
The auditing tool stops capturing and storing the activity in the Records Management system.
When you've run an audit log you then have the option to file it as a record.
A message confirms that the audit log has been filed as a record in the selected folder in the File Plan.
Depending on your browser you'll be prompted to open or save the file or it will be saved automatically. The exported audit log is an HTML file.
A separate window opens displaying the audit log.
A message prompts you to confirm the action.
You can also add custom metadata that you can associate with each of these different types of records management objects.
You can choose from text fields, date pickers, check boxes, and if you've set up a list of values [188], selection menus.
If required you can choose to make specific custom data mandatory, so that users have to include it when they are completing a record.
The right column lists any custom metadata that's already been defined for the selected object.
The New Metadata page displays.
This name is used as the label on the Edit Metadata page.
The type can be of the following values:
Type | Description |
---|---|
Text | Adds a text field to the Edit Metadata page. When you select this option, you can select the Use selection list check box, so instead of a text field there will be a selection menu of the list created with the List of Values tool [177]. |
Check box | Adds a check box to the Edit Metadata page. |
Date | Adds a date field to the Edit Metadata page. |
You can easily edit any custom metadata that you've set up.
The right column lists any custom metadata that's already been defined for the selected object.
The Edit Metadata Property page displays.
These are displayed when you open the Define Roles tool. You can create as many more roles as you need.
Capabilities control what each role can do in the Records Management system, and with nearly 60 unique capabilities to choose from, they can vary hugely between roles.
You assign users and groups who will all require the same levels of functionality to a role (a user can be assigned to multiple roles at the same time). Assign users and groups to roles using the Users and Groups tool [191]. You can manage roles to change the capabilities that they have.
Capabilities don't conflict and are not hierarchical. A user can be granted a single capability and that capability will not grant any further capabilities. Any user can have zero or more capabilities within the system. A user that has no capabilities is effectively barred from the Records Management system.
All existing roles are displayed when you open the Define Roles tool.
The list of capabilities assigned to that role display in the Capabilities column.
There are five default Records Management roles, but you can add as many more as you need.
The New Role page displays all available capabilities, which are organized into groups. You can choose individual items or an entire group to define the categories for the role you're creating.
For example, to select all capabilities for controlling folders, click Select All for the Folder Control group.
A message prompts you to confirm the action.
The IMAP protocol allows email applications that support IMAP to connect to and interact with Alfresco repositories directly from the mail application.
Alfresco has multiple maps between email headers and Alfresco metadata properties set up by default. You can view these with the Email Mappings tool.
This means that when an email is saved to Records Management, metadata from the email header is captured and mapped to metadata for the record.
For example, an email Subject heading is mapped by default to the Alfresco property title. This is displayed as in the Email Mappings tool as messageSubject to cm:title. The email header field messageSubject is on the left and is separated by the word “to”, which indicates that it is mapped to a property cm:title.
When you're viewing emails within the Records Management system, the title property shows the email’s Subject heading.
As well as the default mappings, you can also add your own or delete existing ones.
You can select an Alfresco property or a custom property.
The new mapping displays in the list of email mappings.
This removes the mapping from the list.
The following default events are available in Records Management:
Records Management provides an extensive list of events, but it's easy to add to these.
The New Event page displays.
You can edit all events, whether they are system defaults or ones that you've created.
The Edit Event page displays.
You need to provide values for these lists so that users can select from them when they edit metadata. The recommended values for Supplemental Markings are Confidential, Restricted, Secret, Top Secret and Unclassified.
You can also set up new lists as needed, and you can use these lists when you create custom metadata [200].
Where the value is a text string, you can also enter the value using a list of values menu. For example, on the Edit Metadata page, you enter the value for the Mimetype field by selecting a value from the menu.
The New List dialog box displays.
The Edit List page displays.
The value name displays in the Values table.
The selected value is highlighted.
The Add Access dialog box displays.
You must enter at least three (3) characters.
A list of users and groups matching the search criteria displays.
The user or group displays in the right column. You can add as many users and groups as required.
If you need to rename a list of values then it's very easy to do.
The Rename List dialog box displays.
The names given to individual relationships are based on the different types of referencing, and are what makes each one unique.
You can see the default relationship types that are included in Records Management and you can create new and manage existing relationships.
The New Relationship page displays.
The values you enter display in the File Plan when a user creates the reference.
The new relationship appears in the list.
The Edit Relationship page displays. You can't change the relationship type; only the field values can be modified.
Once you've assigned them to a role [206] they'll be able to use the level of Records Management functionality that role has been given.
All existing roles are displayed. When you click on a role the groups and users assigned to that role are displayed.
Existing groups and users assigned to the role are displayed.
The Add User or Add Group page displays.
All users or groups matching your search are displayed.
The new group users is added to the role.
What are the differences between a DoD 5015.2 and standard Records Management sites?
When you create a Records Management site you can choose to create a DoD 5015.2 site or a standard site. If your organization is required to meet DoD 5015.2 compliance, then select DoD 5015.2-STD. Records on a DoD 5015.2 site have additional madatory metadata the must be completed. Mandatory metadata includes the originator, the originating organization, the publication date, the destroy action.
back to top [216]How does classification interact with standard Records Management permissions?
There are two levels of interaction between classification and permissions. To view a classified file or record you need to have read permissions for that file and the required clearance level. To classify a file or record, or edit the classification, you need to have read and file permission and clearance to use the classification level(s) involved.
back to top [216]Having the required clearance level isn't all that's needed to view a classified record. You also need to have the required permissions, including but not restricted to permission to view the category, permission to view the folder, and permission to view the record.
back to top [216]Why are the tags showing more files than I can see?
Depending on your security clearance level, some files or records might be hidden from you in Alfresco. The tags link displays the total number of files that have that tag, but when you click it you'll only be able to see those that you have access to.
Why can't I upload a file when I have the required permissions?
In each folder you can't have multiple files of the same name. You might have permissions to add files, but may not have security clearance to see, for example, files that have been classified as Top Secret. If you try to upload a file when there is already one in the folder, even if you can't see it, you'll receive a message: Unexpected error occurred during upload of new content.
back to top [216]Are RSS feeds secure?
RSS feeds are secure, but the login credentials are stored by the browser you're using and not Alfresco. As such it's recommended that you close your browser after logging out of Alfresco and / or lock your computer while you're away from it.
back to top [216]Why isn't hot backup working properly?
The default behavior for classified records is "immediate delete", which means that content is deleted immediately, and will not be included in a hot backup. If you have performed a hot backup and you try to retrieve content that was deleted, a Requested resource is not available message is displayed.
back to top [216]Records uploaded using CIFS, WebDav, or FTP don't have any content?
There's a known issue that when users with the Records Management User role and Read and File permissions add a record using CIFS, WebDav, or FTP, the record is added but it's content is removed. Other issues may also occur. It's recommended that users in this situation are given an alternate Records Management role to resolve the issue.
back to top [216]The key difference between an accession and a transfer is that when records are accessioned they are no longer the responsibility of your Records Management system. When transferred (to another physical location) you are still responsible for the record. Accession reports can be used to record when a record was accessioned, where it went, and why.
Links:
[1] https://docs.alfresco.com/../topics/alfresco-video-tutorials-rm.html
[2] https://docs.alfresco.com/../concepts/rm-gs-overview.html
[3] https://docs.alfresco.com/../concepts/rm-intro.html
[4] https://docs.alfresco.com/../tasks/rm-install-proc.html
[5] https://docs.alfresco.com/../tasks/rm-upgrade-proc.html
[6] https://docs.alfresco.com/../concepts/rm-admin-intro.html
[7] https://docs.alfresco.com/../references/rm-user-faqs.html
[8] https://docs.alfresco.com/../references/rm-glossary.html
[9] https://docs.alfresco.com/../concepts/welcome-gs.html
[10] https://docs.alfresco.com/../concepts/rm-tutorials-01.html
[11] https://docs.alfresco.com/../concepts/rm-tutorials-02.html
[12] https://docs.alfresco.com/../concepts/rm-tutorials-03.html
[13] https://docs.alfresco.com/../concepts/rm-tutorials-04.html
[14] https://docs.alfresco.com/../concepts/rm-tutorials-05.html
[15] https://docs.alfresco.com/../concepts/rm-tutorials-06.html
[16] https://docs.alfresco.com/../concepts/rm-tutorials-07.html
[17] https://docs.alfresco.com/../concepts/rm-tutorials-08.html
[18] https://docs.alfresco.com/../concepts/rm-tutorials-09.html
[19] https://docs.alfresco.com/../concepts/rm-tutorials-10.html
[20] https://docs.alfresco.com/../concepts/rm-tutorials-11.html
[21] https://docs.alfresco.com/../concepts/rm-tutorials-12.html
[22] https://docs.alfresco.com/../concepts/rm-tutorials-13.html
[23] https://docs.alfresco.com/../concepts/rm-tutorials-14.html
[24] https://docs.alfresco.com/../concepts/rm-tutorials-15.html
[25] https://docs.alfresco.com/../concepts/welcome-rm.html
[26] https://docs.alfresco.com/../concepts/rm-record-lifecycle.html
[27] https://docs.alfresco.com/../concepts/rm-gs-managers.html
[28] https://docs.alfresco.com/../concepts/rm-gs-users.html
[29] https://docs.alfresco.com/../tasks/rm-recordcategory-add.html
[30] https://docs.alfresco.com/../tasks/rm-dispschedule-create.html
[31] https://docs.alfresco.com/../tasks/rm-dispschedule-createsteps.html
[32] https://docs.alfresco.com/../tasks/rm-set-financial-year.html
[33] https://docs.alfresco.com/../tasks/rm-recordfolder-add.html
[34] https://docs.alfresco.com/../tasks/rm-set-permissions.html
[35] https://docs.alfresco.com/../concepts/rm-fileplanstruct-create.html
[36] https://docs.alfresco.com/../concepts/rm-dispschedule.html
[37] https://docs.alfresco.com/rm-set-financial-year.html
[38] https://docs.alfresco.com/rm-records-manage-reference.html
[39] https://docs.alfresco.com/rm-dispschedule-edit.html
[40] https://docs.alfresco.com/../concepts/rm-manage-permissions.html
[41] https://docs.alfresco.com/../tasks/rm-electronic-file.html
[42] https://docs.alfresco.com/../tasks/rm-create-record.html
[43] https://docs.alfresco.com/../tasks/rm-file-unfiled.html
[44] https://docs.alfresco.com/../tasks/rm-metadata-add.html
[45] https://docs.alfresco.com/../tasks/rm-metadata-edit.html
[46] https://docs.alfresco.com/../tasks/rm-record-declare.html
[47] https://docs.alfresco.com/../tasks/rm-dispsched-actions.html
[48] https://docs.alfresco.com/../concepts/rm-records-overview.html
[49] https://docs.alfresco.com/../concepts/rm-easy-access.html
[50] https://docs.alfresco.com/rm-records-manage-link.html
[51] https://docs.alfresco.com/../tasks/rm-recordfolder-manage.html
[52] https://docs.alfresco.com/../tasks/rm-records-manage.html
[53] http://docs.alfresco.com/5.2/topics/sh-uh-welcome.html
[54] https://docs.alfresco.com/rm-admin-intro.html
[55] https://docs.alfresco.com/../concepts/rm-fileplan.html
[56] https://docs.alfresco.com/../concepts/rm-fileplan-manage.html
[57] https://docs.alfresco.com/../concepts/rm-rules.html
[58] https://docs.alfresco.com/../concepts/rm-search.html
[59] https://docs.alfresco.com/../concepts/rm-auditing.html
[60] https://docs.alfresco.com/../tasks/rm-load-testdata.html
[61] https://docs.alfresco.com/rm-rules.html
[62] https://docs.alfresco.com/../tasks/rm-fileplan-access.html
[63] https://docs.alfresco.com/../concepts/rm-fileplan-browse.html
[64] https://docs.alfresco.com/rm-manage-permissions.html
[65] https://docs.alfresco.com/../references/rm-disp-example.html
[66] https://docs.alfresco.com/../tasks/rm-dispschedule-edit.html
[67] https://docs.alfresco.com/rm-export-import.html
[68] https://docs.alfresco.com/../tasks/rm-nonelect-file.html
[69] https://docs.alfresco.com/../tasks/rm-records-manage-requestinfo.html
[70] https://docs.alfresco.com/rm-records-manage-unfiled.html
[71] https://docs.alfresco.com/../tasks/rm-classify-file.html
[72] https://docs.alfresco.com/../tasks/rm-create-version-record.html
[73] https://docs.alfresco.com/../tasks/rm-autodeclare-options.html
[74] https://docs.alfresco.com/../tasks/rm-easy-access-move.html
[75] https://docs.alfresco.com/../tasks/rm-easy-access-hide.html
[76] https://docs.alfresco.com/../references/rm-rejected-records.html
[77] https://docs.alfresco.com/rm-classify-record.html
[78] https://docs.alfresco.com/../references/rm-classification-tips.html
[79] https://docs.alfresco.com/../concepts/rm-sc-overview.html
[80] https://docs.alfresco.com/rm-create-record.html
[81] http://docs.alfresco.com/5.2/concepts/library-organize.html
[82] https://docs.alfresco.com/../tasks/rm-recordcategory-manage.html
[83] https://docs.alfresco.com/../concepts/rm-manage-holds.html
[84] https://docs.alfresco.com/../concepts/rm-export-import.html
[85] https://docs.alfresco.com/../tasks/rm-recordcategory-view.html
[86] https://docs.alfresco.com/../tasks/rm-recordcategory-edit.html
[87] https://docs.alfresco.com/../tasks/rm-recordcategory-delete.html
[88] https://docs.alfresco.com/../tasks/rm-recordfolder-view.html
[89] https://docs.alfresco.com/../tasks/rm-recordfolder-edit.html
[90] https://docs.alfresco.com/../tasks/rm-recordfolder-events.html
[91] https://docs.alfresco.com/../tasks/rm-recordfolder-editdispdate.html
[92] https://docs.alfresco.com/../tasks/rm-recordfolder-freeze.html
[93] https://docs.alfresco.com/../tasks/rm-recordfolder-close.html
[94] https://docs.alfresco.com/../tasks/rm-recordfolder-delete.html
[95] https://docs.alfresco.com/../tasks/rm-records-manage-view.html
[96] https://docs.alfresco.com/../tasks/rm-records-manage-link.html
[97] https://docs.alfresco.com/../tasks/rm-records-manage-reference.html
[98] https://docs.alfresco.com/../tasks/rm-records-manage-review.html
[99] https://docs.alfresco.com/../concepts/rm-records-manage-unfiled.html
[100] https://docs.alfresco.com/../tasks/rm-records-manage-events.html
[101] https://docs.alfresco.com/../tasks/rm-records-manage-editdate.html
[102] https://docs.alfresco.com/../tasks/rm-records-manage-dispdate.html
[103] https://docs.alfresco.com/../tasks/rm-records-manage-freeze.html
[104] https://docs.alfresco.com/../tasks/rm-records-manage-reopen.html
[105] https://docs.alfresco.com/../tasks/rm-records-manage-delete.html
[106] https://docs.alfresco.com/../tasks/rm-search-addhold.html
[107] https://docs.alfresco.com/../tasks/rm-create-hold.html
[108] https://docs.alfresco.com/../tasks/rm-export.html
[109] https://docs.alfresco.com/../tasks/rm-export-fileplan.html
[110] https://docs.alfresco.com/../tasks/rm-import.html
[111] https://docs.alfresco.com/../concepts/rm-rules-define.html
[112] https://docs.alfresco.com/../concepts/rm-rules-defined.html
[113] https://docs.alfresco.com/../concepts/rm-rules-linked.html
[114] https://docs.alfresco.com/../tasks/rm-rules-define-create.html
[115] https://docs.alfresco.com/../tasks/rm-rules-define-link.html
[116] http://docs.alfresco.com/5.2/tasks/library-folder-rules-new.html
[117] https://docs.alfresco.com/../references/rm-rules-substitutions.html
[118] https://docs.alfresco.com/rm-rules-change-link.html
[119] https://docs.alfresco.com/../tasks/rm-rules-new.html
[120] https://docs.alfresco.com/../tasks/rm-rules-edit.html
[121] https://docs.alfresco.com/../tasks/rm-rules-reorder.html
[122] https://docs.alfresco.com/../tasks/rm-rules-inherited.html
[123] https://docs.alfresco.com/../tasks/rm-rules-delete.html
[124] https://docs.alfresco.com/rm-rules-define-create.html
[125] https://docs.alfresco.com/../tasks/rm-rules-change-link.html
[126] https://docs.alfresco.com/../tasks/rm-rules-break-link.html
[127] https://docs.alfresco.com/rm-search-syntax.html
[128] https://docs.alfresco.com/../tasks/rm-search-access.html
[129] https://docs.alfresco.com/../tasks/rm-search-create.html
[130] https://docs.alfresco.com/../tasks/rm-search-saved.html
[131] https://docs.alfresco.com/../tasks/rm-search-save.html
[132] https://docs.alfresco.com/../tasks/rm-search-print.html
[133] https://docs.alfresco.com/../tasks/rm-search-export.html
[134] https://docs.alfresco.com/../tasks/rm-search-saved-delete.html
[135] https://docs.alfresco.com/../concepts/rm-search-syntax.html
[136] https://docs.alfresco.com/rm-search-daterange.html
[137] https://docs.alfresco.com/../concepts/rm-search-examples.html
[138] https://docs.alfresco.com/../concepts/rm-search-fields.html
[139] https://docs.alfresco.com/../concepts/rm-search-specialfields.html
[140] https://docs.alfresco.com/rm-search-fields.html
[141] https://docs.alfresco.com/rm-search-specialfields.html
[142] https://docs.alfresco.com/../tasks/rm-search-text.html
[143] https://docs.alfresco.com/../tasks/rm-search-wildcards.html
[144] https://docs.alfresco.com/../tasks/rm-search-multiple.html
[145] https://docs.alfresco.com/../tasks/rm-search-phrases.html
[146] https://docs.alfresco.com/../tasks/rm-search-exactterm.html
[147] https://docs.alfresco.com/../tasks/rm-search-dates.html
[148] https://docs.alfresco.com/../tasks/rm-search-daterange.html
[149] https://docs.alfresco.com/../tasks/rm-search-specialtypes.html
[150] https://docs.alfresco.com/../tasks/rm-search-emptystring.html
[151] https://docs.alfresco.com/../tasks/rm-search-components.html
[152] https://docs.alfresco.com/../tasks/rm-search-operators.html
[153] https://docs.alfresco.com/../tasks/rm-file-report.html
[154] https://docs.alfresco.com/../tasks/rm-audit-viewing.html
[155] https://docs.alfresco.com/../concepts/supported-stacks.html
[156] https://docs.alfresco.com/../tasks/rm-amp-install.html
[157] https://docs.alfresco.com/../tasks/rm-amp-uninstall.html
[158] https://docs.alfresco.com/../tasks/rm-create-site.html
[159] https://docs.alfresco.com/../concepts/rm-ref-global-props.html
[160] http://docs.alfresco.com/5.2/concepts/supported-platforms-ACS.html
[161] http://support.alfresco.com
[162] http://docs.alfresco.com/tasks/amp-install.html
[163] http://docs.alfresco.com/tasks/uninstall-amp.html
[164] http://docs.alfresco.com/5.2/concepts/dev-extensions-modules-management-tool.html
[165] https://docs.alfresco.com/rm-load-testdata.html
[166] http://docs.alfresco.com/5.2/concepts/upgrade-path.html
[167] http://docs.alfresco.com/5.2/concepts/ch-upgrade.html
[168] https://docs.alfresco.com/rm-amp-install.html
[169] https://docs.alfresco.com/rm-upgrade-2308.html
[170] https://docs.alfresco.com/../tasks/rm-upgrade-2308.html
[171] https://docs.alfresco.com/../tasks/rm-console-access.html
[172] https://docs.alfresco.com/../concepts/rm-audit-intro.html
[173] https://docs.alfresco.com/../concepts/rm-custmeta-intro.html
[174] https://docs.alfresco.com/../concepts/rm-roles-intro.html
[175] https://docs.alfresco.com/../concepts/rm-emailmap-intro.html
[176] https://docs.alfresco.com/../concepts/rm-events-intro.html
[177] https://docs.alfresco.com/../concepts/rm-lov-intro.html
[178] https://docs.alfresco.com/../concepts/rm-relationships-intro.html
[179] https://docs.alfresco.com/../tasks/rm-userrights-view.html
[180] https://docs.alfresco.com/../concepts/rm-usergroups-intro.html
[181] https://docs.alfresco.com/../tasks/rm-audit-access.html
[182] https://docs.alfresco.com/../concepts/rm-audit-actions.html
[183] https://docs.alfresco.com/../tasks/rm-audit-startstop.html
[184] https://docs.alfresco.com/../tasks/rm-audit-filerecord.html
[185] https://docs.alfresco.com/../tasks/rm-audit-export.html
[186] https://docs.alfresco.com/../tasks/rm-audit-viewlog.html
[187] https://docs.alfresco.com/../tasks/rm-audit-clear.html
[188] https://docs.alfresco.com/rm-lov-intro.html
[189] https://docs.alfresco.com/../tasks/rm-custmeta-create.html
[190] https://docs.alfresco.com/../tasks/rm-custmeta-edit.html
[191] https://docs.alfresco.com/rm-usergroups-intro.html
[192] https://docs.alfresco.com/../tasks/rm-roles-view.html
[193] https://docs.alfresco.com/../tasks/rm-roles-add.html
[194] https://docs.alfresco.com/../tasks/rm-roles-edit.html
[195] https://docs.alfresco.com/../tasks/rm-roles-delete.html
[196] https://docs.alfresco.com/../tasks/rm-emailmap-add.html
[197] https://docs.alfresco.com/../tasks/rm-emailmap-delete.html
[198] https://docs.alfresco.com/../tasks/rm-events-add.html
[199] https://docs.alfresco.com/../tasks/rm-events-edit.html
[200] https://docs.alfresco.com/rm-custmeta-intro.html
[201] https://docs.alfresco.com/../tasks/rm-lov-create.html
[202] https://docs.alfresco.com/../tasks/rm-lov-edit.html
[203] https://docs.alfresco.com/../tasks/rm-lov-rename.html
[204] https://docs.alfresco.com/../tasks/rm-relationships-create.html
[205] https://docs.alfresco.com/../tasks/rm-relationships-edit.html
[206] https://docs.alfresco.com/rm-roles-intro.html
[207] https://docs.alfresco.com/../tasks/rm-usergroups-add.html
[208] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__dod-differences
[209] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__classification-permissions
[210] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__classification-hidden
[211] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__tags
[212] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__duplicate
[213] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__rss
[214] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__delete
[215] https://docs.alfresco.com/rm-user-faqs.html%23rm-user-faqs__cifs
[216] https://docs.alfresco.com/rm-user-faqs.html%23top