Wednesday, December 03, 2008
Sign-up

WebSource CPQ

Your are @  Forum
 
  

Hola guest, we invite you to visit each of our topic-specific forums and enjoy the community of helpful people there.

You are welcome to explore our message boards and read what our members are saying. However, only registered members may reply to an existing post, start a new conversation thread, or vote in polls.

Membership is 100% free. Please Sign In with your username (if you are a member) or Sign Up for a membership.

  
 
  Forum  Discussions  CPQ Roadmap  Top 10 CPQ Features for future release
Disabled Previous
 
Next Disabled
New Post 3/13/2008 2:48 PM
Poll
User is offline Alex Knezevic
4 posts
No Ranking


Top 10 CPQ Features for future release 
Modified By Alex Knezevic  on 4/4/2008 12:35:52 PM)

Based on a recent customer poll, Webcom, Inc. has published the following list as the top 10 requested features.

What are your thoughts?

Name

Description

Current Behavior

Desired Behavior

Product Rule Wizard

More user friendly rule (dependencies, rules, triggers) administration.

Creating product rules scares the users, even though it is not really that difficult. However, they appear daunting until administrators get used to it.

Create a more graphical UI for creating rules. Attached is an example of one possible approach.

Sequencing products on CART

User should be able to move products (items) up and down while in the shopping cart.

The sequence of products in the shopping cart can not be changed by the user.

Allow users to reorder items in the shopping cart as well as in the output document.

Attribute Where Used

Where used should find all places (expressions, etc.) where an attribute or attribute value is used.

The Attribute Where Used feature does not check expressions or eval statements other than in Rules/Triggers.  If an attribute is used somewhere else, Where Used does not find it.

If an Attribute is used ANYWHERE in the model, Where Used should find it. Also replace R with something more intuitive for where used functionality. Also, clicking on where used for a product attribute only shows rules where attribute is used and not where individual attribute values are used. While this is not a bug, many users assume that no attribute value are used either if entire attribute is not used. This needs to be improved.

Adjustable Session timeout

Users often request a longer timeouts so sales reps/admins do not lose information mid config/management.

Admin has 20 min timeout.

Admin can specify timeout of admin login as well as user session. See attached SFDC example.

Debug

Ability to debug a configuration session.

Users cannot turn on the debugger and obtain debug results easily.

Ability for a user (administrator) to turn on a debugger and to obtain debug results administratively without ftp access to the server.

Not Complete

It would be a nice feature to have the required attributes stand out of be highlighted to allow the user to quickly determine which attributes are the required ones.

User may not know which attribute needs to be selected and which tab to go to

Highlight attributes and tabs where they are located.

Laying out Attributes

Visual layout tool for attributes (drag and drop)

It is not easy to specify layout of attributes with in a step, tab and product.

Use AJAX to visually position (design) attributes. Something similar to www.netvibes.com

IF Syntax

Improved IF syntax builder.

Some find it difficult to create a correct if syntax. We have to type it in or use a syntax builder by clicking one element at a time.

Allow a user to place the entire If statement or several nested if statements in the syntax builder with one click. Create something like this
[IF](condition...){true action...}{false action...}[ENDIF]. Allow them to specify how many nested ifs as well.

Attribute Names and Values

Special characters in attributes and attribute names.

Currently users can define attribute names and/or display values with characters which will cause problems if those attributes are used in rules or expressions.

Encode these characters so that our parser does not get confused when they are encountered or prevent them from being used when defining attributes.

Admin Changes Audit Trail

Ability to see who made admin changes.

There is no way to see who changed what in the admin and when

Ability to have an audit trail in the admin.

 
Disabled Previous
 
Next Disabled
  Forum  Discussions  CPQ Roadmap  Top 10 CPQ Features for future release
CPQ User Group | All Rights Reserved