Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No use of providing appId to enigma session creation? #992

Open
ettlitetlov opened this issue Dec 7, 2023 · 0 comments
Open

No use of providing appId to enigma session creation? #992

ettlitetlov opened this issue Dec 7, 2023 · 0 comments

Comments

@ettlitetlov
Copy link

Description

Expected getting handle to app given ID

Steps to Reproduce

  1. Using enigma.js in node.js and SensUtilities.buildUrl
  2. Marking up correct path to QlikSense engine using host, prefix, and appId.
  3. Calling session.create(config);
Expected behavior

As stated in documentation: for appId in buildUrl: "The app ID. If omitted, only the global object is returned. Otherwise both global and app object are returned."

Actual behavior

Only session is returned, and I wonder what the point of using appId in config if that is the case, since to connect to a actual app requires additional global.openDoc(appId)

Environment

Library
[x ] Node.js
[ ] Browser
Operating system
[x ] Windows
[ ] OSX
[ ] Linux
Qlik Sense
[x ] Desktop
[ ] Enterprise

Versions

  • Node.js: 16.20.2
  • Browser:
  • Qlik Sense:
  • Operating system:
  • enigma version 2.11.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant