{"id":44258,"date":"2019-02-04T14:51:26","date_gmt":"2019-02-04T06:51:26","guid":{"rendered":"http:\/\/localhost\/help\/?page_id=44258"},"modified":"2026-08-23T17:12:26","modified_gmt":"2026-08-23T09:12:26","slug":"sentinel-release-4-6-2","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/sentinel\/sentinel-releases\/sentinel-release-4-6-2\/","title":{"rendered":"Sentinel Release 4.6.2"},"content":{"rendered":"\n

\"\"<\/a><\/p>\n

P2 Sentinel 4.6 introduces compatibility with P2 Explorer 4.6 and later.\u00a0\u00a0<\/p>\n

This release incorporates Explorer's security framework into the core Sentinel product, allowing better integration between the two applications. It also moves the Case Management web interface into Explorer, which allows for easier management of cases via an improved web experience.<\/p>\n

P2 Sentinel version 4.6.2 is a patch release, which adds further options for handling suppressed events, and begins to move Sentinel's documentation into the Explorer Help Center.<\/p>\n

\n

Compatibility with P2 Explorer<\/h2>\n

P2 Sentinel is now compatible with P2 Explorer 4.6.5.<\/p>\n

\n

BadDataSuppressionBehavior Setting<\/h2>\n

This new configuration option allows a way to control whether Bad Data Suppressions are raised or not. Options are: Suppress<\/strong> or None<\/strong>. This is useful in conjunction with the NullDatumBehavior<\/strong> option as a way to ignore Null data points.<\/p>\n

\n

Hide Suppressed Events Option<\/h2>\n

There is a new \u2018Hide Suppressed\u2019 option in the Event Viewer. This option can help reduce the total amount of events loaded and can, in some instances, lower the time to load the events.<\/p>\n

\n

Changes to Help Documentation<\/h2>\n

Help links in the software now point to the Sentinel section of the Explorer Help Center, from which documentation can now be accessed.<\/p>\n

https:\/\/oihelp.corporate.ifs.com\/help\/sentinel<\/a><\/p>\n

The P2 Sentinel Studio User\u2019s Guide has been transitioned to online documentation only.<\/p>\n

\n

400 Character Limit removed from Case Title and Description<\/h2>\n

It is now possible to use more than 400 characters for Case Titles and Descriptions.<\/p>\n

\n

Security<\/h2>\n

In P2 Sentinel versions 4.1.5 and earlier, security privileges were defined in the SentinelConfig.xml file, with default roles allocated to them. Roles and users were managed from within the compatible version of P2 Security (P2 Security versions 4.1.9 and earlier).<\/p>\n

In Sentinel 4.6, security privileges are defined in P2 Explorer\u2019s Security module.<\/p>\n

Read more: Security<\/a><\/p>\n

In Explorer\u2019s Security user interface, you can create and manage roles, allocate privileges to them, and then associate roles with users, thereby controlling what users can do in Sentinel.<\/p>\n

This method of managing Security is more accessible (a user with the Security Admin privilege can maintain this at any time), as well as more flexible, with the ability to associate various combinations of privilege with the different roles.<\/p>\n

Sentinel\u2019s Privileges in Security<\/h3>\n

Sentinel\u2019s privileges in Security are allocated at two levels: the Module<\/strong> privilege, Sentinel Admin, which cascades into all the Sentinel privileges (giving full access to Sentinel), and the Sentinel<\/strong> Resource<\/strong> privileges, which limit roles to specific areas of functionality within Sentinel.<\/p>\n

To configure Sentinel\u2019s security (roles and which privileges are assigned to these, and users), you require a role that has the Security<\/strong> Admin<\/strong> privilege. Details for configuring roles, users, and for allocating privileges within Security are located in separate online help topics in the Security menu of the P2 Explorer Help Center: https:\/\/oihelp.corporate.ifs.com\/help\/p2-server\/<\/a>.<\/p>\n

The Security Admin role, required for administering security functions:<\/p>\n

<\/p>\n

Module privileges in Security; here the Sentinel Admin privilege has been allocated to a role:<\/p>\n

<\/p>\n

Resource privileges for Sentinel; the Sentinel Admin privilege cascades to all Sentinel privileges, for a role:<\/p>\n

<\/p>\n

Resource privileges for a role that doesn\u2019t have the Sentinel Admin privilege; here, different combinations of privileges can be set:<\/p>\n

<\/p>\n

For administering security for Sentinel users, see details in the Sentinel Installation and Administration Guide<\/em>.<\/p>\n

Privileges Assigned in the Sentinel Application<\/h3>\n

Some privileges can still be allocated at the workspace level: \u2018Security Roles\u2019 and \u2018Approvers\u2019.<\/p>\n

For example, if you want a role to have Workspaces View privileges or Workspaces Approver privileges for some of the workspaces only, you can switch this privilege off at the Resource privilege level for that role, and apply the privileges within individual workspaces. Details can be found in the Managing Workspaces<\/strong> section, in the P2 Sentinel User\u2019s Guide.<\/p>\n

\n

Case Management<\/h2>\n

Cases are still raised from within P2 Sentinel (if Case Management is enabled in the Sentinel configuration file), but they are now viewed and edited from P2 Explorer, instead of the P2 Case Viewer.<\/p>\n

This change builds on the existing relationship between P2 Sentinel and P2 Explorer, and Cases now benefit from the many features of the P2 Explorer framework.<\/p>\n

Read more: Case Management<\/a><\/p>\n

New Case Options<\/h3>\n

There are two additional case options: Case<\/strong> Title<\/strong> and Case<\/strong> Description<\/strong>. As with the other case options, a default is available and configurable in the Sentinel Configuration file. Both of these fields can be edited for a particular Test, if required, and both of them can include tokens.<\/p>\n

<\/p>\n

Case URLs<\/h3>\n

The URL command for opening a case in P2 Explorer is:<\/p>\n

https:\/\/[server name]\/ P2.Explorer\/cases\/[CaseId]<\/strong> where [server name] is the name of the Explorer Server and [CaseId] is the case\u2019s ID.<\/p>\n

This is a change from the previous URL, which was:<\/p>\n