Stump the Panel » End Users and Information Workers

WSS3.0 - Totalling items passing through radio button stages

(5 posts)
  1. cepes
    Member

    Hi:
    I am using a List as a simple Sales Pipeline with 6 stages (radio buttons). My view of this list shows how many prospects are in each stage at that moment.

    I was asked to show how many prospects we've "quoted" vs how many we've "sold" but because each stage is a pass through, except the "Sold" (which is an end stage) I have no idea how many were quoted.

    Can you help me figure out a workflow or a method whereby each prospect, as it passes through the "quoted" sales stage, gets recorded so I can get a grand total "quoted" to run against the number "sold?

    Thanks!

    Charlie Epes
    Buffalo, NY
    Wss 3.0
    SPD 2007

    Posted 9 months ago #
  2. Charlie - Rethink your architecture a little bit. I have the same type of scenario I'm building for a client who wants to track the on-boarding process of new employees: where are they in the processing cycle.

    With six stages, how about six columns? Each column is a radio button, or checkbox if you prefer. Give each column a stage name. Each prospect will be an item. When a prospect has completed a stage, click the "Completed" button for that column.

    The advantage to this approach is you can filter by any stage and have a much more granular way of tracking your data. Setup a filtered view that "archives" prospects who have completed the entire process. Now you've got a historical reference with a simple change to another view.

    Lots of fun here if you take it a little deeper with metadata about each stage.
    Mark

    Posted 9 months ago #
  3. Can you add columns to the list?

    Maybe you can write the quoted amount to a comments field (with append text) with an SPD workflow or populate a new, hidden field, when the state changes.

    Posted 9 months ago #
  4. Paul - Unless I'm mistaken, the problem is one of state... where in the process is each client. I agree with you that it would be nice to be able to carry around metadata with each quote, including the amount quoted. What do you think of the proposed solution, one column for each state?

    Mark

    Posted 9 months ago #
  5. cepes
    Member

    Hi Mark:
    Regarding a column for each stage, that a cool idea... sometimes we overthink things, I guess.

    The one issue I see is that this method relies on the user to complete each stage (click each stage). Summing all numbers with each stage depends on the user... and my users (A-type sales folks) have training issues!

    I think Paul's method might serve me best since I can let a workflow do the work by recording the quote stage to another field and I can give the training-challenged users the simple "choose one option". I'm open to other opinions though.

    Charlie

    Posted 9 months ago #

RSS feed for this topic

Reply

You must log in to post.