opening an app in a new browser instance

[apparelbusiness.com]

Hello,

I have an app is started directly from a url link below. User clicks on the below link and it takes them directly to the APP. In the app there a multiple buttons on the left hand side.

https://xxxxxxx.com:6080/build/production/Runner/index.html?app=4029#main

P1.png




When the user clicks on the button “Sales Flash” above they are getting the error below.

P2.png


But if the app is started from the main login page and then the user clicks on the Button "Sales Flash" it works fine. Is it possible to start a new app in the setup where the app is called directly and then try's to open a new app in a new browser ?


p3.png


P1.png

[Johnny Major]

You need to be running within the Portal if you want to launch other applications outside of the original application. So, instead of running the application standalone, you would need to launch the Portal and pass the application to auto-start, in your case, the "Dashboard." The Valence guides have more information on calling the portal and auto starting a specific app;

[apparelbusiness.com]

http://192.168.1.1:7060?user=vvadmin&password=vvadmin



The parameters available are as follows (you may specify any combination of these in any order on your Valence URL):

• &user=xxxxx (optional) - sets the Valence user ID logging in (what the user would otherwise type into the login page)
• &password=xxxxx (optional) - sets the password for the &user. If not supplied or not correct, the user will be sent to the standard Valence login prompt. Note that passwords encoded in this manner are human-readable, so this approach may not be appropriate for all situations. See "Pre-generating a Valence Session ID" section below for an alternative approach.
• &environment=xxxxx (optional) - sets the environment for the session. This is the unique numeric “ID” value associated with the environment ID (see the Environments Guide for further information). If &environment is not supplied and the user is authorized to more than one environment, the user will be logged in to the last environment they were using, or if they've not logged in before then the first environment in their list will be selected.
• &customSid=xxxxx (optional) - sets the pre-generated Valence session ID to be used, thereby bypassing the need to include user/password/environment parms in the URL, or having the user prompted to log in. It is only necessary to construct a new session ID if the user is not already logged in to Valence, as the Valence Portal will automatically bind to the active session ID in the browser if one already exists. See next section for details on creating a custom session ID.
• &app=xxxxx (optional) - sets the Valence app ID to auto-launch. This is the unique numeric “ID” value associated with the app (see the Apps Maintenance guide for further information). If not specified then the standard Valence Portal will appear with all authorized apps listed in the navigation tree.
• &portal=xxxxx (optional - “true” or “false”) - controls whether the user should have access to standard Valence Portal functionality in this session. If set to false, then only the app specified in the &app parm will be accessible. Valence will still handle all the back-end processes normally controlled through the portal, such as library list adjustments, user swapping and security verification. Setting &portal to false will save some loading overhead as numerous portal-related objects are omitted.
• &autoStart=xxxxx (optional - “true” or “false”) - controls whether the autostart apps should be loaded or bypassed. If not specified, this value defaults to false when &portal is set to false, true otherwise.

So I would set it up something like this ? Where do I tell it what app to autostart.

http://192.168.1.1:7060?autoStart=true

[sean.lanktree]

You would want to pass "app=YOUR_APP_ID".

[apparelbusiness.com]

Something like this.

http://192.168.1.1:7060?autoStart=true&app=12345

[sean.lanktree]

I do not think you want autoStart=true.

[apparelbusiness.com]

This appears to have worked....as I am able to start up the other app in a new browser window....