Licensing by session type

SyteLine allows named and concurrent licensing based on session type. Among other benefits, this feature allows named users to be logged in multiple times using different types of sessions, but only consume license modules for the appropriate type of session.

One of these session types is associated with each license module:

  • Full Client: This session type is used for a fully trusted client where form licensing grants permission to the form and all of the IDOs used by that form. This includes Windows clients and web clients where the web rendering is not in FormOnly mode.

    For example, when users log in from a Windows client on a computer, it is a "full client" session, and they can access both forms and IDOs.

  • Web Form Only: This session type is for web client rendering in FormOnly mode.

    When a user logs in from a mobile device, it is generally a "web form-only" session, that is, through a URL that includes the "formonly" URL parameter. The "web form-only" session type also applies to forms displayed through our Microsoft Office Integration.

  • IDO: This session type is used for programmatic (automated) access to the application's IDOs and their methods.

    For example, when users log in through the SyteLine Microsoft add-in or through a SyteLine portal, it is an "IDO" session, because they access SyteLine IDOs rather than forms.

  • IDO Custom User: This session type is used for SyteLine REST web service calls only. This session allows multiple (concurrent) web service calls to consume one license token for a given user and user module. An IDO Custom User session type matches any modules defined as IDO session type.
    Note: To leverage this session type, this header attribute must be specified as part of each REST web service call:

    X-infor-MongooseSessionType: CustomUser

    Any REST web service calls that do not contain this header attribute are executed with a standard IDO session type.

  • Undefined: No session type is defined. You should see this only if an orphaned connection record still exists from an earlier version of the application.
  • Additionally, there is a $service session type that is not associated with any module. The $service session type is used by framework utilities such as TaskMan. Under a service session, access to licensed form and IDO resources is granted without consuming any license tokens.