DESIGN AND DEVELOPMENT OF BUSINESS

MANAGEMENT APPLICATIONS
(Done at “OPENTEXT”)

A Project Report (Phase II)-ECE18R499

submitted in partial fulfilment of the

requirements for the award of the degree

of

Bachelor of Technology

in

ELECTRONICS & COMMUNICATION ENGINEERING

by

GONUGUNTLA VANDANA (9919005322)

DEPARTMENT OF ELECTRONICS & COMMUNICATION ENGINEERING

SCHOOL OF ELECTRONICS, ELECTRICAL AND BIOMEDICAL
TECHNOLOGY
KALASALINGAM ACADEMY OF RESEARCH AND EDUCATION
(Deemed to be University)
KRISHNANKOIL-626126, TN (INDIA)

MAY- 2023

i
MAJOR DESIGN EXPERIENCE INFORMATION

Student Details : Gonuguntla Vandana

9919005322
External Supervisor : I S Praveen Kumar
Internal Supervisor : Dr. K. Jeya Prakash
Internship Title :
DESIGN AND DEVELOPMENT OF BUSINESS
MANAGEMENT APPLICATIONS

Name of the Company : OPENTEXT

Program Concentration : Software Development

Area
Subject(s) as : Java, JavaScript
Pre-requisite
Constraints : 1. Identification and extraction of related information
to the project perspective. Understanding the exact
requirements of client support requests.
2. Analysing and interpreting the appropriate approach
in addressing the issue addressed by client is a
time-consuming process hence, more research work is
included in consideration of the current industry
standards for the verification process.

ii
 DECLARATION BY THE STUDENT
I certify that,
a. the project report submitted by me is original and authentic and has been done at
“OpenText” under the guidance of “I S Praveen Kumar, Senior Manager” from
“OpenText” and “Dr. K. Jeya Prakash, Associate Professor”, ECE Department
during a period from 22-12-2022 to 22-06-2023. The work has not been submitted to any
other Institute for any degree or diploma.
b. I have followed the guidelines provided by the department and “OpenText” in preparing
the report. I have conformed to the norms and guidelines given in the Ethical Code of
Conduct of the University.
c. Whenever I have used materials (data, theoretical analysis, figures, and text) from other
sources, I have given due credit to them by citing them in the text of the report and giving
their details in the references. Further, I have taken permission from the “Company”,
whenever necessary.
The matter presented in this project report has not been submitted by us for the award
of any other degree elsewhere and it is submitted by us on partial fulfillment of the
requirements for the award of the Bachelor of Technology in Electronics &
Communication Engineering to the Department of Electronics & Communication
Engineering, Kalasalingam Academy of Research and Education (Deemed to be University)
Tamilnadu.
Project Final Review Viva-voce held on 28/04/2023.

Signature of Candidate(s)
Gonuguntla Vandana (9919005322)
This is to certify that the above statement made by the candidate is correct to the best
of my knowledge.

Signature of Supervisor(s)
Date: Dr. K. Jeya Prakash
Associate Professor

Head of the Department

Department of Electronics & Communication Engineering,
Kalasalingam Academy of Research and Education (Deemed to be University) TN

Internal Examiner External Examiner

iii
 ACKNOWLEDGEMENT

We are indebted to Kalasalingam University Founder and Chairman

“Kalvivallal” Thiru T. Kalasalingam, “Illayavallal” Dr. K. Sridharan, Chancellor, Dr.
Shasi Anand, Vice President, Dr. S. Narayanan, Vice-Chancellor and
Dr. V. Vasudevan, Registrar, Kalasalingam Academy of Research and Education for
funding my project work.

In preparing this report, we were in contact with many people, researchers,

