It appears that your firewall may be blocking trisys.co.uk or you are encountering an error.

Please contact your IT administrator to configure your firewall to recognize all sub-domains of trisys.co.uk and trisys.biz The ports that should be opened for these domains are 80 and 443.

If that does not resolve the issue, then please submit a support ticket at http://www.trisys.co.uk/support.

TriSys 5.00 Software Release Notes

Build: 5.00.128

11th July 2002

  1. New script method available from any config form to change the current view: FormObjectsLocal.FormRef.SetView(sViewName, lRecordId).
  2. DbMigration creates 2 new fields on SearchCriteria table: PostCodeHomeAddress and PostCodeWorkAddress
  3. New search criteria fields available on Options-->Post Code Search menu of candidate search and requirement forms: Home Address & Work Address. Both or only 1 can be selected. They determine whether the post code search will join on the home address or the contacts work address. The settings are preserved with each candidate search or requirement.
  4. Pop-up message when a duplicate SearchCriteriaId is found, is now suppressed and replaced with a call to write the error to the diagnostic log file if enabled.

 

 

Build: 5.00.127

5th July 2002

  1. Form_Unload ( Cancel ) event now works correctly to prevent form from unloading when Cancel status set to True. The correct function signature is now generated in the script designer.
  2. DbMigration creates a new field: QueryProperties.IgnoreSearchCriteria which is available as a check box in the query designer.
  3. When the Query - Ignore Search Criteria option is checked, the fast search, combo search and tab letters are disabled and do not affect the programmed query SQL.
  4. Cloning a user account now clones the form properties (FormContextUser table - form colours, menus, icons etc..) and UsrCfgUsers settings.
  5. Right mouse clicking on partially viewed grid rows does not cause a run-time error.

 

 

Build: 5.00.126

22nd June 2002

  1. frmCompanies now has multi-grid/tab capability in the same fashion as frmContacts.
  2. This allows multiple SQL query views to be configured in Form Designer to show various views of companies.
  3. Added 0-9 tabs to frmCompanies to cater for companies beginning with numbers e.g. 3i, 4th Dimension etc...
  4. Fixed minor bug in setting the Default Query in Query Designer for frmContacts.
  5. Fixed remaining bugs relating to comments searching introduced in 5.00.123 for Always Show Comments option.

 

 

Build: 5.00.125

18th June 2002

  1. Fixed bug relating to comments searching introduced in 5.00.123 for Always Show Comments option.
  2. Added extra form field error handling to manage incorrectly exported form definitions.

 

 

Build: 5.00.124

14th June 2002

  1. Extra error checking added to CShowForm to handle cases where FieldDescriptions are Nothing in FormFields collection.
  2. Removed all TODO message boxes.

 

 

Build: 5.00.123

29th May 2002

  1. TimeSheet data entry now allows selection of the timesheet period 6 days prior to the start of the placement to allow for start dates which fall in between period dates.
  2. When using modal virtual forms, can now use Initialisation.GlobalParameterValue to pass variables rather than having to use hidden form fields.
  3. Can now send HTML formatted e-mails from actions when using Outlook. See this tutorial document.
  4. Possible to use <<ClientContact.ContactId>> and <<Candidate.ContactId>> in action e-mails in order to e.g. pass in URL's to web services/pages.
  5. New option in Options-->Setup-->Search called Always Show Comments in Candidate Search Results which takes effect on the display of candidate search results and shows the candidate comments rather than the CV hits or full CV in the lower window beneath the results grid.
  6. Candidate search now shows CV hits in all cases where it is configured to do so.

 

 

Build: 5.00.122

18th May 2002

  1. Form designer now creates VARCHAR fields instead of TEXT fields where the default text field length is 255 characters.
  2. New script event Grid_AfterFilter is raised after the user has filtered a grid column. This allows e.g. re-calculation of totals.
  3. Legacy performance limit on contact/company search of 1024 has been removed.
  4. Auto login mechanism has been re-implemented.

 

 

Build: 5.00.121

9th May 2002

  1. Activity Search form frmActivitySearch is now scriptable. This allows designers to add extra search criteria to the search for note/histories and scheduled activities.
  2. This version will not run unless DbMigration 5.00.121 has been applied.
  3. Update to VBScript friendly function available from Selection object: Function FastContactSelection ( Clients as Boolean, Candidates as Boolean, DefaultCandidate as Boolean, AndSQL as string ). This allows the script developer access to the fast search technology in TriSys for popping up dialogues for the users to select contacts whilst allowing tighter control over the dynamically generated SQL statement.  This is now documented with a full example in the latest script tutorial. This function was first developed in build 5.00.54.
  4. Mail-Merge problem introduced in build 5.00.110 caused by NULL SkillCategory.Description fields is now fixed.
  5. When applying a filter to a grid, any actions or reports printed from the grid are performed from the filtered recordset.
  6. Entering a REPD code into Form Designer when not licensed is only necessary for the first accessed report.
  7. New action form methods available to explicitly instantiate the Id collections. This is useful when an action is invoked from the menu to operate upon a scripted grid, and the script developer wishes to programmatically add the contact collection. The new methods should only be called where the respective Id collection is Nothing and are as follows:
    • InstantiateContactIdCollection
    • InstantiateCandidateIdCollection
    • InstantiateCompanyIdCollection
    • InstantiateRequirementIdCollection
    • InstantiatePlacementIdCollection
    • InstantiateTimeSheetIdCollection
    • InstantiateEntityIdCollection

 

Build: 5.00.120

30th April 2002

  1. Companies form (frmCompanies) now wired with Grid_RowLoaded event which can be used to colour company records.
  2. New company contact form now has extra fields to facilitate more accurate data entry:
    • Title (Mr, Mrs etc..)
    • Male/Female
    • Job Title
  3. In order to capture the creation of a new company contact, a new event AfterNewCompanyContact has been developed in build 5.00.120.
    This passes the ID of each new contact as a parameter.
    The benefit of this is that the script developer can set any business rules for new clients e.g. workflow, reminders, skills etc.. even pop-up data capture windows
    This event fired BEFORE the contact form is loaded (if requested by the user).
    The following example shows how to access this event:
     
    ' 30 April 2002 - Called after a new company contact added but
    '  before the contact form is loaded (if requested).
    Public Sub Form_AfterNewCompanyContact ( ContactId )
         MessageBox.AppMsg "You added a new contact: " & ContactId & _
              " to company: " & m_CompanyId
      
         ' Do something with the new contact record
         Set Contact = Initialisation.Contacts.FindFirst(ContactId)
         With Contact  
              .Comments = "Added on " & StringFunctions.VBFormat(Now, "DDD DD MMMM YYYY") & _
                   " by " & Initialisation.Name & " from company form."
              .Update
         End With
    End Sub

     

  4. In order to capture the deletion of each candidate from the shortlist on the requirement form, a new function AfterDeleteShortlistedCandidate has been developed.
    This passes the ID of each contact as a parameter and is called for each candidate that is deleted from the shortlist.
    This fires both for selected contacts and where all are removed.
    The following example shows how to access this event:
     
    ' 30 April 2002
    Public Sub Form_AfterDeleteShortlistedCandidate ( ContactId )
        MessageBox.AppMsg "Deleted " & ContactId & "?"
    End Sub

     

 

Build: 5.00.119

19th April 2002

  1. When the registry setting to prevent login setup is set to False (5.00.114), the test connection dialogue is not displayed when the connection to the server is unsuccessful.
  2. In Requirement and Placement forms, the company & contact lookup fields' .Tag property is set before the Field_Change event is raised in script

 

Build: 5.00.118

28th March 2002

  1. When file ref fields drag/dropped or the find document button is used, the UNC path in the .Tag property is set before the Field_Change event is raised in script.

 

Build: 5.00.117

28th March 2002

  1. Now possible to delete the last company address without causing a SQL syntax error.
  2. Action form can now be configured to show the following specific contact reference fields:
    • WorkTelNo
    • MobileTelNo
    • FaxNo
    • EMail
    • HomeAddressStreet
    • HomeAddressSuburb
    • HomeAddressCity
    • HomeAddressCounty
    • HomeAddressPostCode
    • HomeAddressCountry
    • HomeAddressTelNo
    • HomeAddressFaxNo
  3. FormFunctions.GetAFormInstance and FormFunctions.isFormLoaded now work for entity forms.

 

Build: 5.00.116

20th March 2002

  1. When running a candidate search and moving focus to another form, pressing the list bar candidate search button does not reload the users' search list thus causing an object variable error when the search results are next accessed.
  2. Candidate search algorithm changed with respect to comments searching. This now utilises a separate UNION clause rather than an OR clause in order to improve performance on legacy SQL Server computers.

 

Build: 5.00.115

15th March 2002

  1. Script Grid_RowLoaded event not fired during grid initialisation, only during row population.
  2. Yes/No fields can now be set to ReadOnly and are correctly disabled on the form at run-time.
  3. New Alignment field added to FormFields table by DbMigration. This can be maintained from form field properties and can be set to Left (default), Centre or Right. Centre is not a valid setting for certain windows widgets, but no run-time error will be raised. Where the field is an updateable number field, and the field is right aligned, the spin control is displayed in the left of the data entry field.

 

Build: 5.00.114

1st March 2002

  1. CV Auto-Recognition View-->Unreferenced CV's option now handles > 32767 documents without raising a run-time error. This was caused because the windows progress bar common control only allows integer values for the .value property.
  2. Can delete tasks associated with new entities.
  3. Added new registry setting to prohibit access to the login-->setup functionality. This is to help 'lock-down' a workstation to prevent problem users changing connection settings. The registry setting is HKEY_LOCAL_MACHINE\Software\Technical Recruitment Industry Systems Ltd\TriSys 5.0\Login Setup and if this is set to False, then the setup hyperlink is disabled on the login screen.

 

Build: 5.00.113

22nd February 2002

  1. Grid filtering enabled from right mouse pop-up menu on grids with associated form designed Query or unbounded scripted grids. This allows for easy to use yet powerful filtering of large data sets. For more information, please read this associated documentation.
  2. New scripting function: DataWidgets.GetUnboundScriptedGridRecordsetFromHwnd which allows the script developer access to the unbound recordset. The script tutorial contains a detailed example of usage.
  3. When attachments dragged and dropped from Outlook into FileRef fields on config forms, no run-time error is raised.

 

