Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Reducing data entry.
As a general design and implementation principle it seems to me that the less data entry a user needs to do, the better. Much better.

If an interaction can be reduced to a button or a picklist, or got rid of entirely, all the better. Generally, users don't want to enter data.

In this regard, to start off:

- having to enter a 'subject', each time for a quote, sales order, and invoice is tedious for users... They will often duplicate what they entered at a previous stage. They struggle to think of a new subject each time. They don't see the point.

Once an 'opportunity name' is entered, can this become the 'subject' of subsequent quotes, sales, orders and invoices that follow from that opportunity?

I realise that 'subject' is probably a primary database key. However, that is not the user's problem etc.

(Perhaps it could be auto-generated on save from opportunity name plus status or similar.)
Hi Ronan,

Nice to see you around here <!-- s:-) --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":-)" title="Smile" /><!-- s:-) -->
First, sorry for taking a while to get back to you, I was concentrated on a few projects and the latest release.

Your question here is something we have on our road map to solve. Our idea is to permit the administration user to indicate which fields are the module identifier and also create a mapping of fields between related modules so the administration user can copy values from one to the other on creation.

Those two together would permit you to reduce the "unnecessary" subject field.

I have to add that what you are asking for here is something we do a lot for our client's customizations <!-- sSmile --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="Smile" title="Smile" /><!-- sSmile -->

<!-- m --><a class="postlink" href=""></a><!-- m -->

Forum Jump:

Users browsing this thread: 1 Guest(s)