academicians, and practitioners. They have contributed towards our understanding and
thoughts. We wish to express our sincere appreciation to our supervisor, Mr. I S Praveen
Kumar, for encouragement, guidance, critics, and friendship. We are also very thankful to
Dr. P. Sivakumar, HoD-ECE and Project Coordinators Dr. K. S. Dhanalakshmi, Associate
Professor-ECE, Dr. V. Hima Deepthi, Professor-ECE and Dr. M. Kalpana, Associate
Professor, for their guidance, advice, and motivation. Without their continued support and
interest, this project report would not have been the same as presented here. We wish to
express our sincere thanks also to Nanochip Solutions, Bangalore for providing problem
statement and to the industrial experts Mr. Manjunath, Mr. Manoranjan and Ms.
Vijayashree for providing technical inputs for the implementation of the project. Librarians
at Kalasalingam Academy of Research and Education also deserve special thanks for their
assistance in supplying the relevant literatures.

We thank all the teaching and non-teaching faculty of ECE department for their help
to complete this project work. We are also grateful to all my family members, friends and all
others who have aided at various occasions. Their views and tips are useful indeed.
Unfortunately, it is not possible to list all of them in this limited space.

iv
 ABSTRACT

The purpose of this study is to understand the usage of Appworks platform by

OpenText and create various applications and web pages as required by the clients. This
report provides the knowledge of different tools and platforms we use in giving the client
required outcomes and how to improve the performance or efficiency of the websites by
making the changes. AppWorks is a low-code application development platform developed
by OpenText. It is designed to help organizations build custom business applications quickly
and easily. AppWorks offers a drag-and-drop interface that allows developers to create
applications without writing extensive code. The platform also provides a library of pre-built
components that can be used to speed up the development process. With AppWorks,
developers can create custom applications for various business needs, such as document
management, customer relationship management, and supply chain management. The
platform also integrates with other OpenText products, such as Content Suite and Process
Suite, to provide a comprehensive solution for enterprise information management.
AppWorks supports both cloud and on-premises deployment, giving organizations the
flexibility to choose the deployment option that best fits their needs. The platform is also
designed to be scalable, allowing organizations to start small and expand as their business
needs evolve. Overall, Appworks is a powerful and flexible low-code application
development platform that enables organizations to quickly build custom business
applications with minimal coding effort. Its integration with other OpenText products and
support for cloud and on-premises deployment make it a versatile solution for enterprise
information management. There are many customers like DHMC, FedEx and others whose
use AppWorks for their daily business information and managements which makes it concern
less and flexible environment and on or off cloud deployments. This AppWorks is also
present in the android and iPhone, there will be frequent upgrades for the application with
new feature requests or changes are made.

v
 TABLE OF CONTENTS

CHAPTER TITLE PAGE

MAJOR DESIGN EXPERIENCE INFORMATION ii

DECLARATION iii

ACKNOWLEDGEMENT iv

ABSTRACT v

TABLE OF CONTENTS vi

LIST OF FIGURES vii

LIST OF ABBREVIATIONS viii

1 INTRODUCTION
1.1 INTRODUCTION 1-3

1.2 RESEARCH GOALS 4

2 PROJECTS
2.1 HISTORY PANEL INCONSISTENCY IN RUNTIME 5-6

2.2 FORM BUILDING BLOCK ERROR 7

3 AUTOMATION
3.1 AUTOMATION 8

3.2 HISTORY PANEL AUTOMATION 9-11

3.3 MODIFY ASSIGNEE AUTOMATION 12-14

4 DELIVERABLES DEVICE VALIDATIONS

4.1 VALIDATIONS 15-18

RESULTS AND DISCUSSIONS 19

CHAPTER SUMMARY 20

INTERNSHIP JOINING REPORT

vi
 LIST OF FIGURES

FIGURE NO. Title PAGE

Figure 1.1 Features of AppWorks 2

Figure 1.2 Appworks homepage 3

Figure 1.3 Building blocks in AppWorks 4

Figure 2.1 Web page view of history panel 5

Figure 2.2 Maximized panel view of history panel 6

Figure 2.3 Minimized panel layout after resizing the window. 6

Figure 2.4 Entity creation for form building Block 7

Figure 2.5 Tooltip for dropdown in webpage 7

Figure 3.1 Console output for history panel automation 11

Figure 3.2 Console output for modify assignee automation. 14

