Release Notes v6.1.0.1 HF05

• There is no Settings/Gear while selecting Attachment in Map Fields in Create Record Action & Update & Parse content in Update Action. So, there is no restriction on the allowed file extensions at Parser level.
• As of now only 33 extensions are allowed as provided in attached excel file.
• For .msg type attachments, emails to a ticket are parsed with attachments as .eml or .msg only. So, for .msg type attachments, the file name is .eml or .msg.

• There is no Settings/Gear while selecting Attachment in Map Fields in Create Record Action, Update, and Parse content in Update Action. Therefore, there will be no restrictions on allowed file extensions at Parser level. 
• As of now, only 33 extensions are allowed in the attached excel file. 
• For .msg attachments, the emails are parsed to a ticket with the attachments preserved as either .eml or .msg files. In summary, for .msg files, the filenames will be displayed as either .eml or .msg.

Users were experiencing discrepancies in the Service Requests Analyst Dashboard. All the information on the Dashboard was incorrect.

1. Log in to the application (as Analyst or End user)
2. Click Service Management application.
3. Refresh the page.
4. Verify the pinned icon of the sub menu.

1. Log in to Apex application.
   
   
2. Navigate to Incidents > Manage Incidents.
   Or
   Navigate to Incidents > My Incidents.
   
   
3. Click an Incident ID to view the ticket details.

Steps: 

1. Log in to the Apex Application as an End User.
    
2. Navigate to Service Management > Service Request > My Service Requests.
   
   
3. Click New on the My Service Requests List page.
   
   
4. Provide all the required details and raise the Service Request.
   
   
5. Log in to the Apex application as an Analyst.
   
   
6. Navigate to Service Request > Manage Service Requests.
   
   
7. Click the newly raised SR ID hyperlink.
   
   
8. On the Service Request details page, check and verify the Links tab. 

Prerequisite:

Analysts should not have access to the specific workgroup. 

Steps: 

1. Log in to the Application as an Analyst.
   
   
2. Navigate to Service Request > Manage Service Request.
   
   
3. Open a new SR.
   
   
4. Click the Change History icon on the top panel.
   
   
5. Check the tabs of Change History, Communication History, Workflow History, Link History, SLA History, & Access History. 

Note: It is applicable to all the modules in Service Management.

Steps:

1. Log in to Application as an Analyst.
    
2. Navigate to Change > Change Request > Manage Change Request.
    
3. Select CR ID.
   
   
4. Validate UI on the Approval Timeline.

1. Log in to Apex application.
   
   
2. Navigate to Service Request > click Manage Service Requests.
   Or
   Navigate to Incident > click Manage Incidents.
   
   
3. Scroll down the page. Click Messages tab.
   
   
4. Verify the links under User Communication section.

Prerequisite: 

1. Create a Catalog with Multichoice and map with Controls. 

Steps: 

1. Log in to Apex application as an End User.
   
   
2. Navigate to Service Management > Service Request > My Service Requests.
   
   
3. Click New and navigate to New Service Request configuration page.
   
   
4. Select a Catalog that has multichoice control. Provide information in all the mandatory fields and click Submit.
   
   
5. On the My Service Requests List page, click the SR ID hyperlink and navigate to the Service Request Details page.
   
   
6. Check and verify all the fields on the details page. 

Steps: 

1. Log in to Apex application as an Analyst.
   
   
2. Navigate to Service Request > Manage Service Request.
   
   
3. Click New. 

Steps: 

1. Log in to Apex application as an Analyst.
   
   
2. Navigate to Incident > Manage Incident. 

Note: The records are displayed when user location is applied as a filter. 

1. Log in to Apex application.
   
   
2. Navigate to Incident > click My Incidents.
   
   
3. Click New.
   
   
4. Fill in all the mandatory fields.
   
   
5. Verify the field under How do you categorize your issue.

Advance Filter on the List page was not working as expected in the Incident Module. 

1. Log in to Application as an Analyst.
   
   
2. Navigate to Incident > Manage Incidents.
   
   
3. Select View on the list page.
   
   
4. Add Advance Filter.

Steps:

1. Login to the Apex application.
   
   
2. Select any module under Module.
   
   
3. Navigate to Form Designer > Form Relation.
    
4. Click New > Enter the mandatory details > click Next.
   
   
5. In the Set Values stepper enter the Source values > Enter Target values > Click the + icon to add multiple fields and verify if you can add.  

Steps:

1.    Login to the Apex application.

2.    Navigate to Incident > Manage Incidents. 

3.    Click New > Select Tenant > Click on Category icon. 

4.    Verify if the Category and Sub-Category lists are sorted in alphabetical order. 

Steps:

1. Login to the Apex application.
    
2. Select Module as Incident.
   
   
3. Navigate to Incident > Manage Incidents. Incident List page is displayed.
   
   
4.  Hover over the left side menu and click the pin icon at the top.
   
   
5. Refresh the screen. 

Configure the Azure_User_Profile_Image_API in the API Configuration that can be used to retrieve user profile images from Azure AD. 

1. Navigate to Design Studio > Module > API Configuration.
   
   
2. Click New.
   
   
3. Create the Azure_User_Profile_Image_API similar to the Microsoft Graph API Configuration.
   
   
   
4. In the API Details section, Enter the URL as https://graph.microsoft.com/v1.0/users/user_prinicipal_name/photo/$value.
   
   
   
5. In the Authentication Type, select OAuth 2.0 and provide the necessary configurations in the respective fields as per Graph API.
   

• Incorporating the User profile image provides personalized user experience.
  
  
•  Visual identity improves trust with the platform.