Build: 5.00.112

15th February 2002

  1. Document reference fields added to action forms, now correctly link to the document path.
  2. FileRef fields on config forms and Scheduled Activity/Note History dialogue now accept windows explorer file drag and drop.

 

Build: 5.00.111

21st January 2002

  1. New script method exposed on all data entry and virtual forms: FormUnload which can be called to explicitly close the form. This is useful when implementing wizards when the form is closed upon completion of the last task. Example: FormObjectsLocal.FormRef.FormUnload.
  2. When a fixed query in frmContacts is flagged as non Visible, the query does not show as a tab.
  3. When more than 1 attachment is specified to be appended to an e-mail action, this now correctly appends all documents providing they exist at run-time.
  4. Deleting contacts from the company form now has error checking to intercept SQL errors and prevent termination.
  5. Activity search using free text now identifies whether the SQL Server has the correct free text index for the Task table. If this is not setup, the query uses a standard pattern match on the Task.Description field.

 

Build: 5.00.110

14th January 2002

  1. Form Designer now creates the Universal Data Source.tmm file fields to be exactly the same as those generated at run-time.
  2. Action field placeholder <<Candidate.Name>> is substituted correctly for the e-mail body.
  3. New Snooze option: Pick Date which allows for a specific date (defaults to tomorrow) to be selected for the selected activity alarm. This is useful for e.g. Friday afternoon alarms which you want to leave until Monday morning!
  4. The candidate priority search now works in a more intuitive fashion i.e. Above means higher priority not vice-versa. Now when users search for candidates with Above Medium Priority, they will find candidates with Medium and High priority.

 

Build: 5.00.109

17th December 2001

  1. Where the UserId's are > 32767, candidate search works correctly.

 

Build: 5.00.108

14th December 2001

  1. New Form Designer option:

        Tools-->Search

    which invokes a non-modal dialogue for entering in a keyword which is used to search for either specific fields or script code. The search results are shown in a master/detail view with the form in which the field/script resides shown in the master listbox, and the 'hits in context' view shown beneath for each row selected. Double click the list box to launch the associated script editor or form designer.

  2. Entity form never loads the VCR to view all existing records on open. User must explicitly request the use of the VCR by using the fast search combo on the main toolbar.
  3. Un-clearing an activity from the monthly view now correctly refreshes the grid to show the unticked activity.
  4. When the addresses and contacts grid on the company form are on the same tab, the addresses grid refreshes upon the addition/editing of any contacts.
  5. Selecting a date and creating a new activity (by double clicking or right mouse pop-up menu) on the diary management weekly view, correctly picks up the specified date rather than inheriting this from the daily view date.
  6. When UserId's are larger than 32767, the diary does not overflow.
  7. Where an ' character is used in a town post code (e.g. Bishop's Stortford), the post code table build and searching work correctly.

 

Build: 5.00.107

Friday 7th December 2001

  1. Virtual forms calling actions from script now works without permissioning problem. This fixes a problem introduced in build 5.00.103.

 

Build: 5.00.106

Friday 7th December 2001

  1. When using keyboard to filter modal searches, the top record is always selected even if the grid row is not selected using a mouse click. This fixes a problem introduced in build 5.00.079
  2. Fixed delete user problem to correctly re-assign contact ownership to specified user.

 

Build: 5.00.105

Thursday 22nd November 2001

  1. When an action is invoked from the placement search form, the list of placements is correctly collected from the grid and the action shows the details.
  2. When skills are scanned in the contact form, the skills list box label is refreshed to show the correct number of skills.
  3. When assigning a CV in the contact form, the relative path is saved to the database, not the absolute path. This bug was introduced in build 5.00.091 on 7/9/01.
  4. Inconsistent scan CV now fixed so that only non lookup config fields are scanned i.e. those not associated with a config field.

 

Build: 5.00.104

Friday 16th November 2001

  1. Fields of type: Contact created in form designer now automatically generate a further 3 fields used entirely for displaying the contacts company, company address and home address.
  2. The use of these fields is documented here.
  3. Query forms now handle contact/company/user lookup fields.

 

Build: 5.00.103

Thursday 25th October 2001

  1. Contact form does not overwrite the street number after a post code lookup on save.
  2. If a user is not permissioned for an action, a warning message is displayed and the action form is not loaded.
  3. Spin increment fields in action forms always allow spinning according to field rules in form designer.
  4. New scripting object EMailGateway exposed through script. See tutorial for more details.

 

Build: 5.00.102

Wednesday 24th October 2001

  1. Lotus Notes object instantiation now invoked for every e-mail rather than retaining the reference to the Notes.exe client. This prevents the Notes client from crashing when closed if TriSys is still open.

 

Build: 5.00.101

Friday 19th October 2001

  1. In order to increase the timeout of the script engine, a new UsrCfgUsers super user setting allows the configuration of the number of milliseconds to wait for a script to complete. The FName: ScriptTimeoutMilliseconds, of FType=I, should set the FValue to the number of milliseconds (default 30000).
  2. Updated scriptable event introduced in build 5.00.095 which is available from both requirement and candidate search forms which is raised when a contact is added to the shortlist either via the shortlist button or via active searching pop-up window.

    Public Sub Form_AfterShortlist ( ContactId, ActiveSearching )

    This event is called after the contact is added to the underlying tables (CandidateSearchHits, RequirementCandidate, RequirementCandidateAction) but before the associated grids are refreshed. This gives the scripter the opportunity to manipulate the underlying records, or indeed add the record to other unrelated tables (customised lists). The first parameter is the id of the contact record and the second is set to True if the contact is shortlisted from active searching.

  3. Post Code Nearest Builder utility now identifies all 1.6 million UK post codes (previously a number of newer London addresses were not recognised).

 

Build: 5.00.100

Thursday 18th October 2001

  1. Major re-write of post code lookup and searching for commercial, technical and support reasons (see internal design document for details). Most important changes are highlighted here.
  2. Removed dependency on TriSysPostCodeLookup.dll from both TriSys and Nearest Builder utility.
  3. Removed dependency on QAS DLL's from TriSys.
  4. Login setup in TriSys no longer has options for configuring the location of the QAS initialisation files as they are no longer required.
  5. Company Search, Candidate Search and Requirement Candidate Search now have an overwritable city/town combo which is populated from all cities/towns setup in the town/post code maintenance. If a radius is supplied and the nearest builder has correctly created the search tables, the new nearest radial search will be invoked.
  6. The new radial searching algorithm does not generate temporary tables on the fly during searching. These are pre-processed by the nearest builder to facilitate lightning fast post code searches utilising the power of the SQL Server database engine.
  7. New scripting object PostCodeLookup exposed through script. See tutorial for more details.
  8. Script function: GetRequirementCollectionWithinPostCodeRadius no longer available as post codes searches now based upon registered town's.
  9. New PostCode Nearest Builder utility which can build the following:
    • a new format.NRS file with only AddressId field
    • the PostCodeLookup table which is populated from all post codes and addresses in the PAF
    • the PostCode_Town tables, one for each town in the TownPostCode table
  10. Placement Search can now have additional frames programmed from script.

 

Build: 5.00.099

Tuesday 9th October 2001

  1. Scan CV function from contact form now works correctly again. Bug introduced when building a new scan skills utility on 15th Sept 2001 (affecting all builds from 5.00.093 to 5.00.098).

 

Build: 5.00.098

Friday 5th October 2001

  1. Crystal reporting bug related to context sensitive curly braces, introduced yesterday has been fixed.

 

Build: 5.00.097

Thursday 4th October 2001

  1. Overflow errors when printing extraordinarily long recordsets now fixed. This may expose Crystal limitations.
  2. When a query results in duplicate contacts, running an action against the grid does not cause a duplicate collection key error.

 

Build: 5.00.096

Thursday 4th October 2001

  1. Exposed method on requirement and candidate search forms to allow script to reset the selected candidates for shortlisting/deletion:

    • FormObjectsLocal.FormRef.InitialiseCheckedRowsArray

 

Build: 5.00.095

Friday 21st September 2001

  1. Active searching pop-up window now shortlists candidates using an open requirement form. This is done to centralise the shortlisting process. When the user selects a candidate for shortlisting, a requirement form is opened and the active searched requirement is opened. If a requirement form is already open, the pertinent record details are loaded. This has the advantage that shortlisted candidates are visually added to the grid after shortlisting from active searching.
  2. New scriptable event available from both requirement and candidate search forms which is raised when a contact is added to the shortlist either via the shortlist button or via active searching pop-up window.

    Public Sub Form_AfterShortlist ( ContactId )

    This event is called after the contact is added to the underlying tables (CandidateSearchHits, RequirementCandidate, RequirementCandidateAction) but before the associated grids are refreshed. This gives the scripter the opportunity to manipulate the underlying records, or indeed add the record to other unrelated tables (customised lists).

  3. Company contact relationship hierarchy introduced in 5.00.092 has been tested and fully implemented. See this document for details of implementation and operational procedures.

 

Build: 5.00.094

Thursday 20th September 2001

  1. Entity views implemented in 5.00.091 have now been tested and bug fixed where necessary.
  2. If any other users diary permissions are not set to View for the current user, then no greyed out menu item will be shown in the Diary Manager Options->View Users Diary menu.
  3. Optimised the load of users into the Diary Manager Options->View Users Diary menu so that these are cached in advance.
  4. When the user selects the Diary Manager Options->View Users Diary->All Users menu option, only tasks belonging to those users whose diaries can be viewed are shown.
  5. Fixed EntitySearch form resize problem where the search results showed the form scroller halving the view.

 

Build: 5.00.093

Monday 17th September 2001

  1. New method exposed on Action form to allow script to close the action form during Form_AfterLoad event: FormObjectsLocal.FormRef.FormUnload.
  2. If only the 'Use in addition to search criteria on search tab' check box is updated and the record saved, this correct value is saved to the database.
  3. When a candidate is shown in the search results, the CV is not inherited from the previous record if no CV is found.
  4. Double clicking record selection grids in rapid succession does not attempt to load multiple forms simultaneously.

 

Build: 5.00.092

Thursday 13th September 2001

  1. This version will not run unless DbMigration 5.00.092 has been applied.
  2. Task grids do not refresh if visible when activity alarms are refreshed.
  3. Company relationship and contact relationship tree views now correctly show the hierarchical relationships specified using the associated grid.
  4. Deleting contacts and companies referenced in a relationship hierarchy, does not cause a referential integrity error.
  5. New table created: CompanyContactRelationship which models the relationships and hierarchies between the company contacts so that an organigram of company contacts can be shown on the company form. 
  6. New fixed field created on company form to add the tree view hierarchy to the company form. This feature has not been fully implemented and tested yet so please refrain from enabling in production databases.
  7. Due to bugs/design flaws discovered in Windows 2000 Terminal Services' handling of INI files, the TriSys32.ini file access is now performed without using the native Windows API functions.
  8. In Windows terminal services environment, there is no need to manually copy a TriSys32.ini file to each user's WINDOWS folder. As long as a C:\WINNT\TriSys32.ini file exists on the server, TriSys will copy this to the users own private WINDOWS folder if one does not exist.
  9. Actions invoked from entity forms now pass in the collection of candidates so that note/histories and scheduled activities can be created involving multiple candidates.

 

Build: 5.00.091

Friday 7th September 2001

  1. This version will not run unless DbMigration 5.00.091 has been applied.
  2. If an action is run from a requirement form, only if the action has been defined as a shortlist action, will the candidates referenced in it be added to the shortlist.
  3. New MailMerge object exposed to script to allow easy and flexible access to the internal mail merging mechanism. See this document for more details.
  4. Entity views have been implemented but are still in beta test. Do not attempt to enable entity view types until you have a suitable test database and have read this document.
  5. View replaced by Links on data entry forms. This is because the View menu is now reserved for entity views.

 

Build: 5.00.090

Monday 3rd September 2001

  1. Cancel status now correctly identified 100% of the time.
  2. Virtual unbound scripted grids now enabled for script developers. This adds performance and ease of use to the current techniques for populating grids from SQL statements. See programmer oriented document for details.
  3. All grids which have associated Queries defined in form designer now have column sorting enabled (via right mouse column header click).
  4. Job title search in Placement Search and Requirement Search forms works correctly.
  5. New Requirement status: On Hold. This can be invoked by adding the fixed field in Form Designer to the requirement form. This should be added to the same panel as the existing Live/Filled/Dead check boxes. New reports are available which incorporates this new status.
  6. Requirement Search form now has an option to select On Hold.
  7. New search option on both Candidate Search and Requirement form: Options->Show Candidates Having Either Free Text OR Skills. When this menu option is checked, the results from CV free text and the search skills are OR'd together so that candidates who have either free text or skills will be displayed in the search results grid. When not checked, the results are AND'd together so that only those candidates found in both are displayed.

 

Build: 5.00.089

Friday 31st August 2001

  1. Script editor shows the script name in the caption so that when minimised, each script can be easily distinguished.
  2. When an icon has been assigned to a new entity form, or virtual entity, the correct icon is shown in the associated main binder tab.
  3. When an icon has been assigned to a new entity form, or virtual entity, the correct icon is shown in the top left corner of the form caption. This should be a 16x16 pixel icon.
  4. Script editor automatic cursor repositioning incorrectly has been fixed.
  5. Script editor correctly identifies the difference between functions, subs and properties and script containing these words.
  6. Additional grid related functions available from script to make programming grids very easy by abstracting the low-level details. See programmer oriented document for detailed examples.
  7. Form designer now ensures that databases opened with the File->Open menu are also synchronised to the expected database version.
  8. Resetting default search criteria does not cause an error which closes down the application.
  9. The 'User Skills in Search' (User in Addition...) check box is now remembered as part of the default search criteria if enabled in Requirement form.

 

Build: 5.00.088    *** Warning: This is a Beta release. It has not been tested or validated outside the development centre. ***

Thursday 30th August 2001

  1. This version will not run unless DbMigration 5.00.088 has been applied.
  2. Pop-up modal selection grids now close without selecting when the form close icon (cross at top right of window) is pressed.
  3. The system option: Options->Setup->Search Tab->Save Candidate Search Results into Snapshot Table has been removed as it is now obsolete.
  4. DbMigration creates candidate search results queries for both Candidate Search and Requirement forms. 
  5. Candidate Search and Requirement forms now pick up a configurable candidate search results query and associated grid columns. Thus it is now possible with this release to add any contact related field to the candidate search results grid. See associated document for instructions.
  6. Default search criteria now used as default for new candidate search and requirement records.
  7. When adding a new candidate search, the user is prompted for the search description. The record is then saved with the users' default search criteria. This saves the user having to remember or be prompted to manually save the search record after searching.

 

Build: 5.00.087    *** Warning: This is a Beta release. It has not been tested or validated outside the development centre. ***

Tuesday 28th August 2001

  1. Each subsequent version of TriSys will check that the database has been migrated to the last known migration. This version will not run unless DbMigration 5.00.087 has been applied.
  2. If NOT skills grid not designed onto Requirement form, no record load error is generated.
  3. 2 new buttons added to Candidate Search form: Save & Reset. These have the following pop-up menus:

     

    Save
    Candidate Search Save the current search criteria for this candidate search record
    Default Search Criteria Save the current search criteria as the users default criteria

     

    Reset
    Default Search Criteria Reset the current search criteria to be the same as the default search criteria i.e. users defaults
    Factory Default Criteria Reset the current search criteria to be the same as that for a new search i.e. factory defaults

          

  4. DbMigration creates new Save and Reset buttons for Requirement form which operate the above pop-up menus once selected. These are available from the Field Selection dialogue and must be manually dropped onto the designed form to activate saving and resetting search criteria for Requirement Candidate searching. See associated document for instructions.

 

Build: 5.00.086    *** Warning: This is a Beta release. It has not been tested or validated outside the development centre. ***

Friday 24th August 2001

  1. DbMigration adds a new column SearchSkills.NotSkill. This denotes that skill searches can retain NOT skills. Primary key for SearchSkills table updated.
  2. Candidate Search form now has NOT skills grid located beneath the skills grid. Buttons are provided for Add, Remove and Remove All. Grid works the same as original with full drag/drop capability.
  3. NOT skills are retained for each saved search.
  4. DbMigration creates new NOT skills grid for Requirement form together with buttons for Add, Remove and Remove All. These are available from the Field Selection dialogue and must be manually dropped onto the designed form to activate NOT searching for Requirement Candidate searching. See associated document for instructions.
  5. Requirement Industry Skills list box now operates like the same list box on the Candidate Search form i.e. it allows searching by typing consecutive letters of skills to locate each skill.
  6. Requirement Industry Skills list box now contains the correct list of skills when the skill category is Show All. Previously this did not show the same list as that for candidate search.
  7. Dirty form on load caused by txt box field focus coded around by ignoring programmatic manipulation on lost focus event.

 

Build: 5.00.085

Thursday 23rd August 2001

  1. Using the Add button on a requirement or candidate shortlist, will show the fast contact search and default to Candidate rather than Client Contact.
  2. Adding the <<Placement_UserId>> field to a mail-merge now pulls through the correct user name. 
  3. When fields of type Contact, Company or User are used in a mail-merge, the correctly linked contact/company/user names are pulled through.
  4. Report license now enables script development for the selected report. Report designers can still design report forms, but now attach script.
  5. UserId combo reference fields (Requirement, Placement) now populate automatically in action forms when designed in.
  6. Company search form now allows single word/phrase searching of company comments.
  7. Requirement and Placement search now optimised for comments/description free text search.
  8. Cancel function status' now processed correctly from scripted event handlers.

 

Build: 5.00.084

Thursday 2nd August 2001

  1. Form designer limits only 1 script window per script to be open at any time. This removes the risk that developers may have multiple versions of the same script open at the same time and overwrite changes.
  2. New TriSys32.ini file setting to override the built-in logic which forces the selection of the contract/permanent and PAYE related fields:

            Contact Field Visibility Logic=False

    When this is set to False, no field logic is applied which forces the display of the end date, hourly rate, overtime rate, salary, bonus when the contract/permanent check boxes are updated, and also the LTD company, registration number, NI fields when the PAYE check box is updated.

     

Build: 5.00.083

Monday 30th July 2001

  1. Diary View options Time Interval is now persisted between invocations.
  2. Setting report availability in Form Designer for more than one form at a time does not generate a SQL error.
  3. Full support for Office XP. Word 2002 is now supported for mail merging. Word 2002 is part of Office XP.

 

Build: 5.00.082

Wednesday 25th July 2001

  1. Only action and report buttons force a dirty save check on invocation. This now allows users to skill up a contact using the lookup buttons without having to save the contact details each time.
  2. Scheduled Activity/Note History form can be opened from script for specified TaskId. This is available through the function: FormFunctions.LoadFormByName("frmActivityNoteHistory", CLng(TaskId), "")
  3. Adding ContactRelationshipGrid fixed field to forms now generates the correct columns.
  4. New function available to script to obtain a collection of requirements which are within a specified radius of a specified post code. This function is Initialisation.Requirements.GetRequirementCollectionWithinPostCodeRadius and is demonstrated in the scripting tutorial.
  5. Support for Lotus Notes E-Mail. New Notes E-Mail Client Automation Method available in Setup->Options dialogue on E-Mail tab. Requires Lotus Notes client version 5 or later.
  6. E-Mail mechanism now no longer reliant upon TriSysEMailGateway.dll. All e-mail clients are automated directly from TriSys without incurring potential switch-to automation errors.
  7. In view of the changes to e-mail, it is worth re-capping the various options:
  • MAPI - uses Microsoft Mail API control: MSMAPI32.OCX version 6 or later. This should only be set if Outlook Express is the preferred e-mail client and if any e-mails are to be sent direct to the outbox without user intervention/confirmation. Any e-mails sent using MAPI are synchronous i.e. they will block TriSys from processing until the user presses the send button in the e-mail send dialogue and/or the e-mail is cancelled or ends up in the Outbox.
  • Outlook - uses Outlook object library and should only be set if Outlook is the preferred e-mail client. E-mails can be sent direct to the Outbox and are processed asynchronously i.e. TriSys continues processing whilst the e-mail dialogues are displayed.
  • mailto: - uses the currently specified windows default e-mail client (recorded in the registry by windows). This should only be set if no e-mails are to be sent directly to the Outbox, or if multiple file attachments are never required, or if the e-mail client is not Outlook, Outlook Express, Lotus Notes e.g. Novell Group Wise. Any e-mails sent using mailto: are processed asynchronously but will always show a send dialogue. Some e-mail clients fail to register themselves properly with windows rendering the mailto: mechanism useless.
  • Notes - used the Lotus Notes client version 5 or later. This should only be set if Lotus Notes is installed and mailto: does not function correctly. More information relating to this will mechanism be documented in due course.

 

