eThority 6.0 Release Notes

baasopchoppySecurity

Nov 5, 2013 (4 years and 1 month ago)

153 views


















eThority
6.0 Release Notes














eThority 6.0 Release Notes

2

|
P a g e


TABLE OF CONTENTS


1

DATA ARCHITECTURE
ENHANCEMENTS

................................
................................
................................
..

4

1.1

M
ICROSOFT
.N
ET
4.0

................................
................................
................................
................................
..

4

1.2

W
EB
S
ERVER
.N
ET
4.0

................................
................................
................................
................................

4

1.3

S
PLIT THE
R
EPORTING
D
ATABASE

................................
................................
................................
................

5

1.3.1

Segregation of Data

................................
................................
................................
...........................

5

1.3.
2

Split the Reporting Database File Groups

................................
................................
.........................

5

1.3.3

Possible Errors that may be recoverable

................................
................................
..........................

5

2

ENHANCED SECURITY ME
ASURES

................................
................................
................................
............

6

2.1

N
EW
U
SERS

................................
................................
................................
................................
................

6

2.2

S
EPARATION OF
D
UTY

................................
................................
................................
................................
.

6

2.3

S
ESSION
I
NACTIVITY

................................
................................
................................
................................
....

6

2.4

D
EFAULT
O
RGANIZATION
S
ETTING

................................
................................
................................
...............

7

2.5

O
RGANIZATION
K
EY
G
ROUP
E
NFORCEMENT

................................
................................
................................
.

7

3

ETHORITY DATABASE CO
NNECTION MANAGEMENT

................................
................................
.............

8

3.1

F
ORM
C
HANGES
................................
................................
................................
................................
..........

8

3.2

C
ONFIGURATION
C
ONVERSION
................................
................................
................................
.....................

9

3.3

D
ATABASE
C
ONVERSION
I
TEMS
................................
................................
................................
..................

10

4

ETHORITY 6.0 FEATURE

ENHANCEMENTS

................................
................................
.............................

11

4.1

U
SER
K
EYS

................................
................................
................................
................................
...............

11

4.2

D
ATA
R
EQUE
ST

................................
................................
................................
................................
.........

13

4.2.1

File Type

................................
................................
................................
................................
..........

13

4.2.2

Importing

................................
................................
................................
................................
..........

13

4.2.3

Defini
tion

................................
................................
................................
................................
..........

14

4.2.4

Cleansing

................................
................................
................................
................................
.........

14

4.2.5

Required Relationships

................................
................................
................................
...................

14

5

ENHANCED ENCRYPTION

................................
................................
................................
..........................

15

5.1

E
N
HANCED
E
NCRYPTION
K
EY

................................
................................
................................
....................

15

6

DATABOOKS

................................
................................
................................
................................
................

16

6.1

C
HANGES TO
R
OOT
D
ATA
B
OOK
D
IALOG

................................
................................
................................
.....

16

6.2

D
ATA
B
OOK
P
RINTING

................................
................................
................................
................................

16

6.3

D
ATA
B
OOK
P
RESENTERS

................................
................................
................................
..........................

17

6.4

S
YSTEM
D
ATABOOKS

................................
................................
................................
................................

18

7

MAINTENANCE FORMS
................................
................................
................................
...............................

19

7.1

A
LL
F
ORMS

................................
................................
................................
................................
...............

19

7.2

G
LOBAL
P
REFERENCES

................................
................................
................................
.............................

20

7.3

L
ICENSE
K
EY
U
PDATE

................................
................................
................................
...............................

21

7.4

D
E
FAULT
D
ATA
L
OCK

................................
................................
................................
................................

22

7.5

D
ATA
R
EQUEST
M
AINTENANCE

................................
................................
................................
..................

23

7.5.1

Pre and Post Processors

................................
................................
................................
.................

23

7.5.2

Source Preprocessor

................................
................................
................................
.......................

24










eThority 6.0 Release Notes

3

|
P a g e


7.
5.3

Pre and Post Processors

................................
................................
................................
.................

25

7.6

D
ATA
R
EQUEST
T
ABS

................................
................................
................................
................................

26

7.6.1

Field Info Tab

................................
................................
................................
................................
...

26

7.6.2

Tr
ansform Fields tab

................................
................................
................................
........................

27

7.6.3

