Data Policy Engine
The LongJump data policy engine provides support for business rules that trigger actions based on specified criteria of the data. This functionality enables automation of processes around data records to consistently and intelligently enable business processes around data.
Policies can be action-based (whenever a record is added, updated, deleted, or its ownership changed) or calendar-based (scheduled to repeat based on supplied frequencies and times). These policies detect values and conditions of the data fields and based on them, execute a variety or combination of actions including: sending an email, assigning a task, updating the record content, delivering a SOAP message to an external system, or running internal Java code.
Notification Engine
Whenever a change of ownership occurs or workflows advance through states, LongJump provides the facility to notify parties via email on those updates. This ensures every interested person is updated on key information.
Validation Engine
LongJump provide data validation at the point of user data entry. Using a simple functional language similar to spreadsheet formulas, sophisticated value and Boolean type validations can be easily added to data fields to limit data input.
Calendar and Task Management
LongJump enables business teams to orchestrate their calendars and tasks and directly relate them as activities around their data records. This provides a unique dimension to LongJump data to include a historical context of what happened in relationship to this record and it enables team members' calendar events and tasks to have a context around the record. Coupled with data policies, tasks can be automatically assigned based on certain criteria triggers to drive data into an operational mode.
Web Forms
User-definable web forms provide a way to embed code into any HTML page that can be directly used to add a new record into LongJump. LongJump provides the complete code as both a single-line of JavaScript or as raw <FORM> code that users can customize to fit the theme of their site. |
|
Workflow Designer
LongJump's Workflow Designer enables data records to move across an organization to support project management, fulfillment transactions, and multi-level authorization and approval. The Workflow Designer, using a graphic layout tool, allows for the design and management of state conditions, routing of processes and sub-processes, and rules checking for data criteria. In addition, workflow progress can be easily reported on and have data policies assigned to them.
LongJump also enables email approvals via email to provide mobile users with the ability to trigger next steps on business processes.
Email Integration
Like calendars and tasks, records that have an email field can be emailed to directly and those emails are included as activities associated with a record. Email integration into the operational processes plays a pivotal role in driving additional awareness about a given record. It can often help the user adoption process for new applications.
In addition:
- LongJump also provides rich HTML template support for emails, user-definable templates with mail-merge-style variables, and open tracking.
- For users of Microsoft Outlook, LongJump offers plug-ins to synchronize contacts, tasks, and calendars, as well as mark emails as activities directly from Outlook.
- Coupled with data policies, emails can be automatically sent based on certain criteria triggers to drive data into an operational mode.
- Emails sent from other email clients can be logged as activities directly in the contact record or as tasks.
Document Control
LongJump provides document storage as a central repository for teams, as well as record-based document storage for files related to a specific record. The central document repository acts as a lightweight content management system with support for folder permissions, uploading various versions of documents, and file and image hosting without requiring an FTP or Web site.
Record-based documents allow for file storage in regards to specific records for safe keeping. For example, businesses may wish to keep a customer's logo files or the warranty information of an asset with the actual data record.
|
