4Customer Permissions

Allow Customers to Edit Fields on the Account Settings Page

When customers log in to the customer portal through PTA, by default they cannot edit the fields on that page.

This is because the allow_external_login_updates attribute of the input widgets on the page defaults to false. If you want to retain the default behavior, you will probably want to remove the Account Settings and Change Your Password pages and any links to them. If, instead, you want to let customers change their contact information, you can add attributes to the fields you want to be able to edit.

Follow these steps to allow customers to edit fields on the Account Settings page.

  1. Open the account/profile.php file.

  2. To let customers edit the First Name and Last Name fields, locate the line of code that defines the ContactNameInput widget and add the allow_external_login_updates attribute to it. The code looks like the following:

    <rn:widget path="input/ContactNameInput" table="contacts" required = "true" allow_external_login_updates="true" />
  3. To let customers edit other input fields, locate the line of code that defines the FormInput widget for the field and add the allow_external_login_updates attribute to it. For example, the code to let customers change their email address looks similar to this:

    <rn:widget path="input/FormInput" name="contacts.email" required="true" validate_on_blur="true" allow_external_login_updates="true" />
    Note: Regardless of how you set the attribute for the Username field ( contacts_login), customers cannot change this field when PTA is enabled.

How You Use Pass-Through Authentication with Service Level Agreements

In addition to requiring login on customer portal pages, you may want to restrict certain pages only to customers who have a specific type of service level agreement (SLA).

These code examples assume you want to edit the Ask a Question page to require an SLA.

If you require an SLA to submit incidents, edit the meta tag line of the ask.php file. Your modified code might look something like this, where the added code is in bold text.

<rn:meta title="#rn:msg:ASK_QUESTION_HDG#" template="standard.php" 
clickstream="incident_create" login_required="true" 
sla_required_type="incident" sla_failed_page="/app/error/error_id/2"/>

If you require an SLA to request a chat session, edit the chat/chat_landing.php and chat/chat_launch.php files. Your modified code might look something like this, where the added code is in bold text.

<rn:meta clickstream="chat_landing" include_chat="true" 
login_required="true" sla_required_type="incident" 

sla_failed_page="/app/error/error_id/2" />
<rn:meta title="#rn:msg:LIVE_CHAT_LBL#" template="standard.php" 
clickstream="chat_request" login_required="true" 
sla_required_type="incident" sla_failed_page="/app/error/error_id/2" 
/>