Re: D2W Navigate from Create to List
Re: D2W Navigate from Create to List
- Subject: Re: D2W Navigate from Create to List
- From: Theodore Petrosky <email@hidden>
- Date: Wed, 06 Nov 2013 09:27:06 -0500
Is there a reason that you should not create an attribute that describes a 'New' item.
I have to do this with duplicates. My users select an object and make 10 duplicates. I set a boolean attribute (isADupe) to true. it remains true until they edit the object.
when I return from 'duplicating' the original object, I select all objects that are marked 'isADupe', and present a short list. These object remain 'dupes' until they are edited and saved.
So if they want 10 duplicates of an object where each object is nearly identical except for the due date, make 9 duplicates and edit each one changing the due date. As you save the edited object, set isADupe to false.
BTW, thank you for "Learning the Wonders'! It is really helping me learn the missing pieces.
Ted
On Nov 6, 2013, at 8:38 AM, Markus Ruggiero <email@hidden> wrote:
> What is the best way to handle the following customer request in a Neutral Look D2W application?
>
> After pressing <Save> on a create page the customer wants to got to a list page displaying the just created object. Maybe the user wants to add a bunch of objects and might eventually miss-type a code and then not be able to figure whether he has entered the correct value. And while working off a list of data to enter he might lose track of which entry he has to add next. In other cases the creation of an object is pretty simple but afterwards editing is necessary due to very complex background processing that cannot take place before an EO has been properly saved.
>
> Standard D2W behaviour is going back to whatever page was shown when the user pressed <New>. Customer wants to see what was just created. I was thinking of a generic next page delegate on any Create* page configuration. I know how to create a list page and return that, but the problem is how to best populate that list with the one entry that has just been saved. I was thinking of creating an array datasource for the list page with that one object, but should this not be a database datasource? How would I then create a proper fetch spec? As there are many different types of EOs I cannot just pick some common attribute and create a qualifier for its value. The only real identifier would be the primary key but that is of course not modeled.
>
> Thanks for any ideas.
> ---markus---
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden