amos business suite vrs. 9.1 release notes rev2

AMOS Business Suite

version 9.1.00

Release Notes

Revision 2, November 2009

AMOS Business Suite -- Release Notes version 9.1.00 ii

Documentation Copyright and Disclaimer

Copyright

Copyright � 2009 SpecTec Group Holding Ltd. Limassol, Cyprus, World rights reserved. No part of this publicationmay be stored in a retrieval system, transmitted or reproduced in any way, including but not limited to photocopy,photography,magnetic or other record,without the prior agreement andwritten permission fromSpecTecGroupHoldingLtd. Documentation office.

Furthermore, unless specifically stated in the Software PurchaseAgreement duly signed by both SpecTecGroupHoldingLtd. and the user, the user will not distribute, reproduce, or allow access to by a third party this documentation, withoutthe prior, written approval from SpecTec Group Holding Ltd. Documentation office.

Whenever an authorised copy is made of all or any part of the documentation, all titles, copyright notices, patent noticesor other proprietary markings must also be reproduced in full and included with the copied product. The User shall notalter or remove any copyright notices, patent notices or other proprietary markings affixed to or distributed throughoutthe documentation.

Disclaimer

SpecTec Group Holding Ltd. makes every effort to ensure the information contained in this document is correct at thetime of printing. However, as products of SpecTec Group Holding Ltd. are constantly being updated and maintained,discrepancies may arise from time to time between this documentation and the Product to which it applies. SpecTecGroup Holding Ltd. makes no representations or warranties regarding the content or accuracy of the documentation, andspecifically disclaims any implied warranties of merchantability of fitness for any particular purpose. Furthermore,SpecTec Group Holding Ltd. reserves the right to make documentation changes from time to time in regards to style,layout, and content without any obligation by SpecTec Group Holding Ltd. to notify any person of such changes orprovide users with updated documentation revisions.

Trademarks

All brand and product names to be found in this document or the product to which it applies are trademarks of theirrespective companies.

AMOS Business Suite -- Release Notes version 9.1.00 iii

IMPORTANT

This release of the AMOS Business Suite is a full installation. Please ensure that

you follow in--house back--up procedures prior to installation.

If you are upgrading from earlier versions of AMOS products than those

immediately prior to this release, we recommend that you read all release notes

for the versions in between to familiarise yourself with the changes that have

been made to the application between your current version and this one.

Problems may be encountered when attempting to open context sensitive help

files (CHM format) from a network client machine. This can be rectified by

mapping the installation directory on the server to anetwork drive on each client

machine and then setting the default directory parameter on the client to point

at the mapped drive. To use the PDF Help, please rename the file ’amosmp.pdf’

found in the Help folder in the installation folder, to ’amosw.pdf’.

The context sensitive help files for some products are still under development,

so the information on some help pages may be incomplete.

A new parameter was introduced with patch 8.6.19, Prevent Update on

Quotation with Selected Vendor. Customers who applied that patch and set the

parameter, will need to check/reset the parameter after upgrading to version 9

or above.

AMOS Business Suite -- Release Notes version 9.1.00 1

1 Introduction

1.1 About this ReleaseAs of this release, the individual module versions are alignedwith the version numberof the AMOS Business Suite. This release comprises the following module versions:

AMOS Maintenance and Purchase 9.1.00

AMOS Quality and Safety 9.1.00

AMOS Voyage Management 9.1.00

AMOS Personnel 9.1.00

1.2 CompatibilityThe AMOS Business Suite version 9.1.00 has been tested on the following:

Windows2008 ServerEnterpriseEdition

Windows2003 ServerEnterpriseEdition SP2

Windows XPSP3

WindowsVistaEnterpriseEdition SP1

ASA9.00.02.3642

X X

ASA10.01.3579

X X X

ASA11.0.1.2308

X

Oracle 9.2 X

Oracle 10.02 X X X

Oracle 11g X

MS SQL20059.00.3215.00

X X X

MS SQL200810.0.1600.22

X

The AMOS Business Suite version 9.1.00 supports the following:

32--bit OS:

� Windows 2003 Server SP2

� Windows XP SP3

� Windows Vista SP1

� Windows 2008 Server

