My Profile

Overview

The My Profile page allows users to access their Personal Information, Preferences, Bill To and Ship To information. Users typically access this page by clicking the My Profile icon or from the User Navigation Menu.

Watch Video  Video icon

My Profile page

The following properties are available for the My Profile page:

Main Information
Property Description
*Login

The username that the user will use to login to the system. The Login cannot be the same login as any other user on the site and can be changed after the user is created.

See the Host Company Login (Username) Guidelines section below for Login name criteria information.

Password

The password that the user will use to log in to the site. Leaving the password field blank will create a temporary password. Selecting the Email Password checkbox will send an email containing the password (either manually entered by the admin or generated by the system) to the email address in the Email field.

After the user has been created, a Reset Password button will allow the admin to reset the user’s password. The new password will be emailed to the user.

*Email

The email address of the user. If applicable, the system will send approval notifications and broadcast emails to this email address.

  • You can give any user multiple email addresses in his/her user profile. In the Email field, separate multiple email addresses with a comma. For example: email1@email.com, email2@email.com. All emails sent by the system to a user will be sent to all email addresses defined in the user's profile.
  • Email addresses can be validated to enforce that all active user email addresses are unique. See the section Unique Email Address Validation section below for more information.
Type The user type of the user. For more information on user types, see the topic User Administration Overview topic.
Permissions

User Administrator

Select this option to allow the user to create new users and modify other users.

  • This option only displays for FullAccess Type users.
  • Prior to Release 18B, the User Administrator option was labeled Create/Modify Users.
  • For more information, refer to User Administration Overview

Access Administrator

Access Administrators can create and edit Administrator groups.

  • The Enable Administrator Groups setting on the General Site Options page must be set to Yes to enable this option.
  • This option is always enabled for the Host Company SuperUser and defaults to disabled for all FullAccess users.
  • When Administrator Groups are first enabled, the SuperUser must assign Access Administrator permissions to other FullAccess users.

Allow Proxy Login

This option allows administrators to log in as another user to verify changes to their setup or isolate issues reported by users.

  • The Enable Administrator Groups setting on the General Site Options page must be set to Yes to enable this option.
  • Users must be logged in as a SuperUser or a FullAccess user with Access Administrator permissions to change the Allow Proxy Login permission.

Web Services

When selected, the user can only access the system by logging in through the SOAP or REST APIs. The user will not be able to access the Oracle CPQ user interface.

For more information on Oracle CPQ Web Services see the topics An Overview of Web Services 2.0 and SOAP APIs and REST API Overview topics.

Enabled SSO

If the User is enabled for Single Sign-On login and the site is enabled for SSO, the user can access login via this method.

If the External SSO ID is set it will be used for SSO, otherwise the User's Login will be used.

For more information on permissions, refer to User Permissions.


Personal Information
Property Description
*First Name The user’s first name.
Last Name The user’s last name.
*Company Name The user's company name
Job Title The user’s job title.
Phone The user’s phone number.
Fax The user’s fax number.
Preferences
Property Description
Language Preference The user’s preferred language. The admin can choose from a list of the site’s supported languages. The user will see system defined strings on both the admin and user side of the application in this language. For more information on languages and translations, see the topic Internationalization Overview.
Currency Preference The user’s preferred currency. The admin can choose from a list of the site’s supported currencies. With a few exceptions, all Transactions created by the user will use the user’s preferred currency. For more information on these exceptions and how Transaction currency can be determined, see the topic Selecting Transaction Currency.
Number Format

The user’s preference for how decimals are separated in Configuration and Commerce Float attributes (whether the radix point is a period or a comma). The admin can choose between ####.## where a period is the decimal separator and ####,## where a comma is the decimal separator.

  • Float attributes do not have thousands separators.
  • Currency attributes are formatted based on the Transaction’s currency.
Units The user’s unit-type preference. The user will see this unit-type preference as the default unit for all numeric Configuration attributes that are tied to a Conversion Class. The admin can choose either the System Default unit-type to show (which will be either English or Metric), or English or Metric units to be shown as the default unit. For more information on units and Conversion Classes in CPQ, see the topic Unit Conversions.
Javascript/Advanced HTML Opt-In

While Oracle CPQ does not endorse or guarantee the use of JavaScript customizations, we recognize that some customers have extended the Oracle CPQ. Customizations may present a security risk, conflict with new Oracle CPQ platform features, data may be corrupted or lost, maintenance and support may be difficult, cross-browser support must be verified, performance may be impaired, and testing is required for each upgrade. Customers should consider carefully the relative benefits of JavaScript customizations in light of the associated risks.

Beginning in Oracle CPQ 22B, administrators must opt in to add customized advanced HTML/JavaScript to the site. This checkbox must be selected in order for the user to add or modify customized JavaScript or Advanced HTML scripts. If a user attempts to add custom advanced HTML without this setting selected, an error message displays indicating the opt-in setting is required. When this occurs the JavaScript/HTML content is blocked from entry. The user can remove the JavaScript/Advanced HTML content or opt in. This setting reminds users of the risks associated with JavaScript/Advanced HTML customizations and they take responsibility for the risks to their site.

Date/Time Format

The user’s date and time format preference. The user will see dates formatted within the application in accordance with his/her preference. The admin can choose between several Date/Time Format options:

  • MM/dd/yyyy h:mm a
  • MM/dd/yyyy HH:mm
  • dd/MM/yyyy HH:mm
  • dd.MM.yyyy HH:mm
  • yyyy/MM/dd HH:mm

Note: A user’s Date/Time Format setting will not be used in places within the application where date and time format can be explicitly set by the admin, such as in a Document Designer or Email Designer output.

Time Zone The user’s time zone. The user will see all dates/times within the system based on his/her Time Zone. Refer to Time Zones for a complete list of supported time zones.
Notification Preference

When Email is selected for Notification Preference the user will receive approval notification emails, Submit sub-action notification emails, and Transition Rule notification emails from the system. When Email is not selected, the user will not receive any notification emails from the system, even if the criteria to send him/her a notification email is met.

Note: Users that elect not to receive notification emails from the system will still receive Broadcast Emails.

Delegated Approver The active user that will receive the same approval notifications as the user and can approve or reject Transactions on his/her behalf. Typically the Delegated Approver is set by the user when he/she will be out of the office and cannot access the system to perform his/her approvals. For more information, see the topic Delegated Approvers.
Bill To and Ship To

Bill To and Ship To filelds

Property Description
Bill To Fields

The user’s address for billing.

For Host Company users, Bill To fields are not typically used as an actual billing address, but rather they are typically used to give sales rep contact information attributes values on Transactions. All Bill To fields are system variables and can be referenced as attribute defaults and in BML functions.

Ship To Fields

The user’s address for shipping, which can be set to use the Bill To address information by selecting the Same as Bill To checkbox.

For Host Company users, Ship To fields are not typically used as an actual shipping address, but rather they are typically used to give sales rep contact information attributes values on Transactions. All Ship To fields are system variables and can be referenced as attribute defaults and in BML functions.


ClosedUser Integration Page

On sites that are set up to integrate with Salesforce or eSignature (DocuSign), a User Integration button exists on the bottom of the Admin tab of the User Administration page.

User Integration button

Clicking User Integration opens the User Integration page.

User Integration page

The User Integration page is used to store partner login credentials and to generate or revoke the user’s OAuth tokens. For more information on the User Integration page, see the topic Integrations and the User Integration Page. For more information on the integrations that utilize the User Integration page, see the topics Salesforce Integration and DocuSign eSignature Integration.


Notes

Clicking My Profile displays information related to the logged in user.

Related Topics

Related Topics Link IconSee Also