Relationships Tab

................................
................................
................................
............................

28

7.6.4

Tran Tags Tab

................................
................................
................................
................................
.

28

7.6.5

User Keys Tab

................................
................................
................................
................................
.

28

7.6.6

Im
port Log Tab

................................
................................
................................
................................

29

7.7

D
ATA
C
ONDUITS

................................
................................
................................
................................
.......

29

7.8

E
VENTS

................................
................................
................................
................................
....................

30

7.9

U
SER
M
AINTENAN
CE

................................
................................
................................
................................
.

30

7.9.1

Permissions Tab

................................
................................
................................
..............................

30

7.9.2

User Keys Tab

................................
................................
................................
................................
.

31

7.9.3

Ex
ceptions Tab

................................
................................
................................
................................

32

7.10

U
SER
K
EYS
M
AINTENANCE

................................
................................
................................
....................

33

7.11

R
OLE
M
AINTENANCE

................................
................................
................................
..............................

34

7.12

U
SER
G
ROUP
M
AINTENANCE

................................
................................
................................
.................

34

8

ADMINISTRATION ENHAN
CEMENTS

................................
................................
................................
........

35

8.1

S
YSTEM
H
EALTH
C
HECK
................................
................................
................................
............................

35

8.2

D
EFAULT
W
EB
S
ITE
V
ALUES

................................
................................
................................
......................

39











eThority 6.0 Release Notes

4

|
P a g e


1

Data Architecture Enhancements

1.1

Microsoft .Net 4.0

eThority Enterprise 6.0 now uses Microsoft .Net version 4.0. Both 32 and 64 bit
installations are supported.

.Net version 4.0 must be installed on the server prior to the installation of or upgrade to eThority 6.0


1.2

Web Server .Net 4.0

To enable the eThority Enterprise 6.0 web sites to function, you must enable Microsoft .Net 4.0 on y
our web
servers. Please take the following steps to ensure success:


Open your IIS Manager and

click the ISAPI and CGI Restrictions:





Make sure that ASP.NET v4.0.xxxxx is set to “Allowed” for the 32 or 64 bit applications:













eThority 6.0 Release Notes

5

|
P a g e


1.3

Split the Reporting Da
tabase

eThority Enterprise 6.0 introduces a separation of data between the eThority Enterprise system data and
additional data that has been imported for use within the eThority Enterprise system.


This separation keeps the imported data as well as its re
ference tables and relationships in their own database.
Additionally, the eThority Enterprise tables for definition and control are in a separate database.


It is recommended that administrators address any automated backup plans that may currently be in

place in
order to specify which databases to back up. The “current” databases must be at the latest 5.0 build
(5.0.73.2205) prior to splitting the imported and system data.


Note
:
Y
ou will need approximately 1.5 times your reporting database size for the

separation process to finish.


1.3.1

Segregation of Data

The four databases are:

Database

Contents

Purpose

EThority

System tables

Users, Data Conduits, Permissions

Reporting

Imported tables

All content imported by the client

Cache

Cache tables

Predictive
Caching Engine output

Extensions

Extension tables

Extension system of record data

1.3.2

Split the Reporting Database File Groups

Previously, the imported data in the Reporting database had one file group for data and indexes. This is now
split into 3 file grou
ps: Primary, eThorityIndexes, and eThorityXefs. This separation allows administrators to
more granularly control the disks where the file groups reside and in return, improve performance.


Version 6.0 can now optionally enforce the uniqueness of Data Requ
est Keys. Previous versions of eThority
allowed Data Requests to contain duplicate
keys.

With

the new option, a check can be run before any other
actions to ensure that the defined keys are unique. If duplicate keys are found, it is recommended that the
y be
corrected before continuing the data split and the upgrade


however, this is considered optional.


Note
: This action requires the eThority databases to be at least version 5.0 (5.0.73.2205).


1.3.3

Possible Errors that may be recoverable

If the followin
g errors are reported, try clicking ‘Migrate’ again which will re
-

start the separation process where it
left off. Please see below for a list of common errors of server contention.



Could not proceed with index DDL operation on table ‘XXXX’ because it con
flicts with another
concurrent operation that is already in progress on the object. The concurrent operation could be an
online index operation on the same object or another concurrent operation that moves index pages like
DBCC SHRINKFILE



A severe error
occurred on the current command. The results, if any, should be discarded.



Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not
responding.











eThority 6.0 Release Notes

6

|
P a g e


2

Enhanced Security Measures

2.1

New Users

We are now using 3 database a
ccounts for eThority Enterprise rather than the single ‘eThorityUser’. This
change will assist in the enhanced security measures included in the 6.0 upgrade. Please make note of the
following:



eThoritySystem is used to update the eThority Enterprise meta
data definitions



eThorityUser is used for running Databooks, eXcerpts and Dash (dashboards).



eThorityImporter is used to import your data into eThority Enterprise.

2.2

Separation of Duty

Separating the duties of each of the three database accounts will enhance

the protection against unwanted
actions in the databases. Each account will be allowed specific permissions to perform function against the
database. Some accounts will have read
-
only access in some databases.

2.3

Session Inactivity

In version 5.0, you could
set the number of minutes that a session could be active (Session Time Limit Settings).
In version 6.0, you can also specify how many minutes of inactivity (Session Timeout Settings) will trigger an
automatic log out of the user session.


The inactivity l
ooks at all forms (windows) that are open in the session. In the example below, there is no
Session Time Limit
, but there is a 5 minute
Session Timeout Setting

specified for Inactivity.


Note:


If you edit this while sessions are active, the open windows w
ill continue to have the previous timeout
and new windows and sessions will have the new timeout. This should be set while users have no access to
eThority.















eThority 6.0 Release Notes

7

|
P a g e


2.4

Default Organization Setting

In eThority 6.0, a new eThority user is assigned to a default org node when created if there are no org nodes
assigned previously to the user. This capability is showcased in the example below.

Note
: This feature is not available for installations of
the Multi
-
Tenant package.



2.5

Organization
Key Group Enforcement

In eThority 6.0,
an Org Key Group may only have a single Org Key Value
.


Warning: If you have previously set up an Org Key Group with multiple values, you
should convert the values to a single

composite value
and change the Org Key Group
to use the single composite value
before upgrading to eThority Version 6.0.











eThority 6.0 Release Notes

8

|
P a g e


3

eThority Database Connection Management

3.1

Form Changes

This following form has been modified to reflect the enhancements made to secu
rity and the segregation of
data
in

this 6.0 release.


Previous












eThority 6.0 Release Notes

9

|
P a g e


6.0 eThority Database Configuration Form

3.2

Configuration Conversion

When opening the new eThority Database Configuration form, the login account for new users will automatically
load with the password as the current eThorityUser account.


These new login accounts are also created and mapped to the assigned database accoun
ts when the reporting
database is being split.


You may choose not to implement the separation of duty security by assigning the logins for all accounts to be
the login for the existing eThorityUser account.


Note
: If you choose
not

to implement the separ
ation of duty security, converting the users to be different login
accounts at a later time is a manual process. It is important to note that this process may require an eThority
Professional Services engagement in order for the users to be implemented ap
propriately.













eThority 6.0 Release Notes

10

|
P a g e


3.3

Database Conversion Items

The ID columns within the reporting database holding tables have been enlarged in eThority 6.0. This will allow
for significant growth in the table sizes.


The change is also important for those data requests
that overwrite large numbers of records with regularity as
well as for those doing snapshots on larger data sets or those that have a high snapshot frequency. The
maximum value goes from more than 2 billion to more than 9 Quintillion (Million, Billion, Tr
illion, Quadrillion,
Quintillion)


Change in value range


ID Columns

Minimum Value

Maximum Value

Current

-
2,147,483,648

2,147,483,647

Upgraded

-
9,223,372,036,854,775,808

9,223,372,036,854,775,807











eThority 6.0 Release Notes

11

|
P a g e


4

eThority 6.0 Feature Enhancements

4.1

User Keys

A new concept, User Keys, is included in the 6.0 release. User Keys allow users to map values between the
logged in user and values in a Data Request where the user can be uniquely identified.


It may be helpful to think of User Keys as
your

own extension

to the eThority user record. For example, you may
have a Data Request with a column for “department” and you would like to limit the logged in user to their
respective department. With this new feature, you can create a User Key that is mapped to this col
umn. You can
assign the appropriate department User Key value to eThority Users, then create a filter in a root DataBook that
specifies department = UserKey(Department).


Examples of other User Keys would be Employee ID or Location.


Once defined, User Key
s can be used in any DataBook as part of a filter or in PowerFields.


When creating a filter after you have defined User Keys, you will notice a new radio
button in

the upper right of
the Filter Builder dialog.




In the example above, the filter is retur
ning only those rows where the ‘Division’ column matches the value in the
‘Division’ user key for the currently logged in eThority user.













eThority 6.0 Release Notes

12

|
P a g e


When creating a PowerField, User Keys are available both in the Condition Builder, as shown above, and in the
Expres
sion Builder. In the Expression Builder, User Keys are available as a new type of Constant, selectable in
the lower left portion of the dialog.




Note:

If a DataBook contains a User Key in a filter or PowerField and a user attempts to open that DataBook
and the user has not been assigned a User Key value, they will receive the following message when trying to
open the Databook:














eThority 6.0 Release Notes

13

|
P a g e


4.2

Data Request

4.2.1

File Ty
pe

Fixed Length File Type is also included in eThority 6.0. This feature allows the import of a fixed length file by
defining the columns visually by start and end position within the record by selecting the start and end columns
in the displayed data grid
.


When a DataRequest uses a Data Conduit with a File Type of Fixed Length Text, the Define Fields panel of the
Data Request Maintenance form will look like this:



From here, click Add to define fields. You can either enter the Start Position and length

of each column
manually, or use the visual representation of the file below to click the start and end position of each column.

4.2.2

Importing

In eThority 6.0, the Data Request Import functionality has been improved significantly. The speed increase is
between

30% and 80% depending upon the nature of the import and the data in the import.


Note
: Beginning in this release,
uniqueness for Data Request fields marked as “Key” can now be
enforced
. The import will be rejected if there are duplicate values observed
in any column marked as “Key”.











eThority 6.0 Release Notes

14

|
P a g e


4.2.3

Definition

PowerFields

The Data Request definition now supports creating PowerFields in the Data Request and users may choose a
storage type for the PowerField. It can be materialized (stored in the holding table) or eva
luated at runtime
(DataBook presentation only).


4.2.4

Cleansing

Using the new Materialized PowerField in a Data Request now allows you to apply rules to the incoming data
and alter the data that will be stored in eThority. Using the Transformation PowerField wi
ll allow you to apply
rules (including any defined
User Keys
) to the incoming data and alter the data that will be displayed in eThority
DataBooks.


*
Note
: A Data Request that has
User Keys

defined may not have Materialized or Transformation PowerFields.
The reverse is also true. Having Materialized or Transformation PowerFields will prevent defining User Keys on
that Data Request.

4.2.5

Required Relationships

W
hen creating
r
elationships between Data Requests you have the option to mark a relationship as “Requir
ed”.
If you do this, whenever you use the Primary Data Request in a DataBook, the Data Request marked as
“Required” will automatically be added to the DataBook.


In addition, if a Relationship is marked as “Required”, the Secondary Data Request’s fields w
ill appear and be
available in Materialized or Transformation PowerFields on the Primary Data Request.


Note
: If you add a “Required” relationship to an existing Data Request, or mark an existing Relationship as
“Required”, that relationship will
automatically be added to the Root DataBooks that use that Primary Data
Request.











eThority 6.0 Release Notes

15

|
P a g e


5

Enhanced Encryption

5.1

Enhanced Encryption Key

eThority 6.0 allows you to choose whether or not to implement an enhanced encryption key. This encryption
key would be used when
eThority is encrypting and decrypting passwords and other data inside eThority.
Once
the enhanced encryption is chosen, it can NEVER be undone.


Note:

You may choose to implement the enhanced encryption at a later date.












eThority 6.0 Release Notes

16

|
P a g e


6

DataBooks

6.1

Changes to Root DataBo
ok Dialog

When creating a new Root DataBook, the presentation of the Data Request Relationships has changed. They
are now shown as a Tree, indicating more clearly how the Data Requests are related. Also, any “Required”
Relationships are shown in red and
cannot be removed without removing the Data Request that is related.



6.2

DataBook Printing

When printing a DataBook, you now have the ability to hide or show the page footer. This is useful for printing
extremely wide DataBooks using oversize paper, as hid
ing the page footer will allow PDF printing to more
appropriately scale.