Build: 5.00.081

Friday 20th July 2001

  1. Reports with a form now invoke the form to capture data input parameters after the report is instantiated. This has the benefits of being able to control the full SQL Query in script which includes all context related information. Another benefit is that any report related errors are identified before the user is prompted.

 

Build: 5.00.080

Friday 13th July 2001

  1. Crystal report invocations now tolerate the invalid property error 438 which is incorrectly raised by the Crystal run-time engine.
  2. QAS post code searching using nearest database now handles data sets larger than 32767 post codes. This necessitates a new TriSysPostCodeLookup.dll. This is not COM compatible with previous versions so requires a REGSVR32 /U of the existing DLL and a REGSVR32 of the new one.

 

PostCode Utilities 

Friday 13th July 2001

These files provide the libraries, utilities and test programs which support the QAS post code lookup and nearest builder.

Folder/File

Comments

TriSysPostCodeLookup.dll

The post code lookup library. This must be registered using REGSVR32 in order for TriSys and these utilities to use it.

TriSysQASNearestBuilder.exe

The nearest builder to build the QAS nearest database using the post codes in the TriSys SQL Server database.

Lookup Test.exe

The post code lookup test program.

Nearest Test.exe

The nearest builder test search program.

 

Build: 5.00.079

Thursday 12th July 2001

  1. Actions run from entity forms now correctly pass through the referenced contact/company/requirement etc.. details. 
  2. Modal grid search can now be filtered using the keyboard. When the user presses any key, this is reflected in the caption and this filters the first visible character field. The filter is displayed in the caption. The backspace can be used on the filter.
  3. DbMigration creates a new field: FormField.ScriptOnly. This is set by the designer in FD for fields on forms which are to be controlled only under script control. Such fields are not populated on load, or saved with other fields. This can be used to control the population of reference fields on actions.

 

Build: 5.00.078

Wednesday 11th July 2001

  1. Removed stack control limitation which prevented script recursion. 
  2. Added new function MessageBox.VBMsgBox which provides same functionality as VBScript MsgBox except that messages can be logged using diagnostics if enabled.
  3. Actions invoked from buttons now force a save of the underlying record before invoking the action.
  4. Form designer now adds AddNew{EntityName} buttons to contact forms for new entities.
  5. AddNew{EntityName} functionality from contact form now passes correct contact Id to the action.

 

Build: 5.00.077

Tuesday 10th July 2001

  1. Fixed stack control bug to prevent script recursion or stack overflow. This bug was introduced in 5.00.073 on 17th June.
  2. Birthday wizard now works correctly without error.

 

Build: 5.00.076

Thursday 28th June 2001

  1. All forms now correctly capture keyboard focus upon open and view without requiring mouse button intervention.
  2. As a result of this, all tab orders for config form fields now correctly have the cursor positioned ready for faster data entry.
  3. Now possible with many forms to use the keyboard only to find and edit records.
  4. Fixed bug where pressing the list bar button for an already open form, resulted in the form being displayed but without focus.
  5. Fast Search now works in Company form.
  6. Shortcut key Ctrl-F4 now enabled for closing forms.
  7. Shortcut key Ctrl-F now enabled for invoking fast search dialogue when the following forms have focus:
  • Contacts
  • Companies
  • Contact
  • Company

Thus it is now possible to open the contacts/companies form (Alt, E, C or Alt, E, N), run a fast search (Ctrl-F), view results (Cursor keys), open the selected record (Ctrl-O or Enter), update fields (tab, keys) save (Ctrl-S) and finally close the form (Ctrl-F4) without using the mouse at all.

 

Build: 5.00.075

Tuesday 19th June 2001

  1. QAS Post Code integration modified to only instantiate the TriSysPostCodeLookup.dll when a post code operation (lookup/nearest search) is required. This allows the nearest builder to now update the TriSys.nrs file even when users are logged into TriSys.
  2. New database detection parameters when Configure-> Show Configuration menu is selected. This checks whether the Insert Into/Bulk Copy database option is set. If it is not (i.e. Off) then candidate searches will not work as they expect to be able to create temporary tables and insert into them during results processing. The other option which is checked is the Truncate Log on Checkpoint option which if not set will cause the transaction log to grow indefinitely.
  3. Crystal Reports with embedded database locations (database.dbo.table) and table aliases are now correctly re-assigned during report invocation. This enables easier integration of complex reports developed by third parties.

 

Build: 5.00.074

Tuesday 19th June 2001

  1. Skill synonyms now fully supported. Synonyms can now be used in free text searching, scan skills and CV auto-recognition scan skills. Follow this link for a full description of the synonyms integration.
  2. If CV cannot be read during scan skills operation, then an error message is displayed informing the user.

 

Build: 5.00.073

Sunday 17th June 2001

  1. TimeSheet data entry formulas replaced with script in standard actions database.
  2. TimeSheet period combo now only shows the periods which are within the parent placement start/end dates.
  3. When an existing TimeSheet, user cannot change the period.
  4. No overflow when mail merging more than 327 contacts. This was caused by calculating the percentage complete and overflowing the 32767 integer limit.
  5. Reworked Options->Contact Users menu on contact form. This now has explicit menu options to Add, Remove and Set Owner users. Only the assigned users are shown in the menu, and even then only up to 5 are displayed. Further users can be viewed using the More.. option. This work was necessary in order to process hundreds of user accounts efficiently and with minimal menu access.
  6. Stack control mechanism implemented to prevent script calling TriSys objects which in turn fire script which can then result in inefficient recursion or stack overflow.
  7. Fixed bug introduced in build 5.00.067 on 26th April 2001 which reset the previous post code search results in all cases causing shortlisting from a post code search to ignore the previously cached post code results. This now works correctly for both scenarios.
  8. Added Ordering number spin control to Query properties in form designer so that the order of the query can be set. It is up to the designer to ensure that these are entered sequentially in the order required.
  9. When the default query is specified for queries in form designer, other queries associated with the same form, have their default query flag cleared.
  10. In order to be more terminal server/Citrix friendly, it is now possible as any user (e.g. non administrator) to log in from a different workstation than the current login. The normal controls are in place such that the other session is forced to log off within 2 minutes which may trigger the new session automatic logoff sequence.

 

Build: 5.00.072

Wednesday 6th June 2001

  1. In order to prevent the mail merge data source .TMM file containing too many fields for Word, a new UsrCfgUsers super user setting allows the entities to be limited. The FName: MailMergeIgnoreEntityList should set the FValue to a comma delimited list of entities which are not to be made available in the .TMM file. This must be setup before the form designer is used to create the universal data source template, which of course must be run before the mail merge templates are designed. 

 

Build: 5.00.071

Monday 4th June 2001

  1. Grid_KeyPress events expose the KeyAscii parameter which can be set when masking data input.
  2. Script functions which expose parameters occasionally set the parameter to 0. This has been fixed.
  3. If the string <<Initialisation.UserId>> is added to frmContacts queries, it is automatically replaced by the current logged in UserId before execution. This can be used to show only the relevant contacts for a particular user, user group, or branch.

 

Build: 5.00.070

Friday 25th May 2001

  1. New get/let script friendly property: Initialisation.GlobalParameterValue which allows programmers to share their own run-time variables between all instances of script engines.
  2. When loading entity record form, the wildcard search not invoked when the underlying record is known e.g. from history menu. This makes the loading more efficient.
  3. New UsrCfgUsers flag which if set to False, will disable the Quicken style auto-match combo lookups (e.g. JobTitle, Department etc..). The flag is FName=AutoMatchLookup, FType=B, FValue=False. 
  4. Entity search forms now only load 1 instance per entity. This is in keeping with contacts, companies, requirement search and placement search where only 1 search form is necessary.
  5. Entity forms are now subject to the multiple form instances settings so that it will not be possible to continually launch form instances.
  6. Virtual forms are now subject to the multiple form instances settings.
  7. If the string <<Initialisation.UserId>> is added to any query, it is automatically replaced by the current logged in UserId before execution. This can be used to show only the relevant contacts/companies etc.. for a particular user, user group, or branch.
  8. New TriSys32.ini file setting to override the built-in logic which forces the display of the contract/permanent related fields:

            Requirement Tab Logic=False

    When this is set to False, no field display logic is applied which forces the display of the permanent fields (salary, bonus etc...) when permanent is checked, and the contract fields (pay/charge rates etc..) when contract is checked.

     

 

Build: 5.00.069

Wednesday 9th May 2001

  1. Candidate search form now exposes all buttons in 800x600 screen resolutions.
  2. Candidate search form now further exposes the search results grid to allow finer control by script of both the column layout plus SQL used to generate it.

 

Build: 5.00.068

Tuesday 8th May 2001

  1. TimeSheet hours data entry does not now raise a run-time error. 

 

Build: 5.00.067

Thursday 26th April 2001

  1. When searching using a post code radius (using QAS libraries), removing the post code or city from the search correctly resets the search parameters and the old post code results are not used.
  2. Citrix/terminal server combination sometimes causes the disk serial to return 0 because the C drive may not exist. TriSys now locates the appropriate local fixed drive.

 

Build: 5.00.066    

Tuesday 24th April 2001

  1. Modal virtual forms do not show up in the main binder New menu.
  2. When config fields are not visible on certain form versions, saving the record with those forms does not overwrite the value obtained from forms upon which it is available.
  3. Field validation on save is also not performed for those fields which are not available on the form in above scenario.
  4. Where a Group By clause exists in a query, the context substitution for the current data does not cause a SQL error.
  5. History records for new entities now work after program is restarted (where form references are refreshed).
  6. Virtual forms cannot be linked to using entity builder.

 

