Announcing 

Strongpoint is excited to announce some powerful new features and enhancements in our latest product release, Version 5.4. Thanks to our active and knowledgeable user community for their suggestions and guidance.  To book a session to implement any new capabilities, please contact your account manager or email us at support@strongpoint.io

Thank you very much to our extremely active, and knowledgeable, user community for their suggestions and guidance, allowing us to create incredible value in this release.

Pre-Release

Version 5.4 is now available in your sandbox for pre-release. Since we cannot push updates to your sandboxes, please update the Strongpoint bundle in your sandboxes to ensure you are using the latest version in all accounts.

Full Release

Starting August 17, we will be pushing the 5.4 upgrade to your production account during off-peak hours.

Managed Customers

If you are a customer with a managed upgrade process, we will contact you to schedule the upgrade to your production account, per the process defined with you.

If you are not a Managed Customer and would like to know more - reach out!  We’d be happy to work out the details with you.

New Functionality

Feature

Clean-Up

Audience

Administrators

Overview

Many NetSuite customers have hundreds if not thousands of unused searches that clutter up their account.  Unused searches damage productivity and make it difficult to find authoritative searches causing users to recreate them over and over again. However, cleaning up that many searches on an ongoing basis was impossible, until now.  Strongpoint’s Automated Search Cleanup Tool:

• Identifies searches to be cleaned up based on customizable rules (i.e. date last used, who uses them, words in the name, inactive owners etc).  Strongpoint automatically excludes sensitive searches such as searches used in scripts or workflows.

• You can run it manually or have it run continuously

• Customizable emails are sent to search owners and users giving them the option of retaining the searches

• Any searches not flagged to be retained are automatically archived

• Archived searches can be restored if required

Automated Search Clean Up User Guide

Opportunistic Clearance (Beta)

Product Area

Intelligent Change Management

Feature

Change Clearance

Audience

Auditors, Administrators

Overview

Reviewing and clearing non-compliant changes is a critical step in ensuring that no high risk changes are happening to your account without proper approval.  However, there can be accidental non-compliant changes on that list if someone forgot to put a customization on the Change Request.

We are adding more “intelligence” to our Intelligent Change Management so the system can evaluate and clear changes more intelligently.  This will reduce the set of non-compliant changes, which will reduce the amount of time required to review changes.

• If a change to an object results in a change to another object that wasn’t approved in the Change Request, Strongpoint will automatically do an impact analysis.

• After the impact analysis, if that object is deemed to be a safe change, Strongpoint automatically clears it and attaches it to that Change Request. The fact that it was cleared by the system is documented on the Change Log for clear auditability.  Otherwise a Non-compliant Change is logged.

• Examples of changes would be:

  • changes to a script deployment associated with an authorized script change,

  • adding authorized scripting to a field that did not previously have any scripting, or

  • changing a custom record or form by adding a field

• Examples of changes that would not be approved are:

  • adding scripting to a previously scripted field

  • removing a field from a record

  • any change associated with a specific policy such as a tighter Financial records policy

Opportunistic Clearance User Guide

Enhancements

Customization Record Simplification

Overview

We very excited to streamline the Customization Record so you can find what you need faster.  

• All dependencies are clearly displayed in on place

• The number of tabs have been reduced

• Only the fields relevant to the customization type appear

• A ERD tab enables you to drill through dependencies without leaving the customization record for faster analysis

Customization Record User Guide

Segregation of Duties (SoD)

Product Area

Enterprise Compliance

Feature

Segregations of Duties (SoD)

Audience

Auditors, Administrators

Overview

Several improvements have been made to the Segregation of Duties Change Request process. The release includes the following features:

• Improved SoD violation messages with option to create a change request right from the pop up message box saving clicks to get it approved.

• User friendly step-by-step assistance on a streamlined Change Request form that will save significant time for users requesting SoD related changes.

• Auto route of the Change Request to approvers based on policy or select additional approvers on the Change Request, which will save time and effort in creating a Change Request.

• Approver/s will receive an email alert and be able to preview the roles and permissions requested to be assigned prior to approve of a change request. This allows an approver to get insight into what exactly they are approving.

Segregation of Duties User Guide

Date Last Used (DLU)

Overview

Strongpoint now uses System Notes search to retrieve the date last used for Fields, saved Searches and records for increased accuracy.  We have also added a “Last Used Status Field” to provide a description of the status of the DLU analysis.

Date Last Used User Guide

ERD Filters

The ERD is one our most popular tools.  We have added filters to enable users to see a focused ERD and reduce the time required to find objects. Field Name and Date Last Used filters were added in the ERD. These optional filters are helpful when the Record Type has many fields.

ERD User Guide

Changed By Field Status Updates

Product Area

Intelligent Change Management

Feature

Change Clearance

Audience

Auditors, Administrators

We added two new values in the Changed By field so users can clearly understand relevant information.  There are now three possible values of Change By:

• User ID:  The user who made the change

• Pending Autospider:  New - This value will be in the Changed By field when the Autospider still needs to run to determine the User ID

• Could Not be Determined: New - This value will be in the Changed By field when the User cannot be determined since there are no System Notes or History Notes for that object type.

Changed By User Guide

Coming Soon

We are actively working on our next release. Exciting, new functionality is on the way to deliver best in class service! Here is a sneak peak at what you can look expect:

• GDPR Privacy Pack

• Service Now Integration (Beta Stage)

• Change Request Simplification