As the screen customisation process is virtually “drag and drop”, changes can be accomplished in minutes – even developed/ prototyped interactively with the user requesting the changes which can be a major benefit within projects, boosts your support team credibility and can bring a breath of fresh air to revitalise existing installations. |
If you are keen to hear more about how the effect this level of customisation can have on your users ( without changing a single line of base Intentia code, hence protecting your Intentia support and upgrades ) then contact eVentura and we will be delighted to share with you how these can be achieved with minimal cost and timescales in your organization.
|
How Is This Achieved?
As you may be aware, Intentia Explorer stores the presentation of screens as View Definition (.mvx) files. So, for example CRS610.mvx is the View Definition for Customer Maintenance.
These View Definitions are stored in folders within a defined structure and the same Intentia function can appear in one or more of these folders. Whenever a program is called by Intentia, it accesses these folders in strict sequence and uses the first instance of the specific function it encounters. You may recognize this technique as the way on which all upgrades/ enhancements/ modifications are managed by Intentia. |
With eVentura Visualfx , we use standard Intentia tools to ensure that customized View Definitions are stored in the highest folder in this list – thus the customized version will inevitably be used in anger, yet the original View Definition is never ever amended by customisation. In fact, we strongly advocate the creation of a specific new folder to the above list so customised functions are completely segregated and can be switched ON and OFF in moments.
In the case of the requirement by use of Visualfx to display images etc within screens, we provide additional functions to the amendment process itself to specify our add-on features and during the installation process of Visualfx we automatically install a small number of .ocx and dll objects to the PC itself to execute these.
|