Customer Fixed Issues and Known Issues Denali SP3 HF07

On this page: Hotfix Merges | Customer Fixed Issues | Known Issues 

Hotfix Merges

The following Hotfix versions are merged with this release. Please refer to the respective Release Notes for details.

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Denali SP3 HF07 version.

Issue #Issue DescriptionScenarioResolution

90799

Disabled Implementation options in the Field Configurations page was not taking effect while creating or updating Change Records

1.     Click Change > Configuration > Field Configuration

2.     Select a Tenant to view the list of configurations

3.     Under implementation section, set all the fields to disabled.

Despite that, when any new Change Record was being created or existing record was updated, Is the Change Implemented or Rolled Back and Assigned To fields are not getting disabled under implementation tab of the record.

Now, when any new Change Record is being created or existing record is updated, the Is the Change Implemented or Rolled Back and Assigned To fields are getting disabled under Implementation tab of the record.

90559

The movement details of the inactive fixed asset were not displayed on the Asset Movement Details page. 


You can access the Asset Movement Details page by navigating Asset-> Asset Inventory > Fixed-> Open Inactive Assets > Asset History->Movement History-> Click on Movement ID hyperlink.

Now, the movement details of the inactive fixed asset are displayed on the Asset Movement Details page. 

89379

The PATCH_Scripts folder was automatically creating scripts and the scripts were not getting deleted post the script execution. Hence, a lot of space was consumed.


This issue was observed in Summit Asset Management agent for Windows devices.

Now, the fix is done in Agent version 2.5.5.23

90800

The following issues related to SR reminder feature were observed:

  • Post creation of an Incident, the Priority value was not captured in the e-mail that was triggered to the workgroup.
  • On the Incident list page, the value of Priority was blank for the Incidents that were created using the SR reminder feature. Whereas the Priority value of the same Incident was displayed the on the Incident details page.


Prerequisites:

1. SR Reminder job must be scheduled and running

2. Priority must be configured in the Incident list page configure columns


Now, the Priority value is captured in the e-mail that was triggered to the workgroup and also, on the Incident List pages.

89999

The following issues related to the Auto Creation Setting were observed:

  • The already existing configurations were not populated on the AUTO CREATION SETTINGS List page.
  • On the AUTO CREATION SETTINGS details page, the user was required to manually specify the Symptom and Description under the TARGET section.

This issue occurred post upgrade of application to Denali SP1 version.

Now, the issues are fixed.

  • The already existing configurations are populated on the AUTO CREATION SETTINGS List page post execution of the migration script in DenaliSP1HF11 DB.
  • On the AUTO CREATION SETTINGS details page, the Symptom and Description are auto-populated on the TARGET section.
90244

On the CONFERENCE CALL – TWILIO LIST or CONFERENCE – WEBEX LIST page, when the user clicks the configured Bridge Name or Site Name, the fields under the DETAILS section displayed blank.

The details filled in by the admin while configuring the conference call were not getting displayed.

The CONFERENCE CALL – TWILIO LIST or CONFERENCE – WEBEX LIST page can be accessed using Admin > Advanced > Notifications > Conference Call.

Precondition:

Configure a conference call for Twilio and WebEx.
Now, for all fields, the values are getting displayed.
90072On the CHANGE HISTORY pop-up, for the Status field, the Changed By was displayed blank. This issue occurred when the Service Request was closed automatically by the system.

Pre-requisites:

  1. Select Request Closing Mode as Auto and enter the Number of days in Auto Closing Days field at Tenant Level Configuration.
  2. Configure 'Auto Close SR' Job.
Now, if the system auto closes a service request, the Changed By value is captured as SYSTEM for the Status field instead of blank.
89559

The "Root Cause Analysis" page controls were displayed under the "Additional Information" tab on a Problem Record page with ‘New’ status. This issue existed only for the configured text box custom attribute on the Problem record page.

Precondition: Configure a text box custom attribute in the Additional Information tab.


Steps:

  1. Navigate to Problem >> Problem Record List
  2. Select a Problem Record from the list by clicking on a PR ID with status ‘New’.
  3. Type some text in the configured text box.
  4. Press SHIFT + ENTER keys or only ENTER key.

Now by hitting ENTER key or Shift + ENTER key on the configured textbox, the controls displayed under Additional information tab are correct.

92377Is PIR Required information along with Analyst details was not displayed in CHANGE HISTORY pop-up page. 

