A self-service database can help you eliminate silos.
Most user-developed solutions are at the mercy of their underlying data sources. The data layer makes “businessperson-friendly” data sources and related services available. The data layer simplifies the interface to keep users from getting in over their heads. It is critical for the success of process management.
Making data easily available to users will make them much less likely to access data sources in ways that are less secure and less accurate.
The data layer brings together, in a single repository, the information needed to build cross-functional solutions. The database reflects the entire extended organization, rather a particular application. It is the anti-silo.
Database management requires no technical skills, is automatically tuned and optimized, and is highly scalable. There is no low-level management such as patching, backups, or configuration. Reliable and secure, the database is constantly monitored and administered by dedicated professionals whose only job is to manage the database. Databases are instantly available to anyone who needs them with just a few mouse clicks; there’s no waiting to provision databases.
Data security rules are isolated and managed independently from the rest of application business logic. This eliminates the need for applications to have to code, test, and maintain their own complicated security logic. Database sharing rules can be defined by user, profile, role, group, and record level. This protects against inadvertently giving the wrong person access to data.
Organizational hierarchy is built into the database. This allows access privileges to be set at different levels of the organization; e.g., a manager can automatically have access to the records of their team members. Yet another complication the solution builder doesn’t have to worry about.
New systems can be brought online quickly, because being enabled by Salesforce App Cloud eliminates the steps to acquire, install, and maintain software, and provides immediate access to accurate and complete data in a single location, obviating the need to build new interfaces or cleanse data, or waste effort due to incomplete information or looking for information.
The trick…is to introduce bits of automation that will fit into the work and do useful things, and then make it possible for people to work with those bits of automation embedded in the systems while leaving them the discretionary space to exercise the kind of judgment they need to exercise to really get the work done.
– Derek Miers – Process Innovation and Corporate Agility (2007)
Start defining your workflow automation steps today!
A step is a unit of work; it identifies an activity or task(s) that needs to be done before the flow can move forward. Steps are explicitly defined and operationally independent units of functionality. Each flow consists of multiple steps, and a single step can be in multiple flows.
Workflow automation steps are a complete unit of work
Workflow automation steps are not executed until its pre-conditions are met, and is not completed until it satisfies the rules for completion.