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.1301
By using the Users and User Groups General properties you can define how to manage project protection. For instance, you can enable the protection on project editing, active the password management in Runtime, etc.
To modify the Users and User Groups General properties, select "Users & User Groups" from the Project Explorer window with the mouse and use the Movicon "Properties Window".
To verify the General properties common to Users and User Groups please refer to the "Users and User Groups General Properties" paragraph.
This selection allows you to activate the Runtime Users management so that new users can be added, changed, deleted during project runtime. In order to execute these functions the appropriate commands in 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 makes the Runtime Users file property of the project is was created in and therefore unaccessible by other projects. In fact when enabled, information is added to the .rtusers file which can be taken from the GUID project associated to the Runtime Users or taken from the 'Runtime User Access Code' property value if valued.
The setting in the propriety code file is done once only at first file save, therefore th 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 modified in the file from the project at Runtime (unless by editing within the file directly if not encrypted).
Obviously for more effective security it would be best to encript the file 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 allows you to define the User Level where the ones above will not be able to carry out any editing in Runtime. For example, if "User Level 5" is set, this means only users up to the fifth level can carry out any editing during 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, such as in a Client-Server configuration.
The network path can be specified in various ways:
''\\Nome_PCServer\FolderName\RTUsers.rtusersFileNome'' (i.e.: ''\\Server1\SharedFolder\RTUsersDB.rtusers'')
''\\IP_PCServer\FolderName\RTUsers.rtusersFileNome' (i.e.: ''\\192.168.22.44\SharedFolder\RTUsersDB.rtusers'')
''UnitàDiRete:\FolderName\RTUsers.rtusersFileNome'' (i.e.: ''Z:\SharedFolder\RTUsersDB.rtusers'')
or when using Window CE systems:
''\NET\RTUsers.rtusers''FileName"(i.e.: ''\\NET\RTUsersDB.rtusers'')
Therefore, in cases of a pure Client project, only the ".rtusers" file path needs to be set as described above, whereas Client-Server projects with Parent-Child technology with one or more Server projects (Child projects) sharing the same runtime users file resource, being 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 cases where the Parent project is not specified with a file or another runtime users file name, this management will always use the Parent project's file without considering those 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 in a machine outside the domain, the ".uxp" file in which Movicon saves modified passwords, must be enabled with anonymous access. |
This option can be used in objects set with "Password Levels" to run command/s associated to the object once user has logged in, with having to re-click object again.
|
In cases running Parent-Child network Client projects, the "Run Commands after Login" property is only considered by the Father project "Users and User Groups" level settings. |
This selection permits you to activate project protection by using passwords. When the protection is enabled only users with Developer rights (level 1024) can open the project in development mode.
|
Keep in mind that a project with active protection will not request any passwords at the system startup in Runtime, but the Developer password will be required (Level 1024) for entering in programming mode or for opening the project in programming mode. Before activating the password protection, the system will ask that there be at least one user with Developer password (level 1024) present. WARNING! If the User Name of Developer Password is forgotten, it will not be possible to open the project in programming mode. |
This selection permits you to activate the project's password manager during Runtime phase. By doing this you can associate different password levels to the project commands according to their requirements.
|
When the project's password management is enabled the System's operations (or Administrator) such as closing the project, can only be done by Users with Administrator rights. |
Enable CRF21- Part 11 Settings
Enabling this property, the 'Electronic Signature' property or the User's Description will be used as the Electronic Signature in conformance to the "FDA21 CFR Part 11" normative. For example, the 'Electronic Signature' is used to describe the User uniquelyin the 'User' column of the table referring to the TraceDB feature or a Data Logger set on command, when data is edited or when the Data Logger is commanded to do something.
This selection permits activation of User settings editing in conformity with the "FDA21 CFR Part 11" normative.
This property is used for setting the minimum number of characters which must be used for composing the Name of Users setup in the project.
|
Four characters is the minimum length set by Movicon for default. We suggest you don't use less than this for normative and security reasons. |
This property is used for setting the minimum number of characters which must be used for composing the Password of users setup in the project.
|
Six characters is the minimum length set by Movicon for default. We suggest you don't use less than this for normative and security reasons. |
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 i 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 are released.
Once the dialog window closes, the message will be written 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.
