DEVX-func.png

DEVX-pricing.png

 

Ostendo Update Notes from August 2013

There are 4 significant areas either added or updated that merit further explanation. 

  • Operations Centre: This new screen is one of the most useful and functionally rich screens within Ostendo. In essence it pulls together activities from across the system, and primarily allows for the Customer or Supplier to become the centre of the universe.
  • Call Centre: We have enhanced this screen to allow for multiple actions per ticket, linked Styles, Pipelines, Graphical Timeline view, Linked History Notes and Tracking Codes.
  • Email Services: This new module allows for automatic emailing of reminders, ticket actions, follow-ups and Sales Delivery confirmations; the ability to request information via emails from employees in the field; send files (like photos) and notes back, to automatically link to orders and tickets; and request and process spreadsheets for remote data collection (i.e. Service Sheets &Sales Quotes).
  • Customised Data Entry Screens & Remote Synchronisation: We have significantly enhanced the built-in Edit View designer to allow for drag & drop forms design. This is invaluable when building simple forms that are laid out in a manner that looks like a paper based form, but allows for interaction with the database. Remote offline data entry for where such things as Jobs and Sales Orders can be captured and then synchronised back to head-office (using this and our built-in synchronisation routines).                       

Operations Centre Overview

aug-update01.jpg

The Operations Centre (found in the CRM module) is a new screen designed to pull together activities and emails that have occurred within Ostendo or emails that have been assigned to Customers, Suppliers or activities via the email add-in (forwarded or BCCed) . Think of the Operations Centre as an Operational Portal to business information, Key Performance Indicators and Statistics.

The idea behind this new screen was to allow the user to view activities, based on the premise that an entity or module was the centre of the universe, in other words, if I was dealing with a Customer I would want to know everything about that Customer, and be able to transact their common requests or actions.  We also considered that it was important to understand the key measures and statistics that pertained to what was being looked at. 

Options Available in the Operations Centre

The main Operations Centre screen is divided into 3 major panels:

Conditions & New Activities Bars

aug-update02.jpg

New Activities Toolbar: The first toolbar provides the ability to create new activities based on the Type that has been selected in the Type dropdown (Customer, Supplier, Customer Asset, Manufacturing, Sales, Jobs, Purchasing, Un-Assigned Emails and To Do). As an example, if you’d selected ‘Customer’ you’d be able to such activities as: (Sales Orders, Job Orders, Emails, Call Tickets, Payments etc...) 

