The 2023.1 release makes it easier to use the Greentree Desktop interface and quickly complete common tasks, like closing and finalising jobs. This release also addresses a range of issues identified in previous releases.
For MYOB Partners, version 6.2 of Packman also includes new features when used with Greentree 2023.1.
New features
Close and finalise jobs in bulk
You can now close or finalise multiple jobs at the same time by using the new Bulk Close/Finalise Jobs form. This saves you the hassle of having to find and close each job one by one.
Open the new form by going to Process > Job Cost > Bulk Close/Finalise Jobs. Choose which jobs to view by entering your Job Selection Criteria and clicking Search Now. For example, you can select a profit centre or charge type combination, or a sub-set of specific jobs.
Close Jobs tab
The Close Jobs tab lets you both close jobs that are open and reopen jobs that have previously been closed.
To close jobs, select the checkboxes in the Close Job column and click Close/open jobs. After closing a job, the Close Date field defaults to the date you closed the job. If needed, you can enter a different date.
To open jobs, deselect the checkboxes in the Close Job column and click Close/open jobs.
For closed jobs to appear in the list, make sure you select the Closed checkbox in the Job Selection Criteria section.
Finalise Jobs tab
To finalise a job, select the checkbox in the Finalise Job column and click Finalise jobs. You can't reopen finalised jobs or change the Finalise Date.
Results tab
After you close, reopen or finalise a job, the Results tab opens. It shows you what changes you made, and if the change was successful.
Drag and drop files for Outlook Office 365
You can now drag and drop files, including Outlook Office 365 messages and attachments, to attach them to masterfiles and transaction records. Make sure you drop the file directly on the Attach Document icon.
You can only attach a file if the program you're dragging it from (e.g. Outlook or Windows Explorer) has either the same administrator rights as Greentree or more comprehensive administrator rights.
(NZ only) Automatically calculated leave for all employees
When an employee requests leave, MYOB Greentree automatically calculates how much leave they need for the dates they enter. Previously, this wasn't being done for some employees. Now, leave is automatically calculated for employees that:
have a working calendar
have a definition of a week, and
whose leave is set to be calculated in weeks and/or days.
This saves employees the trouble of manually calculating their leave, as well as saving them the headache of accidentally getting it wrong.
The leave is calculated using the employee's definition of a week.
This improvement has been made to both MYOB Greentree Desktop and Browser. On the HR Leave Request Entry form in MYOB Greentree Desktop version, the Use Calculated Leave option is selected by default for these employees.
Set a primary address when importing customer delivery addresses
When using the gtCustomerDeliveryAddress FREEfunction, you can use the new isPrimary parameter to set a delivery address as the customer's primary address.
If your Greentree setup uses FREE functions, you need to register the new version of the GreentreeInterface.dll and GreentreeInterface.exe files (version 4.4.0.0) in ...\bin64. Update any spreadsheets using the Greentree Interface with the new XLA version (MYOB_GreenTree_FREE.xla).
Minor improvements
On the eDocs Module Control form, you can now add more than one person to receive warning emails about licencing limits.
The Windows Designer menu item has been renamed from Designer to Windows Designer. You can access it by going to System > Customisation > Windows Designer. This makes it easier to distinguish it from the Query Designer Manager and Process Flow Designer menu items.
To make it easier to set up the right email credential service, options on the Email Credential Maintenance form. The Server Type dropdown has been renamed Protocol, and the Exchange option in the dropdown has been renamed to Exchange Web Services.
AUSTRALIA UNSAFE-ONLYOn the Protected Earnings tab of the HR Module Control form, a row for 2023 has been added to the protected earnings amount table. From 01/01/2023, the protected earnings amount is $456.53. If you manually entered an entry for 01/01/2023, it won't be overwritten.
It's now easier to read large numbers at a glance on the JC Job Maintenance form. Numbers higher than a thousand are now displayed with a comma.
Rebuild ODBC View is now available as a standard script in the Database section of the System Scripts form. Previously, it was only available as an HR script.
Performance improvements
Faster HR Pay Summary report
The new standard HR Pay Summary report runs noticeably faster – especially for sites with many employees and years of payroll.
If your site has a custom report called HR Pay Summary, it will be overwritten by the new standard report. Before upgrading to 2023.1, you need to rename your custom pay summary report.
You can also improve performance of custom pay summary reports by using new report methods.
Keep your custom report by renaming it
Before upgrading to 2023.1, export the custom report.
Upgrade to 2023.1.
Rename the new standard report. For example, "HR Pay Summary (standard 2023.1)".
Import your custom report.
New report methods that improve performance
Instead of using queries, the new report selects pays by using new report methods. You can use these report methods to improve performance of custom HR pay summary reports.
There's a method for each profile:
Batch profile uses a Pay Batch (HRPayBatch) method: Get HR Summary Pays for Batch.
Employee profile uses an Employee (HRPerson) method: Get HR Summary Pays for Person.
Pay Group profile uses a Pay Group (HRPayGroup) method: Get HR Summary Pays for Pay Group.
Date profile uses a Company method: Get HR Summary Pays.
The report methods take From and To parameters for ranges:
batch number (doesn't apply to the Pay Batch method)
branch code
pay date
pay group name (doesn't apply to the Pay Group method)
person code (doesn't apply to the Employee method)
profit centre code.
The methods apply HR security checks: the user must have permission to report payroll transactions, and must have reporting access to an employee to see related pays that match the Security View selected when running the report. They return an unsorted collection of Pays matching the criteria. The range checks based on codes and names are not case-sensitive.
Improving custom report performance
You can improve performance on custom HR Pay Summary reports by removing queries, then adding and applying the new report methods.
Although your custom reports might be different from the standard report, you should still be able to make the changes – even if profiles, sections and queries have been renamed, hidden or removed.
To be able to make the changes correctly, you need to understand how to select different sections of the report in the Report Design screen.
Understanding report sections
In the Report Design window, you need to remove queries, then add and apply report methods for the Batch, Date, Employee and Pay Group profiles.
Each profile is made up of an inner section and outer section (except Date, which only has one section). You can tell which section you're working in by how many squares appear in the grid.
If you click the inner section, seven squares appear.
If you click the outer section, three squares appear.
You can also tell which profile the section belongs to by checking the Current section and Name fields on the left.
1. Open the custom HR Pay Summary report
In Greentree desktop, go to System > Customisation > Report.
In the Report Customisation window, select the custom HR Pay Summary report, then click Edit. The Report Design window opens.
2. Remove queries from profiles
In the Report Design window, right-click the inner section of a profile and choose Select by... > Query. The Edit Query selection window opens.
In the Selection Criteria section, select each query and click Delete.
Click Done.
In the Confirmation window, click OK.
Repeat steps 1–4 for all the profiles.
3. Add the new report methods to the profiles
In the Report Design window, right-click the outer section of a profile and choose Set Method Parameters.
You can tell if you've clicked the outer section by checking the Name field. For example, if you click the outer section of the batch profile, the field will say Batch profile.
In the Method Parameters window, click Add.
In the Choose Method window:
For the Batch Profile, select Get HR Summary Pays for Batch and click OK.
For the Pay Group Profile, select Get HR Summary Pays for Pay Group and click OK.
For the Employee Profile, select Get HR Summary Pays for Employee and click OK.
For the Date Profile, select Get HR Summary Pays and click OK.
In the Method Parameters window, in the Methods used section, select the method you just added. For example, Get HR Summary Pays for Batch.
Complete the Parameter set to column:
Click the blank Parameter set to value for a row. The Source for window opens.
Set the Type field to Parameter for every row.
Select the parameter that matches the Parameter Name for that row.
Repeat steps 4–5 for each profile.
4. Apply the report methods to the profiles
In the Report Design window, click the inner section of a profile.
Click the Shows field on the left.
In the Select Property window, select the new report method you added for that profile and click OK. For example, Get HR Summary Pays for Batch.
In the Report Design window, click Save. You've finished improving the performance of your custom HR Pay Summary report.
Faster to copy or delete bill of materials
It now takes less time to copy or delete a bill of materials. This is especially useful for companies with factories that use the same components to make multiple different products.
Security updates
Updated security confirmation window
This release updates the Security Confirmation window, which opens when establishing OAuth2 credentials for sending and retrieving emails.
The window now uses a WebView2 browser control, just like when Greentree displays maps, licence information, STP information and eDocs PDFs.
This release depends on several libraries that were introduced in Greentree 2022.1 along with the requirement for Microsoft Edge WebView Runtime to be installed on client machines. It also releases new versions of GreentreeMail.dll 2.1, GreentreeMailCore.dll 2.1 and Microsoft.Identity.Client.dll 4.48.1.
Packman 6.2 (MYOB Partners only)
As an MYOB Partner, you can now download Packman version 6.2 from the Greentree FTP site. This includes Packman.exe and Packman.dll. The new version:
Prevents you from applying test packages to production systems.
Lets you reduce runtime by skipping Greentree Browser screen optimisation.
These features are only available if you use Packman 6.2 with Greentree version 2023.1 or later.
Test package prevention
You can no longer apply a test package to a production system. To be able to apply test packages to test systems, select the Is a test system setting on the Test System tab of the General System Preferences form.
If you're a value-added distributor (VAD), you need to be careful with the Create as a test package setting in Packman when creating custom packages or when running Packman in unattended mode, as you won't be able to apply the package to a production site.
Skip Greentree Browser screen optimisation
If you have access to Packman menu security, you can use the new Prevent optimisation of browser screens option.
By default, on a system that has Greentree Browser enabled, Packman optimises Browser screens after applying all packages in the Packages directory. If you apply packages individually, then skipping optimisation on all but the last Packman run will reduce runtime.
To make sure you don't forget to optimise Browser screens when applying the last pack, you'll see a message when logging into the Greentree thin client as a super user.
As a fallback to skipping screen optimisation, you can now start the Initialise/Optimise Browswer task from the Task Scheduler form. This does a full rebuild, including screen optimisation.
Packman 6.2 also improves the fallback for skipping relational view generation. You can now use the Rebuild ODBC View HR script with the current setting (include/exclude HR classes). If you don't have the HR module, Rebuild ODBC View is also now available as a standard script in the Database section of the System Scripts form.
You can also skip screen optimisation or relational view generation when launching Packman from the command line. To do so, set the new parameters preventBrowserScreenOptimisation and preventRelationalViewGeneration to true. This overrides the the values used in the last Packman run.
Resolved issues
For one of the following resolved issues (00012151), there are extra steps you need to take to fix files previously affected by the issue..
Greentree Desktop
Issue IDs
Description
00012151
ACTION REQUIRED
If you saved a report as a PDF or created PDF pay slips in eHR, an error could occur when trying to open those PDFs: "Failed to load PDF document." This occurred if the original report included image files that were too large.
This has been resolved. You can no longer create PDFs that can't be opened. Instead, you'll get a warning: "The PDF could not be generated because the size limit was exceeded."
What to do when you get the warning
When you get this warning, you need to manually reduce the size of the image files attached to the report. You can reduce the file size either by compressing the image file or by changing the file type. For example, an image might be 1.1MB if you save it as a BMP file, but only 34KB as a PNG file.
Fixing previously affected PDFs
If your Greentree site is configured to retain copies of pay slips in PDF format, upgrading to this version won't remove a cached invalid PDF.
If the Cache pay slip on the server setting is selected in the eHR Module Control and a PDF pay slip fails to load, you need to:
Modify the report definition.
Deselect the Cache pay slip on the server setting.
Request the pay slip.
Select the Cache pay slip on the server setting again.
00012275
If a user-defined field was set on a WebView form or page, then **not initialised** is displayed in the field when it should be empty. This has been resolved.
You couldn't attach a file to a form by dragging and dropping it onto the attachment icon. This feature has been added. For more information, see Attach files by dragging and dropping them.
00010367
The Recalculate JC Summary Totals system script was incorrectly converting foreign currencies to local currency if the conversion was set to divide, not multiply. This has been resolved.
00012303
On the Inbound Filing form, emails retrieved from Exchange didn't include an email address in the To field. This has been resolved. This resolution has been deployed as a new version of GreentreeMailCore.dll 2.1.0.0.
00011755, 00012408
On various forms, if the Assigned User had been set as inactive, an error would occur: "The Assigned User Field has been cleared because the user is inactive." Clicking OK in the error message wouldn't close the message window. This has been resolved.
00011569
On the AR Apply Unapplied Transactions and AP Apply Unapplied Transactions forms, if you selected a transaction in both the Debit transactions and Credit transactions tables by using the date field, you couldn't click the Match button. This has been resolved.
00011135
When creating a receipt for a shipment with more than one serial/lot line, Greentree required you to enter serial/lot numbers for all the lines, even if you only selected one line. This has been resolved.
00012368, 00012390
Administrators weren't able to change the profit centre group for an employee. This has been resolved.
00012320, 00012394
If an item's batch size wasn't defined as a whole number in its bill of materials, factory orders for that item were being incorrectly rounded up to the nearest whole number. This has been resolved.
00012325
When copying the contents of a table by clicking Send table contents to clipboard, then the formatting of the contents could be incorrect when you pasted it into other software, like Microsoft Word. This has been resolved.
00012121, 00012357
When running either standard or site specific system scripts, an error could occur: "An error has occurred (4013) Result of expression overflows Integer precision." This has been resolved.
00012452, 00012176
For consolidation companies, an issue prevented users from accessing the WebView Designer and Reports and Documents modules. This has been resolved.
00012419
When trying to view HR details for pay groups, person positions or injured persons, an error could occur: "An error has occurred (4) Object not found." This has been resolved. The Validate trees HR system script now includes trees on pay groups, person positions and injured persons.
00012382
On the HR Employee Maintenance, Pay Entry and Terminate Employee forms, clicking the Leave Balances icon could cause an error: "Could not calculate Standard Pay: Update outside transaction". This has been resolved.
00012208
If a user has been selected in the Link to User field on the Security tab of the HR Employee Maintenance form, using the gtHREmployee FREE function would delete the selected user from the field. This has been resolved.
00011978
When importing a pay into an existing batch that has had a payment created for at least one employee, an error could occur: "An error has occurred (1086) Class of object is invalid in this context." This has been resolved.
00011946
Cancelling a refund could cause an error: "An error has occurred (1086) Class of object is invalid in this context." This prevented you from printing the Job Transactions Report. This has been resolved.
00011239, 00012395
On the Processing System Status and Setup form, the Task Manager System housekeeper wasn't running, which meant you had to manually manage the email and printing queue. This has been resolved.
00011152
When running a custom script, a 1271 error could occur: "An attempt was made to perform an operation eg. beginTransaction etc that is prohibited in this context." The underlying exception for this error wasn't being reported. This has been resolved.
00011544
When running Inspector queries, an error could occur: "An Error has occurred (1090) Attempted access via null object reference." This happened with collections whose nominal type was Object, like the allObjects collection on a CRMAlertBucket, accessed by inspecting an alerts collection. This has been resolved
00011981
Backpays were incorrectly included in the calculations for leave accruals. This occurred if an employee accrued leave as a percentage of an accumulator, and the Use TT from source line for back pay calculations checkbox was selected on the Back Pay Configuration form. This has been resolved
00012080
Scheduled reports were still being run after the date when they were meant to stop. The Stop Date field has been removed from the Schedule Setup window. You can still cancel scheduled reports manually
00012204
When opening favourited or bookmarked HR scripts, an error could occur: "You do not have privileges to this form."
This has been resolved. The Change Pays and Delete Accruals HR scripts have been removed from the Scripts tab of the HR Setup form. Now, you can open the HR scripts directly from the HR > System > Payroll menu. Normal menu security applies to them, and you can bookmark and favourite them. All users who previously had access to the scripts can still run them
N/A
Multiple forms had issues with incorrect background colours. Two forms had issues when being resized. These have been resolved
N/A
When a report indicator was set up to use a character field, the result wasn't displayed correctly. This has been resolved
00012384
On the Payment Selections form, deselecting a branch wouldn't remove that branch's suppliers from the Selected suppliers table. This has been resolved
00012405
On the Get Claim Items tab of the JC Job AR Invoice Entry form, the claim line showed the value left to be invoiced, even though it was already invoiced for the full value of the claim. This has been resolved
00012428
Users couldn't use versions of the JC Activity Code Group Maintenance and JC Profit Centre Group Maintenance forms customised with Windows Designer, only the default versions. This has been resolved
00012409
When using the gtGLJournal FREE function, if the batch number was longer than the maximum length set on the Company Maintenance form, an error could occur: "JournalUpdate - ?INTERNAL ERROR - 0 -". This has been resolved. The error message is now easier to understand. For example, "Batch number 1234567890 exceeds the limit of 9 characters." This new error message applies to all FREE functions that use batch numbers
00012490
When customising the POS Sales Entry form in Windows Designer, an error could occur: "An error has occurred (4) Object not found." This has been resolved
00012510
When running the Windows thin client, importing reports could cause an error: "The file does not contain a report definition." This has been resolved
00012504
The On Order quantity for an inventory item could be a negative amount. This issue could occur on a PO shipment if you selected a purchase order, then put the purchase order on hold before saving the PO shipment. This has been resolved. Now, you can't save the PO Shipment Entry form if a purchase order is made unavailable for shipment after selecting it
00012526
When importing CRM quotes, rules weren't being triggered. This caused the quotes to be imported without approval. This has been resolved
00012538
If approvals were added as part of an A&A rule with the programmatic On Submit condition selected, then manually assigned approval details weren't being displayed
00012601
Users who only have Team access couldn't click the Instant Alert icon because another icon covered it. This has been resolved
00011240
If a tree name had five or more characters, an error could occur: "An error has occurred (4031) Index used in substring is out of bounds." This has been resolved
00010443
When using Query Designer, an error could occur: "All equals as leaf of source collection not supported as yet." This has been resolved
-
On the Reports Library form, exporting a saved report to a Microsoft Excel file didn't work. This has been resolved
00011946
On the Job Maintenance form, applying a cancelled refund could cause an error: "An error has occurred (1086) Class of object is invalid in this context." This has been resolved.
0009066
NEW ZEALAND ONLYProtected earnings calculations for child support payments were incorrect. This has been resolved
00012299
A problem could occur when issuing a purchase order for a service request that has an assigned job. If you added a second line to the purchase order, that second line could incorrectly be set to the service request job, instead of the purchase order job. This has been resolved
N/A
When running the Enterprise Search indexing task, an error could occur: "Exception 1072 Object has been deleted in the current transaction". This has been resolved
00012472
On the Related tab of the Organisation Maintenance form, double-clicking a date in the Expected date column wouldn't open the record. This has been resolved
00012556
On the Quote Maintenance form, changing the Quantity for a quote incorrectly added .01 to the Retail Rate. This has been resolved
WebView
Issue IDs
Description
N/A
If a user's password contained < or >, they couldn't log in. This has been resolved
Greentree Browser
Issue IDs
Description
N/A
When drilling down from a bookmark or service request workflow panel to a call or service request, any attached photos and signatures weren't displayed. This has been resolved
00012471
Changes to an organisation's contact name weren't being saved. This has been resolved
eDocs
Issue IDs
Description
00006365
A licencing error could prevent users from logging in. This has been resolved. To prevent users from being locked out, eDoc licences are no longer checks when users log in to the thin client. Instead, licence warning emails are sent based on how the eDocs Module Control form is set up. You can also now add multiple warning email recipients.
This change is also listed as a minor improvement in the new features section of these release notes.
When using a script to scrape data from documents, a 1035 error could occur if certain data had too many characters. This prevented the rest of the documents from being scraped. This has been resolved. Now, if the error occurs, the rest of the documents continue to get scraped, and the error message is more helpful – for example, "100000:Reference too long for SO Sales Order (102)".
00012269
When logging in on the Email Credential Maintenance form, the Security Confirmation window was incorrectly opening in Microsoft Internet Explorer, instead of the user's default browser. This has been resolved. For more information, see Security updates.
00012511
When creating AP invoices and sales orders from scraped data, a decimal overflow exception (4033) could occur if you assigned an invalid quantity to a line item. This has been resolved
00012536
The Token Management form was displaying and sending email notifications for deleted tokens that related to eDocs source lines. This has been resolved
N/A
When using the thick client, trying to view eDocs for customer remittances could cause the Jade node to crash. This has been resolved
00009976
On the eDocs Type Maintenance form, an issue could occur if you added a checkbox that to display tax inclusive customers. If the checkbox was set to be selected by default, it wouldn't stay selected when moving from one record to the next. This has been resolved
00012594
If a user entered their personal email login information on the Security Confirmation screen, they could accidentally import personal email data into eDocs. To reduce the risk of this happening, the Security Confirmation screen now defaults to the relevant email credentials. It also includes a message advising the user to enter credentials for the prompted email address.
eRequsitions
Issue IDs
Description
00002693, 00011603
Two issues affected requisitions for foreign suppliers:
The currency rate defaulted to a fixed rate instead of the supplier's rate.
The sell rate for any job costing line items was incorrect.
These have been resolved.
00011675
When opening an eRequisition, if a sub-location was selected in the Location field, then the main location was displayed instead. This has been resolved.
00012488
If an inventory item didn't have an active preferred supplier, the item couldn't be saved on an eRequisition. This has been resolved
eReporting
Issue IDs
Description
00012338
When emailing invoices, Greentree wouldn't create a PDF if there were a large number of AR invoices for a customer. This has been resolved
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.