DBMS:

� MS SQL 2005

� MS SQL 2008


� Oracle 9.2

� Oracle 10.02

� Oracle 11g

� ASA 9.0

� ASA 10.01

� ASA 11.0

AMOSBusiness Suite supports the above platformswithin their own boundaries. Forexample:MS SQL 2005Although a table can contain an unlimited umber of Foreign Key constraints, therecommended maximum is 253. MS SQL 2005 cannot process statements on recordsin a table that has more than this amount of Foreign Keys registered against it. Thisresults in being unable to delete a department from within AMOS (as the departmenttable has in excess of 350 Foregin Keys registered against it).

AMOS E--Business Direct (AMOS HTML) was tested on the following e--mail

clients:

Microsoft Outlook Express 6.0.2900.2180

Microsoft Office Outlook 2003 (11.5608.5606)

AMOS Mail versions 5.1 and 7.4

AMOS E--Business Direct (AMOS HTML) is compatible with:

Microsoft Internet Explorer version 5 or higher.

AMOS Business Suite version 9.1.00 is compiled using:

PowerBuilder Version 11.5 Build 3050

Reports made in Crystal Reports use version 10.0.0.533.


2 Common Functionality

2.1 Introduction

These release notes describe the changes made to AMOS Business Suite CommonFunctionality from version 9.0.00 to version 9.1.00.

2.2 Changes

The following changes have been made in this release.

2.2.1 Overview Panels

Using AMOS Overview Panels gives users a quick status overview in different areasof AMOS -- for example, an Overview Panel can be designed to display overduemaintenance work in several different ways -- gauges, ratios and graphs -- all in oneplace. These elements together comprise one Overview Panel.

The presentation of the gauges, graphs and ratios in the panels is fixed but the valueand value definitions are configurable. The settings for the two graphs are based ondata window syntax, which needs to be created in PowerBuilder data window painterand stored in a PBL file. Users can then import the syntax into AMOS.

Once configured, the Overview Panels are displayed in a dedicated window and theypresent current information regarding the status of the area of the application they applyto.

2.2.2 TMSA Yes/No and N/A Scoring

It is now possible to define KPIs to require a Yes or No answer and not a numericalscore. For these KPIs the user no longer has to use percentages to score the SelfAssessments but simply provide a Yes or No answer. It is also possible to defineKPIsto accept the answer N/A. If this option is allowed, and a user registers N/A as theanswer when scoring a Self Assessment, AMOS will prompt for a reason and enterthis in theRemarks field. To enable Yes/No and N/A answers, the Yes, No, and N/Ahave to be converted to percentages in order to calculate the overall KPI score. Thepercentages are defined in the system parameters using two new parameters, ’NotApplicable Score’ and ’Yes No Score’. Users can also define starting codes forsub--elements using the new parameter ’Sub Element Start Code’.

2.2.3 Notes Simultaneous Enhanced Templates

In AMOS 9.0 the ability to add enhanced templates to various tables was introduced.It is now also possible to add Notes text into these tables at the same time as anenhanced template is in use. Two new parameters work together to allow users tosimultaneously insertNote text andDetails, when runningwith an enhanced template:

’Editor -- Additional Detail Data on Unit Level’ and ’Editor -- Use Additional NoteField’.


2.2.4 Dragging and Dropping Attachments

AC#10615, 10614, 10814

It is possible to drag and drop attachments from for example the file explorer. Userscan now also drag and drop attachments from an email client. New parameters are inplace to control this functionality:

� Attachments Maximum File Size -- set the maximum size (kb) for anyattachment used within the system.

� Attachments Oversize Action -- this parameter defines the system’s responsewhen a user tries to add an attachment exceeding the maximum size.

� Attachments File Operation -- this parameter determines the system’s actionwhen a user tries to add an attachment which is not already stored in theGraphics folder for that installation.

� Attachments Store in Database -- when a user adds an attachment, the settingof this parameter determines if the file should be stored in the database, or not.

2.2.5 AMOS Hooks

A hook is a signal sent from AMOS in specified events to allow interaction with userdefined code. This functionality, added in version 9.0 allows users to expand theAMOS suite with additional customisation and extensions. In version 9.1 additionalfunctions have been added to the AMOS Hooks custom object.

2.2.6 Remote Open Lookup

Remote lookup functionality has been added to lookup fields: double--clicking on thecontent of a lookup field will open the original window where that information wasdefined.

2.2.7 Force New Password

AC#3057

A new checkbox has been added to the Users window, ’Force New Password atLogin’. If this box is flagged for any user, the next time this user logs in the ChangePassword dialogwill appear, requiring them to change their password before they canproceed. The Force New Password checkbox will automatically be unchecked oncethe user has changed their password.

2.2.8 Last Login

AC#8411

The Last Login date of a user is now displayed on the Users window. Setting the newparameter ’Disable Account Period’ indicates the number of days of inactivity on auser account (from the last logon) that can go by before the account is disabled. If auser exceeds the number of days at their logon attempt, their account will be disabledand they will receive a message. Set to 0, this parameter is ignored.


2.2.9 Auto Lock AMOS When Idle

A new parameter, ’Idle Timeout’ allows users to set the amount of time, in minutes, forwhich AMOS can be idle before it locks. Once this amount of time has passed, thewindows will remain open but the logon dialog will appear and the current user’spassword must be supplied before access is allowed again. This parameter is disabledwhen set to 0. If enabled, the item Lock Applicationwill also appear on the Filemenuand can be manually selected at any time. Timeout can also be enabled on the Tools> Options window.

2.2.10 Shipdex Expansions

Expansions have been made to the following tables, to support ShipDex protocol:

� Component Type

� Components

� Stock Types

� Images

2.2.11 Remote Workflow Customisation

The option to define the content of the data island within the HTML page has beenadded to the AMOS Remote Workflow functionality. This allows full customisationof the content of the HTML documents including the presentation of the data andwhich data to include.

With this functionality users can write an SQL statement in the configuration file asrequired and AMOS will then produce the data in XML format inside the HTML file.

2.2.12 Column Headers Included in Copy List Functionality

Column Headers, as displayed in the list view are now included when Copy Listfunctionality from the Edit menu is used.

2.2.13 Views Expanded to Store Multiple Sorting Orders

AC#7660

When awindow is saved as aView,multiple sorting on both column order and the datawithin the columns, is now remembered.

2.2.14 Import/Export Support Added

AC#11159

Import/Export support has been introduced for AMOS Quality and Safety tables,except for ImageFile which does not require import/export support.

2.2.15 Personnel Windows Available for Selection

In the Dashboard Configuration, the Designated Window list now allows for theselection of AMOS Personnel windows as well.


2.3 Known Issues

The following known issues are present in this release.

2.3.1 Drop---Downs in Dashboard Web Browser Did Not Work

AC#11808

If a web page on the Dashboard contained a drop--down field, it was not possible toselect anything from it. This issue is solved by adding a registry key on the client:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InternetExplorer\Main\FeatureControl\FEATURE_USE_WINDOWEDSELECTCONTROL]”amosw.exe”=dword:00000001

During installation the application will set this flag regardless of its content. Duringuninstall the application will remove the content of the key and the key itself.

2.3.2 Check Added to PK Columns

A check has been added to all PK columns that the values are >0. Any PK columnswith values <=0 need to be corrected prior to upgrade, or they could cause the upgradeto fail.

2.4 Bug Fixes

The following bugs have been corrected in this release.

2.4.1 Resizing Windows With Classic Editor

AC#11561

On any window with the classic editor in use, although it was possible to manuallyresize the window itself, the area for typing information did not increase.

This has now been corrected.

2.4.2 Translation Omission

AC#8850

Some parts of the system were missing translation support.



2.4.3 Missing Field Chooser Fields

AC#9781

When UDFs were applied in the parameters, they would appear selectable in thecorresponding window Field Chooser. However, in other parts of the system theUDFfields would not be available even though they were activated.

This has now been fixed.

2.4.4 AMOS Action Did Not Update Column in Work Orders

AC#9351

Although performing awork flow transformation containing theAMOS action ’Plan’would change the internal work order status to ’Planned’, the ’PlannedBy’ column inthe WorkOrder register was not updated.


2.4.5 Translation Switched to English on Changing Departments