eThority 6.0 Release Notes

17

|
P a g e


6.3

DataBook Presenters

The DataBook Presenter Dialog on the Root DataBook has been expanded to assist with XSLT definition and
testing as noted below.




When you click ‘Edit
XSLT’, the XSLT editor window will appear. From this window, new buttons are available:




Example XML


Single


This will pop up a dialog containing XML for one row of data from this
DataBook. This XML can be copied for use in external tools to facilitat
e

creation of the XSLT template.



Example XML


Multi


This will pop up a dialog containing XML for up to 500 rows
of data from this
DataBook.



Test Presenter


This will perform the XSLT transformation against the current DataBook, and return
whether or no
t it succeeded.












eThority 6.0 Release Notes

18

|
P a g e


6.4

System Databooks


eThority 6.0 provides
includes a set of System Databooks designed to allow the Data Architects to monitor
system administration activity, perform system usage audits, review import history, etc.
The System Databook
section includes 27 root databooks and over 60 derived databooks available for immediate reporting.















eThority 6.0 Release Notes

19

|
P a g e


7

Maintenance Forms

7.1

All Forms

All Maintenance Forms are consistent throughout the application. Filtering the navigation grid is now always
accomplishe
d via a Quick Filter panel at the bottom of the navigation grid. The Quick Filter now maintains state
for each user on a per form basis. Each time a user returns to a form, the Quick Filter will be set to match the
state that it was in when the user last

visited the form.


The Quick Filter can easily be toggled off and on via the “Active” checkbox that now appears at the top of the
Quick Filter button. The Quick Filter is always set to “Inactive” after a record is saved, in order to reduce the
likelihood that the edited or added record would be filtered out of the navigation grid.















eThority 6.0 Release Notes

20

|
P a g e


7.2

Global Preferences

The Global Preferences form (formerly known as System Configuration) form has changed. The Login tab now
has an option for “Use Enhanced Encry
ption”. This option enhances the encryption used for data stored within
eThority. Please see the example below and the special note regarding how this action cannot be undone. See
section
Enhanced Encryption

for detai
ls.



Note:

Once chosen, this option may
NOT

be undone.













eThority 6.0 Release Notes

21

|
P a g e


7.3

License Key Update

The license update mechanism has also been updated to simplify the process of applying an eThority license in
cases where the eThority instance does not have full access to the internet. When clicking the “License” button,
the user will now be presented w
ith an option to update via the internet or file. Choosing to update via a file will
allow the user to browse to a license file on the local file system and apply that license to the eThority instance.
This allows any user with access to Global Preferenc
es and a license file to update the license. Previously, the
user needed to locate and use the
Content Core Import
tool to apply a license update when internet connectivity
was not available.














eThority 6.0 Release Notes

22

|
P a g e


7.4

Default Data Lock

Default Data Locks can now be set via th
e DataBook tab. When this option is used, the selected Data Lock is
automatically applied to all new Data Requests when they are created.

Using a Data Lock that is only granted to select Data Architects can prevent other users from accessing a Data
Requ
est after it has been saved, but while it is still being configured.

Once fully configured the default Data Lock can be removed (and others applied, if necessary) so the Data
Request will be available to the appropriate users.














eThority 6.0 Release Notes

23

|
P a g e


7.5

Data Request Maintenan
ce

In eThority 6.0, the Data Request Maintenance form contains numerous updates
--

adding functionality to the
form.


The Content Based Access Control (CBAC) Root DataBook is now defined in the General Info tab when a Data
Request is set to allow CBAC.
The Data Request CBAC was previously defined via User Maintenance.


7.5.1

Pre and Post Processors

The pre and post Import processors are stored procedures that you can run before or after an import. The return
values of the stored procedures can be nothing or a
single row of data in this format:


select

@statusCode
as

Status
,

0
as

minutes

@statusCode can be one of three values


SUCCESS = 0


FAILED = 1


POSTPONED = 2


If the returned statusCode is two (PostPoned), the minutes value indicates how long to w
ait before retrying the
import. This allows you to check on the state of another import or its condition and if necessary, postpone the
import a few minutes.













eThority 6.0 Release Notes

24

|
P a g e


7.5.2

Source Preprocessor

