If I were to grant three wishes to a customer on what he would like to have in ERP, 8
out 10 customers would respond with the following choices
1.Automation at the “click” of a button
2.Easy of use of reporting
3.Email alerts

Let’s dwell a little on why the customer would want these options

1.Automation

  • Less user intervention means lesser error
  • Faster throughputs times
  • Better time management to do other activities
  • However less customization

2.Reporting

  • Ease of use or modification of views
  • Easier to the builder (anyone can do it)
  • Don’t need to depend on others

3.Email alerts

  • Reminder on tasks to be done
  • Reminders on approvals
  • Real-time data transfer

Looking at this from a legacy on-premise ERP point would have the cash cow ringing all the way to the bank to the system integrators

Automation would mean huge customization would have to been in place to satisfy the customer demands and let’s not forget maintenance of those customizations for years and years to come

Report Customization of each report would again be charged back to the customer

Email alerts – Customising the system with integration to the legacy ERP to outlook or lotus notes

A decade ago, when computer systems had limited computing power and were built to automate a smaller set of tasks. Back in the day with limited memory, storage and CPU cycles available, functions were broken up into pieces to automate. Today, we have virtually unlimited resources on the cloud, so why limit ourselves to these old concepts?

The speed and responsiveness in which businesses need to compete for demand a more unified approach. Processes that traverse departments and functions need to be 100% automated and synchronized in real-time. There isn’t room for error, manual processes or time delays. Yet many companies have a very big gap between selling, production and fulfillment systems that slow the business down, adding friction and cost along the way. This can be more acute if your business is trying to personalize products and each order is unique. Quite simply, your business will run faster with CRM and ERP on one cloud.

Unlock ERP Information for Real Intelligence

Einstein Analytics and AI have cutting-edge capabilities, but without ERP data, they can’t provide comprehensive business insight. Issues around data fragmentation, master file data management, data latency, and data normalization have long been the cause of stress in many BI projects, and these issues are still “alive and kicking” when ERP and CRM are kept separate. Combining them on the Salesforce Platform using one data model goes a long way toward fixing these annoying data problems. It makes it easier for Einstein to triangulate information across front and back-office functions for things like demand planning and predictive customer behavior analysis. These factors are nearly impossible to correlate when CRM and ERP data is disconnected.

The following things can be improved using automation

Quote turnaround time » Lead time » On-time delivery » Time to respond » Time to reschedule customer orders » First call resolution » New product roll-out » Process changes » Period close » Time to train employees

Now let us drill down further into the details of automation available on the Salesforce platform which is leveraging the Rootstock from other ERP’s.

Salesforce Flow gives you the ability to create a visual representation of a business process. Then, this can be used to drastically reduce the amount of time spent getting information into Salesforce.

Earlier when you required a custom feature in your Salesforce installation to support your business process, the only available options were to create a brand new app and integrate it in your Salesforce or to use existing features in a creative way to achieve the same objective. However, Salesforce evolved, and we now have got Salesforce Flow.

Visual flow can be summed up as an app inside the Salesforce app. Analogically, what methods are to object-oriented programming, visual flow is to Salesforce. To be more precise, a Flow is a wizard or a set of screens in sequential order which can be used to complete a business process. This business process can be anything like filling out a form, or working on a script or even filling out a survey. The Flow has the ability to fetch, edit, and create all Salesforce information in an appealing, quick and smart manner.

Flows can be used to execute business logic, interact with Salesforce Databases, call defined Apex classes and guide the user through screens. There are three main aspects of a Flow in Automation:

Designing: The main reason they are called Visual Workflows is that Flows come with a drag-and-drop interface Flow designer and can be used to diagram a Flow, configure how the Flow executes, and define what it affects- all this without writing a single line of code.

Management: You can manage your created Flow through the setup area. Through this, you can edit your Flow’s properties, activate it, deactivate it, delete your Flow or even trigger it at your will.

Flow Runtime: Once Flows are defined, users can run the Flow through any user call-to-action like a button, tab, link, or even directly from the Flow URL. You can also trigger Flows through an Apex class or a Flow trigger workflow action.

By this, we can clearly know that the Visual Workflow interface is drag and drop. As a result, it’s easy to create a process using the Clicks – not Code process.  Every flow is embeddable and supports custom tabs, Visual Force pages, and Salesforce Sites. Even better, Visual Workflow can create records, look-up to and/or edit existing records, and even delete records.

The key advantage of this Visual Workflow is that it does not require coding, and even if you do not know Apex code, you can still develop business processes.

Listed below are the few things we can achieve using the Visual Flows.

  • It allows you to auto-submit records for approval.
  • It allows you to apply assignment rules on leads or cases that are created by API calls.
  • You can post messages/alerts on Chatter. For example, if the Opportunity status is changed to Closed-Won, post a message on the Chatter group.
  • Once you embed your Flow into the Visualforce page, it allows you to use HTML, CSS, JavaScript, and other Visualforce components.
  • It can be easily maintained by non-developers.
  • Since it is not code, you don’t need to write test classes.
  • You can make changes directly to your production organization, just like other configuration changes.
  • And many more…………

In a data-driven age, modern organizations need access to advanced data analytics solutions to help them improve the business in a wealth of key areas—Salesforce is one of those solutions. And the world knows how good and great the Salesforce Reporting Tools with its Rich Dashboards, Live monitoring of the reports with customized Visual representation’s

  1. Draws the eye to the key information.
  2. Present information in a structured way.
  3. Can Remove clutter that distracts from the main message.
  4. Group data into meaningful time periods.

With all these advantages Rootstock completely stands out when compared to the other ERP by helping the end-user being self-dependent.