What is New in Version 4.00

Reference Contents > Introduction > What is New in Version 4.00

Caliach Vision V4.00 operates with Omnis Studio V5.2.2 or greater.

The following relates to changes made since V4.0000.

New Installers

Caliach have introduced a new installer from BitRock and a new resulting file structure that integrates Omnis Studio into the Caliach Vision folder structure so that just one location on your computer contains all files related to Caliach Vision operation. For Microsoft Windows Vista, Server 2008 and 7, this breaks the convention of placing executable files in the Program Files folder of the C drive and the subsequent security enforcement of UAC. However, it is Caliach’s view that this breach is well worth it for the convenience and of a simple, compact, self-contained and integrated structure.

There are in all 6 installers. A full and demonstration version of each of our supported platforms, Windows, MacOSX and Linux. The Demonstration edition contains pre-licensed Caliach Vision and Omnis Studio Runtime. The Full edition contains a full set of Caliach Vision files and both Omnis Studio Runtime and Design programs with user control to include the Design program, typically only needed by the system manager.

Unlike in the past the installer by default names the folder containing the installation with the version number, so the full version will go to C:CaliachVision-4.00. If that already exists files within it will always be overwritten. Extra files you have created such as Archive files will still remain but if you have archive or custom files from an older version, it is left to you to copy them to the new folder structure from the old one.

Summary of adjustments you may want to make to your converted data

File — System Manager — Privileges and Settings

Menus items that have been added are:

1. File — System Manager — Graphs (Second Generation)
2. File — System Manager — Data Views Design
3. File — System Manager — Key Perfornce Indicators
4. File — Advanced — Language Swap Maintenance by File
5. Masters — Process Routes — Update Operation Times from History
6. Process — Purchase Orders — Create KanBan Orders
7. ScratchPads — Address and Contact Keyword
8. ScratchPads — Translate for Language Swap
9. User menu structure of custom feature entries

Window Tab Panes that have been added are:

1. System Performance

Fields you may want to populate

1. File — System Manager — Privileges and Settins: Users
   • No Login
2. File — System Manager — Company Details: Localisation
   • Base language code and name
   • Language Swap languages
   • Extreme character Unicode (hex)
3. Ledgers — Ledger Manager — Company Details: Data Control
   • Periods of Data Retention: Archive file prefix
4. Masters — Customers
   • Language
5. Masters — Suppliers
   • Language
6. Masters — Marketing
   • Language

Options Added

The following options have been added. For a full listing see the Program Options Listing window topic.

Feature Enhancements

Feature enhancements up to F0410 were released in maintenance updates to V3.1000. F0411 to F0487 were released in V3.10xx maintenance releases. F0488 onwards were released in V4.0000.

F0411 to F0487 V3.10xx Maintenance Released Features

Please refer to http://www.caliach.com/caliach/support/newfeatures/f31100.xml for details on these enhancements.

F0488 Full Support for Unicode

Caliach Vision V4 with Omnis Studio V5.2.2 for the first time fully supports Unicode both in the program and data. See the Unicode topic. This may effect your Keyword Search if you use special characters in your data, if so see also the Keyword System Settings topic. Extreme character control have been added to File — System Manager — Company Details, Localisation tab pane: MCDXUNI. Due to the introduction of Unicode all the use of National character fields has been deprecated and now all Character fields are kSimplechar subtype.

F0489 Mobile Device and Web Custom Extensions

With the introduction of Omnis Studio V5.2.2 you can now build all manner of mobile and web apps that can extend Caliach Vision outside the limitations of a local office network or VPN operation. Apps can be designed for iPhone, iPod, iPad, Android phones and tablets and Windows Mobile smartphones. The release of Omnis JavaScript Client, available as part of Omnis Studio means that one development can be used to support all these platforms. Caliach Vision does not contain any implementation of this as it is seen as too specific to a site and requires a specific type of infrastructure that most users would not have. However, while this item is not really a New Feature, it does extend the possibilities for some customers. To implement such a Custom Feature you would need:

• Specify an application design that needs mobile or web interactive connection to your Caliach Vision data and determine what target client platforms you want supported.
• Program the app using Omnis JavaScript Client remote forms, menus and tasks.
• Have a web server permanently connected to the Internet.
• Install and license Omnis Studio Web Server edition with an appropriate number of licensed users.

F0490 Integrated Engineering Text into Engineering Data

To rationalise a legacy anomaly in the datafile structure the Engineering Data Text file has been obsoleted and the Engineering Data record now contains the text previously held in the Engineering Data Text file. Conversion takes place automatically. However, legacy customised documents will need to be updated to reflect this, if they are to work in V4 and later. To fix: Change field ENTFILE.ENTTEXT to ENGFILE.ENGTEXT, then set it’s $nosecifempty=kTrue and delete the field ENTFILE.ENTSEQ. In WO documents change the ENTFILE.ENTTEXT field dataname to ENGFILE.ENGTEXT.

F0491 Some Menu Shortcut Keys have Changed

