3

I want to do something that's been asked about before, but I am going to give some more reasoning in case I'm missing a better solution.

I am developing a package. As part of this package, there's a custom wizard for creating the case and some related fields. The steps I'd use are:

  1. Log call and caller (and dedupe)
  2. Take notes and determine basic case information
  3. Fill out details about case

I would love to be able to use the case's record type to generate the final page of the wizard. In an ideal world, administrators who install this package would be able to control the layout for each record type and thereby control the final page of the wizard.

Maybe the best way to do this is simply to set the record type in step 2, save all the information, and send the user to the edit page of the Case at the end of the wizard. Does that work? What am I missing here?

Improve this question
4
  • 1
    A wizard would normally only persist changes when the last page is saved; you are suggesting saving on the penultimate page and then showing the standard edit page. But if you label the button that does that "Save & Edit" perhaps it is reasonable.
    – Keith C
    Jun 18, 2014 at 23:38
  • @KeithC That's a great point re user expectations and SF standards. What does that final redirect look like in Apex? return ApexPages.StandardController(case).edit();?
    – Charles Koppelman
    Jun 19, 2014 at 1:49
  • @CharlesKoppelman yep, that's what you're looking for
    – Ralph Callaway
    Jun 19, 2014 at 2:33
  • @CharlesKoppelman Moved the comment to an answer.
    – Keith C
    Jun 22, 2014 at 11:25

1 Answer 1

Reset to default
3

A wizard would normally only persist changes when the last page is saved; you are suggesting saving on the penultimate page and then showing the standard edit page. But if you label the button that does that "Save & Edit" perhaps it is reasonable.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .