 |
To control quality standards and save time you have to automate dozens, hundreds, maybe thousands of tiny business process as precisely as you can. When you do this, standards increase, you save very substantial amounts of time and training for new staff decreases. |
|
|
|
|
Daybook Enterprise provides the solution. Firstly you can build custom reports —they could be your own management reports, job bag summaries, timesheets, call lists, contracts or statements—that are a lot more sophisticated than you would normally find: the reason is that they make use of Daybook Enterprise’s second killer feature, its scripting language. |
|
|
|
|
|
Daybook scripts or macros can be completely new processes that you run by hitting a function key, or from the macro palette; or they can execute automatically while you work. They can be restricted to a particular person or group, or run company-wide. They can also be scheduled to run at a given time. |
|
|
|
|
Here are a few examples of how this powerful feature may be used in Daybook Enterprise: |
|
|
|
|
|
Data Lists
|
|
|
Daybook Enterprise’s Data List Manager is a powerful feature, designed to handle those lists that everyone makes. Daybook Scripting integrates with the Data List Manager, to automate repetitive tasks, thereby saving a great deal of time over the course of a year. |
|
|
|
|
|
For instance, a credit controller might want to regularly view a list for invoices with particular analysis code that are now over 30 days old. Every time this list was called, the ‘rules’ would make sure that it was dynamically updated. |
|
|
|
|
|
Diary Macros
|
|
|
Macros can be set to run from the Daybook Diary, so that you can schedule when they execute. You might, for instance, want to run a long and complex analysis of your data out of normal office hours once a month and return the results to a spreadsheet. |
|
|
|
|
|
Export Manager scripts
|
|
|
Daybook Enterprise can export data to other applications. As well as exporting data from the various tables in the database, you can also use scripts to control the whole process and produce the data to be exported.
|
|
|
|
|
|
Reporting scripts
|
|
|
As mentioned above, you can build scripts into your reports, thereby greatly enhancing their power. |
|
|
|
|
|
Data entry scripts
|
|
|
Whenever you make an entry in a field and tab out of it, a chunk of program code, specially written for you, can run. This feature is ideal for automating those countless small tasks that are peculiar to each organisation. |
|
|
|
|
|
For instance, a salesperson entering a required date on a sales order might need to check the availability of the driver who normally delivers to that area. A script linked to the Required Date field could do the job automatically, giving an alert if the driver had more than a specified number of call already scheduled. |
|
|
|
|
|
Record closing scripts
|
|
|
There are many occasions when the act of closing a record needs to trigger other processes. Unless you can automate these procedures, you run the risk of not doing them. |
|
|
|
|
|
Following on from the example above, closing the sales record could cause an entry to be added to the driver’s diary, scheduling the delivery. If the order were to be over a certain value an alert could be sent to accounts instructing them to double-check credit status. Similarly, closing a large order could prompt the system to check the diary of the salesperson to see whether a follow-up call had been booked for the next day, and, if not, create one. |
|
|
|
|
|
Word-processing scripts
|
|
|
Scripts can gather information to go into a letter or calculate values, when you create a new document, use a template, or run a mail merge. For instance, if you are doing a mailshot about a product, your script could check the Events Manager to see whether your client is coming to a seminar you are holding and, if so, insert a PS saying how much you are looking forward to seeing them there. |
|
|
|
|
|
Case histories
|
|
|
SupportPlan |
|
|
|
|
|
Hopefully this document will have given you some idea of the power and adaptability of Daybook Enterprise. For further information, or to discuss how you might implement scripting, call the Daybook team on 020 7371 7161 or email info@daybook.co.uk |
|