Three menu shortcut keys have changed to accommodate MacOSX use of Ctrl+W. Help – Window Tooltips is now Ctrl+T, Process – Capacity Planning – Show WC Make-to List is now Ctrl+A, and Process – Job Processing – Return Inventory from Job has no shortcut key.

F0492 Method Performance Analysis

Method Performance Analysis feature has been added to File – System Manager – System Timing Test. This allows method performance measurements for program operations. For details see the Method Performance Analysis topic.

F0493 Allow Copy Property for Read Fields

The AllowCopy property has been added to Schemes for Read Fields and Combo Boxes. If switched on, it allows you to select data in read-only fields and copy your selection to the clipboard. By default the Schemes have this property on.

F0494 Vertically Aligned Text on all Windows

A new capability of aligning labels and fields has been implemented to keep texts in line when a style contains different font sizes. It also improves cross-platform appearance consistency. Incorporates the new $vertcentertext property.

F0495 Archive File Prefix added for Ledgers

The field MCDAPRE has been added to Ledgers – Ledger Manager – Control Settings, Data Control tab pane in the Periods of Data Retention group. The Archive file prefix is used to differentiate ledger archive files from one data file to another when multiple-companies use different datafiles.

F0496 Improved File Filter Control for Open/Save Files

Added a new centralised system for setting file filters on open/save file dialogues to handle better the special requirements of MacOSX file types and suffixes. Use of oTerminal.$GetFilter(pType) to set the file filter sting parameter on all platforms in all locations where open/save file dialogues.

F0497 Language Swap Translation of Data

Language Swap feature has been implemented that adds the <datafile>.lng datafile. For ODB there is a new LangName parameter in optODBDatafile terminal options. A Language Swap Maintenance by File line has been added to the Advanced menu. A Translate for Language Swap line has been added to ScratchPad menu that operates on appropriate windows. These two menu lines controls access to Language Swap maintenance. Master maintenance windows have had icon buttons added to invoke Language Swap maintenance. A new system option optLangSwapBlockUsers has been added to control access to languages in the new Language Swap droplist on main toolbar. For a full explanation of the Language Swap system see the Introduction to the Language Swap System topic.

Language Code fields have been added to Marketing, Customers and Suppliers: DEALANG, CUSLANG, SUPLANG. Language Swap controls have been added to File — System Manager — Company Details, Localisation tab pane: MCDLANL, MCDLANN, MCDSWAP and MCDXUNI.

F0498 Data Views

Data Views is a method of encapsulating a data collection design for a graph, list or report. They can have stored results that can be called up for comparisons. Data View designs are stored and can be downloaded from www.caliach.com. For a full explanation of the Data Views see the Introduction to the Data Views topic.

F0499 Graphs 2 (second generation graphs and meters)

A Graphs 2 design environment has been added to design complex graphs with Data View data collection. Graph 2 designs are stored and can be called up on reports and windows and they can be downloaded from www.caliach.com. For a full explanation of the Graphs 2 see the Introduction to the Graphs 2 topic. See below for Known Issues in V4.0000 and Omnis Studio V5.2.2 concerning Graphs 2.

F0500 Key Performance Indicators

A Key Performance Indicators (KBI) feature has been added to exploit Graphs and Data View to display to users on a regular basis. KPIs can be viewed collectively on a single window or individually. For more details see the Key Performance Indicator Maintenance topic.

F0501 Marketing Letters can have Graphic Signature Imbedded

A new report class named rMarketLetterSig can be used for Standard Letters that, when printed, contain a contain graphic image of a scanned signature. For details see the end section of Standard Letter Text Maintenance window help.

Effect of Upgrade on Customisation

Due to the migration to Unicode and some subtle changes in Omnis 5.5 it is recommended for full compliance with Unicode the following changes should be made to your customisation having copied your custom classes into the V4.00 OpenVision.lbs and before deployment:

1. In the design browser right-click on the OpenVision library in the Folders tree, and operate Check…. This will rebuild method indexes and improve subsequent performance.
2. Using Edit — Find and Replace to change the following: chr(13) to kCr, chr(9) to kTab, chr(10) to kLf, chr(1) to unichr(32), for chr(asc(value,len(value))+1) like constructs, chr( needs changing
   to unichr( and asc( to unicode(. Replace all asc( with unicode(.
3. With any import of key values (such as part numbers, customer codes etc), good practice would demand the use of Calculate <value> as nfc(<value>) to ensure string canconical normalisation.
4. Any references to ENTFILE and ENTTEXT should be resolved to ENGTEXT – common with custom Work Orders.
5. Where you may want to exploit the new Language Swap feature custom reports should be modified to the standard outlined in the Introduction to the Language Swap System Reports section.

Known Issues in V4.0000 and Omnis Studio V5.2.2

The following issues are known to exist and should be resolved in a future release of Omnis Studio or Brainy Data software:

• The current PDFDevice V2.62 does not handle Pseudo Fonts and some Unicode character. It displays them as control characters. Fonts supporting non-roman scripts are available and PDFDevice will support them, for example Arial Unicode MS, available from Microsoft.
• Omnis Studio V5.2.2 HTML Control (Help Window) does not handle <br> tags correctly (ST/EC/1297), does not link to a named page reference (ST/EC/1291) or highlight words, as advertised (ST/EC/1292). It also does not resolve the &apos; entity (ST/HP/086) and Help Progect Manager does not interpret Unicode words and characters in words (ST/HP/085).
• Omnis Studio V5.2.2 implementation of right-to-left script entry (e.g. Arabic) is problematic and subject to enhancement requests (ST/DB/790 and ST/HE/1075) so Caliach Vision’s implementation of this is pending.
• Omnis Studio V5.2.2 fails to recognise the $cinst item reference for an Object that inherits a superclass. This did effect correct operation of the Graphs2 implementation but a work-around has been found (ST/NT/666).
• Omnis Studio V5.2.2 Graphs 2 does not correctly implement the $setlinearaxis method. This prevents label control of the axis (ST/GF/310 – Unresolved. Fault in chartdirector. Vendor Limitation).
• Omnis Studio V5.2.2 Graphs 2 $addcustomlabel() does not have a dataSet parameter. This prevents it’s full use (ST/GF/328)
• Omnis Studio V5.2.2 Graphs 2 $setlogscale(kG2axisX) does not work correctly. (ST/GF/328)
• Omnis Studio V5.2.2 Graphs 2 $formatvalue() does not work with a non-visual Graph2 object. (ST/GF/329)
• Omnis Studio V5.2.2 Graphs 2 $angularlabelson parameter can not be assigned correctly. (ST/GF/330)
• Omnis Studio V5.2.2 Graphs 2 $shadow is not documented correctly. (ST/GF/331)
• Omnis Studio V5.2.2 Graphs 2 $slicemove() does not work with an end range. (ST/GF/332)

Caliach Vision V4.0000 Vital Statistics

Compiled in Program Version 5.10. Help data last modified 4 Feb 2013 12:53:00.00. No class.

Reference Contents > Introduction > What is New in Version 4.00

The post Introduction: What is New in Version 4.00 appeared first on Caliach.

What is New in Version 4.10

Reference Contents > Introduction > What is New in Version 4.10

Caliach Vision V4.10 operates with Omnis Studio V5.2.2 or greater.

The following relates to changes made since V4.0000.

New Installers

Caliach have introduced a new installer from BitRock and a new resulting file structure that integrates Omnis Studio into the Caliach Vision folder structure so that just one location on your computer contains all files related to Caliach Vision operation. For Microsoft Windows Vista, Server 2008 and 7, this breaks the convention of placing executable files in the Program Files folder of the C drive and the subsequent security enforcement of UAC. However, it is our view that this breach is well worth it for the convenience and of a simple, compact, self-contained and integrated structure.

There are in all 4 installers. A full and demonstration version of each of our supported platforms, Windows and MacOSX. The Demonstration edition contains pre-licensed Caliach Vision and Omnis Studio Runtime. The Full edition contains a full set of Caliach Vision files and both Omnis Studio Runtime and Design programs with user control to include the Design program, typically only needed by the system manager. All version include our 9 additional program languages.

Unlike in the past the installer by default names the folder containing the installation with the version number, so the full version will go to C:CaliachVision-4.10. If that already exists files within it will always be overwritten. Extra files you have created such as Archive files will still remain but if you have archive or custom files from an older version, it is left to you to copy them to the new folder structure from the old one.

Summary of adjustments you may want to make to your converted data:

1. -none-

Menus items that have been added are:

1. File — Change Language

NOTE: The new Change Language sub-menu is not subject to privileges control.

Window Tab Panes that have been added are:

1. -none-

Fields you may want to populate

1. -none-

Options Added

The following options have been added. For a full listing see the Program Options Listing window topic.

Feature Enhancements

Feature enhancements up to F0513 were released in maintenance updates to V4.0000. F0514 was released in V4.1000.

F0503 to F0513 V4.00xx Maintenance Released Features

Please refer to http://www.caliach.com/caliach/support/newfeatures/f40100.xml for details on these enhancements.

F0514 Dynamic Program Language Change

One installation supports program running in any number of languages with menu control of current visible language. Language translations maintained in individual databases and string files in Extras. Help in multiple languages also dynamically supported. Omnis localisation also can change dynamically. Effects all windows, reports, menus, toolbars, tasks with non-English text substitution from database. Class descriptions and file and field descriptions also translated. New multi-lingual installer and supporting documentation. Extensive revision of Xlate plug-in functionality. For full details see the Program Language Menu topic.

Effect of Upgrade on Customisation

There are no major issues with customisation compliant with V4.00 with one minor exception:

1. Customised reports will not naturally dynamically translate into non-English. However they can be made to do so with the addition of a class method named $MasterClass with a single line of code Quit method ‘<StandardClassName>’. With that any standard class translations are mapped onto the custom report when opened.

Known Issues in V4.1000 and Omnis Studio V5.2.3.1

The following issues are known to exist and may be resolved in a future release of Omnis Studio (the previous issue with Unicode characters in PDF documents has been resolved in this release:

• Omnis Studio V5.2.3.1 HTML Control (Help Window) does not handle <br> tags correctly (ST/EC/1297), does not link to a named page reference (ST/EC/1291) or highlight words, as advertised (ST/EC/1292). It also does not resolve the &apos; entity (ST/HP/086) and Help Progect Manager does not interpret Unicode words and characters in words (ST/HP/085).
• Omnis Studio V5.2.3.1 implementation of right-to-left script entry (e.g. Arabic) is problematic and subject to enhancement requests (ST/DB/790 and ST/HE/1075) so Caliach Vision’s implementation of this is pending.
• Omnis Studio V5.2..3.1 Graphs 2 does not correctly implement the $setlinearaxis method. This prevents label control of the axis (ST/GF/310 – Unresolved. Fault in chartdirector. Vendor Limitation).
• Omnis Studio V5.2.3.1 Graphs 2 $addcustomlabel() does not have a dataSet parameter. This prevents its full use (ST/GF/328)
• Omnis Studio V5.2.3.1 Graphs 2 $setlogscale(kG2axisX) does not work correctly. (ST/GF/328)
• Omnis Studio V5.2.3.1 Graphs 2 $formatvalue() does not work with a non-visual Graph2 object. (ST/GF/329)
• Omnis Studio V5.2.3.1 Graphs 2 $angularlabelson parameter can not be assigned correctly. (ST/GF/330)
• Omnis Studio V5.2.3.1 Graphs 2 $shadow is not documented correctly. (ST/GF/331)
• Omnis Studio V5.2.3.1 Graphs 2 $slicemove() does not work with an end range. (ST/GF/332)

Caliach Vision V4.1000 Vital Statistics

Compiled in Program Version 5.10. Help data last modified 7 Sep 2013 09:15:00.00. No class.

Reference Contents > Introduction > What is New in Version 4.10

The post Introduction: What is New in Version 4.10 appeared first on Caliach.

What is New in Version 5.00

Reference Contents > Introduction > What is New in Version 5.00

Caliach Vision V5.00 operates with Omnis Studio V6.10 or greater.

The following relates to changes made since V4.1000.

Database Change to Client-Server SQL

Caliach Vision V5.00 has been rewritten from V4.10 to use an external SQL Database Server engine. In previous versions the program used the Omnis Native Datafile system. Although this was remarkably successful and reliable it is essentially 1980’s technology that since the early 1990s has not been enhanced, has limits of scale and is not transaction-safe. Modern server-based data engines offer much greater scalability, greatly improved performance and are extremely robust even under heavy multi-user loads. The program functionality has remained substantially the same as V4.10 with some additions to accommodate SQL management and some utility functionality has been deprecated. For an introduction see Client-Server SQL Introduction

What has changed as a consequence can be summarised as follows:

• The four datafiles have been merged into one database, improving performance.
• Built-in SQLite is available for single-user systems. PostgreSQL, MySQL or MariaDB can be used for multi-user sites and requires server installation.
• There are two new auxiliary databases, both of which are local or server SQLite databases. These are User Logon Settings (ExtrasLogon.db) and Dynamic Queries, Sort Sets and SQL Statements (ExtrasStatements.db). Other auxiliary datafiles have been migrated to SQLite databases – CustomLanguage.db, CustomTranslate.db, CustomHelpData.db, CustomWishBugs.db. ProgUser.db has replaced ProgCode.usa and ProgSyst.db has replaced ProgCode.upt.
• A Migration Tool is provided to migrate data, including custom data, from V4.10 into your target server database.
• All activities that write to the database are encapsulated as single-bound-transactions, providing conflict-free robustness with optimal performance. Either everything together is posted permanently or nothing is. Users can never see the data in a half-processed state.
• Most reporting now uses a new structured mechanism for collecting data for presentation. Most report windows now contain Adhoc extra where, Adhoc pre-sort, Reverse sort and Limit fields giving much greater flexibility to get just what you want. Modern server engines use sophisticated optimisation to maximise performance on complex data retrival tasks. As the server now does the work involved network trafic is vastly reduced.
• These changes mean that all customisation must be re-written for the new data standards. Reports must be re-built using the new standard reports provided in OpenVision. Custom code and Plug-ins must be professionally rewritten. There are no conversion tools but so that you can see your old designs without corruption a V4to5OpenVision library tool is provided.
• Stored designs that access data such as Custom Searches, Sales Document Configurations, Data Views, Workflow Alerts and Workflow Triggers will mostly need to be modified to conform to new standards and the use of Omnis functions and syntax must be changed to SQL that can be understood by the server engine.
• Runs under Omnis Studio 6.10. This is a 64-bit executable on Windows and 32-bit on MacOSX. The design edition of Omnis is now an optional extra that needs an individually purchased license key.
• Omnis Studio V6.10 has removed support for the old graphs external that was used in Ad Hoc Graphs. This was already unavailable to Mac users. We have dropped Ad Hoc Graphs as a consequence.

What Menu Items are New?

What Menu Items Have Disappeared

Terminology

With the move to SQL (Structured Query Language) there is a need to change the terminology used in the past with Omnis Datafiles:

Database has replaced the word Datafile. SQLite uses a single operating system file for a single database whereas server database engines can have many databases within them. Caliach Vision connects to one named databse at a time (except for the Copy Database function).

Table has replaced the word File that was used to describe a data set in OND. Tables can be thought of as spreadsheet pages with a defined number of columns and 1 or many rows. There are many tables in a database. A table is defined as having a number of columns, each of a particular data type. For example the parts master table (PTMFILE) has a part number column and a description column. Each entry in the parts master is a row of data with the same columns.

Column has replaced the word Field that now can revert to it’s generally understood meaning of the box you type data into on a window. The field on the window often maps onto a table column in the data.

Row has replaced the word Record that was used to describe an entry in a table.

Schema classes and Table classes have replaced File classes inside Caliach Vision. There is one Schema for each Table (or old File) of data. On client-server data systems the server must hold the data structure but Caliach Vision needs this too. Schemas provide for that and mechanisms are automatically applied to synchronise the server engine if changes occur in the Schemas, rebuilding data if needs be. While Schemas are just data definition repositories, Table classes are mapped dynamic objects that contain functional programming code for data retrieval and manipulation. The two together work hand in glove to connect to the server engine through DAMs (Data Access Managers) which can be thought of as software drivers for communication and translation for a specific engine, SQLite, PostgreSQL and MySQL (MariaDB is a shoe-in for MySQL).

Installers

Caliach have maintained the V4.10-style installation that integrates Omnis Studio into the Caliach Vision folder structure so that just one location on your computer contains all files related to Caliach Vision operation. For Microsoft Windows Vista, Server 2008, 7, 8 and 8.1 this breaks the convention of placing executable files in the Program Files folder of the C drive and the subsequent security enforcement of UAC. However, it is our view that this breach is well worth it for the convenience and of a simple, compact, self-contained and integrated structure.

There are in all 4 installers. A full and demonstration version of each of our supported platforms, Windows and MacOSX. The Demonstration edition contains pre-licensed Caliach Vision and Omnis Studio Runtime and operates on a SQLite engine. The Full edition contains a full set of Caliach Vision files and both Omnis Studio Runtime and Design programs with user control to include the Design program, typically only needed by the system manager. All versions include our 10 additional program languages. However, unlike V4.10 there is now only one TrainingDemo database which when used on the demonstration license self-translates the data to your selected language dynamically.

The installer by default names the folder containing the installation with the version number, so the full version will go to C:CaliachVision-5.00. If that already exists files within it will always be overwritten. Extra files you have created such as Archive files will still remain but if you have archive or custom files from an older version, it is left to you to copy them to the new folder structure from the old one.

Summary of adjustments you may want to make to your converted data:

1. -none-

Menus items that have been added are:

1. -see above-

Window Tab Panes that have been added are:

1. File — Advanced — SQL Statements Manager

Fields you may want to populate

1. -none-

Options Added and Obsoleted

The following options have been added. For a full listing see the Program Options Listing window topic.

The following options have been and one obsoleted in V5.00 and are no longer used.

Feature Enhancements

Feature enhancements up to F0513 were released in maintenance updates to V4.0000. F0514 was released in V4.1000.

F0515 to F0520 V4.10xx Maintenance Released Features

Please refer to http://www.caliach.com/caliach/support/newfeatures/f40100.xml for details on these enhancements.

F0521 Migration to SQL Client-Server Data and disuse of OND

Change in the data access and management from Omnis local database (OND) to client-server SQL using SQLite, PostgreSQL, MySQL or MariaDB. All auxiliary datafiles moved to SQLite databases. Addition of Logon.db and Statements.db. Full functionality of V4.1003 retained. Special migration and re-customisation required.

Help Page Additions and Removals

As a result of F0521 feature enhancement the following help pages have been added:

• Client-Server SQL Introduction
• Logon to Server — Database Connection Settings window
• Logon to Server — Logon window
• Data Selection windows everywhere — Ad Hoc Where and Sort Fields Menu
• Data Selection windows everywhere — Columns Available in Tables window
• Data Selection windows everywhere — SQL Explain Query Review window
• File — Preferences — SQL Log Review window
• File — System Manager — Data View Design — Statement Dynamic Query Selection window
• File — System Manager — Monitor — User Logon Sessions window
• File — Advanced — SQL Statement Manager window

As a result also of F0521 feature enhancement the following help pages have been removed:

• General — Ad Hoc Graphs
• General — Ad Hoc Reports
• General — Datafile and Omnis Data Bridge
• General — User Login (wInitials)
• Advanced — Data File Sizing
• Advanced — OCBD Settings
• Advanced — DataFix Menu
• Advanced — DataFix Window
• Advanced Specials — Set Files Read/Write
• Advanced Specials — 3Com Palm III Data Transfer

Effect of Upgrade on Customisation

No customisation made for pre-V5.00 will function correctly:

1. The CRB (Current Record Buffer) that is a global memory area into which file data is loaded when a Find was performed has been eliminated. All data retrieved from the server must be held in list or row variables and exists only while they are in scope. If you copy say a report class into Open Vision your old field datanames will appear as #???. This is because the old field names are unknown as of V5.
2. Custom code written before V5 needs to be migrated to eliminate references to the CRB, remove any use of DML (Data Manipulation Language) such as Find, Single file find, etc. and the use of $files, $loadcols, $assigncols, $sort and $search without $ref prefixing column names rewritten. Effectively you are better off having code in your customisation professionally re-written by Caliach.

Known Issues in V5.0000 and Omnis Studio V6.10

The following issues are known to exist and may be resolved in a future release of Omnis Studio:

• Omnis Studio V5.2.3.1 HTML Control (Help Window) does not handle <br> tags correctly (ST/EC/1297), does not link to a named page reference (ST/EC/1291) or highlight words, as advertised (ST/EC/1292). It also does not resolve the &apos; entity (ST/HP/086) and Help Progect Manager does not interpret Unicode words and characters in words (ST/HP/085).
• Omnis Studio V5.2.3.1 implementation of right-to-left script entry (e.g. Arabic) is problematic and subject to enhancement requests (ST/DB/790 and ST/HE/1075) so Caliach Vision’s implementation of this is pending.
• Omnis Studio V5.2..3.1 Graphs 2 does not correctly implement the $setlinearaxis method. This prevents label control of the axis (ST/GF/310 – Unresolved. Fault in chartdirector. Vendor Limitation).
• Omnis Studio V5.2.3.1 Graphs 2 $addcustomlabel() does not have a dataSet parameter. This prevents its full use (ST/GF/328)
• Omnis Studio V5.2.3.1 Graphs 2 $setlogscale(kG2axisX) does not work correctly. (ST/GF/328)
• Omnis Studio V5.2.3.1 Graphs 2 $formatvalue() does not work with a non-visual Graph2 object. (ST/GF/329)
• Omnis Studio V5.2.3.1 Graphs 2 $angularlabelson parameter can not be assigned correctly. (ST/GF/330)
• Omnis Studio V5.2.3.1 Graphs 2 $shadow is not documented correctly. (ST/GF/331)
• Omnis Studio V5.2.3.1 Graphs 2 $slicemove() does not work with an end range. (ST/GF/332)

Caliach Vision V5.0000 Vital Statistics

Compiled in Program Version 5.10. Help data last modified 5 Feb 2015 04:35:00.00. No class.

Reference Contents > Introduction > What is New in Version 5.00

The post Introduction: What is New in Version 5.00 appeared first on Caliach.

What is New in Version 5.10

Reference Contents > Introduction > What is New in Version 5.10

Caliach Vision V5.10 operates with Omnis Studio V8.1.2.

The following relates to changes made since V5.0408.

Omnis Studio V8.1.2 and macOS Changes

Caliach Vision V5.10xx is released to run only with Omnis Studio V8.1.x. This release of Omnis Studio is the only one certified and supported by Omnis Software to operate under macOS 10.13, known as High Sierra. Previous versions of Omnis under macOS were written using the Carbon API, which was 32bit. After 3 years of work Omnis have migrated to the 64bit Cocao API and V8 was the first to take advantage of that work. On the surface this will not be noticable to users, except for improved performance. It is however an important step as Apple have warned that 32bit support will not survive beyond macOS 10.13. This means in practice that Caliach Vision V5.1000 will be the only version that is certified to run of macOS 10.13 and future Apple Macs.

Database Structure Changes

Tables Added

The following Tables have been added in V5.1000.

The following columns have been added or changed:

Columns Added or Changed

What Menu Items are New?

Options Added

The following options have been added. For a full listing see the Program Options Listing window topic.

Feature Enhancements

Feature enhancements up to F00618 were released in maintenance updates to V5.0408. F0619 was released in V5.1000.

F0503 to F0513 V5.00xx to V5.04xx Maintenance Released Features

Please refer to http://www.caliach.com/caliach/support/newfeatures/f50000.xml for details on these enhancements.

F0619 Stored report destination added

A new Report Destination has been added. Reports sent to Storage are printed to an internal binary format and then saved into the main database. These Storage reports can then be printed to a normal destination on future occasions by any users with appropriate privileges. The report is saved in a compressed binary format in a new REPFILE table under a name and subject with user and group privileges and extra information associated with emails, such that an email can be subsequently sent. They are then available from File — Print Stored Report and can be eleted or corrected in File — Advanced — Stored Report Maintenance.

F0620 Windows can now resize large objects in a proportional manner when resized

Windows now can resize large objects (lists, multi-line entry coxes, etc) in a proportional manner rather than relying on a single edge-float property. The moving and resizing of objects when resizing a window typically use an edge-float property of the object that in turn relied on the operating system to perform the resizing or moving. This has it’s limitations when many large objects exist together on a window. For example, on the Text pane of the Part Maintenance window where there are 6 large text entry boxes, only the right 3 could expand horizontally and the bottom 2 expand vertically. The ideal is that all 6 expand in a similar way – for width movement by 50% each, and for height by 33.3% each. This proportional behavior does not use the edge-float property and operating system functionality. So as you resize the window with the mouse, the objects do not progressively move. When you finish the resize by releasing the mouse, the objects snap to their new proportional position and size.

F0621 More expansive OK message window for Server error messages

A new re-sizable windows is used for SQL server messages. Such messages can contain more text than can be displayed in a normal OK message. With some server engines the messages can point to statement syntax errors, which needs a monospaced font for that to be useful. Hence the window contains a font switch button.

F0622 Team Calendar display modes added

Team Calendar window display has new display modes. Day, Week and Fortnight views can be in List mode alternatives. Month view has a Digest alternative. There is a new Year Digest view.

F0623 Ledger transactions now have server created datetime and cleared datetime

Ledger transactions now have a created datetime column set by the server. This is separate from the Date column that can be set appropriate to various accounting requirements. In addition there is now a cleared datetime and cleared user Id column so the chronology of allocation and bank reconciliation is recorded. This enables more consistent reports to be produced that can be accurately compared to Bank Statements.

F0624 Additional columns added to improve historical analysis

Additional columns have been added to a number of tables to make historic analysis easier and with better performance. In inventory history the STHDATE and STHTIME have been obsoleted in favor of STHDATT datetime. Work History has had 4 new columns added to allow improvements to KPIs: WOHDEPT records the work centre department. WOHWKCC records the work centre capacity at the time. WOHDEPC records the work centre’s departmental capacity. WOHPCDA record the WO’s planned completion date. Stock Transfers have an added User Id column for audit purposes. Purchase history has an additional PUHPODT column which is loaded with the Purchase Order date. Period Log has an added column holding the process time in seconds. A Program file path for Mac platform column has been added to Link Types.

F0625 optSODisableSohninv to disable the No Invoice checkbox added

A system-level option has been added: optSODisableSohninv Set to 1 will disable the No Invoice on Dispatch checkbox on Sales Order Maintenance. This will NOT prevent it being inheritted from the customer’s default, this option in-effect enforces it.

F0626 Company Details and System Preferences single-user save reduced

Data changes in Company Details, System Preferences and Ledgers Control Settings that need single-user to save have been minimised. Most changes can be saved normally.

F0627 Change All Component Quantities advanced special function accepts drag-and-drop

Change All Component Quantities by a Factor can now be driven by drag-and-drop of multiple parts from the Parts ScratchPad or BoM Listing windows.

F0628 Users are now warned of excessive LogoffDump…txt files.

Users are now warned when 5 or more LogoffDump… files accumulate, with an auto-delete option. The process is performed when closing the About Caliach Vision window.

F0629 Headed List column justifications was been moved into the lists themselves

The column justification (left, right or centre) was controlled along with user changed characteristics such as column widths inside user settings, despite the user having no control over justification. This was a historic anomaly and could lead to column justification being lost and it added complication if columns were added in updates. Column justifications are now set explicitly in a $SetListColAlign method run by the universal window superclass.

F0630 Expired User Token cleansing has been subtly changed to assist forced re-login

Before this change, on user logon all current user tokens were expired, they would all be deleted. This recovery mechanism had the effect in some sites, especially with few users, that it was common for an idle user to have to re-logon especially at times of low activity. The problem is to balance off the interests of post-server-crash recovery and the convenience of users in low-activity circumstances. Some subtle changes have been made. Now, when finding all tokens idle, first any idle tokens with the same user ID will be removed. Then, other idle tokens are only deleted if there are at least 50% of the licensed user. This limits the clean-out in particular in small sites. This does mean, however, that it is possible for dead (very idle) tokens can persist in an untidy way. So there is one addition to the File — System Manager — Monitor window, which identifies idle tokens of more than 6 hours and offers you the opportunity to clear them.

F0631 Option optAcApPayNowTexts added to set AP payments reference and comments

Option added to set the values of document reference and comment on the Pay Now payment transaction. Set option optAcApPayNowTexts to two strings seperated by a comma. These will be used to set the Document Ref. and Comment of the payment transaction. Use the token % to imbed the original transaction document reference.

Caliach Vision V5.1000 Vital Statistics

Compiled in Program Version 5.10. Help data last modified 25 Oct 2017 04:30:08.00. No class.

Reference Contents > Introduction > What is New in Version 5.10

The post Introduction: What is New in Version 5.10 appeared first on Caliach.

About the Help and Reference Book

Reference Contents > Introduction > About the Help and Reference Book

Help and the Reference Book for Caliach Vision derive from the same source and are constructed using a number of software technologies. It is available in HTML form that can be viewed interactively within Caliach Vision itself or by using an Internet Browser. It is also available in Adobe Acrobat PDF form to be viewed and printed by Adobe Acrobat Reader. Hyperlinks are numerous and so it is recommended that it be viewed on computer in either help or pdf form rather than printed.

The Reference Book in PDF form contains many illustrations that are not included in the Help version. If you are viewing the Reference Book using Adobe Acrobat graphics are best viewed at 167%. Printing to any reasonable resolution printer will show the graphics at 60% true size.

The Reference Book is subject-based. It is structured around the program’s Task and Menu structure with HTML pages for each window, menu and taskbar associated with a task. Those not associated with a specific task can be found in the General section.

See the Help Menu topic for an introduction to using the help system.

Generally, it is a good idea to review the Menu of a topic first. In many cases general introductory information is provided in the Menu help. You can also use this topic to navigate through the links to the menu function of interest.

Special Paragraphs

Throughout the Help and Reference Book special notes, warnings and tips are included in the following form.

Software Development Major Release History

Caliach Vision was a development from the experience of CaliachMRP, a software system first released in 1990.

Compiled in Program Version 5.10. Help data last modified 14 Sep 2017 05:05:00.00. No class.

Reference Contents > Introduction > About the Help and Reference Book

The post Introduction: About the Help and Reference Book appeared first on Caliach.

Introduction Topic Contents

Reference Contents

Most topics are related directly to functional windows, menus or toolbars. Click on the topic to view details.

• About the Help and Reference Book
• Installation of Caliach Vision on a Network
• Migrating to Caliach Vision from CaliachMRP
• Upgrading Caliach Vision to V1.10 from Earlier Versions
• Upgrading Caliach Vision to V3.00 from Earlier Versions
• Upgrading Caliach Vision to V5.xx from Earlier Versions
• Upgrading Caliach Vision to a New Version
• What is New in Version 1.10
• What is New in Version 1.20
• What is New in Version 1.30
• What is New in Version 2.00
• What is New in Version 2.10
• What is New in Version 3.00
• What is New in Version 3.10
• What is New in Version 4.00
• What is New in Version 4.10
• What is New in Version 5.00
• What is New in Version 5.10

Reference Contents

The post Introduction Topic Contents appeared first on Caliach.

Installation of Caliach Vision on a Network

Reference Contents > Introduction > Installation of Caliach Vision on a Network

Installation of Caliach Vision has evolved with various versions of the program. Before V5 the database used is a local-area-network system built in the Omnis Studio which could reside anywhere on your local machine or network (assuming network systems permitted). From V5 onwards, with the exception of single user installations such as the demonstration edition, the database is held by a server installed DBMS (PostgreSQL or MySQL).

Caliach Vision V3.10 onward can be downloaded as a self-contained installer, inclusive of Omnis Studio. The actual executable files for Omnis Studio are specific to particular operating systems whereas Caliach Vision files are all cross platform.

Version 3.1 to V4.1

Caliach Vision can operate on a single computer but it is more common for it to be installed on a multi-user network. In this case, as a minimum the datafile must be located on the server. However, you then have the option of having a Server Installation or a Local Installation.

Advantages of a Server Installation:

1. Installation for a site is much faster and simpler – access can be given to a design and/or runtime just by selecting the appropriate shortcut from the distribution directory. Normally the installation is on the system manager’s machine, carry out any updates and then copy to the server. It is not necessary even to leave the supporting directories on the managers machine – simple is best!
2. Likewise, propagation of a major upgrade is simpler, only requiring the vision.lbs to be copied from the distribution directory on the server (after being updated) to each machine on completion.
3. Omnis Studio upgrades are much quicker, not requiring any work on client PCs.
4. Everybody is using the same installation, making query resolution easier.
5. Storage requirement on PC’s is much reduced.
6. All documents can be held centrally, with only shortcuts being needed on PCs.

Disadvantages of a Server Installation:

1. You cannot copy the datafile to another location without the supporting directories (otherwise the library will not run when you try to connect to it, and in fact the only way to get it to run ever again is to copy the directories to the location of the datafile it is locked on to).
2. You must maintain master PCs for full installations of Omnis Studio for NT and 9x, particularly as the new Omnis Studio Windows installer is now the same for NT and 9x and needs to work out which system to install for.
3. To do a major upgrade of Vision, it is necessary to (temporarily) copy the supporting directories into the Vision directory on the first machine being upgraded, and MOVE them back when the upgraded is finished.

The following illustrates a typical server structure. The Data directory would be located on the server with the contents of the Distribution directory being copied to each user computer. Other directories are for the Omnis Studio installations needed to accommodate the operating systems being used by the user computers. The configuration is shown for Windows operating systems, the principals apply similarly to other operating systems.

V5.00 Onwards

With the introduction of client-server technology, the need for a central network location for supporting files that are common to all users is still required. However, unlike earlier versions it’s location can not be assumed by the program, it must be explicitly defined. This is done with an entry in the Terminal/Terminal.inf file. The optServerFolder option must contain the absolute path to the Server Folder on a server that all users have access to at all times.

optServerFolder=Z:PublicAreaCaliachServerFolder

If optServerFolder is missing or blank, the program will fall back on folders local to Vision.lbs. If the path is unavailable when the program starts, a message will warn that you are not connecting.

The contents of the Server Folder are optional, but most typically are:

• Archive folder
• Extras folder
• Help folder
• ProgSyst.db
• ProgUser.db

V5.04 Onwards

From V5.0400 the supporting Strings-??.stb, LangDynamic-??.db and Statements.db were all relocated from the Extras folder, that typically could be in the Server Folder, to the Terminal folder that can only be in the same folder as Vision.lbs.

Compiled in Program Version 5.10. Help data last modified 4 Aug 2016 04:10:00.00. No class.

Reference Contents > Introduction > Installation of Caliach Vision on a Network

The post Introduction: Installation of Caliach Vision on a Network appeared first on Caliach.