Build: 5.00.065    *** Warning: This is a Beta release. It has not been tested or validated outside the development centre. ***

Wednesday 11th April 2001

  1. Reports migration. The reports.ini file is now migrated into the database so that all report configurations are now controlled from form designer and the reports.ini file is no longer used.
  2. Any report can now be customised with an associated form for capturing report parameters, and associated script, which can be used to prepare data for the more complicated reports prior to running the report itself. It is thus possible for any report to be created without being hindered by the limitations of Crystal reports.
  3. Form designer and TriSys options (administrator only) can configure a reports folder from where all reports are read. This allows for central control of reports to eliminate the need to have separate reports on every workstation.
  4. Print button now visible on Entity Search form now that entity search reports are now fully integrated.
  5. The report destination options have been removed as they are specified per report using form designer.
  6. Reports specified as Word Processor, Spreadsheet or Web are saved in the Documents, Spreadsheets and Web reports sub folders respectively. This is a temporary storage area only and files will be overwritten.
  7. New REPD unlock code required for report design.
  8. Form buttons can now be created to run a specified report. The report is invoked with context sensitive SQL clause depending upon underlying record.
  9. Individual reports can now be invoked from script (see script tutorial document).
  10. Full backward compatibility preserved for existing reports e.g. support for prompts and formulas has been retained.
  11. Activity search results now shows the display description i.e. the contact name, company name and brief description.
  12. Action Date when used in an e-mail merge is formatted as DD-MMM-YYYY not with trailing time (bug introduced in 5.00.062).
  13. Word launch from listbar now makes word visible again.
  14. New form property for main form ListBar.ListMargin exposed which allows the vertical margin to be larger. This is useful when making the text wrap.
  15. List bar logo dimensions now retained between invocations so that a smaller list bar logo will correctly cause the list bar to be shown smaller than the default.
  16. Deleting an action linked to a form button does not cause SQL referential integrity error.
  17. Can now delete a button in form designer if an action/report/component ref only. This is necessary when exporting forms with buttons linked to actions or reports.

 

Build: 5.00.064

Tuesday 3rd April 2001

  1. Lookup skills of type list can now be multi-selected using the pop-up skill list by highlighting with the Shift &/or Ctrl keys. This allows for much faster data entry.
  2. Options->Setup dialogue now allows for the List Bar Logo to be set in the Miscellaneous tab. This shows a graphic beneath the list bar on the left hand side of the application. The list bar is resized relative to the width and height of the graphic. This functionality is provided to facilitate product branding e.g. headhunter, temps etc..
  3. New View menu options on main menu so that the List Bar, tool bar and tab views can be turned on and off depending upon the users preference.
  4. New 16x16 icon for placement toolbar button and related forms.
  5. Support for Big Edit Buttons in multi-line text boxes. When the big edit button check box is ticked for the field in Form Designer, an ellipses button is shown top right within the text box on the form. When the user presses it, a large text input dialogue  is shown modally to capture data input.
  6. Form resizing now tolerates widget failure without causing other resize events to abort. Some widgets cannot be resized under certain conditions and this has been addressed.

 

Build: 5.00.063

Sunday 1st April 2001

  1. Support for modal virtual entities. DbMigration adds new field: EntityDescription.ModalForm which denotes when the virtual entity is to be displayed modally in order to capture user input before control is passed back to the calling script code. See Script design and tutorial document for full details of how to implement virtual entity support.
  2. Export of any entity now creates the associated button in the main form for inclusion on the list bar.
  3. C:\Program Files\TriSys32\Images folder does not exist, so graphics files (*.jpg, *.bmp, *.gif) files copied to C:\Program Files\TriSys32\Graphics folder.
  4. Can add client contacts as well as candidates to shortlist grids in both candidate search and requirement candidate search.

 

Build: 5.00.062

Friday 30th March 2001

  1. Virtual Entity/Form support added to form designer. This allows a new blank form to be created using the entity builder. No links to existing entities are made, and the generated form has no default functionality other than the ability to be loaded into the GUI framework and accessed like all other forms. The form functionality is coded entirely using script.
  2. Virtual forms can be exported between databases easily as no underlying SQL tables or data needs to be migrated.
  3. TriSys copies icons (*.ico) and graphics files (*.jpg, *.bmp, *.gif) from the Update folder to C:\Program Files\TriSys32 folders Icons & Images respectively at startup.
  4. Config fields of type Date can now support either date or time. Setting the field properties of a date field in in form designer to have a display format of HH:mm or HH:mm:ss will cause the control to show a spin type time entry input control not a drop down calendar.

 

Build: 5.00.061

Wednesday 28th March 2001

  1. New ActionFunction fields created via DbMigration which can be set in Action builder: EMailCandidate & EMailClient.
  2. Setting these flags explicitly on the Action Function E-Mail tab now overrides the default behaviour relating to sending e-mails which always sends the e-mail to the client contact if the client contact field is on the action form, else it sends it to the candidate if the client contact field is not on the action form.
  3. These new settings are particularly useful when running an interview action where separate action functions allow interview conformation e-mails to be sent to both the client and candidate. See associated demonstration document to describe this mechanism.
  4. If sending an action e-mail, leaving the Note/History &/or Follow-up Activity Text fields blank will allow the e-mail text to be inherited at run-time. This allows a copy of the e-mail to be recorded, and saves having to duplicate the e-mail text.
  5. Action function name can now be 50 characters long - up from 30.
  6. Config field names can now be 50 characters long - up from 32.
  7. Skill categories can now be 50 characters long - up from 32.

 

Build: 5.00.060

Tuesday 20th March 2001

  1. Exposed FormObjectsLocal.FormRef.RunFormAction function to allow actions to be fired from script code. This allows developers to hook actions to script generated grids overriding the TriSys action invocation logic for assigning contacts, companies etc...

 

Build: 5.00.059

Monday 19th March 2001

  1. Skills list box counter caption for company skills now displays correct count.
  2. If query action icon not available on system, no error is shown when loading query form.
  3. DbMigration creates a new flag ActionFunction.NHCreateOnActionDate which is normally false when creating new action functions. The action function form permits this to be set to True allowing the note/histories to be created on the selected action date, not today. This allows for retrospective actions to be run e.g. CV Send (See build 5.00.057).
  4. Candidate Search now has option to Show CV's not Referenced. When checked, this shows any CV's which are not referenced but are indexed. They can be auto-recognised on demand by using the Edit->Auto-Recognise CV option.

 

Build: 5.00.058

Monday 12th March 2001

  1. Added check to ensure object variable not set error does not occur following task generating actions for requirement/placement forms where no record is open.
  2. Indexing server (/s command line option) does not raise object variable not set error on exit.
  3. Save file-as format now correctly saves in rich-text format (RTF) which results in smaller, not larger files.
  4. Mail merging will not merge to a currently open document under any circumstance.
  5. Exposed grid events for programmatically controlling updateable grids now available from script.
    • Grid_AfterInsert
    • Grid_AfterUpdate
    • Grid_KeyPress
  6.  

 

Standard Actions Live Database

Thursday 8th March 2001

  1. Empty Standard actions database ready for production implementation.
  2. Will need latest client software and associated templates and reports.
  3. New Action Function field added. This is available on the Note/History tab. It is called Create Note/History on Action Date and should only be set if the user is permitted to change the action date and thus create the associated note/history on the selected date, not the current date.

 

Build: 5.00.057

Tuesday 6th March 2001

  1. If Action Date is added to an action form, this is used as the Note/History date for all action functions. This allows for retrospective actions to be generated which generate notes/histories on a previous date.
  2. Behaviour of requirement shortlist grid changed so that double clicking the record drills down into the candidate record. To edit the shortlist stage e.g. manually set a date for an action, the right mouse clicked pop-up menu option Edit Shortlist Stage must be selected. 
  3. History menu items now reflect changes to record if updated e.g. the contact name changes on the menu if the contact name is changed and saved on the contact form.
  4. History menu now shows the job title for requirements and placements.

 

Build: 5.00.056

Monday 5th March 2001

  1. When CV auto recognising and selected option on exception is to use new document and auto-recognise, saving the contact details no longer raises a SQL syntax error on Surname. 
  2. Added Action.ShowInMenu field (default=True) to allow designers to specify whether an action shows in the Action menu. Some actions are only relevant as a button action, so inclusion in the menu is unnecessary.
  3. New functions on requirement form to get access to the search results shortlist/delete rows:
    • GetShortlistCandidatesFromSearchResults
    • GetDeletedCandidatesFromSearchResults
    See the scripting design document for detailed explanation and code examples.
  4. Deleting candidates from shortlist where more that 1 action has been run against any candidate, does not raise a foreign key exception.
  5. DbMigration sets read-only file reference fields to non-read-only. Any existing file reference fields which need to be read-only, must be manually changed.
  6. Word documents are again opened only read-only if the option to open read-only is set (Options->Setup->Search->Open Document Read-Only).

 

Build: 5.00.055

Monday 26th February 2001

  1. Removed all support for ODBC with 1 exception. ODBC settings now not available from login setup dialogue. Access to SQL Server is always via OLEDB/ADO.
  2. The only exception is for compliance with ISYS comments indexing which requires an ODBC data source. 
  3. Form designer login now does not have an ODBC tab. Interface between TriSys and Form Designer does not include ODBC settings.
  4. Can now use ellipses button in computer name field to browse a computer in the network. This is implemented in form designer/utilities login and TriSys login setup.
  5. When a user is prompted for a NLIC (No License) code, a hyperlink to www.justassociates.com/TriSysRegistration.asp is available on the unlock dialogue. This will launch the internet browser to access the web site where they may input their challenge code and receive the unlock code via e-mail.

 

Build: 5.00.054