Figure 4.1 Browser validation for icon change 17

Figure 4.2 Tablet validation for icon change 18

Figure 4.3 Mobile validation for icon change 18

vii
 LIST OF ABBREVIATIONS

AWP - Appworks platform

BPM - Business process management

DHMC - Darmouth-hitchcock medical centre

SaaS - Software as a service

QA - Quality assurance

OT - Open text

UI - User Interface

CI - Continuous Integration

CD - Continuous Delivery

viii
 CHAPTER 1

INTRODUCTION

Many companies use AppWorks platform for the management of their businesses and
information or their daily reports of trades. There would be processed when a user initiates a
task, this process is made easier through the implementation of AppWorks in their daily
needs. This AppWorks by OpenText provides us with easier application management and
flexibility of usage of applications.
With less IT involvement, AppWorks automates business processes, enables better decision
making and improves user experiences. It creates new opportunities to re-engineer processes
around customer, employee, and partner needs, deliver seamless digital experiences and adapt
to changing market expectations while improving operational efficiency and managing risk.
There are many features and benefits of using this AppWorks platform that are listed below as
follows:

Features

➢ Dynamic case management:

The dynamic case management feature of OpenText AppWorks provides knowledge

workers with the necessary access to systems, content, and individuals required to advance
cases efficiently.

➢ Mobile app development:

OpenText AppWorks follows a mobile-first philosophy, enabling business users to manage

tasks and access information from any device, at any time, and from any location.

➢ Low-code development:

By leveraging code reuse, simplified development practices, and accelerators, OpenText

AppWorks accelerates the development of process and case-driven applications.

1
➢ Intelligent automation:

With OpenText AppWorks, it is simple to define, optimize, and automate recurring business
processes, while also integrating with RPA tools and incorporating rules within the processes
to standardize operational decisions and guarantee consistent execution.

➢ Flexible deployment:

OpenText AppWorks offers flexible deployment options, allowing businesses to run it on-
premises or deploy it on the cloud for enhanced agility, simplified deployment and updates,
and faster access to new capabilities.

Fig 1.1: Features of AppWorks

Benefits

➢ Build applications faster:

OpenText AppWorks enables businesses to develop applications rapidly, using low-code
development, drag-and-drop modeling, accelerators, and reusable building blocks, resulting
in lower costs.

2
➢ Deliver streamlined, intuitive user experiences:
OpenText AppWorks enables businesses to create smart, content-rich applications that are
tailored to the changing needs of modern work environments, allowing them to provide a
dynamic and relevant customer experience.

➢ Integrate enterprise information:

OpenText AppWorks facilitates the seamless connection and orchestration of information
flows across lead applications and other systems, all from within business applications.

➢ Gain real-time business insight:

OpenText AppWorks provides businesses with pre-built, customizable reports, eliminating
the need for complex tasks involved in building, deploying, and using a separate business
intelligence tool.

➢ Increase developer agility:

OpenText AppWorks facilitates collaborative work between developers and business
experts, leading to faster development cycles and shorter time-to-value for applications.

➢ Deploy easily, on or off-cloud:

OpenText AppWorks is a cloud-native platform that is containerized, making it easy to
deploy and run applications virtually anywhere. This platform simplifies updates and
enables faster introduction of new features.

Fig 1.2: Appworks Homepage

3
 Fig 1.3: Building Blocks in Appworks

Research Goal

• The research objective is to understand the usage and implementation of AppWorks

platform and design an enhanced and flexible application.
• Understand the client requirements and make changes in the code and build an error
free and make concern free output.
• Handle the code changes with great expectations and make them less prone to back
requests for changes and meet the criteria.

4
 CHAPTER – 2

PROJECTS

1. History Panel Inconsistency in runtime

Observed result:
• The carat icon is visible in both collapsed and expanded state if the panel is
maximized.
• If the content is expanded and the panel is resized the carat icon is not visible.
• The icon is visible if the lines are greater than 3.
Expected result:
• The carat icon should not be visible if the panel is maximized.
• The icon should be visible if the number of lines in the comment are greater than
three.
• The icon should be visible even if it is expanded and resized.

