Form inconsistencies

Mark HHP

Hi guys.

I have a form for viewing a quote and at the top are buttons to approve the quote and decline the quote. So far so good.

Now, I have a button at the top for creating a new quote and this runs a process where you pick a client and create a quote for that client. It runs a CREATE then EDIT using exactly the same form. But now process buttons on form are not visible?

kklosson

When the form goes into create mode, it becomes a different animal. I suggest you have one form for create and one for edit and call them as needed. But it stands to reason that your create form is basic - to get the parent record established, then you call the edit form with all of the extra functions on it.

Mark HHP

OK, but I think that's how mine is set up.

It runs a CREATE Quote WITH Quote.QuoteStatus='Draft' etc
then runs EDIT Quote USING ConsultantQuoteEdit which is the special form I use with the processes on it. Everything is the way it should be but any process buttons disappear (I have a QuoteLineItem section within the form which has a Duplicate button, that too falls away)

BenHayat

Mark HHP wrote
OK, but I think that's how mine is set up.

It runs a CREATE Quote WITH Quote.QuoteStatus='Draft' etc
then runs EDIT Quote USING ConsultantQuoteEdit which is the special form I use with the processes on it. Everything is the way it should be but any process buttons disappear (I have a QuoteLineItem section within the form which has a Duplicate button, that too falls away)

Just some thoughts...
Does it happen all the time or occasionally?

Have you verified it's not related to any Access Level restrictions?

Are these buttons towards the bottom of the page which may get pushed down beyond the frame section? If at the bottom, move them to the top to see if that changes.

Mark HHP

Hey,

Yeah, my first thought was that I'd set an applicability or something but no, exactly the same as the form displayed elsewhere.

I've tried adding it top, bottom, next, all of those. Nothing. I just don't understand. I thought that maybe the fact that it needed to be saved first would make a difference but thats why I went with CREATE into EDIT.

Argh!

BenHayat

Mark HHP wrote
Hey,

Yeah, my first thought was that I'd set an applicability or something but no, exactly the same as the form displayed elsewhere.

I've tried adding it top, bottom, next, all of those. Nothing. I just don't understand. I thought that maybe the fact that it needed to be saved first would make a difference but thats why I went with CREATE into EDIT.

Argh!

Just to eliminate another possibility, have you tried to import it into V6 Beta, to see if it behaves the same?

Mark HHP

That is a possibility but I don't have time to try that one out right now. Need to play in V6...

BobK

I remember running into this issue when I first started using AwareIM. My memory is vague, but it might be a limitation with AwareIM. When editing a form from within a process, you can not start another process. Mark, when the buttons display was the form opened via a menu or process?

I also vaguely remember something about using VIEW instead of EDIT, but I don't remember if that fixed this issue or not.

Mark HHP

This was my thinking, yes. I had a Client object with a form displaying all of its attributes and from there it was fine.

I think it is from within a process that the trouble starts. My reason for using a process to access from menu rather than just a create object default button was so that I could assign a client to it.

Maybe I must try rethink that whole structure.

kklosson

My experience is that my first approach is to take the hardest path. Second approach is always much better.

Mark HHP

Yeah, I took a break from the backend for 6 months or so and now I have to get back into it, hence all my simple questions.

I did get around this using VIEW instead of EDIT (thanks Bob)

Strangely, it still allows you to edit. But its sorted!

BenHayat

Mark HHP wrote
Yeah, I took a break from the backend for 6 months or so and now I have to get back into it, hence all my simple questions.

I did get around this using VIEW instead of EDIT (thanks Bob)

Strangely, it still allows you to edit. But its sorted!

When using VIEW Action, use NOEDIT Parameter, if you don't want editing.

Mark HHP

Perfect, thank you. My brain is gradually kicking back in but not as fast as I'd like (we close for the year today)