APPIAN WEBSITE

(Appian workshop, Accenture)

The website is a simple framework for developing applications. Using the 'Appian designer' tool, an unlimited number of sites can be created to meet any business need and provide business-oriented navigation. By developing my site in the application, I gained practical knowledge of creating a good user experience design.

OBJECTIVE

The website's prime objective is to provide a personalized user experience with business-oriented navigation, as well as easy user access to other sites and workspaces via site navigation menu or the URL created in the application. The sites are designed according to the users' business needs and are branded with their corporate identity.

Role

User experience design
Prototyping
Testing

Timeframe

1 week

July 2019

Design

In the application, built my site for online goods sales by creating pages to organize the content.
The pages were customized to show action type, report and record type of customers.
Appian console: Configures administrative settings from branding to navigation bar according to developer specifications, adds community plugins, and creates users.
Tempo: Main area where users will have access to , as well as defines other customized user access sites. It includes information such as News, Tasks, Records, Reports, and Actions of the users.

Actions- To initiate a process
Records- For key business objects with quick access to details and related actions
Reports- To analyze business performances
Task reports- For users to track complete tasks

List of pages in the navigation bar

New customer service requests: This is an action page that generates a new service request for the user who requires assistance with the orders placed.
Service requests: This is an action type page that manages all the service requests placed by the user.
Records: This page type contains the records of all the customers with product purchase information. It also includes placing a new order, most recent orders, recent service requests and most purchased products under the customer record. Customers come from a variety of industries, including transportation, food services, electronic goods, and so on.
Reports: This produces a graphical representation of our actions. It shows a representation of the list of service requests received, products purchased, and customers from whom the products were purchased.
Tasks report: Users can track and analyze the status of service requests at various stages, from request created to closed.

User start page: Users will be able to access pages that system administrators have designated as their start page.

Site Development

The Appian website enables the user to create their own site from the scratch. From developing and designing the application to granting access to users.
Application: Creating a new application functions as a folder, allows the user to keep all the development objects pertinent to our application. Using objects, groups and sub groups can be created.
Data store: The application side representation of a database holding the mapping between database tables, views, and application side datatypes.
Data type: The application side representation of a structure of data with same fields as database tables. As well as an entity in the data store.
Tables in the database and application can be created by defining datastores and datatypes. Constants are also created that points to the data store entity to be able to write to specific database table.
Interface: Creating a form with the fields that will be displayed to the users. The Appian interface can be tested directly in the editor without running the process. It has two modes- design and expression mode.
Design mode: This allows the developer to design the form according to their specifications in order to collect user information.
Expression mode: This displays the interface's code, which can be edited while designing. The code is written in the SAIL programming language.
Process model: To keep track of user form submission processes stored in the database, monitor the process and correct any errors in the flow.

Process

Created an application for online goods sales, where users can buy products from customers.
Objects were created and organized into groups and subgroups. Then I created a data store object to create a database table and datatypes to create fields, which I then linked to the datastore as an entity. This will create the table in the database.
With the groups and tables created, we can now design the Interface form. The form is customized and to display fields, we can call in rule input as a function which consists of the fields created.
To keep track of the process flow, a process model is created that connects all of the pieces that have been created up to this point. The flow is triggered when the user submits the form, and if successful, it is saved in the database. However, if an error occurs, the administrator is notified. Every interface is built with the process model that connects it to the database.
Developed a customized site for easy user access by adding pages, which will be displayed in the navigation bar.
These pages provide information about the users, products purchased from customers, a list of customers and their products, a service request for any product complaint, and tracking of the requests made by the users.

The application is restricted to the administrators only and when the application is published the application security permissions should be adjusted for user access

RESULT

Using the 'Appian Designer' tool, I was successfully able to create a site for the online goods sales as a digital prototype . A practical understanding of how to design a good user experience led to new ways of thinking about how to create a different platform for users' convenience.

Back

APPIAN WEBSITE

(Appian workshop, Accenture)

OBJECTIVE

Role

Timeframe

Design

In the application, built my site for online goods sales by creating pages to organize the content.

The pages were customized to show action type, report and record type of customers.

Appian console: Configures administrative settings from branding to navigation bar according to developer specifications, adds community plugins, and creates users.

Tempo: Main area where users will have access to , as well as defines other customized user access sites. It includes information such as News, Tasks, Records, Reports, and Actions of the users.

Actions- To initiate a process

Records- For key business objects with quick access to details and related actions

Reports- To analyze business performances

Task reports- For users to track complete tasks

List of pages in the navigation bar

New customer service requests: This is an action page that generates a new service request for the user who requires assistance with the orders placed.

Service requests: This is an action type page that manages all the service requests placed by the user.

Reports: This produces a graphical representation of our actions. It shows a representation of the list of service requests received, products purchased, and customers from whom the products were purchased.

Tasks report: Users can track and analyze the status of service requests at various stages, from request created to closed.

User start page: Users will be able to access pages that system administrators have designated as their start page.

Site Development

The Appian website enables the user to create their own site from the scratch. From developing and designing the application to granting access to users.

Application: Creating a new application functions as a folder, allows the user to keep all the development objects pertinent to our application. Using objects, groups and sub groups can be created.

Data store: The application side representation of a database holding the mapping between database tables, views, and application side datatypes.

Data type: The application side representation of a structure of data with same fields as database tables. As well as an entity in the data store.

Tables in the database and application can be created by defining datastores and datatypes. Constants are also created that points to the data store entity to be able to write to specific database table.

Interface: Creating a form with the fields that will be displayed to the users. The Appian interface can be tested directly in the editor without running the process. It has two modes- design and expression mode.

Design mode: This allows the developer to design the form according to their specifications in order to collect user information.

Expression mode: This displays the interface's code, which can be edited while designing. The code is written in the SAIL programming language.

Process model: To keep track of user form submission processes stored in the database, monitor the process and correct any errors in the flow.

Process

Created an application for online goods sales, where users can buy products from customers.

Objects were created and organized into groups and subgroups. Then I created a data store object to create a database table and datatypes to create fields, which I then linked to the datastore as an entity. This will create the table in the database.

With the groups and tables created, we can now design the Interface form. The form is customized and to display fields, we can call in rule input as a function which consists of the fields created.

Developed a customized site for easy user access by adding pages, which will be displayed in the navigation bar.

These pages provide information about the users, products purchased from customers, a list of customers and their products, a service request for any product complaint, and tracking of the requests made by the users.

The application is restricted to the administrators only and when the application is published the application security permissions should be adjusted for user access

RESULT

Using the 'Appian Designer' tool, I was successfully able to create a site for the online goods sales as a digital prototype . A practical understanding of how to design a good user experience led to new ways of thinking about how to create a different platform for users' convenience.