Filtering on logged in user in a mobile persistent login app

[John_Titor]

Hey guys,

So I've realized getcurrentuser and session variables doesnt work as well in persistent login situations.

But I need to filter the list for the logged in user, and trying to get my head around this now.

So as far as I've gathered
When you save the token to local storage you need to store the username
like: e._state.userName = userName (in XBasic) AND localStorage.setItem('userName',userName); (in JavaScript)
When you open the embedded UX you need to retrieve it and pass it into a variable, from witch you'll create the argument for the list filter.
like: var userName = pObj.stateInfo['userName']; ----- But I don't see something like localstorage.getItem ever be used?

And when I get it again in which event should I declare the variable in order for the list to be able to use it as an argument?

This is extremely confusing.

[Davidk]

Re: Filtering on logged in user in a mobile persistent login app

I see no issue using A5WS_GetCurrentUser()... although I would use the current Context.Security functions instead. The sample template for persistent login uses Context.Security.

You should never use Session variables in a mobile app... regardless of the situation. Again, the sample template for persistent login does not use session vars... makes use of state vars... and sets and gets localstorage items.

Work backward from what you want to do. You're working with a List. You need an argument filter. In mobile there are really only 2 ways to provide a filter argument with data:

1. A Session var - which should never be used in a mobile app - so that's out.
2. Set value at Runtime - pointing the argument to a control to get its data... this is what you want to do.

So... if you're going to use, for example, a Textbox Control for the value of an argument... then you must first set the value of that Textbox control.

At whatever point you validate your Username, e.g. after a successful login, set the value of that Textbox Control. Now you can use that Textbox control for the argument value. At that same point, save that Username for future use... e.g.:

a State var
localstorage
Phonegapfile strorage

[CharlesParker]

Re: Filtering on logged in user in a mobile persistent login app

Since I u session vars in my mobile PGB application, I was wondering what are the pitfalls that make it a really bad choice? I believe you, but would like some pointers. Currently all UX components set the companyid with a lookup using the getuser method you listed but not using “context” as suggested.
It seems to be working but it seems it might be a bad choice for future proofing.

Your thoughts would be most appreciated.

[Davidk]

Re: Filtering on logged in user in a mobile persistent login app

If the server isn't there... your session var isn't there. Session vars expire.

[CharlesParker]

Re: Filtering on logged in user in a mobile persistent login app

Ok, but if the alpha server isn't there then there is literally no reason to use my application as it would be impossible to use in my case. Even though I do use pre-rendered UX's and restore from local storage (sometimes) if the session var is not there during a submit or a component load, the submit will fail and the user gets logged out.

I only use 1 session var and that's to get the company_id of the logged in user during component load - beyond that I use arguments.

I do not plan on a disconnected application at this time.
Thanks for answering, btw.
I think we have had this same conversation in the past in another thread so I don't expect a reply here unless you feel the need to expand on something.

[John_Titor]

Re: Filtering on logged in user in a mobile persistent login app

Hey guys,

I've been working of a previous post of David's.

I am using the persistent template, I just want to set the value of a control in the child UX first before I'll go on to add it to a argument, and edited the following:

IN PARENT UX: Replaced end of xbLogin with:

jsOut = "completePersistLogin();"
xbLogin = jsOut
e._state.token = token
e._state.userName = userName
e._state.guid = e.tmpl.guid

IN PARENT UX: Added JavaScript

function completePersistLogin(){

	var guid = {dialog.object}.stateInfo['guid'];
	var userName = {dialog.object}.stateInfo['userName'];
	var token = {dialog.object}.stateInfo['token'];
	
	{dialog.object}.panelSetActive('PANEL_APPLICATION');
	localStorage.setItem(guid,token);
	localStorage.setItem('userName',userName);
	
	//embedded child UX
	var cObj = {dialog.Object}.getChildObject('EventsUX');
	var cEle = cObj.getPointer('LOGGED_IN_AS');
	cEle.innerHTML = userName;	
	
	var ele = {dialog.object}.getPointer('LOGIN_ERRORS');
	ele.innerHTML = '';
	
}

IN PARENT UX: In onRenderComplete

{dialog.object}.stateInfo['userName'] = userName;

note: I keep thinking there should be something like this in there? var userName = localStorage.getItem(userName);

After this thread's com

IN CHILD UX: In onRenderComplete

var pObj = {dialog.Object}.getParentObject();
if(pObj){
	var userName = pObj.stateInfo['userName'];
	var ele = {dialog.Object}.getPointer('logged_in_as');
	ele.innerHTML = userName;
}

I'm not sure why this step is necessary because it looks like the value should already be set in the function completePersistLogin()

Ok, so after this it does change the text in the child control. But changes it to 'undefined'. So it gets the userName variable, but it doesn't have a value.

[Davidk]

Re: Filtering on logged in user in a mobile persistent login app

onRenderComplete has finished running by the time completePersistLogin() is run.

So... yes... you'll need that code to get your userName from localStorage... for the Parent to be setup up properly.

For the Child UX, it depends on how it's set up to run. Is the Child UX onRenderComplete running while the Parent is finishing? Shove a console log or alert statement in both the Parent and Child UX to see in what order things are happening.