AC#11769

When switching departments, the currently translated language would switch back toEnglish. Opening any window would restore the translation but closing windowswould return the language to English again.


2.4.6 CTRL+SHIFT+F9 Open Dialog

AC#10909

Pressing CRTL+SHIFT+F9 would open the Open dialog correctly but clickingCancel would display the Progress window instead of simply closing.


2.4.7 Scroll Bars Added to Company Window

AC#11033

Scroll bars were missing on the Currency Access tab and on the Installations tab ofthe Company window at Tools > Configuration > Company.

These have now been added.

2.4.8 Problem with Dashboard Alert

AC#9710

In Dashboard Alerts there was an error if the SQL statement used contained asubselect.


2.4.9 Spellchecker Opened Behind AMOS

AC#11644

The Spellchecker dialog would open behind AMOS.

This has now been fixed and focus is on the spellchecker dialog when it is opened.


2.4.10 ID Number Series and Use 9 Digits for PK Counters

AC#11382

The parameters ’ID Number Series’ and ’Use 9 Digits for PK Counters’ could be seton isntallation/department level as well as globally, but since the system would onlyconsider the global setting, the installation/department one was unecessary and couldlead to errors.

Now, when these parameters are accessed from installation/department level, awarning tooltip appears stating ’It is recommended that this parameter is set on theglobal level only’.

2.4.11 Lookup Filter Error

AC#10940

Using the lookup buttons in filters to select and insert information into a field, wouldsometimes cause DBMS errors.


2.4.12 Vessel Details Additional Info

AC#11604

Information entered for a record in the user defined fields on theVessel Details registerAdditional Info tabwould automatically be copied to the user defined fields for all theother records in the window. Any changes made to a udf on one record would updateon all the other records in the same udf.


2.4.13 Alerts Area on Dashboard Partially Obscured

AC#11753

When running the Dashboard on an installation without workflow, the webpagewould partially block the alerts. Moving the divider did not move the webpage.



3 AMOS Maintenance and Purchase

3.1 Introduction

These release notes describe the changes made to AMOSMaintenance and Purchasefrom version 7.1.00 to version 9.1.00.

3.2 Changes


3.2.1 Project Window Enhancements

The appearance of the Projects window has been changed in this release. New fields,tabs and buttons have been added. Two newUser Defined Fields have been added andit is now possible to open the Work Orders window from the Projects window usingthe new Project Work Order and Section Work Order buttons.

� Project Properties and Section Properties are now shown on the Generaltab/Section tab, and no longer accessed from the Options menu.

� Project--level attachments, access and order forms are all now listed in tabs.

� The Section tab contains a Jobs sub--tab displaying the job and work orderdetails as before. AbuttonWorkOrder, opens thework order for the current job.

