Session Type
Valid types include these:
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.
: This session type
is for a fully trusted client where form licensing grants permission to the form and all
of the IDOs used by that form. This includes web client and Windows client rendering
where the web rendering is not in Form-Only 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.
: This session
type is for web client rendering in Form-Only mode. For example, when users log in through the Mongoose Microsoft add-in or through a Mongoose portal, it is an "IDO" session, because they access Mongoose IDOs rather than forms.
: This session type is
used for programmatic (automated) access to the application's IDOs and their methods. - Mongoose REST web service
calls only. This session allows multiple (concurrent) REST 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 an "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.
: This is a
session available to - : No session type is defined. This is a rare case. You should see this only if an orphaned connection record still exists from an earlier version of the application.
- Additionally, there is a 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.