Friday 23rd February 2001

  1. Actions run from a requirement form now allow the contact details to be changed and persisted into underlying action functions and stored procedures. Previously only the client contact assigned in the requirement was used even if changed by the user.
  2. New VBScript friendly function available from Selection object: Function FastContactSelection ( Clients as Boolean, Candidates as Boolean ). This allows the script developer access to the fast search technology in TriSys for popping up dialogues for the users to select contacts.
  3. New VBScript friendly function available from Selection object: Function FastCompanySelection
  4. New VBScript friendly function available from Selection object: Function FastRequirementSelection
  5. New VBScript friendly function available from Selection object: Function FastPlacementSelection
  6. Form designer allows exporting form designs/actions/scripts/queries if the computer is not authorised for support, if an EXPF challenge/response code is entered. This allows ad-hoc export on customer computers when normal access is not possible, and protects against illegal copying of actions by customers.

 

Unlock/License Site 

Friday 23rd February 2001

This release comprises the 2 security tools for version 5 to provide challenge/response codes and license customer sites. The zip file is password protected and this password is known only to authorised personnel.

Folder/File

Comments

C:\TriSys 5.00 Utilities

The folder where system administrator only utilities are securely held

TriSys5_Unlock.exe

The TriSys version 5.00 challenge/response code generator and unlock program

LicenseSite5.exe

The site license utility for licensing TriSys customer sites.
TriSys User Licensing.doc Technical Support Only document describing procedure to license sites where access not permitted.

 

Build: 5.00.053

Tuesday 20th February 2001

  1. Generation of action functions now performed whilst a pop-up progress message dialogue is displayed on-top of TriSys. This provides the user with a visual display of progress and related messages. The user will see each function that they have selected being processed in the sequence specified by the action designer (e.g. 1., b. etc..) The user can abort the action processing by selecting the abort button.
  2. Actions which generate mail merges now perform the mail-merge automation with Word in the background. This prevents Word popping up and loading document templates etc... When all action functions are complete, all generated word documents are made visible.
  3. Check boxes on action form which are not functions e.g. Alarm, do not have three states e.g. off/on/greyed. Note: the greyed ticked state forces the function dialogue to display where the user can override defaults.
  4. Read-only reference fields added to action forms do not have associated find buttons (file, contact, company, user etc..) so that they cannot be changed.
  5. Metrics for Graph Sets->Graph for Each User now work correctly.
  6. Removed support for mail-merge reports in Reports.ini. This mechanism was introduced in 1999 and was superceded by Actions.
  7. New, Open, Save & Print menu options available from File menu on main binder.
  8. Consecutive prints (to screen) of the same report, will force closure of the previously run report on the same tab view as the new report. This is to aid the user in identifying which report is more current, save the user the trouble of having to manually close reports, and to minimise the use of un-necessary windows resources.
  9. Adding a new requirement when another user has saved a new requirement during the edit, does not cause a unique error. The new requirement is allocated the next available unique number.
  10. When a script function is called which does not expose the correct signature (function parameters), the name of the function is shown in the error message to help error diagnosis.
  11. All ADO SQL errors are cleared before running any form script code. This ensures that any SQL errors generated by script, are correctly captured and reported from within TriSys.

 

Version 5 Reports

Tuesday 20th February 2001

  1. This zip file contains the complete list of standard actions reports for V5.
  2. All of the original Crystal 4.6 format reports have been upgraded to Crystal 8.0 format.
  3. The reports have been compiled against the Standard Actions SQL Server 7.0 database schema.
  4. In order to use these reports against a non-standard actions SQL server you will need to make the following changes to your SQL Server schema:

     

    • Contact.WorkTelNo:              text --> varchar(50)
    • Contact.MobileTelNo:            text --> varchar(50)
    • Contact.FaxNo:                  text --> varchar(50)
    • Contact.Grade:                  text --> varchar(128)
    • Contact.Department:             text --> varchar(128)
    • Contact.LTDCompany:             text --> varchar(64)
    • Contact.RegistrationNumber:     text --> varchar(50)
    • Contact.VATNumber:              text --> varchar(32)
    • Contact.NINumber:               text --> varchar(32)
    • Contact.EMail:                  text --> varchar(255)

     

    • Company.RegistrationNumber:     text --> varchar(24)
    • Company.VATNumber:              text --> varchar(24)
    • Company.EMail:                  text --> varchar(255) 
    • Company.WebPage:                text --> varchar(255)
    • Company.MainTelNo:              text --> varchar(50)
    • Company.MainFaxNo:              text --> varchar(50)

     

Build: 5.00.052

Thursday 15th February 2001

  1. SQL errors generated from within script code, are correctly diagnosed and reported using normal error handling mechanism. This aids debugging and diagnosis of data integrity related errors.
  2. LoadShortlistStagesCandidates method of Requirement form is publicly exposed to script to allow refreshing of the shortlist grid following script manipulation.
  3. Sending a post-it note as an administrator to all users, will send to all users (even other administrators) other than the sender.
  4. When using post code candidate searching, the post shortlist/delete operation now correctly uses the original cached post code search to re-populate the search results grid.
  5. TAPI (Telephony application programming interface) compliant auto-dial which utilises TAPI32.DLL. TriSys now communicates with the configured COM port on the computer in the same way that Outlook or any other contact management tool does. Configuration of this mechanism simply requires setting the option:  Options->Setup->Auto Dial->Automatic Dial On. Dialling prefix is retained to be used when using a company socket requiring a dialling prefix.
  6. Splash login screen is not now 'on-top' of all other non-TriSys windows during login and initialisation. This allows the users to perform other non-TriSys windows tasks during startup, and also allows miscellaneous system related messages (e.g. Windows Installer kicking in unexpectedly) to be seen.
  7. Main binder restored to full screen maximised if closed in this configuration.
  8. Partial refresh of some config forms addressed. Form should always resize correctly.

 

Build: 5.00.051

Wednesday 14th February 2001

  1. Action lookup fields set to Read-Only in form designer, do not show ellipse ... button in field to allow user to change.
  2. In form design action function and TriSys action when invoked, the e-mail field combo now contains all fields of type E-Mail in addition to the default contact and company e-mail fields.

 

Build: 5.00.050

Tuesday 13th February 2001

  1. Placement form tab logic now correctly refreshes the permanent or contract tabs depending upon the placement type.
  2. Restore form positions on login option now persisted between invocations when set.
  3. Placement View menu no longer has options for the client and candidate contract documents because these have been superseded by the more flexible actions method of generating multiple placement related paperwork.
  4. Clear scheduled activity button on Requirement form does not cause an invalid property error.
  5. CV Auto-recognition CV text (left side) can now be copied to the clipboard using Ctrl-C and pasted into the fields (right side).
  6. When adding a new requirement from a contact record using the Add button on the same tab as the Requirements grid, if the contact is a candidate or client candidate, the requirement does NOT add the contact as the client contact in the new requirement. Only if the contact is a client, are they added to the new requirement as a client contact.
  7. View My Clients/Candidates/Client Candidates options now supported without error in contacts views.
  8. New TriSys32.ini file setting to override the built-in logic which forces the visibility of the contract/permanent related fields on the contact form:

            Contact Field Visibility Logic=False

    When this is set to False, no contact field visibility logic is applied which forces fields such as salary/rates/assignment dates/bonus/benefits etc.. to become visible/invisible depending upon whether the candidate seeks contract or permanent work. The fields which are normally overlaid will need to be repositioned using form designer for this to be effective.

 

Build: 5.00.049

Friday 9th February 2001

  1. Form designer checks for existence of required contact, company etc.. records before generating Universal Data Source Mail Merge File (.tmm).
  2. Form designer does not generate run-time error generating the above file if the EntityDescription table references a table which does not exist. This can happen if form designs are exported but the table schema is not.
  3. Double clicking a grid on a form in form designer shows the grid field name in the caption. Now that grids are fully configurable, this is an aid to script developers.
  4. Licensing form designer for scripting when challenged is now correctly persisted between sessions.
  5. If a date field is designed with a default value to be mandatory then no check box is shown with the date so that the user cannot make the date null during data input.
  6. Script setting default screen values during form events does not cause dirty form on load if the script obeys the recommended programming rules.
  7. Where script code takes responsibility for populating grids using the Grid_BeforePopulation event and wishes to use the Grid_RowLoaded event, the Cancel function parameter is correctly returned from the outer event function.

 

Build: 5.00.048

Wednesday 7th February 2001

  1. Referential integrity error caused by existing RequirementCandidateIgnore record on contact deletion has been fixed.
  2. Dirty prompt on first load of contact form without changes does not now occur.
  3. Reference core entity lookups e.g. contact, user, company etc.. now passed through to actions.
  4. Form scrolling code tightened to restrict scrollbars when form greater than minimum size.
  5. When deleting a candidate with a referenced CV, the user is prompted to delete the CV as well as the contact. If the user deletes the CV, it is deleted and placed into the recycle bin from where it can be permanently removed or restored.

 

Build: 5.00.047

Sunday 4th February 2001

  1. Adding a user with a login name containing space characters is not allowed. Spaces are removed if user attempts to create a login with them.
  2. Script Grid_RowLoaded event enabled in requirement and placement search forms.

 

Build: 5.00.046

Thursday 1st February 2001

  1. Stress ActiveX automation server (5.00.046) fully integrated with TriSys5.exe.
  2. Stressing activated by following this procedure:
    • Copy TriSysStress.exe into C:\Program Files\TriSys32
    • Run TriSysStress.exe to register
    • Run TriSys5.exe with /stress command line option e.g. c:\Program Files\TriSys32\TriSys5.exe /stress
    • Select simulations and options and run once to ensure tests complete correctly
    • Select maximum counter and run continuously to fully stress the system.
  3. Stressing exposes the mechanisms to:
    • Allow maximum stressing of the application/environment/network/database
    • Mimic the behaviour of a typical user although at much greater load parameters
    • Test the stability of the client environment
    • Test the stability/functionality of the application
    • Allow for detailed metrics to allow correct sizing of the entire system
    • Duress the SQL Server to test configuration
    • Allow saturation of terminal server environment with limited CPU/RAM to determine maximum loading
    • Setup 'rolling demos'
  4. Stress functions currently available:
    • Load Contacts, View and Save Contact
    • Load Companies, View and Save Company
    • Load Requirements, View and Save Requirement
    • Load Placements, View and Save Placement
    • Load Diary, View and Save Activity
    • Load Activities, View and Save Activity
    • Load Contacts, View and Print

 

