In this topic Hide
This page is used to view, create, copy and manage Page Views based on your access level. Each Page View includes field options that are available for that page. This list will be different for each Page View.
You can create more than one Page View for the same physical RME page, so that you can assign them to different roles.
As a summary, you can configure:
• If the Page View is current or non-current
• Fields to display on the full page (via either Page Layout Designer or Configure Field Properties button, depending on your system set up)
• Fields to be displayed in the search or summery grid for the page, and the order of fields in the grid
• Custom help page to display instead of the default help page
If the Copy button on the toolbar is active when you have a Page View open, you can also copy a Page View record. This can be useful when creating new, similar Page Views as a starting point.
Note: When you save a custom layout, the Page View becomes customised (Use Custom Layout = Yes). Enhancements in a new release will not be applied to custom page layouts in order to retain your defined personalisation unless otherwise specified in the Release Notes.
Menu path: RME > Users > Page Views Search > Page Views
Each page in the system has a “Page View”. The Page ID for it is shown at the bottom right of the page, for example, FAC001 is the Page ID for the Facilities record page.
A Page View is like a “plan” of the page, listing the fields in it, what fields are shown in the search grid, and in what order. For related items pages (sub-pages within a core record), the "grid" refers to the summary grid shown in the tab on the core record page.
You assign Page Views to roles so that you can control what pages users with each role can access in the system. A role has a defined set of access to elements: Page Views, reports, eForm templates, and Significant Events. When you set up a new user, you create a User record for them. In it, you assign a role to suit them, which controls what they can see and do in the system. For more, see: Users overview, Users and Roles.
You can create more than one Page View for the same physical RME page, to change the layout and assign each view to different roles. As an example, Page View 1 has the default page layout and is assigned to Role X which is assigned to User A. They will see that view with all the fields defined for it. Page View 2 has had fields and related item removed and the layout changed using the Page Layout Designer. This Page View is assigned to role Y which is assigned to User B. They will see that view, which is different to Page View 1.
For both, the location of the page remains the same and is accessed in the same way from the system menu. It’s the same page, just a different view of it. That’s why they are called “Page Views”.
You can do a lot with Page Views. Customising the fields and layout to suit particular audiences (roles) is a key part of tailoring the system to suit your needs.
Click to view or hide: Page Views diagram depicting different views for different roles
1. From the RME Menu, select Users > Page Views.
2. In the toolbar, click the New button.
3. In the Page field, select the physical RME page you want to base the Page View on.
4. Complete the fields, using the table below as a guide.
5. In the toolbar, click Save. To go back to the previous page, click it in the breadcrumb trail or use your browser Back button.
6. When you save the Page View details, the Page View related item lists the fields available for the selected RME page that you can configure for your new Page View. Select a field line in the grid to open the field configuration page. For more, see: Page View Field.
Default Field Name (In page layout order) |
Description |
Page * |
Mandatory for new Page Views; read-only for existing Page ID and name of the physical RME page from which the Page View is created If adding a new Page View, use the lookup to search the list of available RME pages. |
Current? |
Indicates if the Page View is currently in use To make the page hidden from users, slide this to No. |
Use Custom Layout? |
Read only Indicates if a custom layout is currently being used for the Page View rather than the default layout Not relevant for pages with the option to Configure Field Properties as the layout cannot be changed for these. |
Page Description |
Read only Auto-populated description of the selected RME page, displayed when the details are saved |
Configure Field Properties |
Only for core pages, if the Page Layout Designer is not licensed for your institution (Layout Designer button replaces this) Used to customise the field properties in the Page View, such as label name, access type and default value
|
Layout Designer |
Only for core pages; only displays if the Page Layout Designer feature is used by your institution Used to customise the full layout of the Page View, in place of Configure Field Properties When you select this button, the fields for the Page View are displayed in the current layout. You can customise the Page View by dragging-and-dropping fields to add, remove or change the position, change field properties, create field groups or sections, and add, remove or reorder tabs. See: Page Layout Designer |
View Name * |
Mandatory Unique name to identify the Page View and distinguish it from others If the View Name value is used as the menu option in the RME menu, changes in this field will also affect the menu option name. Page Views where the View Name is used as a menu option are identified in the search results in the Used as Menu? column. These are generally key modules pages such as a Project record (PRO001) and an Ethics record (ETH001), as well as the first page for Setup options, such as Fund Scheme FND001 and Facilities FAC001. This cannot be edited. Be aware that if you create a copy of a Page View where the name is used as the menu option, the View Name value will be used in the RME menu for anyone with a role assigned with that view. |
Precedence * |
Mandatory Indicates the precedence for determining the Page View to display when more than one Page View for the same page is assigned to the same user or role • The Page View with the lowest value will be taken as the highest precedence and be displayed, e.g. 1 (unless a specific Page View is assigned to the role or user) • Cannot be the same number as an existing Page View. • If you don't want to specify precedence, do not use 0 as this is likely to be read as the highest by the system. |
View Description * |
Mandatory Brief description of the Page View, such as which role or what it is used for |
Help page |
Default: Default Help page that will be displayed if a user selects the Help link when on this page in RME Initially, this will be set to display the generic RME help page (Default). If this is changed and either made blank, or a corresponding custom file does not exist, a 404 Page Not Found message will display when users click the Help link when viewing the RME page. You can also add custom content within a default help page, or set up your own custom help pages. |
The read-only table below Page View fields shows a summary for the Page View.
Column Name (in grid layout order) |
Description |
Label Name |
Name of the field in the selected Page View |
Access Type |
Read only in this grid Indicates whether the field is required by the system to correctly function, if it is read only, optional, or hidden for the Page View
Mandatory fields and access To enable Page Views to be created for specific roles with mandatory fields included but not editable, this property may be changed for mandatory fields to Read Only or other options. This is only designed to suit specific roles where it is assumed that mandatory fields in the relevant Page View/s will already have a value. Users with these roles will not be creating new records. They will only need to view the details and interact with limited elements in the page. Be aware that if a new record is created by a user where a mandatory field is set with an Access Type of Read Only, Hidden or Optional, the field will be blank so the system will not be able to save the record. For this reason, it is not recommended for wide usage. |
Order in the Grid |
Number to determine the field order in the grid for the Page View shown in either a) the search results grid for core record pages, or b) the summary grid in the tab of a core record for a related item The lowest number will display first on the left of the grid (from zero). If you mark more than one item with the same order number, the system will order them alphabetically, then display the next logical number. Whether the field will be included in the grid is set in Field in Grid. |
Field In Grid? |
Indicates whether the field is included in the grid for the Page View in search results or summary grid The order in which it will be displayed in the grid is set in the Order in the Grid field. |
You can add your own text and links within a generic, default RME help page to provide more guidance to your users. As an example, this could be useful to link to internal procedures or guidelines.
Custom content displays just below the page heading in a defined section. This is limited to plain text to a maximum of 500 characters, and five URL links (maximum link text length of 100 characters) for performance and security reasons.
The process involves editing a JSON file, knowledge of JavaScript is required. You may need assistance from your IT department to complete the steps below.
1. Determine the ID used for the help page. This ID is displayed at the bottom left of the default RME help page. Example: Page ID: PRO001.htm.
2. Go to the
CustomHelp folder on the RME web server under the installation path.
Example path: \\{InstallationPath}\RME\CustomHelp
3. Open the external-help.json file.
4. For each page, define the following in the JSON file, making sure you do not delete any JavaScript code. Separate the code for individual pages with a comma.
| JS element | Description |
"page" |
Enter the Page ID (without the suffix .htm) within the quotation marks. • The ID must exactly match the page ID used in RME. The page ID is displayed at the bottom of each default RME help page. Always use the RME help page ID as some RME pages include an extra letter that is not displayed in the RME page itself, such as S for a search page or M for eForm subsidiary pages. If the ID is not correct, the help page will not include your custom content. • If you add details for two pages with the same page ID, only the first one will be used.
Example: "page": "PRO001" |
"text" |
Enter plain text within the quotation marks, up to 500 characters. • If you want to add a new line break, enter three @ symbols ( ); these are not counted as characters for the limit. • HTML tags will be stripped for security reasons.
Example: "text": "Click on this link to learn more. This is a new line." |
"links" |
For each link you want to add (maximum 5), enter the URL and text for the link as follows: |
"url" |
Enter the full URL link (web address if https:// or a file on a file system, presuming the user has access) within the quotation marks
Example: "url": "https://www.google.com" |
"text" |
Enter the link text that users will click to access the website or intranet within the quotation marks, up to 100 characters • If blank, the URL will be used, up to a limit of 100 characters.
Example: "text": "Google" |
Example code |
|
[ { "page":"PRO001", "text":"Click on this link to learn more. This is a new line.", "links":[ { "url":"https://www.google.com", "text":"Google" }, { "url":"https://www.bing.com", "text":"Bing" } ] }, { "page":"ETH001", "text":"Click on this link to learn more.", "links":[ { "url":"https://www.google.com", "text":"Google" }, { "url":"https://www.bing.com", "text":"Bing" } ] } ] |
|
5. Save your changes to the JSON file. Make sure that the file is not moved to another location.
Result: When a help page is opened from RME, a script will run which parses the JSON file with the links, finds the first instance of a help page file with the same page ID, and if it exists, formats and inserts the block into the page. If no matching ID is found, the content will not be inserted.
Custom help pages in the specified folder are supported and retained throughout future updates of RME.
As an alternative to the generic, default RME help page, you can choose to offer your own help pages. To do this, you need to create and manage your own help files, including your own CSS styling. Be aware that you will need to update your custom help pages for each release, as relevant.
You may need assistance from your IT department to complete the steps below. These steps are also included in the RME Installation and Upgrade Guide.
To display your own help content for a page:
1. Design your own help pages, such as HTML or XML files including CSS styling and images.
2. Place your
help files, including all supporting files, in the CustomHelp
folder on the RME web server under the installation path.
Example path: \\{InstallationPath}\RME\CustomHelp
You can include any
file that can be opened in a browser, such as .jpg, .png, or a URL with
a http prefix to link to another website.
3. To establish links between your custom files and RME, open a Powershell prompt in the Administrator context, and go to the CustomHelp folder. Execute the Powershell script: generate-help-links.ps1. This generates a help-links.JSON file based on the files in the CustomHelp folder, which in turn populates the list of help page options in RME.
4. Go back to RME. In the menu, go to Users > Page Views. Search for and display the Page View for the page you want to link to a custom help page.
5. In the Help Page dropdown, select the custom help page from the list. You can only select one help file per Page View.
6. In the toolbar, click Save. In your browser, select the Refresh button to see the changes you have made.
Custom help pages in the specified folder are supported and retained throughout future updates of RME.
You manage core records from the module search page, Results tab. Select records in the grid and use the New, Delete or Export buttons on the toolbar in Page View search.
Product Key: Modules - Core
Page ID: VIE001.htm