Is this a bug or feature?

BenHayat

I have a form that is called from VP Menu. Menu type is "Change Login details". When I run it, the "Form Menu" at the top doesn't show up. However, if I make a simple query and call the form from query, the form menu shows up.

Is this a bug? If not, what's the logic behind it? I need those form menus to display for Customer when editing his profile.

Thanks!

kklosson

Are you calling using EDIT or VIEW? Try both.

BenHayat

kklosson wrote
Are you calling using EDIT or VIEW? Try both.

No, from Menu, I'm using menu type "Change Login details".
But when I called it from a query with Edit Object, the Form menu shows.
Try using "Change Login details" menu type and you see the problem

hpl123

Ben,
If I recall correctly this has something to do with the RegularUser form and I think the "Change login details" opens up a special type of the form where the form menu, some settings etc. doesn´t work. I have previously tried to change settings on that particular form opened via that command but couldn´t do it.

Think this is a type of bug but you can work around it using processes to open up your form instead.

BenHayat

hpl123 wrote
Ben,
If I recall correctly this has something to do with the RegularUser form and I think the "Change login details" opens up a special type of the form where the form menu, some settings etc. doesn´t work. I have previously tried to change settings on that particular form opened via that command but couldn´t do it.

Think this is a type of bug but you can work around it using processes to open up your form instead.

Yes Henrik, I think you're correct, something to do with Customer being used as LoggedInUser. Because even when I create a process and use Edit action to open up "LoggedInCustomer" and that form, then the Form Menu doesn't show up either.
However, if I create a query to show a list of customers and I pick any to edit with the same form, them the Form Menu shows up.
I've sent it to Vlad, but I hope it's a bug and they can fix it, because I need to provide loggedInUser some actions to perform.

BenHayat

Good news guys, Vlad just responded that, it is a bug and will be fixed. Big relief on my side, because I need to provide users some Action buttons to perform.

hpl123

Ben,
Yeah, you have good thoughts and ideas and I try to give my input (+1 etc.) to things I find good/useful (some others do this as well). I also try to post FR´s for things I think of and I hope to think Awaresoft looks. reviews, considers in some way all FR´s for the future roadmap. Even if we post FR´s and there seems to be support in the community (could be better i.e the involvement, 1+´s etc. could be better), this takes time but here and there small additional features are added so that´s good.

hpl123

hpl123 wrote
Ben,
Yeah, you have good thoughts and ideas and I try to give my input (+1 etc.) to things I find good/useful (some others do this as well). I also try to post FR´s for things I think of and I hope to think Awaresoft looks. reviews, considers in some way all FR´s for the future roadmap. Even if we post FR´s and there seems to be support in the community (could be better i.e the involvement, 1+´s etc. could be better), this takes time but here and there small additional features are added so that´s good.

Oops, this reply should have been in another thread:
https://forum.awareim.com/d/7636/3#p31804

BenHayat

This bug is also fixed in 2027. Confirmed!

mrbdrm

can anyone confirm this bug is still presence but with other BOs on ver 2040?
form menu never show unless i search the BO with query and edit the record.
creating an instance of the BO from a process then using EDIT BO or VIEW BO will give the same result, the form with no menu on it.

BenHayat

mrbdrm wrote
can anyone confirm this bug is still presence but with other BOs on ver 2040?
form menu never show unless i search the BO with query and edit the record.
creating an instance of the BO from a process then using EDIT BO or VIEW BO will give the same result, the form with no menu on it.

The original bug that I reported it, is fixed and still works properly as I tested now. Now you might be hitting on a different bug. Try to create a Test BSV and send it to Support