Defining messages and behavior on the login screens

You can define messages that are displayed on the login screen for OpenPages® and configure certain behavior.

About this task

The login screen can contain the following messages:
  • A system notice

    Can be any text, for example, OpenPages will be unavailable on Sunday 8:00-14:00 due to system maintenance.

  • Checkbox text

    Can be any text, for example, I have read the privacy statement and I agree to the terms and conditions. The user must click the checkbox to log in.

  • A privacy statement

    Can be any text, for example, a company-wide statement about terms and conditions or privacy.

  • A privacy statement link

    Contains a link, for example, to an intranet site with more information about privacy. The link opens in a new tab.

    The link is also used by the Privacy menu item in the Help menu in the Task Focused UI and the Standard UI.

  • An acceptable use policy link

    Contains a link, for example, to an intranet site with more information about acceptable use. The link opens in a new tab.

    The link is also used by the Acceptable Use menu item in the Help menu in the Task Focused UI and the Standard UI.

You define a message's content by using application text strings. If a string is empty, the message is not displayed.

The following example shows all the messages. The numbers correspond to the application text strings listed in Table 1.

Figure 1. Login screen messages and application text strings
login screen with messages

Table 1. Messages and application text strings
# Description Located in the Application Text > Labels category
1 Title for a system notice. The default is System Notice. com.label.logon.system.notice.header
2 Text for a system notice. If empty, the system notice box, including the system notice header, is not displayed. Default is empty. com.label.logon.system.notice.text
3 Text displayed next to the checkbox. If empty, the checkbox and corresponding text is not displayed. Default is empty. com.label.logon.checkbox.text
4 Text for a privacy statement. Default is empty. com.label.logon.privacy.text
5 Title for a privacy statement link. Default is Privacy Statement. The link is displayed if a URL is defined in the Privacy Link URL registry setting. com.label.logon.privacy.link
6 Title for an acceptable use policy link. Default is Acceptable Use. The link is displayed if a URL is defined in the Acceptable Use Link URL registry setting. com.label.logon.acceptable.use

The placement of the messages on the login screen is fixed and cannot be changed.

Figure 1 is the login screen for the Task Focused UI and the Standard UI.

Each locale can have one message. The user's locale determines the message that is displayed. The message that is defined in the en_US locale is the default message if the user's locale is not saved in the browser.

Note: The messages are displayed before users log in to OpenPages. Ensure that the content of the messages is appropriate for users who might not have access to OpenPages.
If you are using single sign-on (SSO), the login screen is bypassed. Users still see the messages, however.
  • If only a system notice is defined, the system notice is displayed on the dashboard when users access the system. The system notice is displayed once per session. Changes are not immediately broadcast. The system notice header that is defined in com.label.logon.system.notice.header is not displayed on the dashboard.
  • Otherwise, the messages are displayed on a blank page in OpenPages with a Continue button. If you defined checkbox text, users must click the checkbox to enable the Continue button. When users click Continue, they can access OpenPages.

For example, if you define a system notice and checkmark text, users see a page that is similar to the following page:

Figure 2. A system notice and check mark text displayed for SSO users
A page is shown with a system notice, a checkmark to accept the terms and conditions, and a Continue button.
You can optionally add HTML formatting when you define application text strings, for example:
  • <b>text</b> displays text in bold.
  • </br> begins a new line.
  • <ul><li>List item 1</li><li>List item 2</li></ul> inserts a bulleted list.
  • <a href="https://insert URL/" target="_blank">insert URL title</a> inserts a link.

Procedure

  1. Click Settings menu > System Configuration > Application Text.
  2. Click filter icon to access the search filter.
  3. Click Labels.
  4. Search for one of the following labels. Click the link to edit the application text.
    • com.label.logon.system.notice.header
    • com.label.logon.system.notice.text
    • com.label.logon.checkbox.text
    • com.label.logon.privacy.text
    • com.label.logon.privacy.link
    • com.label.logon.acceptable.use
  5. Click the name of the locale code you want to modify, for example, en_US.
  6. Add or edit message text.
  7. Click Done.
  8. If you defined a privacy statement link, specify the URL to display when users click the link.
    1. Click Settings menu > System Configuration > Settings.
    2. Edit the Applications > Common > Privacy Link URL setting. Specify the URL of the privacy statement.
  9. If you defined an acceptable use policy link, specify the URL to display when users click the link.
    1. Click Settings menu > System Configuration > Settings.
    2. Edit the Applications > Common > Acceptable Use URL setting. Specify the URL of the acceptable use policy.

What to do next

Log on to OpenPages and verify that the messages display.

Tip: To remove a message, repeat the steps and clear the text in the Label box. If you added a privacy statement link or an acceptable use policy link, clear the value of its registry setting.