� The Projectswindow formerly used the filter for theWorkOrders window. Thishas now been changed, and users can filter specifically for projects, by Rangeof Projects, Sections and Jobs; Start/End Dates; Project Categories; and Title.In particular, it is now possible to filter by the status of a Project itself, insteadof by the status of the related work orders (AC#6127, 4382).

� The Options menu items Details, Additional Info, Attachments, JobDescriptions, Job Description Attachments, Required Parts/Disciplines haveall been removed and the information is now contained in the Section tabsub--tabs.

� The following new Options have been introduced:

-- Copy Project Details onto a new or existing project (AC#6119)

-- The possibility to Move Project Jobs from one section to another

-- Create Job from Job Description, opening a Create Requisition Jobwizard

-- Project Compendium enables the user to export all selected projectdetails to a word document

� It is now possible to set an alternative initial work flow status (including analternative initial lock status) for project work orders. This initial status wouldapply to work orders created from the Projects window (AC#6120).

� When the Projects module is part of the license, it is now possible to filterPurchase Forms by Project Number. Purchase information related to a projectcan now also be viewed directly from the Projects window, in the Order Formstab (AC#7272, 8291).


3.2.2 Component Job Window Enhancements

The appearance of theComponent Jobwindowhas been improvedwhile functionalityremains the same: tabs have been added to the window, replacing the need for theOptionsmenu. Thewindow is now similar in appearance to theComponent Type Jobswindow.

3.2.3 ’Depends On’ Counters

Components may have counters which depend on other component’s counters. Usersnow need the correct combination of access rights (Counters; Update/SetStart/Replace -- Counters with Dependency on the Access Control Functions tab) toUpdate, Set Start or Replace values on counters which depend on other counters, frominside the Components window Counters tab. If a counter does not depend onanything else, it can be adjusted directly in the Components window Counters tab.

Depending counters can be updated as usual from the Counters Update window.

3.2.4 Purchase Reports Print Preview

When running with a theme, a blue gradient rectangle appears around the reports, anda title describing the print out form typehas been added (i.e. Order, Requisition, Letterof Rejection, etc.). If the system is running without a theme, then these reports aredisplayed as before.

3.2.5 Order Confirmation Date

A new parameter ’Order Confirmation Date’ has been added for the MTML portaldriver. Setting this to System tells AMOS to set the Order Confirmation Date on apurchase form to the date theMTML file was processed. Setting it to File tells AMOSto read the Order Confirmation Date from the XML file.

3.2.6 Component Type Details Button

AC#11800

A Details button has been added to the Component Type -- Jobs tab. Clicking thebutton shows the Component Type Job Details (job description text) for the selectedJob.

3.2.7 Vendor’s Ref on Stock Items

AC#9782

The Vendor’s Ref field has been added to the Vendor tab on Stock Types and StockItems, and users no longer have to open the Vendor window (via the Vendors tab) toview this field.

3.2.8 Notes From Vendor Indication in Compare Quotations

AC#9622

When a Note from Vendor is present on a quotation, and the user opens the CompareQuotation window, an icon will appear in the column header for the quotation whichhas a note. Hovering over the icon with the mouse will display a tooltip with thecontents of the Note, so the user can take this into consideration during thecomparison.


3.2.9 Selecting Quotations

AC#10095

Formerly, a Quotation was considered selected when the vendor on the quotationmatched the vendor on the form.However, this assumption is not always true, andnowa quotation is only set to selected when the user chooses Options > Select Quotationin the Quotation window, or the vendor is added to the Form’s General tab and UseQuotation Prices is then checked. If more than one quotation from that vendor existsfor the form (for example different prices for different delivery destinations), the userwill not be allowed to select the quotation on the form header but instead in theQuotations window where they select not only the vendor but the specific quotationas well.

3.2.10 Open Stock Types From Transfer Documents

AC#10306

In Transfer Document Line Items, double--clicking a line item opens the related StockType. This allows the office to subsequently source the availability of that stock typeacross installations.

3.2.11 Purchase Form Filter Advanced Tab

AC#2374

The ’Include Forms of Type and Status’ area on the Purchase Form filter Advancedtab has been expanded to display as many work flow statuses as possible withouthaving to scroll.

3.2.12 Purchase Form Filter Quotation Options

AC#10994

The Form State list on the Purchase Forms filter has been expanded with moreQuotation status filtering options:

� Awaiting Quotation Receive (RFQs sent but none or not all received orrejected),

� Fully Received Queries (RFQs sent and all received or rejected),

� No Quotations Received (RFQs sent but none received or rejected),

� Not All Quotations Received (RFQs sent and some but not all received orrejected).

3.2.13 Accumulated Total in Budget Groups

AC#10009

The Budget Codes within a hierarchy now display Accumulated Total figures in thesame way as these amounts are shown in a parent record. This applies in theBudgetCode window, as well.

3.2.14 Possibility to Save on AMOS HTML

AC#10718

It is now possible to save HTML files and their content, and continue working on thesame file at a later stage. A new button on the form, Save Details, will store the formand details and all information will appear the next time this form is opened. Clickingthe Delete Details button will clear all the previously saved details on this form only-- for example, after the quote has been sent.


3.2.15 Note Field Indicator Added to Quotations

AC#7702

Three new fields have been added to the Quotations window: Note to Vendor, Notefrom Vendor, and Terms and Conditions. These fields indicate if any applicableinformation has been added to the selected quotation.

3.2.16 Show All Functionality in Deliveries

AC#8239

A Show All button and Option menu item have been added to the Deliveries windowfor order forms, to display the cancelled deliveries as well as active ones.

3.2.17 Line Item Field Chooser

AC#10883

The Line Item window fields Form Order and To Order have been added to the fieldchooser. They are also now part of the Copy List functionality.

3.3 Bug Fixes

The following bugs have been fixed in this release.

3.3.1 Datawindow in Work Orders Register Missing

AC#11991

When a user selected a work order in theWork Orders window and clicked the Deletebutton, but then clicked No in the warning dialog that appeared, the datawindow inthe General tab of the window would disappear.


3.3.2 Reports Caused Crash in Certain Circumstances

AC#10665

When filtered by any Job Class, running the following reports resulted in AMOScrashing: Maintenance Reports/Survery due by MISC2, Survery due by MISC2(functions).


3.3.3 Scrolling Problem on Stock Items

AC#7897

Scrolling through records in the Stock Items window did not work correctly, the topand bottom parts of the window did not scroll together.



3.3.4 Orderform Notes Locked Export on MSSQL

AC#9048

During office export while running on MSSQL, AMOS would freeze on the first lineof Orderline for Department 2, and hang the taskserver.


3.3.5 Unable to Print Labels/Print Execute SQL

AC#8735, 9151

After applying patch 8.5.15 if the user opened Stock Items and tried to print a label,although the print preview would appear the actual lable would not print and AMOSwould crash.


3.3.6 Deadlocks --- MSSQL Server 2000

AC#10655

Systems running on MSSQL 2000 would occasionally get deadlock messages whileworking within the Purchase module. The deadlocks would coincide with replicationor import/export tasks running.

Now if this occurs, the user receives a message saying ’A deadlock occurred, whichmeans that a collision with another user (maybe a task server) occurred. Retry theoperation shortly.’

3.3.7 Reporting on Rounds, Completed Date

AC#10730

When reporting on Round work orders, thework order could bemarked as completedand saved without a completed date. This would prevent the system fromautomatically creating the next work order for the round and scheduling theappropriate next due date.

Now, if a round has beenmarked completed but theDateDone field is not set, the userwill receive an error message.

3.3.8 Discipline DDDW Field Size Adjusted

AC#8105

The width of the Discipline DDDW field on the Work Order, Component Job andComponent Type Job windows has been expanded to display all information. If allinformation still cannot be viewed, a horizontal scroll bar is available.

3.3.9 Error Moving Stock Items

AC#10925, 10926

If Depreciation Levels were in use, an error would sometimes occur when a user triedto select Stock Items > Options > Move. Also, the system did not prompt for anydepreciation level when moving a stock item.



3.3.10 Changing Unit on Stock Type

AC#10922

Changing the unit on a stock type (within the Stock Type window) and clicking Saveproduces awarning with the choice to go ahead and save or cancel. However, clickingCancel would save the changes anyway.


3.3.11 Component Type and Address Audit Trail Error

AC#11143

If a user configured an audit trail on the table ComponentType and the fieldCompTypeNo, generated the triggers and closed AMOS, upon reopeningComponents Types > Audit Trail tab, an error would occur. The same error was raisedfor the Address window if a column there was tracked using Audit Trail.


3.3.12 Budget Date Required on Order Forms and Line Items

AC#11297

If the Budget Date was not present on an order form, the Budget Code lookups on theform header and on Line Items did not filter the records and duplicate rows wouldappear. This made it possible to have order form line items with budget codes fromseveral different financial years.

Now, if no Budget Date is set on the order form and the user tries to retrieve budgetsfrom either lookup, they are prompted to set the Budget Date first.

3.3.13 Work Planning Window

AC#9353

The font and resolution in the Work Planning window did not follow the settings inthe operating system.


3.3.14 Missing Masks in History Filter

AC#11371

Certain masks were missing in the Maintenance > History filter fields.

This has been corrected.

3.3.15 Hierarchy Show Numbers Parameter

AC#11079

When the parameter ’Hierarchy: ShowNumbers’ was set to TRUE and a user openedthe hierarchy, the Toggle Numbers button was not indented by default. This madetoggling between showing and not showing numbers confusing.



3.3.16 Purchase Form Notes Unmodifiable

AC#10086

If some purchase forms used a template and others did not, modifyng the notes on oneand then switching from onewith a template to onewithout (or vice versa) would thenprevent any further modifications to the Details tab for either record.


3.3.17 Component Financials Tab Incorrect Information

AC#11451

TheComponents > Financials tabwas displaying incorrect results when users viewedall components. However if they viewedone component at a time, the correct financialinformation would display and the function hierarchy was updated.

This has been fixed and the correct information is displayed for all components.

3.3.18 Scroll Bar Missing in WO Job Descriptions

AC#11456

The scroll bars in the Job Descriptions tab in the Work Orders window wereinconsistent: some job descriptions had a scroll barwhile others did not, and switchingbetween job descriptions would cause scroll bars to disappear from records whichpreviously had one.


3.3.19 Sorting in Line Items Allowed Despite Access

AC#9148

If a user group had the following access:

� Combined Tab -- Read access on Complete System and Read, Edit, Insert,Delete, Execute on General, and

� Registers Tab -- Edit on Forms and Form Active Queries

Users could still access and perform Sort Items on the line items of active forms,disregarding the Functions/Order Lines; Sort Items switch. If Read (CompleteSystem) was not checked, then Sort Items was greyed out.

This has now been corrected and access rights apply.

3.3.20 Related Tab Refreshing

AC#11522

When component types were related in the Component Type window Related tab,whether a simple or two way relation was in use, the information did not show upcorrectly in the hierarchies and other windows. These windows had to be refreshedupon opening to display the information correctly.


3.3.21 Unable to View Order Line Details Without Edit Rights

AC#11670

If the line item details exceeded the window size the user needed to scroll to see allthe details. However, if the user did not have Edit access rights, no scroll bar wouldbe present.



3.3.22 Transaction Codes Did Not Appear on WOs

AC#11737

When a component had one or more transaction codes assigned and a work order forwith required parts, when the work order was selected in the In/Out of Stock window,although the component and required parts would appear the transaction codes didnot.


3.3.23 Transaction Codes Sharing on Component Transfer

AC#11836

When a component was transferred from one installation to another, if the transactioncodes were not shared with the other installation, they were deleted from thecomponent.


3.3.24 Updating Component Hierarchy in Saved Views

AC#11821

If a user opened the Component Hierarchy, toggled the numbers to show and thensaved the results as a View, upon reopening the view the numbers would not showanymore. This has nowbeen corrected, and the parameter ’Hierarchy, ShowNumbers’must be set to FALSE.

3.3.25 AMOS API f_convertftr2bmp Support Expansion

AC#11790

f_convertrtf2bmp did not support conversion of ’Notes to vendor’(orderformportal.notes) and Quotationportal.Notes. Even though the portals do notsupport rich text (i.e. formatting is removed), these fields are used by users who donot use any of the portal functionality, so the function has now been extended tosupport these fields allowing printing of the notes fields. All notes fields supportingRTF arenow supported by the f_convertrtf2bmp function.

3.3.26 Creating Requistion WO Did Not Change WO Window Title

AC#11825

When creating a new work order in the Requisition Work Order window, the newlycreatedwork order numberwould remain on thewindow title even after refreshing thewindow.

This has been fixed and the new work order’s title shows.

3.3.27 UDFs on Stock Items Did not Save

AC#11885

When the parameter Use Stock Types was set to FALSE, data entered in user definedfields on the Stock Items window was not saved.



3.3.28 Not Possible to Tag Consolidated/Unconsolidated Deliveries

AC#11071, 12102

In both theConsolidated andUnconsolidatedDeliveries windows, it was not possibleto check the box for records in the list.


3.3.29 Crash During Report Work

AC#11978

When running on SQL Anywhere 11.0.1 build 2308, the system would crash duringreporting of work.


3.3.30 Restricted Budget Did Not Show in Order Form Filter

When a Purchase Budget had open access and was set on a PurchaseOrder and saved,if the access on that budget was then reset to restricted, it would no longer appear inthe Budget field on the Order Form filter. This meant that users could not filter for allforms tied to that budget.


3.3.31 History Date Written

When reporting work, and a history entry was added to the history register, the field’Date Written’ was populated with the date as registered in the ’Date Done’ field ofthe Report Work windowGeneral tab. This could cause confusion as to which day theworkwas actually done versus which day it was entered into the system. To avoid thisissue, the label of the ’Date Written’ field on the History window has now beenchanged to ’Date Done’ to be consistent with the Report Work window field fromwhich it inherits its information.


4 Personnel

4.1 Introduction

These release notes describe the changes made to AMOS Personnel from version5.7.00 to version 9.1.00.

4.2 Changes

The following changes were made in this release.

4.2.1 Access Rights Improved

AC#11814

TheAccessRights system for theEmployeewindowhas been improved. Now, if thereis no Read access for a certain tab, the tab will be hidden. Without Edit access, the tabwill appear read--only. Insert andDelete access remain the same.Without Read accesson Employee Details, the entire window will be inaccessible.

4.2.2 Bank Account Number Extended

AC#11541

The field AccountNo in use in AMOS Personnel has been extended to contain up to50 characters.

4.3 Bug Fixes


4.3.1 Personnel Memo Not Available

AC#11061

It was not possible to enter text into the Memo field for Employee records.


4.3.2 Invalid Drop---Downs in Personnel Registers

AC#11318

Various drop--down lists inAMOSPersonnel registerswere either empty, or containedthe wrong items.


4.3.3 Personnel Report --- On---Off Signing

AC#11661

It was not possible to select multiple employees/vessels for listing and printing on thePersonnel Report On--Off Signing. Instead users had to print an individual report foreach employee.This has now been fixed andmultiple employees/vessels can be listedand printed on one report.


4.3.4 Payroll Close Period Crash

AC#11599

After closing a period (Crewing > Payroll > Close Period), a fatal error would occurand AMOS would crash.


4.3.5 ProvTermination Table Not in Shared Tables

AC#11101

The ProvTermination table has now been added to the shared tables in the parametersettings.


5 Quality and Safety

5.1 Introduction

These release notes describe the changes made to AMOS Quality and Safety fromversion 4.6.00 to version 9.1.00.

5.2 Changes


5.2.1 Corrective Action WOs Show Incident Number

When a usermade a corrective action in the Incident window, the resultingwork orderwas marked as a corrective action. Now, in the Quality Work Order window a newfield, Incident No, has been added to display which incident the work order belongsto.

5.3 Bug Fixes


5.3.1 Constraint Error When Reporting an Incident

AC#11219

When reporting an incident of type Accident, with the checkbox ’Pollution’ checked,it was not possible to save the incident if ’Environmental Loss’ was set to ’None’.


5.3.2 Missing Tooltips

AC#11221

Three toolbar icons in the Quality > Manuals window were missing tooltips.

These tooltips have now been added.


6 Database

6.1 IntroductionThis section outlines the changes to database structure from AMOS Business Suiteversion 9.0.00 to version 9.1.00.

6.2 Changes

6.2.1 New Tables Including Fields

New Table New Fields

ConvertedEnhancedText ConvertedEnhancedTextIDExportPrefixRelatedIDTextImageImageTypeDeptIDExportMarkerLastUpdated

OverviewPanel PanelIDPanelNameDescriptionDeptIDExportMarker

OverviewPanelAccess AccessIDPanelIDsys_group_idDeptIDExportMarkerLastUpdated

OverviewPanelGauge GaugeIDPanelIDGaugeNameSQLMaxSQLPrimarySQLSecondaryDWSyntaxDeptIDExportMarkerLastUpdated

6.2.2 New Fields in Existing Tables

Existing Table New Fields

AmosUser ForcePasswordChange

LastLogin

BudgetCodeDef LayoutID

Notes

UserTableID


BudgetGroup PresentationModel

CompCounterLog ChangedDate

CompJob UserTableID

CompMeasurePointLog ChangedDate

ComponentUnit LayoutID

Notes

UserTableID

Project UserAddressID

UserDefText01

ProjectJob InclReqDiscCompendium

InclReqPartCompendium

Quotation SelectedDate

SelectedBy

SpareUnit LayoutID

Notes

UserTableID

TMSAKPI YesNoAnswer

NAOption

TMSAScore NotApplicable

Unit Description