Fig 2.1: Web page view of History Panel

5
 Fig 2.2: Maximized panel view of History Panel

Fig 2.3: Minimized Panel layout after Resizing the window.

6
2. Form Building block.
Observed result:
• The tooltip is not visible for the dropdown input.
• The tooltip is not visible for the read only text property.
Expected result:
• The tooltip should be visible for the enumerated text property in the dropdown if
we hover the mouse on it.
• The tooltip should be visible if the enumerated property is read only.

Fig 2.4: Entity creation for Form Building Block

Fig 2.5: Tooltip for dropdown in webpage

7
 CHAPTER – 3

AUTOMATION

Automation testing is a software testing technique that utilizes automated tools and
scripts to conduct tests on software applications or systems. The process involves using
pre-written test scripts and software to automate tedious and time-consuming testing tasks,
thus reducing the overall testing effort and time. Automation testing is widely used in
software development and testing processes, particularly in agile and continuous delivery
environments, where frequent software code changes and updates require swift testing
cycles. Automation testing offers various advantages, including improved test accuracy,
increased testing speed, better test coverage, and reduced testing costs. However, it requires
significant upfront investment in tools, infrastructure, and expertise, and may not be
suitable for all types of testing scenarios. Therefore, it's important to carefully select
appropriate tools, test cases, and overall testing strategies before embarking on automation
testing.
In automation testing, test cases are written using programming languages and
automated testing tools like Selenium, Appium, TestComplete, and many others. These
tools help to automate the repetitive and time-consuming tasks, which are difficult or
impossible to perform manually. By automating these tasks, testers can focus on more
complex and critical scenarios that require human judgment.
Automation testing can be applied to various types of testing, including functional testing,
regression testing, performance testing, and many others. It also supports continuous
integration and continuous delivery (CI/CD) by automating the testing process and
integrating it into the development pipeline.
Overall, automation testing has become an essential part of the software development
life cycle (SDLC), helping to improve the quality and reliability of software products while
reducing costs and time-to-market.

8
1. History Panel

CODE:

package com.opentext.forms;
import org.openqa.selenium.By;
import org.openqa.selenium.WebElement;
import org.testng.Assert;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;
import com.google.common.collect.Table;
import com.opentext.accelerators.ApplicationFactory;
import com.opentext.accelerators.AssertionUtilities;
import com.opentext.accelerators.Base;
import com.opentext.accelerators.ReusableMethods;
import com.opentext.accelerators.WaitUtilities;
import com.opentext.accelerators.WaitUtilities.WaitDuration;
import com.opentext.objectrepository.entity.LayoutBBElements;
import com.opentext.objectrepository.entity.ListCardviewRuntimeElements;
import com.opentext.objectrepository.processexperience.ListBBPEElements;
import com.opentext.objectrepository.processexperience.PECommonFunctionElements;
import com.opentext.objectrepository.processexperience.PEFormElements;
import com.opentext.objectrepository.processexperience.PEHistoryElements;
import com.opentext.objectrepository.processexperience.PEListsElements;
import com.opentext.objectrepository.processexperience.PEResultsElements;
import
com.opentext.objectrepository.processexperience.PEFormElements.PEFormTypes;
import
com.opentext.objectrepository.processexperience.PEFormElements.ToManyRelActionBt
ns;
import
com.opentext.objectrepository.processexperience.PEResultsElements.PEResultMenuButt
ons;
import com.opentext.workflow.processexperience.PECommonFunctions;
import com.opentext.workflow.processexperience.PEForm;
import com.opentext.workflow.processexperience.PELists;
import com.opentext.workflow.processexperience.PEResults;

