06-18-2014, 02:21 PM
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.)
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.)