TriSys V7.02 Software Release Notes

Build: 7.02.045

04 April 2007

1. Temps booking sheet bug fixed.

Build: 7.02.044

03 April 2007

1. DB Schema changes made to improve Email processing performance significantly.

2. CV Send action can now be against multiple Requirements from Requirement search results.

3. Skills/Attributes form now has options to view unlocked, locked and all skills, as well as showing which fields are of type Field Lookup.

4. Diary options - users list now resized to available space to more tightly specify diary views.

5. Removing users or contacts from Schedule Task dialogue does not require confirmation.

6. Tidied 24x24 images in Navigation Bar.

7. When Retain Form In Memory is set, the application correctly closes.

Build: 7.02.040

15 March 2007

1. SMS Action now only records a note history if the SMS was sent successfully.

2. SMS Action cannot be configured to create a separate note history per contact.
   Requires new field on action form, Name: 'chkOneNoteHistory', Type: 'Yes/No'.

3. Activity links are now saved and restored correctly.

4. Activity description search now works as expected.

5. Email processing form now opens selected Email correctly when user has already previously opened the form.

6. When logging in, if the user chooses not to terminate an existing session the login screen re-appears allowing them to continue (in the past a bug resulted in the login screen disappearing).

7. Opening an existing Work History no longer results in an error.

8. Double clicking the contact list within an action no longer results in an error.

9. Clicking a pop up alarm while a modal form was displayed no longer results in an error.

10. When in a Requirement if the user has the CV/Summary displayed and uses the keys to move through the shortlist/search results focus now remains on the grid, allowing them to use keys without having to re-select the grid.

11. The Added By field on the contact record is now set when a users adds a contact.

12. The Requirement Shortlist grid no longer loses user layout changes whenever the grid is refreshed.

13. Re-arranging the order of look ups, or adding/deleting entries will no longer result in negative ordering figures.

14. Weekly Diary view now runs from Monday to Sunday. The first day shown can be altered using a system setting (1 = Sunday, 2 = Monday and so on): DIARY: Weekly View First Day of Week.

15. Female contacts created via CV Auto Recognition will now have the title "Mrs" if they are married, "Miss" if they are not.

16. Deleting a company that is referenced in a contacts work history no longer results in an error.

Build: 7.02.039

07 March 2007 - Call Fusion Beta Release

1. CallFusion integration added for internal testing.

Build: 7.02.038

02 March 2007

1. Visual progress bar form displayed when forms loaded can be turned off by setting the following system setting to False: Show Form Draw Progress.