Build: 5.00.045

Wednesday 31st January 2001

  1. If a company does not have any associated contacts, selecting the requirements/placements tab does not cause a run-time error.
  2. If fixed currency field has been removed from form (requirement, placement etc..) the currency linked to the record will always default to the default currency (ordering=1).
  3. If the Reference field for requirement or placement forms is not read-only, then the user can change the generated reference for new records before saving provided that it is unique.
  4. Entity form tabby_Click event is public to allow script developers to force tab selection and redraw.
  5. If an e-mail action is run, no duplicate e-mails will be sent to any recipient. This was caused if any contacts on the list had no e-mail address.
  6. If an e-mail action is run, no note/history records are created if the contact does not have an e-mail address. This is added to ensure that the audit trail of e-mails sent within TriSys is accurate.
  7. Setting contact owner from the Options->Contact Users menu does not result in a type mismatch error.

 

Version 5 Reports

Wednesday 31st January 2001

  1. This zip file contains the complete list of reports for V5 at present.
  2. Only half the reports in Crystal 4.6 format have been upgraded to Crystal 8.0 format.
  3. The Crystal 4.6 reports will work in TriSys 5.00 providing that an ODBC data source is configured to point at the same OLEDB SQL Server.

 

Build: 5.00.044

Tuesday 30th January 2001

  1. Comments free text search now works correctly in both candidate and requirement candidate search.
  2. In Requirement candidate search, where a CV is indexed but not attached to a candidate record. The CV is correctly displayed within the search results window and can be auto-recognised when the Show CV's not Referenced option is set.
  3. DbMigration creates a new field: FormProperties.HelpContextId which allows any form designed form (form, action, query) to specify what the help context id number is in the .hlp file. This allows for the help file to be customised to specific customer requirements.
  4. HelpContextId can be set using form designer for any form by editing the form properties in the usual fashion (Edit->Form Properties... menu or by double clicking the form caption). This can be set to the actual mapped id in the help file containing the information about the form/action/query.
  5. All reports re-compiled for Crystal 8.0 format using OLEDB Driver for SQL Server.
  6. New help file integrated with on-line context sensitive help where available.
  7. Now possible to license expiry date and concurrent licenses from TriSys using authentication codes. The documentation for this is available to authorised personnel only.
  8. New Unlock utility containing new codes to support above.
  9. Selecting Requirement from an action now provides the options to search requirements to which the contact is related e.g. owner, shortlisted candidate, but also allows the specification of the requirement reference which can be used to list all requirements which match. This is done via a pop-up menu.
  10. If the Delete key is used on any text box in any data entry form, it causes the form to 'dirty' and prompt the user for save on close.

 

TriSys 5.00 On-Line Help  

Tuesday 30th January 2001

This release comprises the 2 help files required for the latest build (5.00.044 or later). This .hlp file is now integrated with TriSys to provide context sensitive on-line help to users.

Folder/File

Comments

C:\Program Files\TriSys32

The installation folder where the help files are to be placed.

TriSys V5 User Help.hlp

The TriSys version 5.00 help file.

TriSys V5 User Help.cnt

The help contents file.

 

Build: 5.00.043

Wednesday 24th January 2001

  1. When action form loading for the first time, the progress dialogue shows the action display name not internal action name. 
  2. New table reference to RequirementCandidateUnderScriptControl within requirement candidate search. If this table exists, then any candidates referenced for the current requirement are ignored in the search results. This is to facilitate customer specific extended shortlist processing by way of the scripting engine as required. TriSys provides no mechanism to maintain this table, it is to be done entirely by the script developer.
  3. CV Auto-recognition now interprets no availability as an unknown date, and availability of x weeks as today + x weeks.

 

Export Wizard 

Wednesday 24th January 2001

This release comprises the export wizard tool and supplementary files 2 necessary for exporting SQL Server data into ASCII files. The ASCII files can be compressed using WinZip to a fraction of the size of the SQL Server backup and can thus be easily e-mailed for faster problem diagnosis. This zip release is password protected and authorised personnel have been appropriately instructed.

Folder/File

Comments

C:\TriSys 5.00 Utilities

The folder where system administrator only utilities are securely held

ExportWizard.exe

The TriSys SQL Server export wizard utility.

Export Wizard Stored Procedures.sql

The SQL script which creates the supporting stored procedures in the SQL Server

ExportWizard README.txt

Release notes for utility

ExportWizard Design Document.doc

User guide and system design specification.

 

Build: 5.00.042

Friday 19th January 2001

  1. Where a Crystal report has been designed (incorrectly) with hard coded table paths (e.g. ITContract.dbo.Contact), this path is dynamically overwritten by the current path in the current database.
  2. Each Crystal report table is automatically checked for schema differences with the corresponding SQL Server table. Each difference is reported to the user for each invocation of a report. This check can be turned off by checking the check box on the first message. Every report should be checked during acceptance testing to ensure that all reports and databases are synchronised.
  3. Where the Crystal report has been generated by an earlier version using ODBC data sources, OLEDB cannot be used to connect the report to the database. If the client computer has an ODBC data source which does not connect to the same database as that currently in use, an error message is raised to inform the user.

Build: 5.00.041

Thursday 18th January 2001

  1. Industry skills form only makes Synonyms button enabled when the skill category is a non config field lookup.
  2. Only non config skill category skills are loaded into the synonyms combo during maintenance.
  3. Date picker scripting events fired for requirement and candidate search forms.
  4. New function available to VBScript to allow access to windows API calls:
    • Miscellaneous.CallWindowsAPI ( sAPIFunctionName, Param1, Param2, ...)
    • sAPIFunctionName is the name of the windows API function 
    • Param1, Param2, ... are the respective variant parameters for the API
    • The function returns a variant which is the return value of the API call
    • Currently GetParent and SetParent are the only implemented functions.

 

Build: 5.00.040

Tuesday 16th January 2001

  1. When in a scheduled activity, pressing the follow-up button and saving the new activity correctly preserves the links to any underlying requirements/placements etc..
  2. New events available for form scripts:
    • Form_ExternalRefresh ( FormName, Id )

                Called when any record is saved to allow refreshing or processing of saved record.

                Parameters are the form name e.g. frmContractorInvoice and the record Id

    • Grid_BeforePopulation ( SQL, Cancel )

      •   Called immediately prior to generating a recordset to populate a grid and after the SQL has been dynamically generated from both the form designed query and the on-screen selections.

       

  3. Button click events raised for search forms e.g. RequirementSearch, PlacementSearch etc..
  4. Entity forms are now restored following login if Save & Restore Form Positions and Restore Form Positions on Login are selected.

 

Build: 5.00.039

Thursday 11th January 2001

  1. Cursor key problem causing tab views to change has been fixed. All text/list boxes now process cursor/arrow keys when expected.
  2. Company Addresses grid on Company form now has a larger row height which allows all of the address to be viewed vertically.
  3. Any grid query default row height can be set in Form designer by resizing at design time.
  4. When candidates are deleted from either the candidate search shortlist or requirement candidate search shortlist, the deleted candidates are added to the deleted candidates grid.

 

Build: 5.00.038

Wednesday 10th January 2001

  1. Form designer can be used to create config fields of type Grid which can be controlled by script only.
  2. New grid event: Grid_RowSelection fired when a grid row is highlighted/selected.
  3. All grid events for all Grid widgets passed to scripting engine.
  4. Status message indicating number of contacts displayed is correct in contacts form.

 

Build: 5.00.037

Tuesday 9th January 2001

  1. Skill synonyms dialogue now modal from Industry Skills form.
  2. Form designer can be used to create fields of type Grid which can be controlled programmatically by script at run-time.
  3. Industry skills list does not disappear when Company form closed.

 

TriSys Web 2000

Tuesday 9th January 2001

  1. Support for expenses.

 

Build: 5.00.036

Sunday 7th January 2001

  1. Sophisticated VB Script code editor implemented in Form Designer providing following features:
    • Familiar VB code editor
    • Key word highlighting - for, next, sub etc...
    • Full support for undo, redo, cut, copy, paste, find, replace
    • Support for loading/saving scripts from/to files
    • Comments highlighting
    • Fully scrollable
    • Horizontal and vertical splitters
    • Line and column position status
    • 4 space tabs
    • Word selection
    • Block selection tabbing
    • Bookmarking
    • Auto-function insertion
    • Function and event positioning
    • TriSys Object function lookup
    • VB Script keyword lookup
    • Multiple script editors to facilitate code sharing

  2. Sophisticated SQL Query editor implemented in Form Designer providing following features:

    • Familiar SQL Server Query Analyser code editor
    • Key word highlighting - Select, From, Where etc...
    • Full support for undo, redo, cut, copy, paste, find, replace
    • Comments highlighting (-- and /* .. */)
    • Fully scrollable
    • Horizontal and vertical splitters
    • Word selection
    • Block selection tabbing
  3. Similar (slightly less functional)  SQL and VB Script editors respectively available from within main application:
    • File->Database->SQL
    • File->Database->Scripting Engine
  4. Diary manager views are no longer appended to the History menu.
  5. Crystal reports now invokable from within non-development (secure) environments
  6. Binder cursor problems where cursor interpreted as tab view click improved. Non visible forms are disabled which helps capture the focus.
  7. Forcing save of contact details without changes does not lose skills.

 

TriSys Full Install

This build is the full setup kit of version 5 utilising the Wise installation system toolkit. This setup kit comprises a single downloadable executable which is password protected.

The setup kit installs the following products/components:

Product Comments
DCOM98 Microsoft Distributed Component Object Model. This is only installed on Windows 95 computers which do not have DCOM.
MDAC 2.5 Microsoft Data Access Components. This is only installed on Windows 95, Windows 98 and Windows NT computers which do not have Office 2000 installed.
TriSys 5.00 These are the standard files including all libraries (DLL/OCX etc..) which are required by the run-time system. The main files installed are detailed here.
Reports Standard set of Crystal Reports and integration information.
Icons & Graphics All 32x32 and 16x16 icons used by the product. Also a selection of graphics files (jpg, gif, bmp) for adding effects to product.
Help The on-line context sensitive help files and FAQ.
QAS Post Code Libraries The QAS UK post code database libraries for customers who have licensed the QAS Post code Address File (PAF) database.

 

 