A Source Preprocessor Stored Procedure can now be specified from the Conne
ction Info tab for OLEDB and
ODBC connections. This is a stored procedure that is run on the source system prior to the import.















eThority 6.0 Release Notes

25

|
P a g e


7.5.3

Pre and Post Processors

The File/Query Info tab allows both a Preprocessor Stored Procedure and a Postprocessor Stored
Procedure to
be specified. These are both stored procedures that must exist on the eThority SQL Server and reside in the
database specified as the eThority Reporting database.















eThority 6.0 Release Notes

26

|
P a g e


7.6

Data Request Tabs

7.6.1

Field Info Tab

The Field Info tab has been renamed “Define Fields.” The Define Fields tab has an integrated Sample Data grid
to show the first few rows of data that will be imported. The Sample Data grid can also be hidden via the “Show
Sample Data” checkbox in order to
increase the space available for the Define Fields grid.



When the connection type is Fixed Length File, the Sample Data grid will appear in a different form
(illustrated above in the File Type section) to simplify configuration of the Data Request.















eThority 6.0 Release Notes

27

|
P a g e


7.6.2

Transform Fields tab

“Transform Fields,” is now also available in eThority 6.0. The Transform Fields tab allows PowerFields to be
applied to the Data Request (as described above). A Preview Data grid displays a sample of the results of the
selected Power
Field when applied to the Data Request. There are two types of Transform Fields: Materialized
and Transformation.



Materialized PowerFields will alter what is actually stored in eThority, whereas Materialized PowerFields
are generally defined to cleanse in
coming data for consistency.



Transformation PowerFields will alter the displayed data in eThority and are generally designed to be
used with User Keys so the displayed values can be adjusted based on the logged in user.


You should
never

use User Keys in t
he Materialized PowerFields because no user is available during the
import. Even if there were, it would mean the data is stored according to the importing user rather than the
viewing user.


Note
:
1)
Creating any Transform
PowerFields
will prevent definin
g User Keys on the same Data Request. You
can use User Keys that are defined in other Data Requests but you cannot define them on this Data Request.

2) Transform
PowerF
ields columns that represent a field that is used to define an Organization Key Value fo
r
securing a Data Request will have the stored value used in the row filtering based on the Org Stamp, not the
result of the Transformation Field. This is to prevent the core security features of eThority from being
circumvented.













eThority 6.0 Release Notes

28

|
P a g e


7.6.3

Relationships Tab

The

Relationships tab has been updated to include a “Required” checkbox. As mentioned above, marking a
Data Request relationship as required forces the inclusion of the related Data Request any time the primary
Data Request is used in a DataBook.


7.6.4

Tran Tags
Tab

The Tran Tags tab has been added to the form. This functionality continues to be available via the menu bar’s
“Tools” button, but is now more readily accessible via its own tab.


7.6.5

User Keys Tab

The User Keys tab is new and has been added to support th
e new User Key functionality (described above in
the section, User Keys). The “Assign Values” button will open the maintenance form for the selected User Key
so that the User Key Values can be easily reviewed or configured (applicable only for users with
User Key
permissions).


It is important to consider that there are two basic items to define: 1) the field in the Data Request that identifies
the logged in user (Associated Field) and 2) the fields that you want attached to the logged in user (Available
Fields).


Note
: Creating User Keys will prevent defining any Transform Fields on the same Data Request.















eThority 6.0 Release Notes

29

|
P a g e


7.6.6

Import Log Tab

The Import Log tab has been updated to provide additional information to the user. Durations for each part of
the import process
are now available. This will assist in determining the source where a Data Request may be
taking too long.


7.7

Data Conduits

The Data Conduit form has been updated to match the style of the other eThority maintenance forms. The
updates have not changed the

functionality of the form.












eThority 6.0 Release Notes

30

|
P a g e


7.8

Events

The Event form has changes in the Quick Filter. There is now an Event Queue Processing Status as a filter
type. The Status dropdown has the following values:



All

Never Queued

Creating Queue Entry

Waiting for Event
Time

Queue Entry Claimed

Queue Entry in Process

Processing Complete

Processing Failed

Not in Window

Data Request Busy

Event Deactivated

Schedule Deactivated

Live Request Deactivated

Force Failed

Event Schedule Deactivated


