Aware IM User Forums

[RocketRod]

1. The 'Choose file' does not get replaced with anything after a user has selected a picture. In the non mobile application it fills in the file spec. As the original wording is maintained it confuses users as to if they have actually selected a picture. Standard wording would be ok it just needs to be different... For example Picture selected or something similar.

2. I also note that after having uploaded a picture you cannot change other attributes on the form and then SAVE as you get the BO has been changed by another user error.

Cheers Rod

[aware_support]

Number 2. has been fixed in build 1515. Cannot do anything about 1. yet
_________________
Aware IM Support Team

[RocketRod]

Point two has raised its ugly head again? Seems the fix you implemented was lost in the move to 5.3.

Happens for both Android and iPhone, i.e. you get the message .....BO has been changed by another .....

Pictures upload fine in both cases.

Cheers Rod

[aware_support]

I am sure the fix was included. Have you cleared your browser cache after the upgrade?
_________________
Aware IM Support Team

[aware_support]

We have reproduced the problem on iPhone. Android should still be OK.

The fix for iPhone will be in the next maintenance release (if you want it sooner please send us an e-mail)
_________________
Aware IM Support Team

[aware_support]

The fix is in build 1533
_________________
Aware IM Support Team

[RocketRod]

Have now installed and tested the latest release. It still does not work for me. Have tried on three different phones, one of which has not been used before. Cleared caches etc on the existing phones.

In my app I:

1. Run a query.
2. Edit an instance in context.
3. Form has three tabs one of which holds two picture attributes only.
4. User uploads a picture (which works fantastically), hits the SAVE button and gets the error message. No other info on the other two tabs has been changed.
5. User has to answer to not save changes and exit the instance.
6. Go back into the instance again and the picture is there and other info can now be changed.

Note: Have several rules on BO which would be fired on SAVE. Did you try with that?

Cheers Rod

[aware_support]

We tested it several times ourselves and it definitely works for us. There was definitely a bug before for iPhones but we are quite sure that we have fixed it in the latest release.

Perhaps this is something specific to your BSV, so why don't you send it to us and describe how to reproduce the problem?
_________________
Aware IM Support Team

[RocketRod]

Ok, I will set up a test BSV and send it to you.

Cheers Rod

[RocketRod]

Found it....found it after 5 hours of testing and trouble shooting!!!!!!

You were correct again!!! An issue related to my app.


I use login and logout notifications to log user access! These are being activated due to the passing off and back to the PICUP utility! They are therefore creating the version issue on the record. Proved it with a sample BSV. The regularuser BO is a reference on my picture BO and the regularuser bo is in the notifications.

So is there some way I can change my notifications to not fire off when Aware passes control to PICUP and back

OR

Do I need to change my notifications

OR

Will you do something so they don't fire off?

Quick reply on this one would be most appreciated.


Cheers Rod

[aware_support]

The best would be to change your notification handling if you can. It would be a problem to make changes to this area again in the code.
_________________
Aware IM Support Team

[RocketRod]

OK thanks for the reply. Will modify my app.