2. When the stress testing is enabled and the start up prompt (7.02.028 #3) is answered with No, stress testing flags are disabled for the session. This prevents unwanted behaviour such as automatic selection of modal dialogues.

3. Fixed bug which allowed override of 'close open forms' dialogue introduced in yesterdays build.

4. The 'close open forms' dialogue displayed either if the number of forms open, or if GDI resources, exceed limits, can be suppressed (i.e. not displayed, and therefore the first item selected automatically) by setting the following system setting to False: Show Close Form Dialogue.

5. Config entity forms and virtual entity forms are retained in memory if the Tools-->Options-->Interface-->Retain form in Memory setting is checked.

6. The Tools-->Options-->Interface-->Retain form in Memory setting is read-only to non-administrators and read only from the setting defined by the system administrator.

Build: 7.02.036

01 March 2007

1. File reference fields lookup buttons restored.

2. Visual progress bar form displayed when forms loaded. This accurately shows the loading of each tab.

3. New system setting to set the maximum number of forms which can be loaded during a session - Maximum Number of Open Forms. Users are prompted to close open forms once the limit is reached. If this is not set or set to 0, there is no limit to the number of forms which can be opened. This setting should be used however in terminal services environments where resources are scarce.

4. System settings are only updated in the database rather than being removed and re-inserted.

5. Adding a new entity search automatically copies the name to the mandatory description field after losing focus to enable faster user operation.

Build: 7.02.034

28 February 2007

1. Task Description Free Text searches now work as expected.

2. Rates calculator updated.

3. Import utility now copes with files of size greater than 65,000 characters.

Build: 7.02.029

21 February 2007

1. CV searches against symbols ("C#", ".NET" etc) when ranking columns are shown no longer results in an error.

2. When the SMS action is run from the Requirement shortlist the system now correctly records the SMS note history against all selected candidates and the Requirement.

3. Entity Search no longer errors when searching against current remuneration.

4. Hidden fields placed on hidden tabs no longer result in errors during form load.

5. New event added "Form_DeleteChildRecords" that fires when a record is deleted to allow custom code to delete child record relationships.

Build: 7.02.028

06 February 2007

1. Stress testing / unit testing utility now updated with following enhancements:

   1. CRUD tests for Company, Requirement and Placement now operational

   2. Automatic settings on start up can be configured in the Application Properties of TriSys to automatically start unit testing with no required user interaction

   3. Contact and Candidate Id's can be set in the Options tab

   4. Details operational logging messages to the Log tab

   5. New contact and company records are created using a random name from the SQL NewId() function. This prevents duplicates in a multi-user test scenario.

2. New application properties settings are:

   1. Stress Testing Mode On - Set to True or False. True will launch TriSys in stress mode on start up

   2. Stress Testing User Count - Set to a numeric value and the stress testing utility will wait for this number of users to log in before commencing tests.

   3. Stress Testing Auto Start Tests - Set to the comma separated tests to be run on start up. Current settings are: Contact CRUD, Company CRUD, Requirement CRUD, Placement CRUD

   4. Stress Testing Auto Start Count - Number of test runs to invoke on start up

3. When /Stress command line option or automated application properties are set, TriSys displays a Yes/No message box question which defaults to Yes after 10 seconds to start the unit testing.

4. User Maintenance form now has additional button on the Network Permissions tab. This button allows the selected SQL Server login associated with the TriSys login name to be completely removed from all databases within the SQL Server. This functionality should only be used when the SQL Server login is corrupt and the user is unable to login to TriSys. SQL login corruption often occurs when databases are relocated between different SQL Servers.

5. When the SQL administrators login details are provided in the login setup form, and the user logs in as a non-administrator account, any matching accounts are removed and re-created with a new random SQL password. This SQL password is fully compliant with SQL Server 2005 complexity requirements, but is never known by the TriSys user as it is encrypted.

6. Licensee details in Help-->About correctly reported. This fixes problem where PWSL code was requested for licensed environments.

Build: 7.02.025

02 February 2007

1. Updated stored procedures for Dashboard to cache OLAP data rather than re-create on the fly for each logged in user. This greatly improves performance on start up.

2. DbMigration adds a new System Setting Cached OLAP Report Days. This is set to the number of days that cached OLAP reports can be displayed before requiring a full rebuild. Default is 1 day.

3. Dashboard charts now default to 3 dimensional settings, and a suitable background colour.

4. New setup kit contains the Unit Test (or stress testing) ActiveX utility. Running TriSys with the /Stress command line utility allows the user to stress both the client and server elements of the system.

5. Fix for Requirement rotation period calculations implemented.

Build: 7.02.024

01 Feb 2007 February

1. Added Logic for Project Entity (this requires specific migration of Project entity).

2. Fixed issue with Requirement rates being selected as Standard.

3. Changed default standard user SQL Login password to deal with SQL 2005 password complexity requirements.

Build: 7.02.023

29 January 2007

1. Fixed issue with View My Option Queries.

2. Altered Timesheet logic problem that locked the Timesheet grid after Sales Invoice Production.

Build: 7.02.022

23 January 2007

1. DbMigration updates all SQL Queries with code for View My options.

2. View My Options enabled for Contact and Company lookups.

3. Disabled button sound on About form.

4. Fixed issue in Requirement Rates that would not allow addition of custom rates.

Build: 7.02.021

22 January 2007

1. Database connection problems enhanced to support web services.

2. Added support for Word 2007.

3. View My options re-written to work with multiple entities and multiple user groups. Users are able to specify which entities (contacts, companies, requirements etc..) to which apply either the View My concept and optionally specify one or more user groups to which they belong. For example a user could specify that they wish to view only the contacts and companies which belong to the London branch, but can view all requirements and placements belonging to the entire company.

4. Disabled button sound on Login setup form.

Build: 7.02.019

19 January 2007

1. Added code to allow deletion of a company from the company form file menu. This code is the same code which is executed when deleting companies from the companies grid.

2. Web service support fully implemented within database classes to permit remote installation of TriSys with connection via TriSys Web Services to appropriate server farm identified by users login credentials in TriSys CRM.

3. Login setup form has new web services tab to select the TriSys web service as the data source.

Build: 7.02.014

16 January 2007

1. Async queries web service support added (Uses new GetADORecordsetAsBytes web service, requires new TriSysAsyncQueries.exe).

Build: 7.02.013

15 January 2007

1. When the Email direct mail action is run against multiple candidates the activities that are produced now insert the appropriate contact info into each activity.

Build: 7.02.012

11 Jan 2007 January

1. Job Title control how has a Hwnd property. This prevents errors in event handlers that use this syntax:

       Set fieldDescription = FormObjectsLocal.ShowForm.GetFieldDescriptionFromWidgetHwnd(fieldObj.Hwnd).

Build: 7.02.011

11 January 2007

1. Dashboard Email deletion performance improved dramatically.
   Requires background delete task to be set up in SQL Agent (Nightly run of 'Exec p_Delete_EMails_Marked_For_Deletion').

2. Application main window state and size now persisted and restored when closed/opened.

3. When the temps booking sheet is filtered by a job title and the user clicks the button to move to the next/previous period the system now allows them to move forward/back to the first period that contains a shift for the selected job title. This allows users to easily locate the first available shift for a specific job.

4. CV Searching now returns a Score column in the search results to allow Candidates to be sorted by CV relevance.

5. Within a Requirement on the search tab the defaults button now allows the user to load criteria from an existing search.

6. The interview action now allows the user to change the client contact to another person at the company.
   Requires a new button to be added to the Interview Action form "LookUpClient".

7. The system now forces all users except "SuperUser" to be a member of at least one group other than the "System Administration" group. The DB migration will create a new group and assign all users to it. From this release onwards the system will prevent any user from being removed from their last group.

8. CV Auto-recognition now allows the user to set the contact Source when Auto-recognising a candidate.
   Requires a new field to be added to the CVAR form "CandidateSource", type=Text, Lookup=True.

9. Bug in Email rule generation that meant creating several rules one after the other could result in invalid rules has now been fixed.

10. Attempting to type into the read only fields on a Requirement/Placement will now launch the appropriate editor.

11. The default country when adding a company address can now be specified using a system setting.
    System Setting: 'ADDRESS: Default Company Address Country'

12. When running the Email action the contact list was limited to 50 contacts. This limit has now been removed.

13. Skill tree selection list no longer limits the grid contents to X rows. All skills are now displayed.

14. The system no longer prevents user permissions being altered for version one of a form.

15. When the Email/Direct mail action is run from a Requirement it now links any note histories created to the Requirement irrespective of the Email type.

16. The View Duplicate Contacts function from the contacts list view menu now works with the new grids.

17. Error during application start up when the application was maximised and restoring form positions related to form positioning no longer occurs.

18. Executing the call contact action against a candidate on a Requirement shortlist now updates the called date within the shortlist.

19. Bug in Placement Search form that displayed invalid salary values is now fixed (v_PlacementSearch view corrected by DB migration).

20. Avery Contact Labels merge now works as expected (Requires the template to be updated to the latest version).

21. New HTML merge meta tag introduced:
    <meta name="Multiple Records Per Document" content="14">
    Specifies that this merge document is designed to merge multiple records into a single document, rather than creating a copy of the document per record. The content specified the number of record each repeatable section can hold. The system will duplicate the repeatable section the required number of times to include the correct number of records.

22. New HTML merge tags introduced:
    ##REPEATABLE_SECTION_START##, ##REPEATABLE_SECTION_END##
    Denotes the start of the repeatable section used when the meta tag described above is used. For an example of these in use see the 'Avery Candidate Labels.htm' file in the V7DemoData share.

23. When the application starts it now checks for a previous instance and gives the user the option to close the previous instance and continue.

24. Tempaid Export functionality added.

    1. For Tempaid Integration to work the following system setting has to be changed:
       
       Payroll Package: Setting = "Tempaid"
       
    
    
    1. New Fields added to frmContact for recording Contacts Tempaid Status
       Fields Added:
       SendtoExport (Yes/No, Default 0)
       TempaidFrame (Panel)
       TempaidBankOk (Yes/No, Default 0)
       TempaidAddressOk (Yes/No, Default 0)
       TempaidCompanyOk (Yes/No, Default 0)
       TempaidContractRef (Text)
       TempaidExportReason (Text)
       
    
    
    1. New Field added to frmTimesheet for recording Timesheet Export Status
       Fields Added:
       ExportDate (Date)
       
    
    
    1. New Field added to frmBackOfficeExports for Selecting Company Export
       Fields Added:
       TempaidCompanySelector (Text, Lookup with no entries)
       - This lookup picks its entries from the User Group and looks for Entries that contain text 'Company', The format for the entries is 'Company A - Tempaid'
    
    
    1. New Database Objects added to support Tempaid Integration
       Objects Added:
       v_TempaidTimesheetExport
       v_TempaidClientExport
       v_tempaidLtdCompanyExport
       f_GetPONumber(@TimesheetID)
       f_GetCurrencyAmountPeriodCurrency(@CurrencyAmountPeriodId)
       TempaidImport (Table containing Tempaid .dat file definitions)
    
    

Build: 7.02.010

08 December 2006

1. When running an action from within the company form the system now prompts the user to confirm if they want to run the action against the selected contacts, or all contacts against the company.

2. When viewing other users diaries the task owner is now shown against entries that do not belong to the current user. This makes it much easier view multiple peoples diaries.

Build: 7.02.009

05 December 2006

1. Entity search now allows the user to move criteria up or down using new buttons, rather than just drag and drop.

2. Entity search now has the ability to split a group of more than two criteria into sub groups when changing the boolean operator. This makes it much easier to construct complex search criteria.

3. Entity search mouse over highlighting glitch fixed.

4. Entity search 'Add to group' button now responds to mouse-overs and shows tooltip text.

5. Minor aesthetic improvements made to Entity search UI.

Build: 7.02.008

01 December 2006

1. The system now supports several new meta tags within the action templates (if these are not present the action will behave as normal):

   1. <meta name="Note/History Enabled" content="False">
      Sets whether this template will generate a note history by default.
   2. <meta name="Follow-Up Enabled" content="False">
      Sets whether this template will generate a follow up by default.
   3. <meta name="Follow-Up Days" content="7">
      Sets the default follow up delay in days from the time the action was run.
   4. <meta name="Follow-Up Alarm"content="False">
      Sets whether the follow up will be alarmed by default.
   5. <meta name="Follow-Up Alarm Lead Time" content="30 minutes">
      Sets the default alarm lead time - must match combo entry exactly.
   6. <meta name="Contact Type" content="Client">
      Specifies the contact type this template is designed for (Client = Client Or ClientCandidate, Candidate = Candidate Or ClientCandidate).
      If set the user will be warned if they attempt to run it against contacts of the wrong type.
      If they are running it against multiple contacts they will be given the option of removing the invalid ones.
   7. <meta name="Source Delivery Format" content="Word Document">
      Sets the default Source Delivery Format option - must match combo entry exactly.
   8. <meta name="Template Delivery Format" content="Attached as an RTF Format Document">
      Sets the default Template Delivery Format option - must match combo entry exactly.

2. Contact Titles can now be deleted using the look up editor.

3. Task search now contains a new search field named completed that will allow the user to easily search for all completed tasks (note-histories and scheduled activities that have been cleared). Requires view update to "v_Task_AllFields", applied to Dev and Test.

4. Contacts can now be searched based upon their company attributes or industry using search functions. Requires the "ContactSearchUsingCompanyAttributes.sql" file (located in DB migration folder) to be run against the customers DB.

Build: 7.02.007

29 November 2006

1. The system now records the output of the Email/Direct Mail and CV send action and attaches it to the generated note history if the output destination is not Email. If the site does not have the Exchange Sync tool running the system setting detailed below should be set to false and then the output will also be saved when the output type is Email.

   • Relies on the following systems settings:
     
     
     • EXCHANGE SYNC: Enabled
       When set to false actions with an output destination of Email will save the output against the note history as the Exchange Sync will not catch the Email at the server level. Defaults to true.

2. Switching between periods where no conversion rate exists resulted in an error. This no longer occurs.

3. Switching between currencies where no exchange rate exists resulted in an error. This no longer occurs.

4. Non fixed queries no longer require an associated form.

5. Grids based upon queries now pick up the maximum number of rows from the query definition.

6. Requirement search results now allow shortlisting/deleting of flagged, selected or all records.

Build: 7.02.006

27 November 2006

1. The system checks switches to see if it should auto generate web passwords for candidates/clients.

   • Relies on the following systems settings:
     
     
     • CONTACT: Gen. web password Candidate
       When set to true the Candidates will automatically have a web password generated. Defaults to true.
     • CONTACT: Gen. web password Client
       When set to true the Clients will automatically have a web password generated. Defaults to true.

2. Added functionality for exporting Payroll details to Resource Link Payroll package.
   Relies on the Stored procedure 'p_GetResourceLinkPayrollExport' and the function 'f_GetResourceLinkDailyHours'.

   • Relies on the following systems settings:
     
     
     • Payroll Package
       The value will be the name of the chosen package.

Build: 7.02.005

22 November 2006

1. Combo fields that have no default value revert to first entry when a new record is created rather than staying at previous setting.

2. Post It Note & Activity Alarms grids now select the first entry by default.

3. CV Send now allows attached CV documents to be named using the contact Id, rather than the candidate name.

   • Relies on the following systems settings:
     
     
     • CV SEND: Use Contact Id for attachment
       When set to true the attached file will be named based upon the candidates Id. Defaults to false.

Build: 7.02.004

20 November 2006

1. Charts licensed correctly.

Build: 7.02.003

17 November 2006

1. CV Send action no longer errors when output format is none.

2. Placement action follow ups are now scheduled for 8am.

3. Call Contact action now retrieves the correct phone number based upon the contact type.

4. ToDo action no longer relies on task type ordering.

5. Editing look ups now retains the previous selection when an entry is moved up or down.

6. Alarm UI moved to right along with new post it notes.

7. Fixed bug in Address Merge that included all lines of a Street address on one line spirited by commas.

8. Added PAYE Cost functionality to Requirement Rates and Placement rates.

   • Relies on the following systems settings:
     
     
     • PAYE Cost Percentage
       When set to 0 the field PAYECostRate on Requirement Rate from and Placement Rate form will be hidden.
       
       

9. 24X SMS provider support added to version 7

   • Relies on the following systems settings:
     
     
     • SMS: Provider
       Should be set to '24X'.
       
       
     • SMS: Username
       Needs to be set to the username provided by 24X.
       
       
     • SMS: Password
       Needs to be set to the password provided by 24X.
       
       

Build: 7.02.002

09 November 2006

1. Post it note UI overhauled. Pop up's removed. New notes now displayed in right hand pane that springs out within the application. This no longer grabs focus allowing the user to continue working whilst still being aware of the post it notes.

2. Alarm check now runs on a separate thread to prevent the main product becoming un-responsive when periodically checking for alarms/post it notes.

3. Outlook VBA interface form (initial form displayed when the user hits the TriSys button within Outlook) now displays and matches duplicates based upon ALL Email address fields.

4. Combos flagged as mandatory will no longer allow the record to be saved unless an entry other than the default is selected. User is prompted saying they must select a non default value for the relevant field.

Build: 7.02.001

30 October 2006

1. Active Searching functionality added. To apply carry out the following steps:

   • Export the new version of the dashboard from the Dev DB (Version 4).
   • Add ActiveSearchingEnabled and ActiveSearchingLastRun fields to the Requirement form (The latter must be read only). These will be added to the DB by the migration, you just need to put them onto the form.
   • Set up a job in SQL Agent to run the active searching stored procedure (EXEC p_RunActiveSearch) as often as required.
     
     
   • Active Searching checks for the following systems settings - when they are not present it will use the defaults shown, therefore they only need to be added if the default behaviour needs to be modified.
     
     
     • ACTIVE SEARCHING: Send Task To Candidate Owner
       Default = 1
       Specifies whether or not to notify Candidate owners when one of their Candidates is added to a Requirement.
       
       
     • ACTIVE SEARCHING: Task Type Id
       Default = 91
       The task type used when notifying the owner of the Requirement/Candidate. 91 = Client Vacancy Update.
       
       
     • ACTIVE SEARCHING: Max candidates to add per run
       Default = 100, -1 = unlimited
       The maximum number of candidates to add to a Requirement each time Active Searching runs.
       
       
     • ACTIVE SEARCHING: Task Text Single Candidate
       Default = 'Candidate ##Candidate_Name## has been associated with Requirement ##Requriement_Reference## - ##Requirement_JobTitle##(##Company_Name## - ##ClientContact_Name##) by active searching. You are receiving this note because you are the owner of the Requirement or candidate.'
       The task text used when a single Candidate is added to a Requirement.
       
       
     • ACTIVE SEARCHING: Task Text Multiple Candidates
       Default = '##Candidate_Count## candidate(s) have been associated with Requirement ##Requriement_Reference## - ##Requirement_JobTitle## (##Company_Name## - ##ClientContact_Name##) by active searching. You are receiving this note because you are the owner of the Requirement or one or more of the candidates.'
       The task text used when multiple Candidates are added to a Requirement.
       
       

2. Work/Education history summaries functionality added. To apply carry out the following steps:

   • Add the following buttons to the contact form and position them as required: WorkHistoryMoveUp, WorkHistoryMoveDown, EducationHistoryMoveUp and EducationHistoryMoveDown.
   • Alter the work and education history queries against the contact form to order the results by the new column named 'Ordering'.
   • Rebuild the contact_all_fields view - and any that rely on it (probably safest to rebuild all).
   • Add the Work/Education History Summary fields to the required contact grid using the grids field selection mechanism.

3. New command line switch added "/openform Form Name" where Form Name is the name of the form that should be opened.
   
   This will cause the application to load the specified form on start up in the same way it loads the dashboard.

4. Call contact action updated so that when it is run from within a Requirement it will show the personal contact details when phoning the selected candidate, and the work details when phoning the client.

5. Post it notes no longer default to "Send to all logged in users" to prevent accidental post it note spam.

6. Post it note pop up no longer has a button selected which sometimes resulted in accidental replies or clears.

7. Requirement shortlist now includes a source field that indicates where the candidate came from (Search results, Active Searching, Web etc).

8. The edit stage form from the Requirement Shortlist allows the user to alter the new field mentioned above, setting the source as desired.

9. Work history records can now be linked to companies within the system, rather than just allowing free text for the employer.

10. Moving a contact to a new company automatically generates a new work history record for the contact, showing the company they have just left.

11. Entity deletion now carries out a check to see if the record is in use anywhere within the system, and if so it will inform the user where, preventing deletion.

12. Deleting a company now carries out the correct deletion code against associated contacts, preventing foreign key constraint violations.

13. Grid component now displays errors using standard handler, preventing it messages being hidden behind the splash screen.

14. Skills Tree selection form grid now takes notice of the default max rows in the grid, rather than only showing 50 rows.

15. Field validation no longer erroneously reports a value as being above the maximum when the field is blank.

16. Field validation no longer errors and prevents saving of a record when the Address, Currency Amount or Currency Amount Period field is removed from the form.

17. Entity searches now persist the SQL generated by the search (no impact for user but can be used throughout the system to re-run the search without re-loading all criteria).

18. DLL and EXE version numbers now synchronised for easier version checking.

Version 8.0 Releases

Version 7.0 Releases