10 More Reasons to Like Arbutus (11-20)
- Frequent software updates
- Auto-loading workspaces
- Enhanced procedure debugging
- Enterprise Client/Server capabilities
- Arbutus SmartApps
- Auto-executing procedures
- Compare tables
- Long, meaningful names
- Re-use printed report import definitions
- Integrate data seamlessly with other tools
Note: The following 10 More Reasons to Like Arbutus are aimed at technical or advanced users. Questions or comments? Please contact us.
Arbutus has a track record of exceeding our user’s expectations. For example, Arbutus automatically checks for updates and advises you of the features in any new release. This is particularly useful given the frequency of Arbutus software updates. Regarding development:
- Actively developed, with new releases available on our Downloads page typically at least twice a year
- User feedback regularly incorporated into new versions
- Automatic or manual check for updates
12. Auto-Loading Workspaces
Workspaces are automatically loaded whenever one of their fields is referenced. The existing manual activation is still supported, but if you use the syntax: workspace_name.field_name then the workspace will be automatically loaded, if it is not already. Automatically loading workspaces may be used wherever an expression is valid, including Views and computed fields.
13. Enhanced procedure debugging
Whether you call them procedures, programs, batches, scripts, or macros, these all refer to automated processes. Arbutus includes a wide range of capabilities that maximize your ability to automate processes:
- The colorized Procedure Editor not only highlights syntax problems, but easily allows you to understand the commands
- Identifying matching parentheses ensures that your formulas are built correctly
- Procedure “step mode” allows you to execute your procedure one command at a time, inspecting or correcting the environment as you go
- Procedure “Breakpoints” allow you to enter step mode at any time during the procedure, so that you can skip over the portions that are operating correctly
- “Save and Run” allows you to easily make changes, then see the effect
Tools Options Editor:
Watch the ArbutusAudit tutorial video, Enhanced Procedure Debugging in Arbutus Analyzer Audit Software, on YouTube:
14. Enterprise Client/Server capabilities
- Access data on IBM zSeries (mainframes), iSeries (AS/400), or Windows, using our native servers
- Move data between servers or between your local desktop and servers at the click of a button, with no ETL or data transformation coding
- Run any procedure either locally or on any server, with no coding changes required
Broad Server Support:
15. Arbutus SmartApps
Each license of Analyzer includes a powerful suite of pre-built audit tests covering five key areas: General Ledger, Accounts Payable, Accounts Receivable, Fixed Assets, and Inventory. The 57 SmartApps have straightforward dialog boxes that make it easy for all levels of users to quickly achieve meaningful audit analysis and reporting. The scripting code is available for each SmartApp for further customization or to be used as helpful templates for other audit tests.
16. Auto-executing procedures
Whenever a table is opened, you have the option of automatically running a specified procedure. This is typically used to ensure the table contains the most current results, but can also be used as an alternative to trigger any action.
For example, any procedure/script can contain as many named sub-procedures as desired. Sub-procedures do not appear in the Overview, but can be referenced from within the procedure, or from other procedures. Calling a sub-procedure uses the familiar ‘DO name’ syntax, except that ‘name’ can now have three variations:
- “name” refers to the separate procedure ‘name’. (like DO Inventory) This is the same as the older syntax
- “name.sub” refers to the sub-procedure ‘sub’ inside the procedure ‘name’. (like DO Utility.cleanup) You might use this if you have a procedure like ‘Utility’, that contains a number of utility functions that you don’t want to be displayed individually in the Overview, or maintained as separate procedures
- “.sub” refers to the sub-procedure ‘sub’ within this procedure. (like DO .user_input) Use this option when you want to bundle an entire application in a single procedure. Even if you rename the procedure, the references inside are still valid
Callable sub-procedures allow you to create truly modular scripts and also allow you much better control over the user interface that your users see. There is no longer any risk that a user might accidentally pick the wrong starting point. Here is an example of a procedure using callable sub-procedures:
SET SAFETY OFF
DO .Get_Parameters WHILE NOT valid
COMMENT this procedure will not set ‘Valid’ to T unless all user inputs are OK
COMMENT ensure they entered a file name
IF length(filename)=0 PAUSE “You must enter a filename”
IF length(filename)=0 RETURN
COMMENT ensure the file name is valid
COMMENT ensure they entered a valid type
IF type5 PAUSE “The type must be from 1 to 5”
IF type5 RETURN
COMMENT do the appropriate calculations here
COMMENT do whatever export/reporting is required
Only the main procedure name is shown in the overview, and this is the only item that a user can select and run. Procedures (including sub-procedures) can be of any length, so even the most complex applications can be contained in a single item.
Watch the ArbutusAudit tutorial video, Auto Executing Procedures in Arbutus Analyzer Audit Software, on YouTube:
17. Compare tables
With Arbutus, you can compare any two tables for differences with just a few clicks. Select the columns to compare, or even select them all. Importantly, the Compare command does not require that the data be sorted. Therefore, it can be used to compare any data files, regardless of format. Specific opportunities this command enables include:
- Where the tables represent the same source at two different points in time, you can use this command to identify changes between the two points in time
- Where the tables represent the source and target in an ETL process, you can use this command to ensure correct ETL transformations were implemented. Arbutus’s compatibility with virtually any data source means that in most situations, both the source are target tables can be directly accessed.
Watch the ArbutusAudit tutorial video, The Compare Command in Arbutus Analyzer Audit Software, on YouTube:
18. Long, meaningful names
The names of all tables, columns, procedures, and more may be up to 127 characters in length. This not only ensures meaningful names throughout your use of Arbutus, but also ensures maximum compatibility with other products that support long names.
19. Re-use printed report import definitions
Arbutus supports the definition of report files as data. Where you have multiple reports with the same structure, Arbutus allows the definitions used to be easily re-used and modified, minimizing the effort involved with defining similar data.
Watch the ArbutusAudit tutorial video, Re-Using Report Templates in Arbutus Analyzer Audit Software, on YouTube:
20. Integrate data seamlessly with other tools
Arbutus LegacyLink™ allows data from any platform to be integrated with Excel, Access, Crystal Reports, databases, and other web or Windows applications.
Our proprietary ODBC driver provides all Arbutus tables, regardless of source, to be seamlessly integrated with any Windows application. This not only allows integration with existing BI and Dashboard technologies, but allows you to create your own BI tools, without the need for expensive third-party BI applications.