Navigation:  Security > User Profiles > Custom_Connection Component

Use Case

An administrator wants that an external identification system be used instead of the list of each estimate or of an active directory.

S/he wants to decide with her/his own code, which profile to use when opening an estimate.

Process

Custom_Connection is a dll used to define the allowed profiles based on a custom logic. the opening of To bypass  the regular logic, tell QDV7 which profile to use:

Required arguments:

The language of the interface thru the menu File>Options>Languages; eight native languages are planned (some are grayed out). Global Variables: SYS_LANG_UI

▪Available profiles names in the estimate

▪System variables: SYS_FilePath, SYS_FileName in case an authorization file is located in the same folder as the estimate

▪Global variables: GLV_TemplateID  as it may determine the behavior.

The component is made up of various functions:

▪GetVersion determines the version of dll

▪GetLoginForLicenseServer allows to pass a special string in place of the Windows login

▪GetUserProfileName lists the allowed profiles before manual selection if several are allowed.

The process is as follows (the regular flow is in bold):

Procedure

Find the component in <installation directory>/SDK/Custom_Connection.

Decompile it and program the functions GetUserProfileName and if needed GetLoginForLicenseServer.

GetUserProfileName can invoke a REST web service or reach a csv file:

Example in VB NET of a function that uses a REST web service:

Example in VB NET of a function that look up a cvs file:

 

Tu keep this customization in spite of QDV7 upgrading, refer to Adding Your Own Files.