|
There are advanced security functions you can perform with the Profile Editor. Advanced security let you enforce additional security on most OrderStream data entry forms.
Advanced security allows you to control access to sensitive information. For example for certain groups
| • | Hide line columns like costing or margins on Sales Order details |
| • | Make any field read only - the specified user cannot change the value eg Customer PO on the Sales Order form |
| • | Hide any menu selections on the header or on right mouse clicks |
| • | Hide selected tabs on a form header – like commission calculations on Sales Order |
| • | Make selected command buttons invisible – e.g. Delete Button on Sales Order |
| • | Make the Item Master information “Read Only” |
| • | Lock the RFQ Module and/or Item Editor |
| • | Prevent editing of item BOMs while allowing Adding or Editing of Vendors |
The following table shows examples of how Advanced Security is implemented.
|
|
|
|
Order Entry
|
Hide costs and margin fields
Make Item Editor Read Only
|
Hide costs and margin fields
Make Item Editor Read Only
Hide Commission Tab
|
Sales Rep
|
Make Item Editor Read Only
Make Delete Button Invisible
|
Make Item Editor Read Only
Make Delete Button Invisible
|
Sales Manager
|
No restrictions
|
No restrictions
|
Production
|
Hide entire form
|
Read only access
|
Making Modules Read Only
If you wish specific users to be able to view a module's information on the form, but you need to prevent them from modifying the transaction without having to approve it, the solution to to use advanced security to make the form read only.
If you see the read only records in the advanced security setup form then you may proceed to assign the control to the desired users as you would any other advanced security control. If you do not see any read only controls on the advanced security setup form, then you will have to add them before proceeding.
The following table illustrates how to enter the records to make eligible modules read only.
|
|
|
|
|
|
|
ReadOnly
|
0
|
frmPurchaseOrder
|
4
|
Lock Purchase Order
|
2
|
ReadOnly
|
0
|
frmReceiving
|
4
|
Lock Receiving
|
2
|
ReadOnly
|
0
|
frmPOInvoicing
|
4
|
Lock Vendor Invoice
|
2
|
ReadOnly
|
0
|
frmWorkOrder
|
4
|
Lock Work Order
|
2
|
ReadOnly
|
0
|
frmShipping
|
4
|
Lock Shipping
|
2
|
ReadOnly
|
0
|
frmSalesOrder
|
4
|
Lock Sales Order
|
2
|
ReadOnly
|
0
|
frmEstimating
|
4
|
Lock Estimate
|
2
|
ReadOnly
|
0
|
frmInvoice
|
4
|
Lock Invoice
|
2
|
ReadOnly
|
0
|
frmCreditNote
|
4
|
Lock Credit Note
|
2
|
After you have entered the records as indicated above you can assign the read only control to the desired users.
sxSystem SecuredControls table Field Reference
The advanced security controls which can be assigned to users are located in the SecuredControls table of sxSystem. In the event you wish to add additional available controls which are not already present in sxSystem you may manually add the required records. Note that SecuredControls records are maintained by running DataTransfer; core system SecuredControls records will possess a negative SecuredControlID. Any SecuredControls records you manually create will be assigned a positive SecuredControlID.
A definition for each field in the SecuredControls table is below. For a complete listing of available advanced security controls see the topics within the section titled Advanced Security Control Listing.
|
|
|
SeradexControlID
|
Identifies a SecuredControls record as a record that has supplied by Seradex as part of the master list of secured controls. When manually adding a new record to the SecuredControls table leave this field blank.
|
ControlName
|
This refers to the internal name of the control you see on the form. Seradex provides this to you when you want to setup a secured control.
|
ControlIndex
|
The column position of the field on a module spread or the position of a tab in a module header which the advanced security control is to be applied.
In the case of adding advanced security to a module spread, while using this field correctly will work, it is recommended to make use of the Description field or the ColumnLabel field instead. The reason is because there are hidden fields on most module spreads; therefore simply counting the fields from left to right may not yield the correct number, making advanced security setup difficult.
When applying advanced security to tabs, the ControlIndex must be specified; the description field cannot be used.
|
ParentName
|
This is the name of the Form that contains the control.
|
Restriction
|
Sets the type of restriction you want to apply to the control:
1 = Locked
2 = Disabled
3 = Invisible
4 = Enabled
5 = Visible
|
Description
|
This description is visible on the OrderStream Advanced Security form.
If you are applying security to a specific field on a transaction form spread (details section of the form), enter the name of the field exactly as it appears on the form (including spaces). If you wish to enter a description you deem appropriate for the secured control record instead of the name of the field, you can enter the description, and then enter the name of the field exactly as it appears on the form (including spaces) in the ColumnLabel field.
If you are not applying security to a specific field on a transaction form spread (details section of the form) you may enter any description you deem appropriate for the secured control record.
|
ControlType
|
This is the type of control you are affecting. The supported control types are:
0 = Tab Control, frame
1 = Form details section (spread)
2 = Menus, combos, text boxes, forms, check boxes, radio buttons, date
3 = Buttons, toolbars
-2 = Label, control arrays (i.e. core fixed User Defined Fields such as those on the Customer Ship To Form)
|
ColumnLabel
|
Please see the Description field explanation. ColumnLabel is used as an alternative to Description when applying security to a specific field on a transaction form spread (details section of the form)
|
|
