Introduction 

StrataVAR PqW provides a robust UI Settings page for administrators to configure key behaviors, defaults, and controls across the quoting workspace. These settings impact how users interact with PqW, how data flows between modules, and how business rules are enforced.

This article reviews the most important settings available in the PqW UI Settings area, explains their purpose, and provides guidance on when and how to use them.

Why UI Settings Matter & Where They Fit in the Admin Journey

UI Settings are foundational for:

• Aligning PqW with your organization’s quoting and pricing processes
• Controlling user experience (default views, required fields, workflow steps)
• Ensuring data consistency (item type, currency, approval flows)
• Reducing manual errors by enforcing business logic at the system level
• Admins should review and update these settings during:
• Initial implementation or onboarding
• Major process changes (e.g., new product lines, pricing models)
• Periodic audits or after user feedback

Overview: Accessing the PqW UI Settings Page

Step 1: Log in to Salesforce with admin privileges.
Step 2: Navigate to the PQW UI Settings app/tab in Custom Settings through Set Up option
Step 3: Open the UI Settings section.

You will see a page with grouped settings, typically organized by functional area (e.g., General, Pricing, Workflow, Imports, etc.).

Key Settings Explained

Below are the most impactful and frequently used settings, based on your screenshots and best practices.

1. Default Currency

What it controls: Sets the default currency for new quotes and projects in PqW.

Why it matters: Ensures consistency in pricing, reporting, and calculations, especially for global organizations.

Recommended usage:

• Set to your organization’s primary transaction currency.
• If you operate in multiple currencies, ensure users are trained to change this as needed per quote.

2. Default Margin and Discount Values

What it controls: Defines the default margin and discount percentages applied to new quote items, often by item type (e.g., Hardware, Software, Service).

Why it matters:

• Drives initial pricing logic and approval thresholds.
• Reduces manual entry and enforces company policy.

Recommended usage:

• Set realistic, business-approved defaults for each item type.
• Review periodically as pricing strategies evolve.

3. Item Type Source

What it controls: Determines whether the quote item’s item type is sourced from the BoM Item or the Master Item.

Why it matters:

• Impacts pricing, margin, and workflow logic.
• Ensures item classification is consistent with your data governance model.

Recommended usage:

• Use BoM Item if you rely on supplier/imported data.
• Use Master Item if you maintain a curated catalog as the source of truth.

4. Approval Workflow Settings

What it controls: Configures when and how quotes require approval (e.g., based on margin thresholds, discount levels, or deal size).

Why it matters:

• Automates compliance with internal controls.
• Prevents unauthorized pricing or discounts.

Recommended usage:

• Set clear, enforceable thresholds.
• Align with your sales operations and finance policies.

5. Import Source Preferences

What it controls: Specifies which BoM import methods are enabled (e.g., API, file upload, manual entry) and default behaviors for each.

Why it matters:

• Streamlines user experience.
• Reduces errors by limiting to approved sources.

Recommended usage:

• Enable only the import methods your team uses.
• Set defaults to match your most common workflow (e.g., API for Cisco, file for others).

6. Required Fields and Validation Controls

What it controls: Defines which fields are mandatory for quote creation, BoM import, or project setup.

Why it matters:

• Ensures data completeness and quality.
• Prevents downstream errors in pricing, reporting, or integration.

Recommended usage:

• Make all business-critical fields required.
• Review after any process or compliance changes.

7. Default Views and Console Layout

What it controls: Sets which tabs, columns, and views are visible by default in the PqW console for different user roles.

Why it matters:

• Improves user productivity.
• Reduces confusion and training needs.

Recommended usage:

• Customize for each major user group (e.g., Sales, Renewal Manager, Admin).
• Periodically review based on user feedback.

8. Error Log and Notification Settings

What it controls: Configures how errors are logged, displayed, and notified (e.g., email alerts, in-app banners).

Why it matters:

• Ensures timely awareness of issues.
• Supports proactive troubleshooting.

Recommended usage:

• Enable notifications for critical errors.
• Set up regular reviews of the error log.

9. Integration and API Settings

What it controls: Manages credentials, endpoints, and toggles for integrations with external systems (e.g., Cisco CCW, ERP, CRM).

Why it matters:

• Enables seamless data flow between PqW and other platforms.
• Reduces manual data entry and errors.

Recommended usage:

• Keep credentials up to date.
• Test integrations after any changes.

Common Checks and Best Practices

• Test changes in a sandbox before applying to production.
• Document your settings and rationale for future admins.
• Communicate changes to affected users, especially for workflow or approval logic.
• Review settings quarterly or after major business/process changes.

What’s Next?

After configuring UI Settings:

• Validate with real-world scenarios (e.g., import a BoM, create a quote, run through approval).
• Train users on any new behaviors or required fields.
• Monitor error logs and user feedback for further tuning.
• For more advanced configuration, see:
• Defining Item Type Rules in PqW
• Configuring Approval Workflows
• Managing Integrations and API Connections

Conclusion

PqW UI Settings are the backbone of your quoting environment’s consistency, compliance, and user experience. By understanding and managing these settings, admins ensure that PqW supports your business processes, reduces manual work, and delivers reliable results for all users.

Related Articles

• Defining Item Type Rules in PqW
• BoM Import Methods and Best Practices
• Error Log Monitoring and Troubleshooting