This property is only managed when the "Enable Password Manager" property has been activated. Otherwise, the Runtime users will not be managed by Movicon.
Movicon Help on Line - Rel. 11.7.1302
Project protion can be managed by using the Users and User Groups General properties. These properties allow you, for instance, to enable the protection on project editing, activate the password management in Runtime, and other.
To modifythe Users and User Groups General properties, select the "Users & User Groups" resource from the Project Explorer window and use the Movicon "Properties Window" that opens when doing so.
To verify the General properties that are common to Users and User Groups, please refer to the chapter on "General Properties common to users and User Groups".
This selection allows you to activate the Runtime Users management so that new users can be added, changed, or deleted at project runtime. In order to execute these functions, the appropriate commands from the Commands list of the Movicon controls or the dedicated Basic Script function must be used.
|
This property is only managed when the "Enable Password Manager" property has been activated. Otherwise, the Runtime users will not be managed by Movicon. |
This property the Runtime Users file proprietary of the project that created it and therefore inaccessible by other projects. When this property is enabled, information will be added to the .rtusers file which is retrieved from the GUID project associated to the Runtime Users or from the 'Runtime User Access Code' property if set with a value.
The setting in the proprietary code file is done once only when the file is saved for the first time. Therefore, the file is linked to the project or group of projects by the code it contains impeding access by other project that do not know the access code.
Once an 'Access Code' has been set in the .rtusers file (set by the project or by VBA functions at runtime), it can no longer be physically changed from the project at Runtime (unless by editing the .rtusers file directly if not encrypted).
To obtain more effective security, the file will need to be encrypted by using the Project's General 'Encripted Project' property.
When the corresponding 'Enable Runtime User Security' property is active, this property allows you to customize the Access Caod inserted as information in the .rtusers file to make it project propriety. When not valued, the access code will be inserted using the project's GUID.
This property is useful for sharing a Runtime User file with several projects that use the same Access Code when set with the path to reach the .rtusers file in the "Runtime Users File" property.
This property is used to define the maximum User Level impeding those levels above this one access to edit the project at Runtime. For example, if "User Level 5" is set, this will mean that only users up to the fifth level can edit the project at Runtime.
This property is used for specifying the path and Runtime users definition file name. The file name can be specified with or without the ".rtusers" extension. In addition, if a path is not specified, the local project folder file will be considered.
It is also possible to specify a network path to allow the same runtime user file to be shared among other applications, for instance in a Client-Server configuration.
The network path can be specified in various ways:
''\\Name_PCServer\FolderName\RTUsers.rtusersFileName'' (i.e.: ''\\Server1\SharedFolder\RTUsersDB.rtusers'')
''\\IP_PCServer\FolderName\RTUsers.rtusersFileName' (i.e.: ''\\192.168.22.44\SharedFolder\RTUsersDB.rtusers'')
''NetworkDrive:\FolderName\RTUsers.rtusersFileName'' (i.e.: ''Z:\SharedFolder\RTUsersDB.rtusers'')
or when using Window CE systems:
''\NET\RTUsers.rtusers''FileName"(i.e.: ''\\NET\RTUsersDB.rtusers'')
Therefore, in a Client project scenario, only the ".rtusers" file path needs to be set as described above. In a scenerio where Client-Server projects use the Parent-Child technology with one or more Server projects (Child projects) sharing the same runtime users file resource, which are Client project users (Parent-Child) managed through the Parent project users, the Parent project will have to be set with the same Parent projects' (Server projects) runtime users file network path. In a scenario where the Parent project is not specified with a file or another runtime users file name, the Parent project's file will always be used without considering those that have been defined at Child project level.
|
When the runtime user file is placed in a network path, the folder in which this file has been saved must be enabled to access various clients. In addition, when projects run on a machine residing outside the domain, the ".uxp" file in which Movicon saves password changes, must be enabled with anonymous access. |
This option can be used in objects set with "Password Levels" to execute command/s associated to the object once the user has logged in so that the user will not need to click the object again to do so.
|
When running Parent-Child network Client projects, the "Run Commands after Login" property will only be considered by the Parent project's "Users and User Groups" level settings. |
This is used to enable project protection with the use of passwords. Enabling project protection will only allow users with Developer rights (level 1024) to open the project in development mode.
|
Keep in mind that a project that has been enabled with protection will not request any passwords when starting up in Runtime mode. The Developer password will only be required (Level 1024) to enter into development mode or to open the project in development mode. To enable password protection, the system will require that at least one user with Developer password (level 1024) be present beforehand. WARNING! If the User Name of Developer Password is forgotten, it will not be possible to open the project in development mode. |
This is used to enable the project's password manager at Runtime. This will allow you to associate different password levels to the different project commands as required.
|
When the project's password management is enabled, the various System operations (or Administrator), such as closing the project, can only be performed by Users who have been given Administrator rights. |
Enable CRF21- Part 11 Settings
When this property is enabled, the 'Electronic Signature' property or the User's Description will be used as the Electronic Signature in conformance with the "FDA21 CFR Part 11" normative. For example, the 'Electronic Signature' will be used to identify the User in the 'User' column of the table referring to the TraceDB funtionality, or a Data Logger command, who edited data or commanded the data logger.
This selection is used to enable the editing of User settings editing in conformance with the "FDA21 CFR Part 11" normative.
This property is used to set the minimum number of characters to be used to compose the Name of Users that have been configured in the project.
|
Four characters is the minimum length set by Movicon for default. In order to comply with the normative and for security reasons, it is advised not to use less than this number. |
This property is used to set the minimum number of characters to be used to compose passwords of user that have been configured in the project.
|
Six characters is the minimum length set by Movicon for default. In order to comply with the normative and for security reasons, it is advised not to use less than this number. |
This is used to enable the recording of each failed user login attempt in the Project's System Log.
This is used to set the minimum numercal digits that the Password must have.
This is used to set the minimum number of special characters that the Password must have.
The special characters that can be used are: (space)!\"#$%&'()*+,-./:;<=>?@[\]^_{|}~"
Enabling this will require the use of both upper and lowercase characters in the Password.
This is used to set the number of previously used Passwords that cannot be reused as a new Password.
No. of Exp. Password Prewarnings
This is used to set the number of Password Expiry prewarnings before the user's password actually expires.
Max. Invalid Password attempts
This is used to set the maximum
number of Login attempts before the user is blocked.
Once the maximum number of failed Login attempts set here has been reached,
a message will appear on screen notifying the user that they will be blocked
and will not be able to attempt another Login until they have been released.
Once the dialog window closes, the message will be reported in the System Log.
To "Release" blocked Users, simply use the User Command type with the "Release" Action.
This is used to set a time that
once expired will unblock the user. When this value is set to '0',
the user will always remain blocked.
This property only carries weight when the "Max. Invalid Password
attempts" property is used to
set the maximum number of failed Login attempts allowed
before blocking the user.
