If you do submit an RFE, do the legwork before submitting it. Detail how you want the app to act and respond to as many scenarios as you can think of.
Axton Grams On 2/8/07, Joe DeSouza <[EMAIL PROTECTED]> wrote:
** You hit the nail on the head Axton.. That's exactly the root of my problems whenever I use diary fields on dialog boxes.. If an original bit of workflow used matching Id's to set values into it, the moment a diary field is added and has to be a part of that dialog (which was my case here) booom... I have to make changes to workflow that sets fields etc.. What I'm thinking of doing is almost close to your suggestion but I don't quite like that idea of creating 2 display only fields, one read only for setting the history part, the other display only for adding new stuff.. Workable but not screen smart on the aesthetic point of view when you are using more real estate to do what could have been done OTB if reading and writing data to and from both the editable and history part of the worklog fields was a little smarter.. As Shyam Attavar, suggested I wonder if this would be useful to have as a RFE as I really think this would save a lot of us a lot of sweat plus have our dialog boxes containing diaries a function better without the need for creating those unnecessary display fields... Joe D'Souza Remedy Developer / Consultant, BearingPoint, Virginia. ----- Original Message ---- From: Axton <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, February 7, 2007 10:33:10 PM Subject: Re: RANT: Diary fields in a dialog box.... ** Just don't use diary fields. In the case of the packaged apps, create a display only character field and allow updates to that field. Unfortunate side effect is that you can not use matching id's in one of 2 actions (on open/set or save/push). Axton On 2/7/07, Shyam Attavar <[EMAIL PROTECTED]> wrote: > > ** Joe, > > In my opinion this would go into the RFE bucket. Maybe worth a shot, > since BMC/Remedy uses diary fields in their OOB applications. > > -- > Shyam > > ----- Original Message ----- > *From:* Joe DeSouza <[EMAIL PROTECTED]> > *Newsgroups:* gmane.comp.crm.arsystem.general > *To:* [email protected] > *Sent:* Wednesday, February 07, 2007 4:51 PM > *Subject:* Re: RANT: Diary fields in a dialog box.... > > > ** > > Agreed, but it does tend to be a bit of a pain if you are doing > something like viewing a record in a dialog box, and that record has diary > fields, and you need to edit that diary field from the dialog box... What > then without any workarounds such as setting the historical part into a read > only field and having a display only field editable to push the new > content... > > > > Maybe I didn't really word my original post properly.. When this dialog > box is opened, it would be nice if the set field happens like it does for > any other field, I'm not contesting that.. But diary fields in the dialog > should have been able to recognize the historical part and open it in a > histry box below the editable part just like it does when you open the > record in a Modify mode... > > > Joe > > > ----- Original Message ---- > From: "Grooms, Frederick W" <[EMAIL PROTECTED]> > To: [email protected] > Sent: Wednesday, February 7, 2007 7:36:23 PM > Subject: Re: RANT: Diary fields in a dialog box.... > > ** I believe that is the correct workflow for the system to do. > > You are doing a Set Fields to the diary field. That always puts that > data into the editable portion. > > Why should it work differently on a Dialog than it would on a regular > form? > How would the system know if you were wanting the data to be the > historical data or just pre-populating data for the user to add to? > > Personally if I am doing something like that I put the historical data > into a display only (read only) character field. > > Fred > > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Joe DeSouza > *Sent:* Wednesday, February 07, 2007 5:38 PM > *To:* [email protected] > *Subject:* RANT: Diary fields in a dialog box.... > > > ** > Wonder why is it Remedy has never addressed to the issue that if you > open up a dialog box that contains a diary field, and there is a set field > action that brings in values from a record on open of the dialog, the Diary > field doesn't behave like its should have behaved. There is no uneditable > historical part for the field and an editable one. Everything from history > gets set to the editable part so if you want to edit its contents it > adds all this plus what you add during the transaction, to the diary for > each transaction > > Any idea as to whether or not this issue will ever be addressed to?? > > Joe > > ------------------------------ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