public class ModifyAssignee extends Base {

9
@BeforeClass
public void Setup() {
ApplicationFactory.launchPE2();
PECommonFunctions.selectHomePageLayout("Home Page");
WaitUtilities.wdWaitVisibility(PEFormElements.peLogo, WaitDuration.MINWAIT);
WaitUtilities.returnPageLoadStatus(PEFormElements.peLogo,
WaitDuration.MINWAIT);
PECommonFunctions.selectEntityToCreateInstance("TaskLineTemplate");
}

@Test(priority = 0)
public void SendDataToInputName() {

ReusableMethods.customSleep(2);
PEForm.setInputTextInTextFields("Name","V", PEFormTypes.CREATE);

ReusableMethods.clickElement(LayoutBBElements.btnCreateInstance);
ReusableMethods.clickElement(PEFormElements.nameinRGC());
ReusableMethods.clickElement(PEFormElements.toOnePickerDisplay);
ReusableMethods.clickElement(ListBBPEElements.getToOneBrowseButton());
// clicks on browser btn
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEFormElements.clickRadiobtninList);
AssertionUtilities.assertElementPresence(By.xpath("(//div[@class='au-target radio-off
grid-select-column'])[1]]"), false, "Radio button is selected");
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEFormElements.btnSelect);
ReusableMethods.clickElement( ListCardviewRuntimeElements.BtnCreateInstance);

PECommonFunctions.selectHomePageLayout("Home Page");
PELists.selectWorkList("In lists and results","AllTemplateTasksToPersons");
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEResultsElements.headerCheckBoxOff);
ReusableMethods.clickElement(PEResultsElements.otResultActions);
PECommonFunctions.selectDropdownOption("Display name", "v2");
ReusableMethods.clickElement(PEFormElements.okButton);
ReusableMethods.clickElement(PEResultsElements.headerCheckBoxOn);
}

@AfterClass
public void cleanUp() {

10
PECommonFunctions.selectHomePageLayout("Home Page");
PELists.selectWorkList("In lists and results","AllTemplateTasksToPersons");
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEResultsElements.headerCheckBoxOff);
ReusableMethods.clickElement(PEFormElements.deletebtn);
ReusableMethods.clickElement(PEFormElements.deleteConfirmation);
}

OUTPUT:

Fig 3.1: Console output for History Panel Automation

11
2. Modify Assignee

CODE:

package com.opentext.forms;

import org.openqa.selenium.By;
import org.openqa.selenium.WebElement;
import org.testng.Assert;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;
import com.google.common.collect.Table;
import com.opentext.accelerators.ApplicationFactory;
import com.opentext.accelerators.AssertionUtilities;
import com.opentext.accelerators.Base;
import com.opentext.accelerators.ReusableMethods;
import com.opentext.accelerators.WaitUtilities;
import com.opentext.accelerators.WaitUtilities.WaitDuration;
import com.opentext.objectrepository.entity.LayoutBBElements;
import com.opentext.objectrepository.entity.ListCardviewRuntimeElements;
import com.opentext.objectrepository.processexperience.ListBBPEElements;
imporcom.opentext.objectrepository.processexperience.PECommonFunctionEleme
nts;
import com.opentext.objectrepository.processexperience.PEFormElements;
import com.opentext.objectrepository.processexperience.PEHistoryElements;
import com.opentext.objectrepository.processexperience.PEListsElements;
import com.opentext.objectrepository.processexperience.PEResultsElements;
importcom.opentext.objectrepository.processexperience.PEFormElements.PEForm
Types;
importcom.opentext.objectrepository.processexperience.PEFormElements.ToMany
RelActionBtns;
importcom.opentext.objectrepository.processexperience.PEResultsElements.PERes
ultMenuButtons;
import com.opentext.workflow.processexperience.PECommonFunctions;
import com.opentext.workflow.processexperience.PEForm;
import com.opentext.workflow.processexperience.PELists;
import com.opentext.workflow.processexperience.PEResults;