Please keep in mind that the Sys
tem Management Functions Service Types: AssemblyMethod, OSMethod and
TransportMethod are no longer supported. In eThority 6.0, only Service Type SQLStatement is supported. If
you have any events using the Service Types: AssemblyMethod, OSMethod or Transpo
rtMethod, the events will
be deactivated.

7.9

User Maintenance

The User Maintenance form has been updated with several functional changes as noted below.

7.9.1

Permissions Tab

Selecting or deselecting a Role no longer clears all permission Exceptions. Any permission Exceptions that
were in place prior to the Role change will now remain in effect until they are individually changed.












eThority 6.0 Release Notes

31

|
P a g e


7.9.2

User Keys Tab

A User Keys tab has been adde
d to support the new User Key functionality. This tab allows the User Key
Values to be set for the selected user.














eThority 6.0 Release Notes

32

|
P a g e


7.9.3

Exceptions Tab

PowerField Content Based Access Control (CBAC) is a new feature that allows one or more PowerFields to be
defined for eac
h Data Request on a per user basis. These PowerFields are limited to the Yes/No Data Type
and are used to determine the user’s rights to access rows of data. If multiple CBAC PowerFields are defined
for the same Data Request, all must return a “Yes” valu
e for the user to have rights to a particular record.


The current Key value CBAC feature grants or denies a single record. PowerField CBAC grants or denies
access to multiple records based on the filter criteria.














eThority 6.0 Release Notes

33

|
P a g e


7.10

User
Keys
Maintenance

The User Keys
Maintenance form allows for the creation and eThority login account value assignments.



This image shows the definition of

DR1 UK”. All eThority login accounts are listed. This allows for the editor to
maintain the values that will map between the eThor
ity login accounts and the value in the Data Requests
assign
ed

to this User Key.


The related assignment of the User Key in a Data Request will look like this.
It assign
s

the field in the Data
Request that maps to the User Key Value as well as the fields t
hat will be available when an eThority
user
sign
s

into eThority.












eThority 6.0 Release Notes

34

|
P a g e


7.11

Role
Maintenance

The Role Maintenance form now displays granted Permissions and Data Locks with a yellow highlight to further
accentuate th
e rights that the Role conveys.
Data Locks are
now maintained through Role Maintenance. This is
because data locks have no purpose or meaning outside the context of a role. There are add and edit buttons
for the data locks that are enabled as necessary. A data lock will now be deleted automatically whe
n it is
removed from a role when the data lock is not used anywhere in the system (not assigned to Data Requests,
Libraries, or other Roles, etc).


7.12

User
Group
Maintenance

The User Group Maintenance form received only one minor update. The “User” sharing
type has been renamed
“Personal” to more clearly communicate that any User Groups with this sharing type will be available only to the
user who created them.












eThority 6.0 Release Notes

35

|
P a g e


8

Administration Enhancements

8.1

System Health Check

A new form has been added to allow the system ad
ministrator to view the status if vital functions in eThority.

There are seven tabs that cover the essential indicators for eThority. Each tab has a button on the bottom that is
for obtaining the latest status. On some tabs there is a Fix button. This Fix
button will attempt to resolve the
issues that are listed.


Database checks for connectivity to the defined databases.















eThority 6.0 Release Notes

36

|
P a g e


Services displays the status for all defined services.




Cache displays the expired and invalid cache tables. The Fix button
will remove the tables.















eThority 6.0 Release Notes

37

|
P a g e


Conduit will attempt to connect to each conduit. Use this sparingly since the attempts to connect can take a
while.




XRef will check for missing XRef tables. If any are missing, you can click Fix to create them.














eThority 6.0 Release Notes

38

|
P a g e


Index
will check for missing indexes on the Data Request holding tables. If any are missing, you can click on Fix
to create them.




Import will check the status of pending imports. Imports are listed if they have been pending for more than 24
hours. If
availab
le,
click Fix to set the status
to
“Manual Completion”.














eThority 6.0 Release Notes

39

|
P a g e


8.2

Default Web Site Values

The defaults for new web site application pools are set like this.

Process Model

Idle Time
-
out (minutes) is set to 0 (zero)

Recycling

Regular Time Interval (minutes)

is se
t to 0 (zero)

Specific Times is set to 2 AM.


You may change these after the web site has been created.


Note
: This is for new web sites only. Existing web sites will not be affected.