In a mature Salesforce Org with hundreds of thousands of records, it might be difficult to know where to start on GDPR compliance. In this post, we’ll cover the steps you need to take to get your Salesforce Org GDPR compliant.
Last week, in response to an increasing number of questions from our NetSuite customers, we showed you how to manage scripts that execute in the Administrator role. One thing it didn’t cover, however, was workflows that execute as Administrator. The process for resolving this with Netwrix Strongpoint or Flashlight is similar — but there are some additional considerations that merit discussion in this post, particularly if you want to avoid material deficiencies on audit.
As your business grows, so will your Org. And while a highly customized Salesforce Org reflects a booming business, there’s a critical difference between necessary complexity and technical debt. In the spirit of spring cleaning, we wanted to share two strategies for reducing technical debt: Salesforce data cleansing, and cleaning up unnecessary customizations and metadata in your Org. Both go hand-in-hand in improving usability and adoption.
As you work in NetSuite and evolve your account over time, you’re going to accumulate some baggage. Typically, this baggage will come in two forms: ‘dirty’ data housed in the system, and obsolete metadata (system customizations), aka technical debt. Though these are two separate issues, they’re closely related — getting rid of technical debt will make your NetSuite account easier to use, which will improve the overall quality of the data within it.
Artificial Intelligence (AI) and machine learning have become integral tools for organizations across various industries. However, the successful adoption of these technologies requires a careful balance between business objectives and security requirements.
