Glossary Item Box

Government Gateway 2.2.0 (MR-01) ISV Developer Help (Doc Version 06/03/08) | Send comments on this topic.

# What's New

# Changes incorporated for release 2.2.0 (MR-01) of the UK Government Gateway (6th March 2008)

Release | Reference | Description
--- | --- | ---
2.2.0 (MR-01) (Help file Doc Version 06-03-08) | View Service transaction status (enabled/disabled) | Each transaction class (Form) within a service can be now be disabled. When a Service it set up on Gateway the status of each class (enabled/disabled) can be set. Subsequently the state of individual transactions can be changed by the Live services Team. To view the status (enabled/disabled) of te transaction in a server the GsoGetServiceInfo has be updated to include this information.

# Changes incorporated for release 2.2.0 of the UK Government Gateway (6th March 2008)

Release | Reference | Description
--- | --- | ---
2.1.0 (Help file Doc Version 06-03-08) | Delegated Rights Management (DRM) | Until now, to control which users (employees) within an organisation/agent have permission to act on the organisation/agent's direct enrolments (or, in the case of a agent client, allocated enrolments too) it was necessary for the organisation/agent to setup and manage a set of Gateway Users/Assistants (through the Gateway UI or Portal specific R&E UI) that map to these employees. The DRM facility improves efficiency by removing the need for an organisation/agent to create this parallel set of Gateway Users/Assistants. Instead the organisation/agent can extend its existing access management system to control which enrolments its employees can act on. To use the RDM facility an Organisation/Agent Gateway User must first create a special DRM User account through the Gateway UI (www.gateway.gov.uk). Then, to assign a organisation/agent employee access to act on enrolment(s): The GsoDelegateRights method is called (using the DRM User credential) by the organisation/agent system to dynamically assign permissions to use enrolments to the employee. Also see Calling the DelegatedRights SOAP Interface). CAP initiates a browser session on the Portal that the employee needs to use on the enrolment(s) assigned to them. See SSO for DRM session users.

#

# Changes incorporated for release 2.0.0 (MR-01) of the UK Government Gateway (4th September 2007)

Release | Reference | Description
--- | --- | ---
2.0.0 - MR01 (Help file Doc Version 04-09-07) | TxE Average Transaction Time (FS001, FS002 and FS004) | A new method GsoGetAverageTransactionTimes has been added to the Portal and Public Interfaces. This method allows clients (i.e. Portal or ISV applications) to determine how long (on average) responses to document submissions of any specified service transaction class take. These average transaction times, calculated for each transaction classes, are also used to return optimised polling interval values back to clients in SUBMISSION_ACKNOWLEDGEMENT messages. This allows clients to intelligently issue SUBMISSION_POLL messages that reduce network bandwidth and loading on the Gateway.
2.0.0 - MR01 (Help file Doc Version 04-09-07) | New Security Token Service (STS) endpoint | The URLs for the 2007/02 endpoints – that support the standard WS-Trust wst:Lifetime (rather than wst:LifeTime) element – on the Security Token Service page were incorrect. They have been corrected.

# Changes incorporated for release 2.0.0 of the UK Government Gateway (19th July 2007)

Release | Reference | Description
--- | --- | ---
2.0.0 (Help file Doc Version 19-07-07) | Government Gateway Transaction Engine (TxE) | The Transaction Engine (TxE) has been rewritten to: Improve performance Provide better integration with the core R&E component Make it possible to extend/enhance the facilities offered by the TxE in the future. The revised ISV developer documentation for the TxE Document Submission Protocol is included in the .chm. The content has been rationalised (reduced), reorganised and corrected where necessary. The online (.chm) format for the TxE documentation should make it more easily accessible to developers. If required a .pdf version of the Document Submission Protocol is available – as extracts from the .chm. Note: The rewrite of TxE has not resulted in any changes to the WS-SOAP Interfaces.
2.0.0 (Help file Doc Version 19-07-07) | Gateway flags | A brief description of each of the Gateway Flags and Controls has been added to the Concepts section.

# SOAP API changes and functionality incorporated in release 1.7.0 of the UK Government Gateway (1st March 2007)

Release | Reference | Description
--- | --- | ---
1.7.0 (Help file Doc Version 05-03-07) | New endpoint set | A new set of Web Service endpoints have been added for accessing the Gateway (i.e. for STS requests, Port Interface, Public Interface, Admin Interface and KnownFactUpload Interface methods). This new set of endpoints support the WS-Trust <wst:Lifetime> element in STS request (rather than the non-conformant <wst:LifeTime> element). The "legacy" set of Web Service can (for now) still be used by existing Portals and ISV applications – however migration should be planned. The following sections have been updated: Calling Methods on the Portal and Public SOAP Interfaces Gateway Soap Public Class
1.7.0 (Help file Doc Version 05-03-07) | Legacy Shim | To continue to support legacy Portals/applications as Gateway evolves and is enhanced, it has been necessary to internally re-architect the SOAP Legacy interface code. The resulting "Legacy Shim" interface is a subset of the SOAP Legacy interface. This subset includes the methods which are actually used by existing implementations and therefore it should not be necessary to rewrite legacy applications. For further information please contact the EDT. Note: The SOAP Legacy interface (and the Shim subset) are not covered in this help file since new Portals/applications do not use these legacy interface.

© Crown Copyright 2008. All rights reserved