Conditions Toolbar: The second toolbar provides the ability to condition what appears in the Activity List and Preview panels. The options are:

  1. Type: This is a dropdown of (Customer, Supplier, Customer Asset, Manufacturing, Sales, Jobs, Purchasing, Un-Assigned Emails and To Do) and sets the primary focus (Centre of the Universe) of the screen.
  2. Name: This is either a lookup (Customer, Supplier, Customer Asset) or a status dropdown (‘Exclude Closed and Updated’ or ‘All Status’).
  3. Display Pending Events: This checkbox allows the users to include pending activities (like pending Purchase Orders and Assembly Orders) when returning the activity list results.
  4. Site: This checkbox and lookup allows the results to be conditioned for a specific company site
  5. Date From: This allows the conditioning of the results for a specific date range (there is a default number of days to look back in the ‘CRM-Settings-OC Rules’ screen 
  6. Date To: This allows the conditioning of the results for a specific date range (the default is the current date) 
  7. Mode: This allows for 3 types of mode (Activity, Relationship & Search). An explanation of each is as follows:
    1. Activity: This is the default mode, and when set, pulls back all activities for the Type selected (i.e. Where Type = ‘Customer’ an example of the activities pulled back would be: Sales Quotes, Sales Orders, Sales Invoices, Customer Payments, Customer Emails, Customer Notes, Customer Tickets etc...). These Activity Types are defined in the ‘CRM-Settings-OC Activities’ screen, therefore, you are able to add your own (where you have defined a user defined table / solution), or you are able to modify the standard Activity Type SQL to suit a specific company requirement. 
    2. Relationship: This mode allows you to select a type of Activity (i.e. Sales Invoice) and it’s ID (i.e. Invoice Number), and return all other related activities (i.e. For a Sales Invoice the related activities would be: Sales Orders, Job Orders, Customer Deposits, Customer Payments, Emails, Notes, Sales Deliveries, Call Tickets). These Relationships are defined in the ‘CRM-Settings-OC Relations’ screen, therefore, you are able to add your own (where you have defined a user defined table / solution), or you are able to modify the standard Relationship SQL to suit a specific company requirement. Note: While in the Activity List you are able to right click on a specific activity and select ‘Show Relationship’, this will then automatically set the mode to ‘Relationship’ and the ID from the highlighted activity.  
    3. Search: This mode allows you to search through either all activities (or a specific type) for a series of characters or phrase. The search checks for descriptive, note, reference, order number, and code fields for that sequence of characters anywhere in those fields. This is useful for finding correspondence that might contain say a Project name (searches email bodies, history notes, linked document notes etc...). The fields that are searched are defined in the ‘CRM-Settings-OC Search’ screen, therefore, you are able to add your own fields to suit a specific company requirement.       

Types

Activity Panel

aug-update03.jpg

List Tab: The Activity List is the hub of the screen, and displays the activities determined via the Conditions Toolbar. Each Activity can optionally be colour coded to make for ease of recognition (set in the CRM-Settings-OC Activities screen). There are 14 columns in the list which display key information about the activity (i.e. Date, ID, Status, Style, Value, Balance, Due Date, etc...). The actual value linked to that column will depend on the Activity Type. Under each Activity Type record there is a description (in Blue Italics) which provides for more information about that activity and what it might relate to.

Priority Notes Toolbar: You’ll notice in the above screen shot, that there is a toolbar displaying a Red Alarm clock icon, with the caption ‘IMPORTANT:’ just to the right of it. This will only display if there are priority notes flagged against the Type selected. Against History Notes you are now able to flag the note as priority (this can also be done via the right click menu when you’re on a note). This priority note feature is designed for where there might be something important to remember next time say you’re talking to a customer or supplier.    

aug-update04.jpg

Filter Condition Bar: Like used elsewhere in the system you’re able to define conditions and link them to a button that in toolbar at the top of the Activity List, enabling a user to narrow down what appears. This is ideal for presenting information based on different roles in an organisation (i.e. as a credit controller you may wish to only see only outstanding invoices, unapplied payments, unapplied deposits, and any notes or emails for each invoice – this is actually one of the standard filter buttons for Customers).   

aug-update05.jpg

Balance Bar: This only displays if the Type = ‘Customer’ and shows the Outstanding customers balance, any unapplied payments or deposits, and the outstanding balances aged according to the aging period definition in the ‘File-Financial Configuration-Aging Periods’. Each of the captions to the left of the values can be clicked on/off which then filters the Activity List displaying only transactions that relate to that period (i.e. you may wish to view only invoices that are more than 60 days). At the end of the Balance Bar there is a button ‘Statements’ that, when clicked on will generate a Customer Statement for Customer currently selected. 

 Please Note: The date range in the Conditions panel will be adjusted if necessary to display the outstanding invoices, payments or deposits     

aug-update06.jpg

Right Click Menu (from with the Activity List):  This menu displays after right clicking on the Activity List (the ‘Set Priority to True / False’ is only available when on a Note). Actions are as follows:

  1. Show Relationship: This will then automatically set the Mode (in Conditions Panel) to ‘Relationship’ and the ID from the highlighted activity, so that all activities related to the activity you’re on are displayed.
  2. Set to Activity Mode:  This sets the Mode (in Conditions Panel) to Activity and displays all activities for the other conditions specified.
  3. Go Back: This goes back to the previous conditional settings (like Back with a web browser).
  4. Create Note: Automatically creates a History Note based on the activity you’ve currently selected. 
  5. Create Internal Email: This creates an email passing the Activity Type and ID to the subject of the email and setting the email address based on the default held against the Activity Type (CRM-Settings-OC Activities).
  6. Create External Email: This creates an email passing the Activity Type and ID to the subject of the email and popping a selection screen for the email addresses held against the Customer and or Supplier and their contacts.
  7. Create Ticket: This creates a Call Ticket passing the Customer or Supplier and also the Activity Type to the Relates to option in the Call Ticket (if that Activity Type is available in the Relates To dropdown).

aug-update07.jpg

KPI Tab: This tab displays Key Performance Indicators (KPI’s) that pertain to the Type and name selected in the Conditions Panel. In other words if you’ve selected a Customer, then the KPI’s will relate to that customer. You’ll notice there is a drill down grid to the right of the main KPI grid, this displays information that makes up that KPI value. The definition of these KPI’s can be found in the CRM-Settings-OC KPIS screen. KPI percentages can also be colour coded based on their value (is defined in the ‘CRM-Settings-OC KPI Indicators’ screen).

Statistics Tab: This tab displays Statistics that pertain to the Type and name selected in the Conditions Panel. In other words if you’ve selected a Customer, then the Statistics will relate to that customer. There is optionally a drill down grid to the right of the main Statistic grid (depend on whether it has been defined), this displays information that makes up that Statistic value. The definition of these Statistics can be found in the CRM-Settings-OC Statistics screen.

Info Tab: This tab displays general information about the Type and name selected in the Conditions Panel. In other words if you’ve selected a Customer then you may wish to display address and contact details. The definition of this is in the CRM-Settings-OC Rules screen.

Preview Panel

aug-update08.jpg

This panel dispalys theat least 2 of the following tabs (dependant on the Activity Type selected):

  1. Inquiry: This displays a standard inquiry for that Activity Type (as defined in the CRM-Settings-OC Preview screen).  Not applicable to Emails, Notes and Linked Documents
  2. Report:  This displays a standard report preview for that Activity Type (as defined in the CRM-Settings-OC Preview screen).  Not applicable to Emails, Notes and Linked Documents
  3. Email: This displays the HTML representation of the linked email (along with attachments, embedded images and web links). This is only applicable to emails.
  4. Note:  This displays the notes and header information of the History Note. This is only applicable to History Notes.
  5. Document: This displays the document notes and header information of the Linked Document (you’re able to display the linked document by clicking on the embedded document path). This is only applicable to Linked Documents that have been flagged as Correspondence.
  6. Contacts: This displays all contacts for either the Customer or Supplier. The tab will not display if the company has no contacts defined. You are able to right click and email that contact directly.
  7. Assets: This only displays for Customers with Customer Assets defined. You are able to right click on a specific asset within the grid, and then by selecting the ‘Show Relationship’, the main Type in the Conditions Toolbar will be set to ‘Customer Asset’ the Name will be pre-filled with asset name and the Activity List will now display any related activities for that asset.
  8. History: This displays for Customers and Suppliers, and list a ranked history of all products and services (either sold or purchased) for the period as defined in the CRM-Settings-OC Rules ‘Invoiced History Days Back’ field. There are also columns that indicate the average discount per product and whether that product or service is in growth or decline (compares to the previous period – i.e. For 365 Days the comparison would be for the previous 365 Days).
    aug-update09.jpg
  9. Pricing: This only displays for Customers, and lists all Price Levels, Special Pricing, Discounting and Order Pricing Rules that apply for the current date, and into the future. 
  10. Timeline: This only displays when the Activity is linked to a Call Ticket. A Timeline view of the Actions/Stages is shown, giving a graphical representation of status of that Ticket. 
    aug-update10.jpg
  11. About: This is a graphical file (edited through the Ostendo Graphical Editor) that can used as a graphical help (or just to display the Ostendo Client’s logo)

To Do

This is one of the Types available in the Conditions panel and displays any Calendar Reminders, History Note Follow-ups, Outstanding Ticket Actions and Quote Follow-ups that relate to the user logged into the Ostendo. Where there is an Employee linked to the event (i.e. Ticket Actions), the ‘Default User for Reminders’ held against that Employee is used for this display.

aug-update11.jpg

Right Click Menu (from with the Activity List when in ‘To Do’):  This menu displays after right clicking on the Activity List. The primary option for ‘To Do’ activities is ‘Update to Actioned’ – this flags the Calendar Reminder, History Note Follow-up, Quote Follow-up or Ticket Action has being completed.    

Outlook Add-In

aug-update12.jpg

We have developed a Microsoft Outlook add-in that will allow the user from with Outlook Assign and Un-Assign emails to one of the following (The add-in will attempt to automatically assign based on the senders address, but you’ll still be required to click on the assign option) :

  1. Customer
  2. Supplier
  3. Sales Invoice
  4. Sales Order
  5. Job Order
  6. Customer Payment
  7. Customer Deposit
  8. Purchase Order
  9. Purchase Invoice 
  10. Purchase Shipment
  11. POS
  12. Call Ticket
  13. New Customer Ticket (this generates a Call Ticket and links the email to that Ticket)
  14. New Supplier Ticket (this generates a Call Ticket and links the email to that Ticket)

For this functionality to work you’ll need Ostendo Web Services running and have downloaded the Web Services script called ‘outlookdata’ via the ‘Download Online Template’.  Please make sure you have the latest version for this new version (use the ‘Check for an Update of this Template’ in the Script Editor)

Installing the Add-In

Please Note: This has changed from the previous install - To install the MS Outlook Add-In we have provided a simple installation executable (called ‘OutlookAddIn.exe’ – which can be found in the Ostendo directory). This, will both Install, and Un-install the Outlook Add-in. 

There is also an INI file called ‘ostoladdin.ini’ which is installed and will need to be configured. You are able to specify the IP address for your web server, the directory for linked attachments and embedded images, and the number of characters you type before the search dropdown list is activated in the outlook add-in (narrows down the records in the list).

A generic script (where Outlook is not the email client e.g. GMail) will also be supplied for the commercial release which will allow emails to be forwarded or BCCed to a predefined email address where the queue service will then automatically bring them into Ostendo (attempting to auto assign based on the sender address).

User Security

aug-update13.jpg

You’re able to exclude Activity Types, KPI’s Statistics and Activity Descriptions in the ‘Operations Centre Exclusions’ within the ‘System Configuration-User Security & Options’ screen.  Like the standard user security, you are able to inherit these rights if the user has been setup to Inherit Security from another user. 

Call Centre Overview 

The Call Centre (found in the CRM module) has been revised to allow for multiple actions per ticket, linked Styles, Pipelines, Graphical Timeline view, Linked History Notes and Tracking Codes. 

aug-update14.jpg

Call Style

The Call Style determines the style of Ticket (i.e. Opportunity, Customer Claim, Capital Approval, etc...). Against the Call Style (CRM-Settings-Call Styles) you’re able to define the following:

  1. Whether the Ticket Actions are modifiable – in other words, can you add or delete actions.
  2. The default Pipeline linked to this Style. The Pipeline is setup independently and is effectively a template of stages and actions (see CRM-Settings-Pipelines, CRM-Settings-Pipeline Stages and CRM-Settings-Pipeline Actions)
  3. Whether this Style is a Sales Opportunity (for reporting purposes)
  4. Whether this Style is an Order Approval (for reporting purposes)
  5. The following fields can be activated for reporting purposes (if any are activated they will appear in a tab within the Ticket based on the name of the Style):
    • Expected Revenue
    • Expected Costs
    • Probability %
    • Completion %
    • Employee Responsible
    • Strengths (Notes Field)
    • Weaknesses (Notes Field)
    • Risks (Notes Field)
    • Benefits (Notes Field)
    • Competition (Notes Field)

Action Information

aug-update15.jpg

We have now added the ability to include multiple actions for a single Ticket. Each action can have the following fields:

  • Stage Seq: This defines the sequence for that stage within the actions for that Ticket (defaults from the Pipeline – if used)
  • Stage: This the Stage linked to the action (must exist in CRM-Settings-Pipeline Stages)
  • Action Seq: This defines the sequence of the action with that stage
  • Action Description: This is a description of the action to be carried out 
  • Assigned To: This is the Employee assigned to this action
  • CC To: This is the Employee that needs to be copied to for this action
  • Required Date: The Required Date for this action (is automatically set if the action was created from a pipeline – based on days after the Ticket creation date)
  • Action History: Notes about that action
  • Complete: A checkbox to indicate whether the action has been completed (this can be done from within the Ticket, via the To Do list in the Operations Centre, or via an email response to an emailed action – see Email Services for more information on this)
  • Sign Off Date: This is the date the action was completed (is normally automatically set)
  • Signed Off By: This is the Employee that completed the action  
  • Emailed: Indicates whether the action has been emailed to the assigned employee
  • Auto Email: This is either automatically set (from a Pipeline) or can be manually set, and, assuming that Auto Emailing has been activated, will email the employee (using their employee email) – see Email Services for more information on Auto Emailing. You’re also able to right click and manually email the action.
  • Auto Email Lead time: This determines the number of days before the action is due that the email will be automatically emailed to the Employee (assuming that Auto Emailing is running)    

Timeline

aug-update16.jpg

This displays a graphical view of the Stages (Milestones), Actions and Ticket Required Date. You’ll notice that the Stages and Ticket Required Date is above the Timeline, and the individual Actions are below the Timeline. Each Stage can be colour coded (CRM-Settings-Pipeline Stages) and Actions that are linked to that Stage have a colour coded triangular indicator. 

If an Action is completed there is a checkbox that displays just to the left of the Action Description – see image: 
aug-update17.jpg

Email Services Overview

aug-update18.jpg

Email Services is an exciting new part of the Ostendo Framework that allows for the following:

  • Automatically emailing out Ticket Actions, System Alerts, Calendar Reminders, Sales & Job Quote Follow ups and History Note Follow ups
  • Automatically receiving correspondence emails and auto assigning them to Customers or Suppliers (also checks all contacts) based on the originating email address -this allows for email Forwarding and Blind Copying (BCC) and is smart enough to check if the email was forwarded from an employee and then determine who the originating source was. If the email address was not recognised it will be logged as un-assigned and can be assigned through the Operations Centre.
  • The ability to automatically receive reply emails from Ticket Actions, System Alerts, Calendar Reminders, Sales & Job Quote Follow ups and History Note Follow ups emails and do the following:
    • An employee can complete or flag as done the following (Ticket Actions, Calendar Reminders, Sales & Job Quote Follow ups and History Note Follow ups) by replying with the word DONE at the beginning of the email subject – more detail later.
    • An employee can also email files (photos, PDF’s, documents etc...) and have them automatically appended to a Job Order/Quote, Sales Order/Quote or Ticket
    • An employee can also email notes and have them automatically created as History Notes and linked to a Job Order/Quote, Sales Order/Quote or Ticket
  • The ability for an employee to ask for a query to be emailed back embedded in the body of the email (the body is formatted in Html) – see image: 
  • The ability for an employee to request and process a form/spreadsheet via email. This basically means that data entry activities like: Service Sheets, Quotes, Orders, Time sheets etc... can be setup using spreadsheets and then emailed back to Ostendo for automatic upload   
  • Automatic emailing of a Sales Delivery Advice, defined against the Customer  

Setting up Email Services

Email services uses Queue services to schedule the automatic polling of receiving from, and sending to, email addresses. The first thing to do is setup the defaults for your outgoing and incoming email accounts in the Queue Settings screen (for Incoming emails you’ll able to specific many of these for different purposes i.e. Forwarding Correspondence emails, EDI emails, Request emails): 

aug-update19.jpg

Outgoing Emails

Once you’ve set the defaults up, there 2 more things you’ll need to do; Define what activities you would like to have automatically emailed, and then schedule the Auto Emailing to run at pre-determined intervals.

Step 1: You’re able to add one or more off the following 6 activities to be automatically emailed (Calendar Reminders, Ticket Actions, History Note Follow-ups, Quote Follow-ups, System Alerts (Individual Alerts are also flagged as requiring emailing), Sales Delivery Advice Notifications). For each you have the ability to set an override for the email address they’re sent to, a default email address if the activity doesn’t have an email to send to (i.e. For Quotes follow-ups the Sales Persons email is used therefore if there is no Salesperson or that employee doesn’t have an email address then the Non-Assigned Email Address will be used), a BCC email address, and lastly whether this record is active. 

aug-update20.jpg

Step 2: Now you’ll need to define a Queue Schedule record for the frequency you wish to send the emails out (via the Queue Schedule screen): 

aug-update21.jpg

Incoming Emails

Receiving incoming emails is automated via the Queue Schedule, we have added the ability to receive from either POP3 or IMAP accounts and then automatically log those emails in a table within Ostendo (table is called EMAILLOG). Any attachments are also stored based on the attachment path defined in the Queue Settings (and can be further segregated via a sub folder name as defined in the schedule record). The receiving of emails can be split into 3 different types:

  1. To Be Assigned: This type of email is for correspondence emails that are typically forwarded to Ostendo for auto linking to Customer and/or Suppliers
  2. Data Only: This type of email is for where data is being emailed for further processing (i.e. EDI, E-Commerce  Orders, Remote Data Synchronisation)
  3. Response: This type of email is for where you’re able to reply to, and sign off, actions, follow-ups and reminders. As previously mentioned you can also Query data, send through files and notes, and request and process spreadsheets (i.e. Service Sheets, Quotes etc...)

There are 2 things you’ll need to do to get the incoming emails running:

Step 1: You’re able to add one or more off the following 3 email types (To Be Assigned, Data Only, Response). For each of these you enter a linked email address (you’re able to have multiple email addresses for each type). 

aug-update22.jpg

Step 2: Now you’ll need to define a Queue Schedule record for the frequency you wish to receive from each of the email accounts. 

aug-update23.jpg

Using Email Services

Once you have setup email services (and you have Queue Services running) you’re able to start using a number of features immediately (The ability to run a Query and Request / Process a Form requires some more setup – explained later in this paper). 

Response Emails:

 Following are instructions on how to interact with the Ostendo Response Emails (theses are also available by typing in ‘Help’ in the email subject line and emailing to the email address you’ve setup for that type (i.e. response@development-x.com). You’ll then receive a reply from Ostendo with the following instructions – useful for employees out in the field.  

Responding to Quote or Note Follow-ups, Calendar Reminders and Ticket Actions

When you receive an email with an Action, Follow-up, Reminder or Action from Ostendo, you are able to let the system know that you have actioned this by replying to the email and appending the word DONE to the beginning of the email subject (i.e. you may receive an email to remind you to follow-up on a specific Sales Quote. The subject of the email would read something like: {SQ#14661936} Ostendo Quote Follow Up for Customer: [XYZ Limited] Quote No: [S301306])

So when replying to Ostendo to indicate you have followed up, you simply append DONE to the beginning of the Subject making sure you have included a space between the word DONE and the rest of the subject (i.e. DONE {SQ#14661936} Ostendo Quote Follow Up for Customer: [XYZ Limited] Quote No: [S301306])

If action notes are required when completing an action, they can be added into the body of the reply, terminated by typing the character ']' twice (i.e. ]]) 

Sending and Adding Files and History Notes to Jobs, Sales and Tickets

You're able to email files (i.e. Photos, PDFs, etc...) by simply attaching the file to an email and formatting the email subject based on the following.

The subject needs to start with the word FILE (followed by a space) and then followed by either JOB, SALES or TICKET with the character # (hash) either side of the Order Number or Ticket ID (i.e. FILE JOB#125000#).

If notes are required for the linked file they can be added into the body of the reply, terminated by typing the character ']' twice (i.e. ]]) 

You're also able to email notes (History Notes) by simply attaching the file to an email and formatting the email subject based on the following.

The subject needs to start with the word NOTE (followed by a space) and then followed by either JOB, SALES or TICKET with the character # (hash) either side of the Order Number or Ticket ID (i.e. NOTE TICKET#78990#)The actual History Note is added into the body of the reply, terminated by typing the character ']' twice (i.e. ]]) 

Running a Query and returning the Results as an Email

You're able to run a pre-designed Query and have the results automatically formatted and returned within the body of the email.

The subject needs to start with the word QUERY (followed by a space) and then followed by the pre-defined Query name with the character # (hash) either side of the Key Value (i.e. QUERY JobInfo#125000#)

Requesting a Form (Spreadsheet)

You're able request a pre-formatted Form (Spreadsheet) and have that automatically emailed back with specific cells pre-filled if defined that way.

The subject needs to start with the word REQUEST (followed by a space) and then followed by the pre-defined Form name 

with an optional character # (hash) either side of the Key Value (only if needed) (i.e. REQUEST ServiceSheet#125000#)

Processing a Form (Spreadsheet)

You're able attach a pre-formatted Form (Spreadsheet) and have the data automatically inserted into Ostendo.

The subject needs to start with the word PROCESS (followed by a space) and then followed by the pre-defined Form name (i.e. PROCESS ServiceSheet)

Data Only Emails:

This type of email is for receiving emails designed to contain data, like EDI gateways with external companies, Orders and Payments from E-Commerce sites and data being sent from a remote site for synchronisation. These applications require a specific script written that will process the data accordingly.

To Be Assigned Emails:

This type of email is for forwarding Correspondence emails from individual email clients to be either automatically assigned to Customer and/or Suppliers via the originating email address, or manually assigned within the Operations Centre. Typically where the user is not using Outlook or doesn’t wish to use the Outlook add-in. 

Email Queries

An Email Query provides the ability for employees to request a pre-defined query to be run and retuned via email (in an HTML format). The queries are defined in the ‘File-Email Services-Email Queries’ screen and can only be requested by active employees (checks their email address).

  1. Query Name: This is the name the Query is referred to in the Email Subject line
  2. Query Description: This is an internal description of the Query
  3. Email Subject: This is the subject text that will be sent back to the employee (i.e. Assembly Order Detail for [KEYFIELD]) – you’re also able to place the [KEYFIELD] in the subject, which will be replaced with the Key field value passed for the query (see image)
  4. Header Title: This is a title that appears as a title for the header fields in the Body of the email (see image)
  5. Header Note: This allows for notes to printed directly under the Header Title in the body of the email
  6. System Header SQL: This is the system SQL statement (will only be filled in where the Query is standard system supplied one) and can’t be modified, but can be copied and used in the Company Header SQL.
  7. Company Header SQL: This is the company SQL statement which is where you can create the SQL statement to be used for the Header fields
  8. Lines Title: This is a title that appears as a title for the lines fields in the Body of the email (see image)
  9. Lines Note: This allows for notes to printed directly under the Lines Title in the body of the email
  10. System Lines SQL: This is the system SQL statement (will only be filled in where the Query is standard system supplied one) and can’t be modified, but can be copied and used in the Company Lines SQL.
  11. Company Lines SQL: This is the company SQL statement which is where you can create the SQL statement to be used for the Lines fields
  12. Footer Note: This allows for notes to printed in the footer of the body of the email
  13. Lookup Index: This links to a Lookup Index (like used in Report & View Conditions) and is for running the Email Query under ‘General-Run Email Query’.

Email Forms

Email Forms is a component of the Ostendo Email Services. The purpose of Email Forms is to automatically process spreadsheet (.xls) forms sent in by users. 

Email Forms can be used in a variety of ways. For example:

  1. An estimator may be using an excel spreadsheet to generate all the information required to prepare a quote. If this spreadsheet information is prepared in a certain prescribed form, he could email it to Ostendo and a quote could be generated in the system without having to re-key in the information into the Ostendo Quote Detail and Lines screens.
  2. Service personnel could be emailed service sheets in the form of spreadsheet attachments. They could use tablets or laptops in the field to view the job information in the spreadsheet and at the same time fill in notes, time & material usage. The completed spreadsheet form is then emailed back to a designated email address where a Queue Service script can be run at regular intervals to update the relevant job or timesheet tables.
  3. A spreadsheet form can be designed to collect all sorts of data. Ostendo Email Forms can facilitate such data collection needs by receiving the emailed forms, processing them, and updating any Ostendo system or user-defined tables.
  4. Email Forms can replace paper forms. Paper forms are often required to be filled, reviewed, and approved before the data in those forms can be loaded into Ostendo (for example New Customer process). A spreadsheet form can be designed for the same purpose. Instead of pushing paper, the spreadsheet can be circulated via email and filled in by various individuals before finally being sent to a designated email address and a new Customer record is automatically generated in Ostendo.  

How it Works

Ostendo Email Forms consists of the following pieces:

  1. The Spreadsheet Forms
  2. The Email Forms Process Flow
  3. The scripts:  EForms-PROCESS script and EForms-REQUEST script
  4. Error Correction

The Spreadsheet Forms: 

Out of the box, Ostendo comes with a few basic Email Forms (these spreadsheets are protected by default – the password to unprotect is ‘ostendo’). These forms serve as samples and can be modified by users to meet their specific requirements. Apart from a couple of basic rules, users can decide how they want to layout their forms. They can even build in data validation rules, protect certain fields and so on. 

Forms consist of Field Names and Values.

There are two types of fields – Fixed Fields and Multiline Fields. In order to differentiate between these two types of fields, and between field names and values, the following rules must be strictly followed:

  1. All Field Names must be enclosed in square brackets with no spaces (e.g.  [JOBNUMBER] )
  2. In any given row in the spreadsheet. a [FixedFieldName] must not have another [FixedFieldName] next to it. The cell to the right of a [FixedFieldName] will be the Field Value.
  3. Where there are two or more [FieldNames] next to each other in a row, that group represents the headings for Multiline Fields. The first (leftmost) [FieldName] in that series is the GROUP name. The rest are all column headings.
  4. The cells immediately below column headings are the respective multiline field values. A blank row denotes the end of the multiline data rows.
  5. There can be one or more Fixed Field Name-Value pairs in a row.
  6. There can only be one set of Multiline data in any row.    
  7. Every form must have a form name specified next to the [FORMNAME] cell.

As an example, take a look at the following JOBFORM:
aug-update25.jpg

Email Forms Process Flow:

aug-update26.jpg

The Email Forms screen is used primarily to identify forms which are requested by users with a requirement to pre-fill with data from header records before being emailed to the requestor.

The SQL extracts all the required data and the field names must match exactly those defined in the form. There needs to be a parameter for the KEYFIELD in the condition of the SQL (i.e. ‘where ordernumber = :KEYFIELD’)

The FormFileName specifies where the blank form is kept. Ostendo makes a copy of the blank form, fills it with the extracted data and emails it to the user.

Whenever a form is emailed to Ostendo, it is logged in the EMAILLOG table either as a PROCESS or REQUEST. 

A PROCESS form is already filled with data that needs to be processed by Ostendo (for example to create a new customer record or Job Quote, etc.).

A REQUEST is basically to request for a spreadsheet form from Ostendo and usually involves pre-filling with some header data from the database.

aug-update27.jpg

The INCOMINGDATA table is used to temporarily hold the spreadsheet data for easier processing. 

The scripting function ProcessIncomingData scans the spreadsheet, identifies the Fixed Field Names and values and store them as (H) records – one Fixed Field name and value per record. Multiline Column Names and Values are stored as (L) records – each record holds one line of data (i.e. multiple fieldname + value pairs together with the Group name.

The Email Subject Parameters:

When sending a form to be processed, the email subject line must be as follows:

Subject: PROCESS formname

  • where formname is the name of the form used in the attached spreadsheet.

When sending a form as a request, the email subject line must be as follows:

Subject: REQUEST formname#keyvalue#

  • where formname is as above and keyvalue is the value of the keyfield used in the SQL associated with this form. In this case the form name and the keyvalue must be terminated by the ‘#’ character.

The Scripts: 

Two scripts are provided to handle the basic forms provided with Ostendo. This scripts can be modified to suit the users’ needs if required.

The EForms-PROCESS script scans the EMAILLOG for records relating to PROCESS forms. It extracts the data into the INCOMINGDATA table and then process the data as required for each form.

The EForms-REQUEST script scans the EMAILLOG for records relating to REQUESTs, fetches the form from the location specified in the EMAILFORMS table, calls the PopulateSpreadSheetData function to fill the spreadsheet with the required data as per the SQL specified in EMAILFORMS and sends it off to the requestor.

Error Correction:

If there are errors in the forms that are sent in to be PROCESSed, then the EForms-PROCESS script will flag the error(s) in the INCOMINGDATA table.

Someone needs to be designated to review the error batches in INCOMINGDATA table via the screen ‘File-Email Services-Email Form Errors’, and make the required corrections and untick the ‘In Error’ flag. 

Once the records are corrected, all the records relating to the form will be processed again the next time EForms-PROCESS is run. There is no need to make changes to the spreadsheet form as only the INCOMINGDATA records will be processed again after correction.

Customised Data Entry Screens 

We have significantly enhanced the Edit View developer to allow for drag & drop forms design (new Style called ‘Custom Entry’), and have provided the ability to capture signatures, freehand drawings, and digital photos. There are numerous uses for this feature – here are a few examples:

  • Remote Data Entry (i.e. Service Sheets, Order Entry, Trade Show POS, Call Tickets, Quality Test Results, etc...) – Where information is captured and then send back to head office (synchronised) for further processing. We have standard functions for synchronising the data with the remote device (more information will be sent out on how Development-X will be working with Partners/Customers to help put together vertical solutions for industries at a no-charge basis so that very quickly we have a library of industry solutions)   
  • Simplified Entry Screens with Ostendo – This could be anything from a cut down version of the Item screen, to, a tailored Sales Order entry screen.

The screen shot below is a simple example of a Service Sheet designed to allow job information to be captured in a user defined table (including 2 signatures, a freehand drawing, and some digital photos which are all stored within the database). 

aug-update28.jpg

This would run on a remote windows tablet, and then be electronically sent back to the office when the internet was available, so it could then be invoiced out.   

Following is an example of a Simplified Item screen that could used for specific users in organisation that only had rights to modify a handful of fields: 

aug-update29.jpg

Additional Enhancements

User Security
We have added a new field called ‘Email Address’ to the User Options tab. This is used if System Alerts are flagged for emailing.

System Alerts
We have added the ability to Email alerts linked to the defined user (or users). You can also still opt to have the alert display in the Alerts Viewer.

Payment Methods
We have changed the ‘POS Bank Account’ to ‘Bank Account’ allowing for this to automatically default when in the standard Customer Payments screen (previously only defaulted in the POS Payments screen).

Customers Messaging
We have added the ability to format messages for the following screens (like the Item Messages you’re able to include merged field values - i.e. The Balance for [CUSTOMER] is [TOTALAMOUNTDUE]):

  • Customer: This message appears in the Operations Centre 
  • Payment: This message appears in the Customer Payment screen
  • Order: This message appears in the Sales Order, Job Order and Sales Delivery screens
  • Invoice: This message appears in the Batch Invoicing screen

Supplier Messaging
We have added the ability to format messages for the following screens (like the Item Messages you’re able to include merged field values - i.e. The Credit Terms for [SUPPLIER] is [CREDITTERM]):

  • Supplier: This message appears in the Operations Centre 
  • Order: This message appears in the Purchase Order screen
  • Invoice: This message appears in the Purchase Invoice screen

Sales Deliveries – Changing Picked Qty’s, Serial Numbers etc
We have added the ability to modify the Quantities, Serial numbers, Batch Numbers, Expiry Dates, Revision Numbers, Grades, Colours and Sizes after the Delivery line has been picked. This will automatically create any reversal entries required.

Sales Rules
We have added the following new rules:

  • Auto Pick All Items: If this flag is set, all items (including any with characteristics – i.e. Serial Numbers, Batch numbers etc...) will automatically be picked based on oldest first logic. 
  • Exclude S/Ns from Auto Pick All: If this flag is set (and Auto Pick All Items is set) serial numbered items will be excluded from the Auto Pick.
  • Quote Follow up Required: This indicates that a follow-up call is required for any Sales Quotes (the follow-up date is calculated from the next rule). The follow-up appears in the To Do list (in the new Operations Centre based on the Reminder User linked to the Salesperson – in the Employees screen) and is optionally emailed (using the Salesperson Email address); with the ability to flag the follow-up as ‘Done’ via a reply email (see Email Services for more information on this)   
  • Follow up Days from Quote Date: This determines the time in days after the Quote has been created that a follow-up call should be made. 
  • Delivery Advice Query: This is the Email Query name used for emailing the Customer a Delivery Notification (the settings for each customer can be found in the ‘Customer-Outputs-Deliveries’ tab). See Email Services for more information on this.

Job Rules
We have added the following new rules:

  • Quote Follow up Required: This indicates that a follow-up call is required for any Job Quotes (the follow-up date is calculated from the next rule). The follow-up appears in the To Do list (in the new Operations Centre based on the Reminder User linked to the Salesperson – in the Employees screen) and is optionally emailed (using the Salesperson Email address); with the ability to flag the follow-up as ‘Done’ via a reply email (see Email Services for more information on this)
  • Follow up Days from Quote Date: This determines the time in days after the Quote has been created that a follow-up call should be made. 





Ostendo® adds advanced inventory, job costing, manufacturing, service and distribution to your accounting system.

Development-X Limited

Developers of Business Software since 2000 for...

  • Sales, Service and Preventive Maintenance
  • Engineering and Fabrication Job Shops
  • Wholesale Distributors and Retailers
  • Contractors, Trades and Projects
  • Manufacturers

For More Information

Australia
New Zealand
Malaysia
Singapore
South Africa
International

info@development-x.com

Phone

1800 151 251
0508 111 999
+60 3 9223 3188
+60 3 9223 3188
+27 11 640 5913
+64 9 525 3612