Release signed off and check list completed by engineering

Start DateExpected End DateDocumentation ReviewFunctional TestingBuildRTS Status
24/06/2020


02/07/2020PritamPritamv3.1.0

IN-PROGRESS

Signed Off06/07/2020PritamPritamv3.1.0


Status Legend 

NOT IN SCOPE 

QUEUED 

IN-PROGRESS   

COMPLETED

FAILED



How it works review

Copy table from _New features for documentation

FeatureHow It WorksStatus
ServiceNow_Creating a ServiceNow Test Instance

COMPLETED

How It WorksInternal Documentation




NOT STARTED



NOT STARTED



NOT STARTED



NOT STARTED



NOT STARTED



NOT STARTED



NOT STARTED



NOT STARTED



New features by release review

Copy latest release feature links from Features by release.

QUEUED

Page Title

Issue

Response

Status

PS: To access the Schedule Job, the user will also require the x_1e_connected.Tachyon_admin role.

Done.

PS: A one liner for the Upgrading section will look nice

  to kindly address.

DJW  Changes implemented by .


PS: The Supported version for ServiceNow says Orlando however the next line also says Domain Separation feature is supported on Orlando. So, that makes no sense. It would make sense if we list 'all' other versions which are supported with ITSM 3.1 whether or not it support Domain separation and then we add the 3rd point below:

  1. A working ServiceNow instance must be set up. This can be a demo instance or a production/vendor instance. It can also be either a single domain or a multi domain instance.
  2. The following versions of ServiceNow are supported:
    1. Orlando
  3. The Domain separation feature is supported on Orlando only.
  4. If you are using this App in multi tenant mode, please enable the "Domain Support" plugin on your ServiceNow instance

  to kindly address.

DJW  Changes implemented by .

Can we also add the below or something similar in this page or under Configuration for a Multi-Tenant instance page, if possible:

When Domain Separation feature is enabled in 1E Core as described here, the Single Tenant configuration settings which was previously configured are on longer used.

DOne by KJ on  


None



COMPLETED

None

COMPLETED

PS: I think the ITSM documentation is not updated with the following pre-req/configurations:

Domain separation:

  1. We need to enable Domain separation in existing 1E Core instance under App Configuration in Servicenow. Once enabled then these 1E Core settings are ignored and the 'Multi-Tenant configurations' settings are considered. Also the Application config under ITSM>Admin is no longer valid once Domain separation is enabled.
  2. Also when we are installing the Mid Server, we should login with the correct user and download the MidServer installer and try to install it. If the user doesn't belong to the correct domain then he will end up installing the Mid-Server for the incorrect domain where user has rights.
  3. Remember to switch between domains when setting the multi tenants. So, tenants would be added under it's own domain
  1. Refer 1E Core post-installation tasks
  2. Added the line on MID Server here.
  3.   to kindly address.

DJW  Changes implemented by me.


  • Upgrade ITSM to 3.1.0. Please refer to Upgrading for more details.

PS: This page should contain the updated screenshot showing the latest version of ITSM connect under My Company application



None

COMPLETED

None


FAILED

COMPLETED

None


COMPLETED

None

COMPLETED

We still have this issue in this release however we also got it under the known issue page. Hopefully it will be fixed in next release


COMPLETED

None

COMPLETED

  • 1E Support page, access all the information you need to contact 1E support directly in the 1E ITSM Connect app. Please refer to Troubleshooting for more details.
None

COMPLETED

1E ITSM Connect app messagesNone


Known issuesNone




Product functional testing

Feature

Functional Testing notes

Status

Retrieve Instructionsno issues discovered


Domain Separationno issues discovered
Running, approving instructions and viewing responsesno issues discovered


App Configuration

no issues discovered

   

Scheduled Jobs


Mid Server

no issues discovered


Logs

Supportno issues discovered


Instruction Historyno issues discovered


Instruction Definationno issues discovered




Product functional issues

Issue

TFS

Description

Status

1. Service Catalog Connect App instruction set are visible under ITSM application post instruction retrieval.

196841

Expected result. I don't see extra instruction sets on the incident page when user has ITSM-v2 and ServiceCatalog Connect on Same instance.


2. ITSM Plugin dependency on Incident Management.

198136Since, there is no way to validate the second fix, I just checked that the normal workflow is working smoothly without any issues. And I could not find any issues


3



NOT STARTED

4



NOT STARTED

5



 NOT STARTED



Sign off list

Check List

Area

Description

Status

1

SalesForce

Add new features to SalesForce Ticket

IN-PROGRESS

2

SalesForce

Update Portal with download file

QUEUED

3

SalesForce

Update portal with announcement page

QUEUED

4

HubSpot

External customer message

QUEUED

5

Internal

RTM Announcement

QUEUED