Hi @eqbstal 

Firstly, no: IFSAPP is not treated differently - it is affected by the context mapping, like other users.

I would recommend you try just putting USER=IFSAPP and see if that works.  That would indicate that the issue is with either the USERGROUP part or the OR.

I have a customer that found an issue with the USERGROUP mapping in UPD 8.

Paul,

Thanks for the tip.

It didn’t work for me. I even had the condition include spaces (‘USER = IFSAPP’ instead of ‘USER=IFSAPP’).

Odd, I’m thinking of a bug. What condition would fit all users, where I don’t want to fall back on the Global context?

I first try USER != NA (A non existing user). Grrr. Even that doesn’t work.

My process:

Make change to Context Mapping for Site related context. Save

Sign off from mWO

Enter Pin code for user IFSAPP. Sign in.

Dashboard is showing.

I earlier made a change on both the Global and Site related context for card My Work.

The My Work card for the Global context is showing up.

With the mapping of USER != NA I would expect the My Work that is following the Site related context.

mWO Service 10 version: 10.9.1326.0 is in use.

Steve

I've had issues getting this to work myself. Make sure your user doesn't below to two contexts e.g. one via a company mapping and one via a user mapping. If that happens it will revert to the global config.

Try clearing mobile cache (in IEE) and initialise your device. 

Currently there is only one:

I cleared the cache on the device (no data available in cache to refresh)

I can’t find the option in IEE to clear the mobile cache.

Next step that I did was to Initialize the device.

Result: global context was taken.

I think that I’m going to ask help via LCS.

Currently there is only one:

I cleared the cache on the device (no data available in cache to refresh)

I can’t find the option in IEE to clear the mobile cache.

Next step that I did was to Initialize the device.

Result: global context was taken.

I think that I’m going to ask help via LCS.

In Solution Manager\System Information and Utilities\Refresh Server Cache there’s a ‘MobileApplication’ cache that can be cleared.

I too have a case with support for this issue, but so far they haven’t been able to re-create it. Great if you can log one too!

Grr, I misread your post anmise. I tried to locate the refresh cache in Aurena while you told me/us to look in IFS EE.

I refreshed it there.

Initialized the device (from the device it self, an iPad).

Still not showing the correct context.

I will commence preparing an LCS case.

Steve

I did some further testing on this and got it working.

Steps I used:

1. Created a new context for ServiceApp.
2. Changed label for Site and added a new custom field (Cf_Severity).
3. Mapped it to my user. 
4. On the mobile device logged out and disconnected from the app
5. Connected/Re-activated .

Let me know if this works for you as well. I’ve only tested with the simplest mapping so far i.e. User=USERNAME.

 

Thanks for the effort. I still encounter problems. Also the Custom  Fields don’t work in mWO (as this seems to me the trick to get the context to work).

Hm, that’s too bad. Can you try from scratch creating a brand new context and connect it only to your user e.g. User=eqbstal in the Configuration Context Mappings?

What do you mean Custom Fields don’t work in mWO? They don’t show up? Have you added them to the sync entity and published custom fields (they should still show up before this, but be unusable).