What’s new
- Implementation of license management
- Visualization report of GL entries for the JOV Project Journal
Implementation of license management
Starting from this version, an OMZY license will be required to operate the application's functions. The demo license is necessary to try the application. You can obtain a demo license by contacting sales at the following address: https://omzy-app.com/contact/
The demo license can only be installed in a sandbox environment, while the production license can be installed anywhere. There are 2 types of licenses: Basic and Enterprise.
The Basic license allows project management within the company and does not allow resources from different companies to collaborate on the same projects.
The Enterprise license allows associating different companies with a project domain, enabling multi-company collaboration among all companies associated with the same domain.
After receiving your license file by email, follow the procedure below to install it:
Search for JOV Licence using the magnifying glass.
Actions => Import License
Drag and drop the file received by email into the designated box.
If the file is for a demo license, these steps must be performed in a sandbox environment.
Assign users to the license.
a) Search for JOV OMZY Users using the magnifying glass.
b) Press the Edit List button and add as many users as allowed by the license.
Only users with a full BC license can be assigned.
- OMZY is now ready to be used.
Visualization report of GL entries for the JOV Project Journal
From the unposted project transactions JOV Project Journal, it is now possible to preview the entries that will be posted to the company mentioned in the batch when the transactions are posted. To view the transactions from the JOV Project Journal screen: Home => Transaction Preview
Technical
| Features | No. of application | specification |
|---|---|---|
| 3626 | Implement license management. | |
| 3630 | GL entries viewing report for the JOV Project Journal | |
| 5521 | Validate use of a category in payables before allowing deletion. | |
| 5521 | Update category description on the invoice if it has been modified in JOV Category. | |
| 5653 | In a project invoice, make it possible to click on a total (group) to display the detail of transactions. | |
| 6147 | BUG-000015 | Populate productivity code in project journals. The Productivity Code of the General section has become Default Productivity Code. Add an optional Productivity Code column in the Hours Type Allowed section. This column makes it possible to choose a productivity code as with the General section field. Behaviour of this field: In the JOV Project Journal, the Productivity Code field will be populated first with the Productivity Code value of the task Line. If empty, take the Productivity Code entered in the category based on the Hours Type. If empty, take the value of the Productivity Code for the General section of the category. |
| 6149 | BUG-000011 | Changes to the impact of task characteristics on task copy.When the Copy Characteristics box is not checked, the inheritance of the contract type will be from the project header, otherwise from the parent task if it exists.  |
| 6184 | Category copy when the productivity code is mandatory. | |
| 6216 / 6220 | BUG-000016 | JOV Projet – Move the project invoicing department to the top of the page. |
| 6221 | Correction of the Invoicing Budget calculation when the preparation is run multiple times. | |
| 6237 | Make it possible to enter a markup higher than 100% in billing methods. |