Issues Resolved - Orbis Software Ltd
Issues Resolved - Orbis Software Ltd
Issues Resolved - Orbis Software Ltd
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
TaskCentre Web Service Connector Tool 1.0 Service<br />
Release 4<br />
Document Version 1.0<br />
P151-1_0-RN<br />
Document Number: FM-OS-140 Issue: 02 <strong>Orbis</strong> <strong>Software</strong> Limited © 2013
Table of Contents<br />
REVISION HISTORY ............................................................................ 1<br />
COPYRIGHT ........................................................................................ 1<br />
TRADEMARKS ...................................................................................... 1<br />
INTRODUCTION .................................................................................. 2<br />
Purpose of the document .................................................................... 2<br />
Build Information ............................................................................... 2<br />
NEW FEATURES ................................................................................... 3<br />
1.0 Service Release 4 ......................................................................... 3<br />
1.0 Service Release 3 ......................................................................... 3<br />
1.0 Service Release 2 ......................................................................... 3<br />
1.0 Service Release 1 ......................................................................... 3<br />
ISSUES RESOLVED .............................................................................. 4<br />
1.0 Service Release 4 ......................................................................... 4<br />
1.0 Service Release 3 ......................................................................... 9<br />
1.0 Service Release 2 ........................................................................ 10<br />
1.0 Service Release 1 ........................................................................ 12<br />
KNOWN ISSUES ................................................................................ 20<br />
1.0 Service Release 4 ........................................................................ 20<br />
UPGRADE INSTRUCTIONS ................................................................. 21<br />
Pre-requisite TaskCentre Versions ....................................................... 21<br />
Backward Compatibility Considerations ................................................ 21<br />
Upgrade Steps .................................................................................. 21<br />
Reporting Installation Problems .......................................................... 22
Revision History<br />
Revision History<br />
Date Name Version Comments<br />
12 th November<br />
2012<br />
Chris Ringrose 0.1 Initial draft<br />
2 nd May 2013 Sue Dear 0.2 Revisions pre-release<br />
2 nd May 2013 Sue Dear 1.0 Issued<br />
1
Copyright & Trademarks<br />
Copyright<br />
The copyright in this document is owned by <strong>Orbis</strong> <strong>Software</strong> 2013. All rights reserved.<br />
<strong>Orbis</strong> <strong>Software</strong> Limited<br />
2 Nuffield Road<br />
Nuffield Industrial Estate<br />
Poole<br />
Dorset<br />
BH17 0RB<br />
This publication may not, in whole or part, be reproduced, transmitted, transcribed, stored<br />
in a retrieval system or translated into any language in any form or by any means without<br />
the prior written consent of <strong>Orbis</strong> <strong>Software</strong> Limited.<br />
Trademarks<br />
<strong>Orbis</strong> <strong>Software</strong> <strong>Ltd</strong> owns the registered Trademark ‘TaskCentre’.<br />
All other Trademarks used within this documentation are acknowledged as the property of<br />
their respective owners.<br />
The information provided in this publication may contain errors, omissions, or<br />
typographical errors or may be out of date. <strong>Orbis</strong> <strong>Software</strong> may change, delete, or update<br />
any published information at any time and without prior notice. The information published<br />
in this document is provided for informational purposes only and is not binding on <strong>Orbis</strong><br />
<strong>Software</strong> in any way except to the extent that it is specifically indicated to be so.<br />
1
Introduction<br />
Introduction<br />
Purpose of the document<br />
To describe the new functionality and issues resolved in this release.<br />
Build Information<br />
The TaskCentre Web Service Connector Tool 1.0 Service Release 4 (Build 805) is a<br />
complete build of this tool for application to TaskCentre installations. This tool will now<br />
have the version number 1.0.805.0.<br />
2
New Features<br />
New Features<br />
1.0 Service Release 4<br />
The following new features have been added with this release:<br />
- The ability to specify custom XML (such as authentication credentials and<br />
internationalisation information) to be inserted into the headers section of the SOAP<br />
input XML schema.<br />
- The ability to specify an x509 client certificate for authentication purposes for SOAP<br />
and REST web services.<br />
- Support for plain text error responses (wrapping and outputting them in XML tags).<br />
1.0 Service Release 3<br />
The ability to specify custom HTTP headers in a SOAP web service configuration has been<br />
added to this release.<br />
1.0 Service Release 2<br />
No new features have been added at this release. The incidents resolved in this release<br />
make the following application services accessible to the tool:-<br />
MS Dynamics CRM 2011<br />
Microsoft Exchange Events service<br />
LinkedIn<br />
1.0 Service Release 1<br />
The following new features have been implemented in this release:-<br />
Issue Number 41301<br />
Description<br />
Implement backwards compatibility mechanism so that tasks built on<br />
previous version of the tool continue to use the previous logic of the<br />
tool. To use the new logic a global connection must be established and<br />
used in task steps.<br />
Issue Number 41001<br />
Description<br />
Optimise WSDL parser to reduce the size of the schemas generated<br />
and hence improve performance.<br />
3
<strong>Issues</strong> <strong>Resolved</strong><br />
<strong>Issues</strong> <strong>Resolved</strong><br />
1.0 Service Release 4<br />
The following issues have been addressed in this release:<br />
Issue Number 41249<br />
Description<br />
Various performance improvements when using SalesForce.<br />
Issue Number 42422<br />
Description<br />
Microsoft Dynamics CRM 2011 REST service speed improvements<br />
creating and editing service.<br />
Issue Number 43069<br />
Description<br />
EBay REST service requires namespace declaration to form a part of<br />
the body at runtime.<br />
Issue Number 43574<br />
Description<br />
HTTP web service support for input and output schemas which use<br />
multiple namespaces.<br />
Issue Number 43616<br />
Description<br />
TomTom web service returns unsupported header.<br />
Issue Number 43623<br />
Description<br />
ODATA string parameters are not correctly escaped.<br />
Issue Number 43642<br />
Description<br />
Exchange 2010 – unable to create tasks with a priority set.<br />
Issue Number 43659, 43664<br />
Description<br />
Exchange 2010 – GetItem operation is missing data.<br />
Issue Number 43723<br />
Description<br />
Exchange 2010 – unable to extract watermark from GetEvents<br />
operation.<br />
4
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 43725<br />
Description<br />
Microsoft Dynamics GP – reads WSDL twice if IP used instead of<br />
machine name.<br />
Issue Number 43744<br />
Description<br />
No mapping available when designing multiple operations using the<br />
same single operation more than once.<br />
Issue Number 43773<br />
Description<br />
Microsoft Dynamics GP – error when initialising task run.<br />
Issue Number 43779<br />
Description<br />
Microsoft Exchange 2010 – GetFolder operation returned XML does not<br />
match schema.<br />
Issue Number 43796<br />
Description<br />
Support for SOAP response from Transwise web service.<br />
Issue Number 43799<br />
Description<br />
Microsoft Exchange 2010 – input schema element options not working<br />
as expected.<br />
Issue Number 43807<br />
Description<br />
XML not being correctly returned from the PowaAPI web service.<br />
Issue Number 43812, 43813<br />
Description<br />
CDATA not being correctly escaped when used in a fixed/dynamic<br />
function.<br />
Issue Number 43829<br />
Description<br />
SOAP service custom headers are not mappable when used inside<br />
multiple operations.<br />
Issue Number 43858<br />
Description<br />
Google Analytics – scope parameter is missing.<br />
5
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 43951<br />
Description<br />
OAUTH can fail at runtime under some circumstances.<br />
Issue Number 43953<br />
Description<br />
EBay shopping service – operations fail at runtime.<br />
Issue Number 43982<br />
Description<br />
EBay shopping service – passed schema set loses information.<br />
Issue Number 43989<br />
Description<br />
EBay shopping service – an exception is being thrown whilst<br />
constructing the output XML.<br />
Issue Number 44001<br />
Description<br />
TomTom web service operations have no parameters.<br />
Issue Number 44009<br />
Description<br />
Companies House – unable to infer schema when designing operations.<br />
Issue Number 44016<br />
Description<br />
Microsoft Dynamics GP - out of memory exception raised when<br />
exporting configuration<br />
Issue Number 44027<br />
Description<br />
SalesLogix 8 - invalid elements in SDATA schema.<br />
Issue Number 44029<br />
Description<br />
SalesLogix 8 – missing request or response elements.<br />
Issue Number 44036<br />
Description<br />
Out of memory exception when importing large TCWX files.<br />
Issue Number 44048<br />
Description<br />
Help files enhanced for new MTOM message format.<br />
6
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 44110<br />
Description<br />
Ebay Trading API – parameter missing from AddFixedPriceItem<br />
operation.<br />
Issue Number 44113<br />
Description<br />
Amazon AWS – runtime error whilst creating constants.<br />
Issue Number 44132<br />
Description<br />
Microsoft Dynamics CRM 4 – cannot create lead id field.<br />
Issue Number 44147<br />
Description<br />
EBay trading API – no data passed at runtime into GetFixedPriceItem<br />
Issue Number 44235<br />
Description<br />
DTL mapper does not correctly set namespaces.<br />
Issue Number 44350<br />
Description<br />
(44341) Land Registry missing security headers when sending xml<br />
Issue Number 44554<br />
Description<br />
Land Registry error trying to set a property if within an xs:choice<br />
Issue Number 44629<br />
Description<br />
Microsoft Exchange 2010, create calendar item fails with missing<br />
attribute.<br />
Issue Number 44637<br />
Description<br />
Equiniti Service x509 when loading WSDL from file, there is no way to<br />
enter certificate<br />
Issue Number 44915<br />
Description<br />
ParcelForce test operation does not show any parameters.<br />
Issue Number 45286<br />
Description<br />
MMO fails to open operation mapping when previous operation outputs<br />
7
<strong>Issues</strong> <strong>Resolved</strong><br />
XML across multiple schemas<br />
Issue Number 45312<br />
Description<br />
HTTP Ops with XML o/p schema that refs types in an HTTP imported<br />
schema cannot be used in MMO's<br />
Issue Number 45463<br />
Description<br />
XML elements with nil attributes cause data sent to be blank<br />
Issue Number 45868<br />
Description<br />
Root element missing - capturing text error returns.<br />
8
<strong>Issues</strong> <strong>Resolved</strong><br />
1.0 Service Release 3<br />
The following issues have been addressed in this release:<br />
Issue Number 41724<br />
Description<br />
MS Dynamics GP 2010 – WSDL parsing fails with out of memory error.<br />
Issue Number 43005<br />
Description<br />
EBay SOAP Find service. Missing operation name in header.<br />
Issue Number 43010<br />
Description<br />
EBay SOAP Shopping service. Unable to parse WSDL.<br />
Issue Number 43108<br />
Description<br />
Operations list ignores selected port/endpoint.<br />
Issue Number 43185<br />
Description<br />
Using culture variant string conversion when generating XML.<br />
Issue Number 43211<br />
Description<br />
SuperOffice SOAP web service. Missing header objects.<br />
Issue Number 43221<br />
Description<br />
Installer fails if short filename support is deactivated in operating<br />
system.<br />
Issue Number 43259<br />
Description<br />
MS Dynamics CRM 2011 REST service. Unlink operation URL not<br />
generated correctly.<br />
Issue Number 43293<br />
Description<br />
MS Exchange 2010. UpdateItem unable to loop map multiple<br />
SetItemField nodes.<br />
Issue Number 43387<br />
9
<strong>Issues</strong> <strong>Resolved</strong><br />
Description<br />
Improvements to the multi op export functionality.<br />
Issue Number 43388<br />
Description<br />
Windows temp directory can fill up with DLLs with frequent web service<br />
calls.<br />
Issue Number 43424<br />
Description<br />
TCWX security improvements.<br />
Issue Number 43531<br />
Description<br />
MS Exchange 2010. Contact node in output XML is incorrectly named.<br />
Issue Number 43543<br />
Description<br />
MS Exchange 2010. GetItem can fail if contact data contains specific<br />
characters.<br />
Issue Number 43568<br />
Description<br />
MS Exchange 2010. GetEvent output XML is not correct.<br />
Issue Number 43598<br />
Description<br />
ODATA missing quotes can cause a protocol error.<br />
1.0 Service Release 2<br />
The following issues have been resolved in this release:-<br />
Issue Number 42319<br />
Description<br />
Resolving schema during step updates with Microsoft Exchange is slow.<br />
Issue Number 42962<br />
Description<br />
Linked-In REST API OAUTH Authentication fails.<br />
Issue Number 42975<br />
Description<br />
MS Dynamics CRM 2011 REST API elements of type GUID sending<br />
dummy values.<br />
10
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 42991<br />
Description<br />
MS Exchange 2010 GetEvents operation fails.<br />
Issue Number 43098<br />
Description<br />
Twitter OAUTH Authentication fails.<br />
Issue Number 43114<br />
Description<br />
HTTP configuration Windows Auth interrogation credentials not set in<br />
service settings.<br />
Issue Number 41658<br />
Description<br />
MS Dynamics CRM 2011 SOAP service retrieve fails at runtime.<br />
Issue Number 42507<br />
Description<br />
MS Dynamics CRM 2011 selected endpoint does not exist.<br />
Issue Number 42980<br />
Description<br />
Client crash due to lack of access permissions to the root of C drive.<br />
11
<strong>Issues</strong> <strong>Resolved</strong><br />
1.0 Service Release 1<br />
The following issues have been resolved in this release:-<br />
Issue Number 40432<br />
Description<br />
SalesForce Multiple Method Operation can cause tool to fail.<br />
Issue Number 40434<br />
Description<br />
SalesForce – Multiple Method Operation destination schema resolving<br />
not presented correctly.<br />
Issue Number 40627<br />
Description<br />
Microsoft Exchange runtime cannot handle arrays of abstract types.<br />
Issue Number 40630<br />
Description<br />
SOAP wrappers can fail with MultipleRootElements<br />
Issue Number 40864<br />
Description<br />
Task with five or more web service connector tool steps fails to<br />
initialise.<br />
Issue Number 41047<br />
Description<br />
Changes to the input data in a Multiple Message Operation are not<br />
always reflected in the error data mapping.<br />
Issue Number 41077<br />
Description<br />
Output soap headers are not included in the output when using legacy<br />
.net wrappers.<br />
Issue Number 41088<br />
Description<br />
Microsoft Exchange FinderFolder cs:choice missing from type<br />
declarations.<br />
Issue Number 41169<br />
Description<br />
Microsoft Exchange FindFolder FindFolderResponseMessage appearing<br />
as an element and not a type in the output schema.<br />
12
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 41238<br />
Description<br />
Microsoft Exchange 2010 GetUserAvailability response not returned<br />
correctly.<br />
Issue Number 41271<br />
Description<br />
Exact Synergy update operation incorrectly converting base 64 binary.<br />
Issue Number 41274<br />
Description<br />
Microsoft Exchange FindItem not working.<br />
Issue Number 41279<br />
Description<br />
VBscript mapping function output parameter is always empty.<br />
Issue Number 41282<br />
Description<br />
Incorrect handling of contact arrays when communicating with<br />
Exchange web services.<br />
Issue Number 41283<br />
Description<br />
Unable to cope with style sheets in RSS feeds. E.g. BBC Weather<br />
Issue Number 41311<br />
Description<br />
No data output from response XML returned from Exchange web<br />
services.<br />
Issue Number 41312<br />
Description<br />
Generated XML does not contain namespace.<br />
Issue Number 41313<br />
Description<br />
Calling GetItem on the Microsoft Exchange web service fails with Null<br />
object reference exception.<br />
13
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 41357<br />
Description<br />
HTTP Operation will not output headers if no body has been defined.<br />
Issue Number 41370<br />
Description<br />
The OAUTH wizard fails on the last step if using HMAC HTTP POST<br />
authentication.<br />
Issue Number 41423<br />
Description<br />
Soap Body excludes date range fields when calling FindItem on<br />
Microsoft Exchange web services.<br />
Issue Number 41453<br />
Description<br />
Invalid schema on multiple message operation output schema<br />
configuration.<br />
Issue Number 41456<br />
Description<br />
Implement a more consistent approach to xs:choice to better match<br />
.Net wrappers.<br />
Issue Number 41506<br />
Description<br />
Sage SDATA sme:relationship attribute is being ignored when<br />
expanding complex types.<br />
Issue Number 41577<br />
Description<br />
SOAP WSDL interpreter does not correctly handle xs:include only<br />
xs:import.<br />
Issue Number 41587<br />
Description<br />
Iwntypen.dll erroneously installed.<br />
Issue Number 41601<br />
Description<br />
Improve handling if importing a configuration from a much newer build<br />
of the web service connector tool.<br />
Issue Number 41658<br />
Description<br />
Microsoft Dynamics CRM 2011 SOAP Service – retrieve call fails at<br />
14
<strong>Issues</strong> <strong>Resolved</strong><br />
runtime with root element is missing.<br />
Issue Number 41686<br />
Description<br />
Unable to interpret WSDL published by the Dusseldorp SOAP Web<br />
Service.<br />
Issue Number 41732<br />
Description<br />
ActiveMode step setting does not function correctly for the web service<br />
connector tool.<br />
Issue Number 41756<br />
Description<br />
Unable to export configurations for Microsoft Dynamics CRM and<br />
Microsoft Exchange<br />
Issue Number 41760<br />
Description<br />
Step config data transformation inconsistencies when expanding types<br />
more than once.<br />
Issue Number 41814<br />
Description<br />
HTTP operation test button fails to return output.<br />
Issue Number 41835<br />
Description<br />
Sage SDATA failing to retrieve namespace from the service schema.<br />
Issue Number 41836<br />
Description<br />
Looped steps in ActiveMode fail to iterate correctly.<br />
Issue Number 41837<br />
Description<br />
Sage SDATA POST operations ignore attributes.<br />
Issue Number 41892<br />
Description<br />
Sage Accpac 6.0a schemas will not validate.<br />
Issue Number 41896<br />
Description<br />
EU VAT checker web service fails with System.NullReferenceException.<br />
15
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 41907<br />
Description<br />
Microsoft Exchange web services output XML is set to default values.<br />
Issue Number 41921<br />
Description<br />
Sage Accpac 6.0a update existing customer fails schema validation.<br />
Issue Number 41929<br />
Description<br />
HTTP Operations advanced option for custom message type is ignored.<br />
Issue Number 41942<br />
Description<br />
Microsoft Exchange CreateItem fails to create Items or Contacts.<br />
Issue Number 41943<br />
Description<br />
Transparently preserve nil attribute in data transformation.<br />
Issue Number 41952<br />
Description<br />
Namespace prefixes in Sage SDATA payloads from Sage Accpac not<br />
handled correctly.<br />
Issue Number 41956<br />
Description<br />
DistinguishedFolderId not mappable when using CreateItem in<br />
Exchange web services.<br />
Issue Number 41963<br />
Description<br />
Runtime should include XML-Schema processing attributes.<br />
Issue Number 41964<br />
Description<br />
Sage SDATA Child relationship entry schemas should automatically<br />
recurse.<br />
Issue Number 41975<br />
Description<br />
Incorrect nil attributes being generated.<br />
Issue Number 41997<br />
Description<br />
Missing method exception when calling UpdateItem on Microsoft<br />
Exchange web services.<br />
16
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 42000<br />
Description<br />
Microsoft Exchange – FindItem is responding with erroneous data.<br />
Issue Number 42042<br />
Description<br />
KeyNotFoundException being thrown when using link operations in<br />
ODATA web services.<br />
Issue Number 42044<br />
Description<br />
Transformed XML is empty if OrbWsc namespace is defined in the<br />
input.<br />
Issue Number 42105<br />
Description<br />
Output data not correctly mapped into output XML.<br />
Issue Number 42106<br />
Description<br />
NullReferenceException when calling Microsoft Exchange FindItem<br />
Issue Number 42110<br />
Description<br />
Microsoft Exchange CreateItem NullReferenceException when building<br />
output data.<br />
Issue Number 42111<br />
Description<br />
Microsoft Exchange CreateItem NullReferenceException when building<br />
input data.<br />
Issue Number 42152<br />
Description<br />
Xs:choice has items incorrectly names.<br />
Issue Number 42165<br />
Description<br />
Microsoft Exchange FindItem failing when a SearchExpression is<br />
specified.<br />
Issue Number 42176<br />
Description<br />
Data transformation will not map onto a fixed/dynamic output field.<br />
17
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 42177<br />
Description<br />
Microsoft Exchange FindFolder operation fails with instance not set to<br />
an instance of object if AdditionalProperties are specified.<br />
Issue Number 42178<br />
Description<br />
Microsoft Exchange FindFolder output schema is not validating when<br />
passed into the XML to recordset tool.<br />
Issue Number 42206/42312<br />
Description<br />
Installer now requires a minimum hotfix level of SR4h.<br />
Issue Number 42213<br />
Description<br />
Microsoft Exchange CreateItem is failing at runtime.<br />
Issue Number 42264<br />
Description<br />
Microsoft Exchange CreateItem with RequiredAttendees or Organiser<br />
for creating a calendar item fails at runtime.<br />
Issue Number 42319<br />
Description<br />
Resolving schema during step updates when using Microsoft Exchange<br />
web services is too slow.<br />
Issue Number 42312<br />
Description<br />
Inconsistencies in mapping output data from one function to another in<br />
the data transformation.<br />
Issue Number 42371<br />
Description<br />
Unable to map nodes with attributes.<br />
Issue Number 42388<br />
Description<br />
HTTP SalesLogix 7.5.4 – Copy operation fails at runtime with root<br />
element is missing.<br />
Issue Number 42405<br />
Description<br />
Configuration dialog ceased to respond if no endpoint is specified.<br />
18
<strong>Issues</strong> <strong>Resolved</strong><br />
Issue Number 42507<br />
Description<br />
Microsoft Dynamics CRM 2011 - selected endpoint does not exist<br />
Issue Number 42545<br />
Description<br />
Microsoft Dynamics AX Customer Create Operation Produces<br />
System.NullReferenceException At Runtime<br />
Issue Number 42550<br />
Description<br />
Microsoft Dynamics AX Customer Find Operation Produces<br />
System.MissingMethodException At Runtime<br />
Issue Number 42556<br />
Description<br />
Multi Operation Error Data empty<br />
Issue Number 42570<br />
Description<br />
SalesForce create runtime error System.NullReferenceException:<br />
Object not set to an instance<br />
Issue Number 42695<br />
Description<br />
Microsoft Exchange 2010 getitem fails with root element missing<br />
Issue Number 42723<br />
Description<br />
Microsoft Exchange 2010 getitem or finditem not outputting correct<br />
elements<br />
Issue Number 42725<br />
Description<br />
Microsoft Exchange 2010 getitem extended property not returning the<br />
value<br />
Issue Number 42758<br />
Description<br />
Microsoft Exchange 2010 failure to update extended property<br />
Issue Number 42760<br />
Description<br />
Error parsing schema when using NetSuite API<br />
19
<strong>Issues</strong> <strong>Resolved</strong><br />
Known <strong>Issues</strong><br />
1.0 Service Release 4<br />
Issue Number 45947<br />
Description<br />
It is not possible to import DTLX mapping files into the mapping pane<br />
from previous releases of the web service connector.<br />
20
Upgrade Instructions<br />
Upgrade Instructions<br />
Pre-requisite TaskCentre Versions<br />
This section provides details of the builds that may be upgraded with the new release. This<br />
tool pack can be applied to Version 4.5 SR4 Hotfix H (Build 1270) installation. Any older<br />
installations of TaskCentre will need to be upgraded to this build before applying this tool<br />
pack.<br />
Backward Compatibility Considerations<br />
The Web Service Connector Toolpack has been designed to ensure that web service<br />
configurations and tasks created in previous releases of this tool continue to run without<br />
issue after upgrading. This mechanism will work as long as these configurations are not<br />
changed in any way via the user interface. If this is attempted, the user will be warned<br />
that some inconsistencies may be encountered.<br />
The backwards compatibility mechanism will execute legacy configurations in the exact<br />
context that they were when they were originally created. This means that any problems<br />
which have been fixed since that release may still exist.<br />
To benefit from all of the fixes and new functionality included in this release, it is<br />
recommended that the web service be recreated and any tasks modified to use this new<br />
connection.<br />
Upgrade Steps<br />
The following TaskCentre Components require upgrading with this release:-<br />
Component<br />
TaskCentre Server(s)<br />
TaskCentre Clients<br />
Data Modeller<br />
SMTP Agent<br />
MS SQL Server Trigger Agent<br />
Oracle Trigger Agent<br />
Workflow Agent<br />
myTaskCentre<br />
Web Service<br />
Upgrade Required<br />
Yes<br />
Yes<br />
No<br />
No<br />
No<br />
No<br />
No<br />
No<br />
No<br />
N.B. .Net 3.5 SP1 must be installed. If not the tool will not install and no error message<br />
is issued.<br />
Run the setup.exe and follow the on screen instructions.<br />
Once installed it is necessary to set up the global configuration for the tool to enable<br />
connection to specific web services.<br />
Any global connections created prior to installing this service release will continue to use<br />
the previous version of the software. To make use of the new features available in this<br />
version a new global connection must be created and task steps reconfigured to use the<br />
new connection.<br />
21
Upgrade Instructions<br />
Reporting Installation Problems<br />
If you have any problems upgrading your current version of TaskCentre please contact<br />
<strong>Orbis</strong> Support.<br />
Tel: 01202 241115<br />
<br />
Email: support@orbis-software.com<br />
22