public class ModifyAssignee extends Base {

@BeforeClass
public void Setup() {
ApplicationFactory.launchPE2();
PECommonFunctions.selectHomePageLayout("Home Page");

12
WaitUtilities.wdWaitVisibility(PEFormElements.peLogo,
WaitDuration.MINWAIT);
WaitUtilities.returnPageLoadStatus(PEFormElements.peLogo,
WaitDuration.MINWAIT);
PECommonFunctions.selectEntityToCreateInstance("TaskLineTemplate");
}

@Test(priority = 0)
public void SendDataToInputName() {

ReusableMethods.customSleep(2);
PEForm.setInputTextInTextFields("Name","V", PEFormTypes.CREATE);

ReusableMethods.clickElement(LayoutBBElements.btnCreateInstance);
ReusableMethods.clickElement(PEFormElements.nameinRGC());
ReusableMethods.clickElement(PEFormElements.toOnePickerDisplay);
ReusableMethods.clickElement(ListBBPEElements.getToOneBrowseButton());
// clicks on browser btn
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEFormElements.clickRadiobtninList);
AssertionUtilities.assertElementPresence(By.xpath("(//div[@class='au-target radio-
off grid-select-column'])[1]]"), false, "Radio button is selected");
Assert.assertTrue(ReusableMethods.isElementDisplayed(PEFormElements.clickRa
diobtninList),"v is slected in the list");
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEFormElements.btnSelect);
ReusableMethods.clickElement(
ListCardviewRuntimeElements.BtnCreateInstance);
PECommonFunctions.selectHomePageLayout("Home Page");
PELists.selectWorkList("In lists and results","AllTemplateTasksToPersons");
ReusableMethods.customSleep(1);
ReusableMethods.clickElement(PEResultsElements.headerCheckBoxOff);
ReusableMethods.clickElement(PEResultsElements.otResultActions);

PECommonFunctions.selectDropdownOption("Display name", "v2");

ReusableMethods.clickElement(PEFormElements.okButton);
ReusableMethods.clickElement(PEResultsElements.headerCheckBoxOn);

@AfterClass
public void cleanUp() {
PECommonFunctions.selectHomePageLayout("Home Page");
PELists.selectWorkList("In lists and results","AllTemplateTasksToPersons");
ReusableMethods.customSleep(1);

13
ReusableMethods.clickElement(PEResultsElements.headerCheckBoxOff);

ReusableMethods.clickElement(PEFormElements.deletebtn);
ReusableMethods.clickElement(PEFormElements.deleteConfirmation);
}

OUTPUT:

Fig 3.2: Console output for Modify Assignee Automation

14
 CHAPTER - 4

DELIVERABLES DEVICE VALIDATIONS

INTRODUCTION:

The deliverables of device validation in software typically include a set of documents

and artifacts that demonstrate the validation process and its results. These may include
validation plans, protocols, test cases, and reports. A validation plan outlines the scope
and approach of the validation process, while a protocol provides step-by-step
instructions for executing the validation tests. Test cases are specific scenarios or use
cases that are tested to ensure the software functions as intended. The results of these
tests are documented in a validation report, which summarizes the findings and any
issues or defects found during testing. Other deliverables may include traceability
matrices that map requirements to test cases, and documentation of any changes or
updates made to the software because of the validation process. The specific
deliverables required may vary depending on the regulatory requirements and the
complexity of the software being validated. Ultimately, the purpose of these
deliverables is to demonstrate that the software has been thoroughly tested and meets
its intended use, is safe, and effective for its intended purpose.

There are various types of validations depending on the context, but some of the most
common types include:

1. Data Validation: This type of validation ensures that the data entered into a system
or application is accurate, complete, and consistent. It can include checks for data type,
format, range, and consistency.

2. Form Validation: This type of validation ensures that all required fields in a form
are completed, and the data entered is valid. It can include checks for formatting, data
type, and required fields.

15
3. Process Validation: This type of validation ensures that a specific process or
procedure is operating correctly and producing consistent results. It can include checks
for process inputs, outputs, and performance.

4. Software Validation: This type of validation ensures that software meets its
intended use, is safe, and effective for its intended purpose. It can include checks for
functionality, usability, performance, and security.

5. System Validation: This type of validation ensures that a system meets its design
and functional specifications and is suitable for use in its intended environment. It can
include checks for hardware, software, and network components.

6. User Validation: This type of validation ensures that users have the appropriate
permissions and access to perform their tasks within a system or application. It can
include checks for user roles, access controls, and security permissions.

Overall, the type of validation required will depend on the context and purpose of the
system, software, or process being validated.

Advantages of Validation in Software:

1. Validation is an important part of software development, and there are several

advantages to implementing validation in software, including:

2. Improved data accuracy: Validation ensures that data entered into a system or
application is correct, complete, and within acceptable limits, which leads to
improved data accuracy.

3. Enhanced security: Input validation can prevent malicious data from being entered
into an application, which can help enhance security and prevent security breaches.

16
4. Better user experience: Form validation can improve the user experience by ensuring
that forms are completed correctly and that all required fields are filled in.

5. Improved efficiency: Logic validation can help identify and fix errors in an
application's logic, which can improve efficiency and reduce the need for manual
error correction.

6. Cost savings: Validating data, inputs, and forms can help reduce errors and prevent
costly mistakes, which can save time and money in the long run.

1. Change icon X to exclamatory mark if there are errors in the form.

Browser Validation

Fig 4.1: Browser validation for icon change

17
Tablet Validation

Fig 4.2: Tablet validation for icon change

Mobile Validation

Fig 4.3: Mobile validation for icon change

18
Result and Discussion

The report provides a detailed account of the internship experience working

on Jaa, JavaScript and selenium automation. Also, it describes the project that I have
done by applying the knowledge of java and JavaScript to real-time scenarios.
Through these projects I was able to improve my skillset.
One of the major tasks in the company includes providing the customers to
experience the seamless experience with AppWorks platform. The projects helped to
brush up on your knowledge on java and software development and create a user-
friendly and efficient web application.
We have created an application to the client based on their business
requirements. In this process of creating the application. I was able to learn new
techniques and best practices for java programming, as well as gain experience
working in a team environment.
In addition to java, I also worked extensively with JavaScript. I was assigned
to make the client code changes for a support request. I have also worked on the
automation in which I gained experience in test automation, which involved creating
and executing test scripts and analyzing test results. I also learned how to work with
testing frameworks such as TestNG and JUnit.
I believe that the skills and knowledge I gained during my internship will be
valuable to my further software career. I have worked and learned about the team
working and gained valuable experiences and knowledge.

19
Chapter Summary

The first chapter discusses the implementation and working of the

AppWorks platform and its usage on the customer side. It gives insights on the
features of the AppWorks and the benefits of using AWP in our businesses.it also
discusses about the add-ons of AppWorks such as OpenText process suite and
OpenText extended ECM, experience platform DXM. It also includes the research
goals.
The second chapter gives insights about the projects I have done and the
implementation of the codes that are required for getting the expected results as per
client requirements. It states both the expected and obtained results and the code that
is implemented to get the desired output.
The third chapter is detailed about the introduction to automation and types
of automation. It also briefs the automation for the projects that I have automated
and selenium automation code that is implemented while performing the automation
for a couple of tickets History panel and modifying assignee.
The last chapter gives details about the deliverable’s device validation. It
explains the different types of validation and it is used for testing an application. It
includes the validations of a ticket that I have validated in all the three scenarios and
attached screenshots of the validation. It concludes with the advantages of
validation in devices before out rolling an application.

20
PRIVATE AND CONFIDENTIAL

16 February 2023

To Whom It May Concern,

Re: Gonuguntla Vandana

This letter will confirm that Gonuguntla Vandana is a Full Time Intern of Open Text Technologies India Pvt Ltd from 22
December 2022 to present.

Additional employment details are as follows:

Position/Job Title: Intern

Gross Annual Base Salary: 180,000 INR

To verify the information above, please feel free to contact Human Resources Shared Services at [email protected].

Sincerely yours,

Christine Loh
VP, HR Operations

 
www.opentext.com - [email protected]

Unless otherwise noted, this message is confidential or privileged, and is intended for the exclusive use of the addressee. Any other person is strictly
prohibited from disclosing or reproducing it. If the addressee cannot be reached or is unknown to you, please inform the sender by return mail.

Page 1 of 1