Script Profile

The Script Profile object allows an Administrator to control the access and permissions that Lua executing objects (Action Items, Generic Items etc.) have to the models and objects in the system. The Script Profile operates like a Profile for Lua executing objects. It is created in the Access Model and Model Authorization is granted in the object itself. Permissions can then be assigned (List, Read, Write, Modify, Execute, Inherit) at an object level, by dragging and dropping onto objects in the respective model panels. Lua executing objects are then assigned to the Script Profile by adding them to the Assigned Objects table property (through either the object picker or dragging and dropping them into the table rows). The assigned Lua executing objects are then conferred the model authorization and permissions of the Script Profile object.

The access and granted permissions of Script Profile are only activated by setting the Lua Security Mode property of the associated Core to "Restrictive".

Script Profile objects are not completely analogous to Profile objects as they cannot be used to login to DataStudio or used by external APIs/OPC clients to access the system. They also cannot be granted Profile Audit Trail Roles.

Use Cases

Assigning security permissions to Lua executing objects in the system

Quick Configuration

Right-click on the Access Model, select New Data Processing Script Profile.
Enter an Object Name in the Common page of Create Profile wizard.
Change Administrative Role to "Administrator" if you want the Script Profile to have full administrative rights (equivalent to the system owner profile created at installation). If selected, then the other General and Model authorization options will be greyed out as they are all applied. Change to "Reviewer" if you want to grant read-only administrative access to all models (except the Access Model). Check the AdministrativeGroup codings for available options.
Expand the Model Authorization section and select the model panel access for the profile from the available options.

Model Authorization grants access to the individual models but they will not be available to the assigned Lua executing objects of the Script Profile until permissions have been set.
Click on the Assigned Objects table property to open the table dialog. Lua executing objects can be assigned to the Script Profile by dragging and dropping them from model panels or selecting thm using the object picker. Click OK when object selection is finished.
Click Create to create the object in the Access Model.
To assign permissions to objects in the model panels, drag and drop the newly created Script Profile onto an object in one of the model panels. The will open the permissions dialog where the List, Read, Write, Modify, Execute and Inherit permissions can be selected. Click Apply to set the permissions.

Object Properties

Common

Object Name: The user-modifiable object name. This name overrides the name which has been supplied by the external system. It must be unique within the collection of objects of the parent object.

Object Description: This is the user-modifiable object description. This text overrides the description which has been supplied by the external system.

Administrative Role

None: No administrative access.
Administrator: Full administrative access.
Reviewer: Read-only administrative access.

Model Access

I/O Model: The I/O system comprises all classes required for managing external data sources and persistent data storage including Time Series and A&E historization.
System model: The system model organizes interfaces and distinct data sources in a logical systems model, defines logical namespaces, redundancy and priorities as well as custom vendor and system settings.
KPI Model: The KPI model comprises all classes which relate to key performance indicators and their organization.
Access Model: The Access Model consists of all classes that allow for setting security permissions to other models and classes. It supplies the features which are required to create and maintain a secure Information Management System.
Server Model: The Server Model lets you manage external Server interfaces of system:inmation and the assignment of other models to the namespace of particular Servers.
ISA-95 Equipment Model: The ANSI/ISA95 Equipment Model may be definitions of sites, areas, production units, production lines, work cells, process cells, or units.
ISA-95 Material Model: The ANSI/ISA95 Material Model defines the actual materials, material definitions, and information about classes of material definitions.
**:
**:

Assigned Objects: Assigned script objects or tree structures, to which this ScriptProfile applies.

System Functionality: Assign the ScriptProfile to System Functionality. For advanced users only.

Custom Options

Compound to hold various structures to customize the object and to be read and written to by Lua-Script code or external interfaces.

Custom String: A generic string buffer to be used programmatically for custom purposes.

Custom Properties

This is an extensible set of named strings which can be used programmatically for custom purposes.

Property Name: A custom property name which can be used programmatically.

Property Value: The value of the custom property which can be read and written programmatically.

Custom Tables

This is an extensible set of named tables which can be used programmatically for custom purposes.

Table Name: A custom table name which can be used programmatically.

Table Data: Handles an entire table organized in columns and rows. The data can easily (cut, copy and paste) be exchanged with table-oriented data of other software products, e.g. MS Excel.