AwareIM URL command parameters

rgates@ttcdas.com

Does anyone know whether these command parameters are valid w/version 4? I am trying to launch awareIM via a embedded URL in a email. The goal is that the user will be prompted for credentials if they aren't logged in. Also, it will take them to the update of the object and objectid passed in the URL.

logonOp.aw?domain=yourBusinessSpaceName&dynamic=true&firstCommand=updateEntity.do?entityName=objectName&entityId=objectId

where yourBusinessSpaceName indicates the business space
dynamic=true indicates that the system has to login if not logged in already
firstCommand indicates the command to execute after login. In this command entityName is the name of your object and entityId is the id of the instance you want to view

The value of the firstCommand must be "URL_encoded"

aware_support

The "firstCommand" parameter is invalid - it is in the version 3.0 format, but the main URL is in the version 4.0 format. You cannot mix the two. In version 4.0 the first command embedded in URL must encode the name of the Javascript function and optional parameter as indicated in the format of links in Aware IM User Guide. The name of the function and parameter should be delimited by "," symbol. For example, the User Guide defines the following function:

startProcess (processName)

The firstCommand parameter must be:
...&firstCommand=startProcess,myProcessName

rgates@ttcdas.com

I looked in the user guide and I see the functions. I don't see the function that says to display a form in either edit or input mode. Also, I need to be able to pass the objectID along with the command so that the form displays with the appropriate record. Is there somewhere else I should be looking in the manual beyond page 376?

rgates@ttcdas.com

A complete sample that is similar to what you had given me with version 3.0 would be very very helpful.

aware_support

We'll add the ability to edit an object into the new build. If you are interested we can send the change to you now before the build (it is in the javascript). You'll have to specify the following parameter for the firstCommand:

...&firstCommand=editObject,myObjectName,myObjectId&...

rgates@ttcdas.com

Yes, I am interested in getting the functionality now. Also, I don't see anything regarding the other parameter dynamic=true. Is this too available in 4.0.

Simply put, I need to be able to have a URL that I can embed in emails that will bypass login if already logged in and then open a Object form in one of the modes edit or add. Also, if the mode 'Edit' is used then I would pass in the URL the objectID.

aware_support

Oops. The "dynamic" functionality 'fell through the cracks" in version 4.0 - only supported in version 3.0. We'll support it for the next build, but you'll have to wait for it. It will be available within a couple of days.

rgates@ttcdas.com

Ok, that would be great.

It seems odd that I am the only person requesting or looking for this missing functionality in 4.0. To me it is more the norm then not to be able to launch an application via a URL into a specific record.

aware_support

This has been implemented in build 1133 available for download now

rgates@ttcdas.com

Could you please prove a example syntax like you did below for version 4?

logonOp.aw?domain=yourBusinessSpaceName&dynamic=true&firstCommand=updateEntity.do?entityName=objectName&entityId=objectId

The value of the firstCommand must be "URL_encoded"

aware_support

This is what you need to enter:

logonOp.aw?domain=yourBusinessSpaceName&dynamic=true&firstCommand=editObject,objectName,objectId

where yourBusinessSpaceName is the name of your business space
objectName is the name of the object you want to edit
objectId is the id of the object you want to edit

For example:
logonOp.aw?domain=CRM&dynamic=true&firstCommand=editObject,Customer,5

rgates@ttcdas.com

Thank you!

rgates@ttcdas.com

When I use the URL as suggested it does take me to the appropriate record. The only issue is that it opens a whole new tab for the application even though I have a current session open.

Secondly, if my session has timed out, it then presents me with a login. This is correct, but the issue is that it loses the original set of parameters that I had passed along in the URL. I have used applications in the past that would redirect to login, but maintain the information in the URL so that it still completes the original set of commands/parameters.

I have seen the losing of original parameters happen with just a general login where I specify domain. If I enter the wrong credentials it takes me to this URL http://appsrv01:9080/AwareIM/logonOp.aw versus the original URL of http://appsrv01:9080/AwareIM/logonOp.aw?domain=IT

aware_support

When I use the URL as suggested it does take me to the appropriate record. The only issue is that it opens a whole new tab for the application even though I have a current session open.

There is nothing we can do about this. When the user does it in the real world it would have to open a new tab!

Secondly, if my session has timed out, it then presents me with a login. This is correct, but the issue is that it loses the original set of parameters that I had passed along in the URL. I have used applications in the past that would redirect to login, but maintain the information in the URL so that it still completes the original set of commands/parameters.

Which parameters do you mean? It is not supposed to lose the business space and if does we will fix it. It should not and will not retain other parameters though

rgates@ttcdas.com

Ok. Well that kind of stinks. So, basically the user needs to stay logged in all day to the application otherwise passing parameters in the URL are useless.

Can I ask why it can't do it? Is it a limitation or just something that you guys don't want to implement.

It does lose the domain parameter if you enter the wrong credentials.

aware_support

As far as losing the "domain" parameter after entering wrong credentials - we have fixed this and the fix will be in the next build.

The "domain" parameter will be retained after timeout as well (it should be retained in the current build). It does not make sense to retain other parameters, such as "dynamic" or "firstCommand" after timeout.

aware_support

The problem has been fixed in build 1135

rgates@ttcdas.com

Do you post what fixes/changes have been implemented in a build?

tford

http://www.awareim.com/changelog/

rgates@ttcdas.com

Thanks Tom.