This setup kit installation has been tested internally on Windows 95 and Windows 98.

The minimum hardware specification is: Pentium 120Mhz, 32Mb RAM

The minimum software specification is: Windows 95, Internet Explorer 4.01, Microsoft Office 97.

The recommended hardware specification is: Pentium II 450Mhz, 64Mb RAM for Windows 95/98/Me and 128Mb RAM for Windows NT/2000.

The recommended software specification is: Windows NT 4 or later, Internet Explorer 5.00, Microsoft Office 2000.

 

The installation will require at most 3 system re-boots for Windows 95. This is because DCOM98 is required for MDAC 2.5 to work on Windows 95 computers.

Windows 98/Me and Windows NT may require 2 re-boots, one for MDAC and one for TriSys 5.00

Windows 2000 may require 1 re-boot only. This is because it ships with MDAC 2.5 as standard.

Any computer with a working Microsoft Office 2000 installation may not require any re-boot because all system files are already installed.

Installed Files

Folder/File Component Comments
C:\Program Files\TriSys32 The folder where the product is installed
TriSys5.exe The TriSys version 5.00 client executable program
FormDesign.exe The form designer executable which, when licensed, can be used to completely customise the product forms, fields, queries, scripts, actions, workflow etc..
TriSys32.hlp Help Main on-line context sensitive help for applications. Note: Currently version 4 only. Version 5 under construction.
TriSysFAQ.hlp Help Frequently Asked Questions
Universal Data Source.tmm TriSys mail merge data source file for Word mail merges invoked from TriSys Actions.
isys.key Key file necessary to use third party ISYS text retrieval engine.
isysoem.pmt Original equipment manufacturer license permit for ISYS.
isys.cwd Common word file for ISYS.
isql32.exe ISYS SQL Server indexing engine.
isys.ixa, isys.ixb, isys.ixc CV's Pre-built document index files for demonstration CV's.

C:\Program Files\TriSys32\Utilities

 Utilities folder where a number of utility programs reside.
p_xxx.sql SQL Scripts utilised by DbMigration to implement business logic Stored Procedure into the SQL Server database.
TriSysQASNearestBuilder.exe QAS Build the QAS nearest database periodically to contain all addresses from SQL Server.
Lookup Test.exe QAS Test the QAS Post Code database libraries to allow post code lookups. Uses QAS-Rapid DLL's.
Nearest Test.exe QAS Test the QAS Post Code database libraries to allow nearest post code search. Uses QAS-Nearest DLL's.

C:\Program Files\TriSys32\Reports

 Reports folder where all reports and associated config file is located.
Reports.ini Reports The configuration file which allows Crystal Reports to be integrated into the application from where users can select the report to be run. Every report available to each user is specified in this file.
*.rpt Reports Suite of 50+ standard Crystal Report version 8.0 files which reports on numerous data views from the SQL Server database.

C:\Program Files\TriSys32\Graphics
*.jpg, *.gif, *.bmp Graphics Selection of graphics files to be used to create special effects in the application.

C:\Program Files\TriSys32\Icons
*.ico Icons Selection of 16x16 and 32x32 icon files which are used in the application. A standard icon editor can be employed to edit and create new variants of these files and configured into the application.

C:\Program Files\TriSys32\CVs

 Demo CV folder.
*.doc CVS 100+ demonstration public domain CV's for free text searching.

C:\Program Files\TriSys32\ ActionTemplates

 Standard Action Templates folder.
*.dot Actions 30+ standard action Word mail merge templates which can form the basis of customised Actions.

C:\{WINDOWS}

 Either c:\Windows (95/98/Me) or c:\WINNT (NT/2000) depending upon operating system.
TriSys32.ini Application initialisation file containing small set of application configuration parameters including database connection, document index, post code locations etc..

C:\{WINDOWS}\{SYSTEM}

 Either c:\Windows\System (95/98/Me) or c:\WINNT\System32 (NT/2000) depending upon operating system.
*.dll, *.ocx Dynamic Link Libraries (DLL) and OLE Customs eXtension (OCX) controls which comprise 'the platform'. These include the VB6 run-time, third party widget DLL's/OCX's, updates to Microsoft system DLL's, ISYS API, VBScript language.

C:\{WINDOWS}\Crystal

 Either c:\Windows\Crystal (95/98/Me) or c:\WINNT\Crystal (NT/2000) depending upon operating system.
p2*.dll Crystal Reports database drivers.
u2*.dll Crystal Reports function and export drivers.

C:\Program Files\Seagate Software

 Seagate Crystal Reports Run-Time libraries
Viewers\ActiveXViewer\*.dll, *.ocx Crystal Reports on-screen view libraries for viewing report inside TriSys.
Shared\*.dll Crystal Reports shared library files
Report Designer Component\craxdrt.dll Crystal Report run-time report designer.

 

Build: 5.00.035

Thursday 21st December 2000

  1. DbMigration correctly creates the SQL join for the requirement placement grid to get the candidate. This is only automatically applied to migrated databases. Existing databases requires that this change is made manually.
  2. New entity form window management issues addressed to allow separate views for search and record forms.
  3. Invoking an existing entity from any grid correctly loads and shows the form in a separate view.
  4. Fast search button invoked from main toolbar correctly fires the entity search modal dialogue.

 

Build: 5.00.034

Thursday 14th December 2000

  1. For grids which have a query defined with the same name as the FieldDescription e.g. ShortlistStages, the grid is initialised only from the query columns, not the form design which was relevant only prior to the implementation of queries. This has 2 advantages:
    • Form load is speeded up
    • In cases where the action has been removed, the problem of missing shortlist stages is irrelevant
  2. When any JobTitle field (Contact, Requirement or Placement) is added to an action form, it is correctly populated from the list of available job titles.

 

Build: 5.00.033

Thursday 14th December 2000

  1. New TriSys32.ini file setting to override the built-in logic which forces the selection of the contract/permanent tabs:

        Placement Tab Logic=False

    When this is set to False, no tab logic is applied which forces the display of the permanent tab when permanent placement is checked, and the contract tab when the contract placement is checked.

 

Build: 5.00.032

Thursday 14th December 2000

  1. Exporting forms from form designer now correctly exports the associated form script.
  2. Ellipses button on form designer login (where using File->Open menu) can be used to locate database on specified server.
  3. Can enter . if local computer name not known in form designer login.

 

Build: 5.00.031

Wednesday 13th December 2000

  1. The default country from the Contact.HomeAddressCountry field is used to default all new address records e.g. contact, company address, bank details.
  2. Drilling down into an existing entity record from the grid (using either double click or the update button) now shows the form.
  3. Login screen tab order is Login Name then password then Login hyperlink. Current focus is the password to speed up regular user login.
  4. Entity Search forms now show grid rows.
  5. Skills grids are now visible when skills tab selected in requirement, placement and company search forms.
  6. Form caption defaults are setup correctly.
  7. Searchable check box in form designer field properties dialogue is correctly enabled.

 

Build: 5.00.030

Monday 11th December 2000

  1. Diary view uses single SQL query only to retrieve each day, week and month view. Improves display time by at least a factor of 4.
  2. Activity search now uses single SQL query to populate grid. Improves search time by approximate factor of 20.
  3. In cases where Crystal Reports connection fails, the connection error is diagnosed immediately and reported. The connection is attempted using OLEDB (for new Crystal 8.0 reports) and then ODBC (for older Crystal 4.6 reports used in TriSys 4.0x).
  4. New colour palette available from form properties dialogue which implements recommended 313y palette for TriSys.
  5. Main binder caption now reflects that set in assigned main form in form designer.
  6. All instances of TriSys Professional captions are replaced with TriSys 5.00 by DbMigration.
  7. All non-configurable form captions are customisable by setting the form properties .Caption property. The form may have to be closed and re-opened for changes to take effect.
  8. Form designer field properties now shows the .TableFieldName property in the form caption.

 

Build: 5.00.029

Friday 8th December 2000

  1. Running an action from the contacts grid correctly places all contacts into the action contact field.
  2. Closing a form without completing mandatory fields does not close the form without saving changes.
  3. Running an action from an empty data entry form is not possible.
  4. When doing fast search from contacts or companies forms, the first record is highlighted to facilitate <Return> key processing for fast drill down.
  5. Job Title candidate search now works without generating SQL error.
  6. Attempt to delete candidates from search results where non selected generates polite message and no action.
  7. Match Requirements to Candidate option now works again.

 

Build: 5.00.028

Thursday 7th December 2000

  1. New file to be placed into the setup kit Update folder: TriSys5Copy.exe.
  2. TriSys5.exe 5.00.028 or later will search for the TriSys5 Setup.exe program and look for an Update folder beneath. If this folder is found and contains the TriSys5Copy.exe then the following rules apply:
    1. If TriSys5.exe in the Update folder is a later build than that installed in c:\Program Files\TriSys32, then TriSys5Copy.exe is launched to copy the newer file over the existing exe.
    2. If FormDesign5.exe exists in the Update folder then that is copied to c:\Program Files\TriSys32 as is any file which does not satisfy the following criteria:
    3. If any .rpt files or reports.ini is found in Update or any sub-folder i.e. Update\Reports, then they are copied to c:\Program Files\TriSys32\Reports.
    4. If any .dll or .ocx files are found in Update, they are copied to c:\WINNT\System32. Note: OCX files may need registering.
  3. Industry Skills form now resizes the splitter control and internal list boxes correctly on open.
  4. TriSys5.exe will only work if the full build (5.00.027 or later) has been installed.

 

Build: 5.00.023 

Friday 1st December 2000

Latest beta release of version 5 products.

Folder/File

Comments

C:\Program Files\TriSys32

The folder where the product is installed

TriSys5.exe

The TriSys version 5.00 client executable program

FormDesign.exe

The form designer executable which, when licensed, can be used to completely customise the product forms, fields, queries, scripts, actions, workflow etc..

Contact us now! Call +44 (0) 1223 393 519 © 1992-2012 TriSys Business Software| History | Twitter | Careers | Partner | Contact Us | Sitemap | Support