Skip to content

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

@ettlitetlov

Description

@ettlitetlov

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @ettlitetlov

        Issue actions

          No use of providing appId to enigma session creation? · Issue #992 · qlik-oss/enigma.js