Pre-requisites: 

  1. Navigate to Change > User > New Change Record. The NEW CHANGE RECORD page is displayed. Specify the mandatory fields and click SUBMIT.
  2. Login as an Authorizer/Approver. Navigate to APPROVAL under ACTIONS. The APPROVAL pop-up page is displayed. Enable the checkbox Is PIR Required?
  3. Navigate to Actions > CHANGE HISTORY. CHANGE HISTORY pop-up page is displayed.

Now, Is PIR Required information along with Analyst details is displayed in CHANGE HISTORY pop-up page.

It will also display the Is PIR Required information, even if it is auto enabled at Tenant level. (Admin > Basic > Infrastructure > Tenant > ACTIONS > CONFIGURE DETAILS > Auto Select "Is PIR Required?)

90731

Rescheduled Reason field was not getting displayed while modifying Planned Start Time field. It was getting saved directly without reset.

Pre-requisites: 

  1. Navigate to Change > User > Change Record List. The Change Record List page is displayed.
  2. Click on CR. The Change Record ID details page is displayed.
  3. Under TIMELINES section change Planned Start Time.
Now, Rescheduled Reason field is displayed while modifying Planned Start Time field.
90288

Issue 1
Owner Workgroup field was disabled.

Issue 2
Rescheduled Reason field was not getting displayed while modifying Planned Start Time field. It was getting saved directly without reset.

Prerequisites for Issue 1
Configure the Task at first level in workflow page.

  1. Navigate to Change > User > New Change Record. The New Change Record page is displayed.
  2. Create a CR with same workflow. Once the CR is created, change Owner Workgroup.

Prerequisites for Issue 2
Create a workflow with approval levels with user Configured status.

  1. Navigate to Change > User > Change Record List. The Change Record List page is displayed.
  2. Click on CR. The Change Record ID details page is displayed.
  3. Under TIMELINES section change Planned Start Time.

Resolution for Issue 1
Now, Owner Workgroup field is not disabled.

Resolution for Issue 2

Now, Rescheduled Reason field is displayed while modifying Planned Start Time field.

90184

User encountering ‘Select Configuration Item’ error message, when selecting a Link Configuration item to service.

Pre-requisites:

  1. Login to the application
  2. Navigate to CMDB > click ADD SERVICE from the right-hand pane.
  3. Enter the required details and click Submit.

A confirmation message appears of creating a service.

Impact Scenario

  1. Login to the application.
  2. Navigate to Change > Change Record List.
  3. Search existing Services from the Filter.
  4. Open the CR widget, click the icon corresponding to the Configuration list.
  5. Click to select the Services for Classification field and click the Search.
  6. Select the check box corresponding to the Service Name hyperlink and click the Link.

An error message ‘Select Configuration Item’ occurs.

Now, the user could link a service as expected.

91739

The configured custom attribute for the CMDB module in Form builder is not appearing as expected.

Pre-requisites:

  1. Login to the application.
  2. Navigate to Admin > Form Builder.
  3. Configure a Group and select ‘2’ from the ‘ of Column’ field in the PROPERTIES section.
  4. Click Save.

Impacted Scenario

  1. Login to the application.
  2. Navigate to CMDB > New Configuration Item.
  3. Select the Tenant and click the Addition Information tab
Now, the custom fields are appearing as configured in the Form Builder.

89995

Whenever a user was activated in Active Directory (AD). After AD import the user status has not appeared as ‘Active’ into the Summit database.NANow, the user status in the Summit database is appearing in synch with AD.
88581

The Admin was experiencing a substantial time delay while searching for a user and to update his details or to add a new user in the application.

Precondition:

Log into the application as an Admin. Search for a user and update his details or add a new user.

Steps:

Navigate to Admin >>Basic >> Users >> Userlist

After removing the unwanted source code, the system performance is enhanced by more than 50% and the Admin no longer experience considerable time delay while updating user details or while adding a new user.

Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali SP3 HF07.

Issue NoIssue DescriptionScenarioWorkaround <if applicable>
88818

The value selected for the Priority is getting cleared after CAB Approval.

Prerequisite:

Configure a PIR Reviewer.

Bug Reproduction Steps:

Click Change > User > New Change Record.

Create a CR by selecting the Change Type as Emergency and e-CAB Approval Required as After Implementation.

Authorize the CR.

Implement the CR.

Approve the CR.

This issue occurs only when the CAB approver approves the CR.

NA
Issue

While trying to uninstall the TLS 1.2 agent from the control panel, a pop-up message “Network connect failed. Please contact Administrator “is displayed and TLS 1.2 agent was not getting uninstalled.

Work around: Using the Uninstall_SAM_SSI.exe, you can uninstall TLS 1.2 agent. (#87625)

Under the Asset Movement Details section of the Asset Transaction Details Report, the assets which are in In-Transit status and waiting for movement approval (such as Return From Repair movement approval, Send To Repair movement approval, and Assets waiting for Deactivation approval) are not getting displayed. (#86416)

Under the Checker Status column of the FIXED ASSET inventory page, When the Fixed Asset is allocated the Asset status is shown as Referred Back even though the Maker-Checker configuration is disable for the Allocate asset transaction. This issue occurred when the Maker-Checker configuration is enabled for the Deallocate and Deactivate Asset transactions and the Checker refers back the asset deactivation request.

In an ideal scenario, the Checker Status column of the FIXED ASSET inventory page must get cleared after allocating the In-Store asset that was referred back by the Checker for asset deactivation request. (#83900)

Mail Parser configured with O365 API cannot run on the summit Proxy Server, it can only run on the Summit Server. Email to ticket creation feature is not supported for the following configuration combination on the MAILBOX page.

 Server Type = O365 API

 Monitoring Source = Proxy Server 

Note: Email to ticket creation works when you select Server Type as O365 API and Monitoring Source as Summit Server.

The MAILBOX configuration page can be accessed using Admin > Advanced > Notifications > Mailbox. (#83831)

When the user re-login into the SummitAI application and performs the same action for the second time on the same page (Ex: MY APPOINTMENTS) and clicks SUBMIT, an error message “Error Occurred” is displayed. 

This issue is found when the user has logged into the SummitAI application using the Microsoft Internet Explorer browser (IE Version: 11.719.18362.0) (#82553).

Issue 1: Urgency and Impact values of Orchestration are not getting updated on the SR details page. Orchestration values should override the Catch & Dispatch values.

Pre-Requisites: 

In Catch & Dispatch configuration page, switch to Service Request Module and select Show As Recommendation checkbox for all.

In the Orchestration Configuration page, select Update if any one action fails in the On Failure drop-down list and keep the Do not update if value already exists checkbox unchecked.

Bug Reproduction Steps:

Navigate to Request > New Service Request.

Create an SR where Orchestration script is linked.

Navigate to Request > Service Request List page.

Access the same Service Request and apply the catch and dispatch value from CINDE Suggestion popup.

After Orchestration script fails, all Service Request details should update as per the Orchestration configuration.

Verify the Service Request details against Orchestration configuration values.


Issue 2: Similar issue was also found for the prerequisite of On Success criteria configuration being Resolve if all actions are successful. This paired with Do not update if value already exists check box not being selected led to a similar bug. (#83602)
SAM Agent unable to block the installed software’s, mapped in the Master profile though the same software is getting block when mapped with the normal profile of an Asset. The master profile should work as default when a normal profile is configured for the Asset. (#82494)

In the Universal Agent, Software installation is not working through Run Book Automation (RBA) script. (#83612)

After configuring the remediation Script as User-preference in the new Universal Agent, the Endpoint Automation (EPA) is not working and the EPA script is always displayed with In-progress status. (#83611)

Post the SAM agent update, the Software Silent Installation functionality using RBA script is not working. This issue is occurred when the Agent machine has two IP addresses (#83770)

The servers with IP Addresses 192.168.100.30, 192.168.100.100 servers, the Universal Agent parameter EPA, Patch Management, and RBA functionalities were not working. The application was showing the following error message (#82939):

Error Message: The underlying connection was closed: An unexpected error occurred on a send.

   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)

   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at SAMAgent.Entwidgets.Service.GetRBAScripts(String sAssetInfo, String sProxyName, ProxyDetails _pxy)

   at SAMAgent.AssetDetails.Agent_RunbookAutomation.ExecuteRBA()

   at SAMAgent.Program.Main(String[] args)

 

When an AD Import record is modified on IE Version 11.719.18362.0, the error message is displayed as “Error Occurred” when you click SUBMIT button on the AD IMPORT page (Admin > Basic > Users > Import > AD Import(#82733).

While raising a CR, if the Requestor is changed after selecting Category and Change Type, the Line Manager and Reporting Manager for the selected Requestor are not getting updated in the workflow.

But after submitting the CR, the Line Manager and Reporting Manager are updated in the workflow based on the selected Requestor.

Similarly, the same issue is happing while raising CR using a template too.

While importing data through the Import Excel option, the Include Sub-Customer value in the respective column can only be True or False for all the statuses in the excel sheet.

To import the excel navigate to:

SR: Request > Configuration > Others > SMS Notification > Select the Tenant > Select the IMPORT option under ACTIONS panel.

IM: Incident > Configuration > Others > SMS Notification > Select the Tenant > Select the IMPORT option under ACTIONS panel.

(#81164)

On the Incident Details/ Service Request Details page (Incident/ Request > User > Manage Incidents/Manage Service Requests > Incident List/Service Request List > Click an Incident ID/SR ID), click the Assigned To drop-down where analysts are displaying, but their availability status is not displayed (#78647).

Application is allowing the Administrators to save the Connector details though there is a validation message while updating the Connector details page. The Connector details page can be accessed from EDIT VIEW page (Operations > Configuration > Networks > View > Edit View > Select the required device from the list > Click the Connector on the Drawing Board > Click Edit Node to update the Connector details > Update the details with incorrect data to pop-up the validation message > Click SAVE).

(#81100)

After adding a new device on the Drawing Board of the EDIT VIEW page sometimes the position of the added device is not displaying correctly on the Drawing Board. The Edit VIEW page can be accessed using (Operations > Configuration > Networks > View > Edit View > Select the Tenant and other required details> Click Add Node icon and click on the empty space of the drawing board to add devices into the View > Click SUBMIT).

(#80641)

The following issues are there on the EDIT VIEW page (Operations > Configuration > Networks > View > Edit View > Click ADD NEW on the ACTIONS panel > On the DRAW VIEW page, select the Tenant and other required details > Click ADD DEVICE on the ACTIONS panel to add devices into the View > On the ADD DEVICE pop-up page, select the devices you want to add to the View and click SUBMIT) while adding a new device to the view:

The existing devices on the page are not getting displayed.

The validation message is not populating while submitting without selecting the devices.

(#80269)

When the Maker-Checker configuration is enabled for the Allocate action and Maker-Checker approval matrix is configured with two levels of approval, on sending the Allocated Assets for Checker’s approval, the following issues are observed:

On the FIXED ASSET page (Asset > User > Manage Asset > Asset Inventory > Click the FIXED icon under the SELECT THE ASSET TYPE section > Click FILTERS on the ACTIONS panel > Select Status as Allocated and provide data in all the other fields > click SUBMIT), duplicate Assets are displayed after the Checker approves the Assets sent for approval.

The Assets do not move to the second level of approval after the Assets are approved by the first level of Approver.

Prerequisites

Enable Maker-checker approval for Asset Allocate transaction. (AdminBasic > Infrastructure > Tenant > Click Filters on the ACTION panel and select the Domain and click SUMBIT > On the TENANT page under the LIST section, select the Tenant for which you want to enable Maker Checker > Click CONFIGURE DETAILS on the ACTIONS panel > Click Asset Management under the MODULES section > select the check box of Enable Maker-Checker > Select Actions for Maker-Checker to Approve as  Allocate > Select the End Time value and click SUBMIT).

Configure No. of Approval level as 2 on the APPROVAL MATRIX page (AssetConfiguration > Others > Approval Matrix > On the ACTIONS panel, click ADD NEW > Specify the details > click SUBMIT).

Send Assets for approval for Allocate action (Asset > User > Manage Asset > Asset Inventory > On the ASSET INVENTORY page, under the SELECT THE ASSET TYPE section, click FIXED > Select the same Tenant for which the Maker-checker is enabled >  Click the In-Store hyperlink of the required Asset Category > Select the check box corresponding to the Asset you want to allocate > On the ACTIONS panel, click ALLOCATE > Specify the mandatory details to allocate the Asset and click SUBMIT).

Bug Reproduction Steps:

Login to the Application as Checker.

Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel.

On the Filter pop-up page, select the Tenant and specify the required details.

Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed.

On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click

Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS

On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details.

Click SUBMIT.

Validate the data.

(#72171)

The GetBulletinBoard Mobile API request is used to retrieve Bulletin Board information. The User ID and Tenant Code are passed as the Request Parameters. In the API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is displayed. (#73031)

Prerequisites:

Configure Bulletin Boards for multiple Tenants.

Bug Reproduction Steps:

Log into the Application as an Administrator.

Configure a Bulletin Board. For more information, see Configuring Bulletins.

Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter.

Check API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is getting displayed.

On the ACTION DETAILS pop-up page, the Target ID is not showing in the Target column when Status of the Orchestration Workflow Script (other than the first Script) is In-Progress, and it is having Target Host Type mapped to From Previous Output valueHowever, the Target ID is displayed after the Script is executed successfully. (#73079)

Note: This issue is found in Incident Management, Work Order, and Service Request Management (SR) modules. Following bug reproduction steps are for the SR module:

Bug Reproduction Steps:

Log into the Application as an Administrator.

Select Admin > Advanced > Automation > Orchestration.

On the WORKFLOW LIST page, click the NEW

On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow.

Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow.

Log out and log into the Application as an Administrator or as an Analyst.

Select Request > Manage Service Requests > Service Request List.

On the SERVICE REQUEST LIST page, specify the Filters and open an SR.

On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab.

On the ORCHESTRATION tab, click the Script When the Script (other than the first Script) is in In Progress status, check the Target column details on the ACTION DETAILS pop-up page. The Target ID is not displaying in the Target column.

After successful execution of the Script (other than the first Script), click the Script hyperlink. Check the Target column details on the ACTION DETAILS pop-up page. Now, the Target ID is displaying in the Target column.

The previous Asset transaction details are not displayed under the Previous Transaction drop-down list on the PREVIOUS IMPORT DETAILS page (Asset > User > Manage Assets > Import > Import Asset > Specify all the details > Click SUBMIT), even though the Assets are approved by the Checker on the MAKER-CHECKER ASSET-APPROVAL page (Asset > User > Manage Assets > Approvals > Maker Checker Approval > Click Filters  on the ACTIONS panel > Specify the filter criteria to view the list of requests from the Maker > Select the Assets that you want to approve under the LIST section > Click APPROVE on the ACTIONS panel > Select the  Approval Status as Approved.) This issue is found when the Asset Maker Checker Configurations is enabled.

(#67240)

When a user opens any page in a new tab in the SaaS Environment, the Switch Tenant pop-up is displayed in all the pages. This issue occurs only when the user is using the Firefox private window/tab. (#72276)

On the ADMIN DETAILS page (Admin > Advanced > Password Management > Administrator > Click ADD NEW on the ACTIONS panel > Specify all the details > Click SUBMIT > Select the Domain Name on the LIST page), the Password field is not displaying the GUID or Encrypted ID of the password and the field is empty. This issue is found when the user is logging into the SummitAI application using Microsoft Internet Explorer browser.

On the Incident Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Incident Management > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

On the Service Request Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Service Request > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and Multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

The configured Bulletin Board (Admin > Advanced > Notifications > Bulletin Board > Select the Tenant > Click ADD NEW to configure the Bulletin details > Click SUBMIT) is displayed on the END USER DASHBOARD page even if the user does not have access to the selected Tenant and Domain.

Overlapping of content is observed on the Pagination bar of all the pages having high amount of data (typically in the range of 5 digits).

Broken image of the logo is displayed in the application when the logo image is deleted from the APPLICATION SETTINGS page (Admin > Basic > Infrastructure > Application Settings).

Workaround: The users need to re-login to the SummitAI application after deleting the logo.

On the AUTO-RESOLUTION SERVICE REQUEST CONFIGURATION and AUTO-RESOLUTION INCIDENT CONFIGURATION page (Admin > Basic > Infrastructure > Tenant > Select Domain > Select Tenant which is configured with Service Request/ Incident Management module > Click CONFIGURE DETAILS on the ACTIONS panel > Under the For End Users tab, select a reason form the Enable Reminder to Callers for Pending Reasons drop-down list > Enable Auto-Resolve Service Requests/ Auto-Resolve Incidents check box > Click Set Fields for Auto-Resolving Service Requests/ Set Fields for Auto-Resolving Incidents link), the users can set the auto-resolution criteria by specifying only white space (not numbers and alphabets) in the Response SLA ReasonResolution SLA Reason, and Solution fields.

The following issues are observed in BI Custom Reports:

When a user downloads the report (in any format), the data is displayed with hyperlinks.

When a user places the mouse cursor on the count link, the tooltip is displayed as [Object Object].

In the exported report, report name is displayed with '+' instead of space.

The Change Record is not created when the CR Requester and Customer Approver are same. This issue occurs even though Do Not allow Customer Approval of CR check box is selected on the Change Management TENANT configuration page. This issue occurs only for the first time when the Tenant is configured.

Workaround: The Administrator needs to unselect and again select the Do Not allow Customer Approval of CR on the Change Management TENANT configuration page (Admin > Basic > Infrastructure > Tenant > Select the respective Tenant for which this issue is occurring > Click CONFIGURE DETAILS on the ACTIONS panel > Enable Do Not allow Customer Approval of CR check box and click SUBMIT > Clear Do Not allow Customer Approval of CR check box and then click SUBMIT, again).

The new SLA Value of an Incident is not displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident) when an incident is moved from New status to In-Progress using Notification Services.

The Pending Reason of an incident is still displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident), when an Orchestration Script fails and the respective Incident is moved back from Pending to In-Progress.

The notification e-mails related to escalation and jobs are triggered only in English language irrespective of the configured language on the NOTIFICATION TEMPLATE page for all the modules (AdminAdvancedNotificationNotification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT).