(this is not for native/phonegap)

On a mobile form, when i'm editing/viewing a Form, and want to press a button to create a new object (like on a customer, and want to add a new note), I want that to come up in a PopUp.
PopUp works fine on desktop - we've all seen that.
But on mobile, here's what I get.
Screen Shot 2018-12-28 at 5.07.54 PM.png

Obviously this is not usable.
Am I doing something wrong?
Did I mess up some CSS?

I tried using these for the Output selector on the Panel Operation:
default, NewTab and SamePanel - all operate the same, but after adding the rec I can't get back to my form. Screen blank.
PopUp AND Modal do the same thing - narrow form, unusable

Except for messages, Popups are not true responsive in Aware's Mobile and I avoid using them on Mobile.
Recently, Support was asking "What is NOT working on Mobile?". Well you should report this to support to be fixed for next version.

Jaymer wrote

ben
what about this thread
V7 Mobile - New option to show form from Process (comment)&hilit=mobile+popup#p35898

whats the syntax to EDIT "in current tab"?

That whole feature request from support related to the link you sent, was shut down (generally 99% of my FR have been shut down since 2014). So, I don't have an answer for you.

I'm thinking PopUp, because I need several things to happen when I click a button on a Form.
FROM a Customer Form:
1) Create the Note
2) Insert the Note into a Customer.om_Notes list
3) Do something else with the data

From Panel Operations, If I use the built-in Create Object, then the Note gets created, but not attached to the Customer.
(Have tried running a process AFTER the Save, but it doesn't have the Customer in Context)

If I use a Process, it uses a Popup and is unusable.

Don't know what to do.

CREATE will not populate the Ob attribute on your note. You have to do that manually.

Either CREATE note with note.obCustomer=Customer or
INsERt Note into Customer.omNotes when you Save

PointsWell wrote

Either CREATE note with note.obCustomer=Customer or
INsERt Note into Customer.omNotes when you Save

yes, i know that.
problem is that is in a process, and the process makes a unusable popup.

i can do a ENTER NEW x WITH xxx AND VIEW
but I still need to do other processing after, so I have more statements after this one, so the process makes a popup.

Popups, though we don't necc. like them, usually display fine on Desktop.
Issue is on mobile they are foobar.
Thats the real issue.

Jaymer wrote
PointsWell wrote

Either CREATE note with note.obCustomer=Customer or
INsERt Note into Customer.omNotes when you Save

yes, i know that.
problem is that is in a process, and the process makes a unusable popup.

i can do a ENTER NEW x WITH xxx AND VIEW
but I still need to do other processing after, so I have more statements after this one, so the process makes a popup.

Popups, though we don't necc. like them, usually display fine on Desktop.
Issue is on mobile they are foobar.
Thats the real issue.

I went through this crap 2 years ago and had to change my whole approach and design "Differently" (app dependent) for the Mobile.

6 days later
Jaymer wrote
PointsWell wrote

Either CREATE note with note.obCustomer=Customer or
INsERt Note into Customer.omNotes when you Save

yes, i know that.
problem is that is in a process, and the process makes a unusable popup.

i can do a ENTER NEW x WITH xxx AND VIEW
but I still need to do other processing after, so I have more statements after this one, so the process makes a popup.

Popups, though we don't necc. like them, usually display fine on Desktop.
Issue is on mobile they are foobar.
Thats the real issue.

i dealt with something similar before and its a nightmare with mobile.
especially when i have a process that evaluate a condition and there is another rule after.
aware will force a popup and i dont like them at all on mobile.

i can do a ENTER NEW x WITH xxx AND VIEW
but I still need to do other processing after, so I have more statements after this one, so the process makes a popup.

In my mind Pop Ups are a problem in mobile apps and I try and not use them when it comes to designing mobile apps. I would always use ENTER NEW x WITH xxx AND VIEW and then follow through with the rest of the Process statement using object rules. If there is another object to be created in the process list then let the Object rule do an ENTER NEW x WITH xxx AND VIEW and so on . This way you could totally do away with pop-ups.

Somewhere in the object rule, you would have to cater for the deletion of the already created object, if it was aborted or for whatever reason it should not exist. If you use flags on the object and set them based on conditions to fire background process rules you can get quite creative

You can set the form width, I use 300px or 350px. That's the only thing that works for me. Issue is obviously user phone size.

Aware IM will respect the width of the form if it is specified. Now, if the width is NOT specified there is a bug in the current system, where it uses all available width minus 300px (this is good for desktop, but not mobile). This bug will be fixed in the new build, that is coming soon. When the bug is fixed the system will use available width minus 30px on mobiles.

Now about popups on mobiles in general. You should use them sparingly. You all know that when you use "UI" actions in a process (such as EDIT, ENTER NEW etc) Aware IM will usually force a popup window. UNLESS the "single tab mode " property has been set for the process. This property has been specifically designed to avoid popups on mobiles and you should use it. Combined with the "mobile transitions" property of a visual perspective it should give the most authentic user experience on mobiles. At least, in theory.

aware_support wrote

Aware IM will respect the width of the form if it is specified. Now, if the width is NOT specified there is a bug in the current system, where it uses all available width minus 300px (this is good for desktop, but not mobile). This bug will be fixed in the new build, that is coming soon. When the bug is fixed the system will use available width minus 30px on mobiles.

Thanks Support, for saving me the time to get to the bottom of this and I'm glad it is resolved.
Thanks again!

6 years later