Extensible Development

Kit (EDK)2.0
Objectives

Introduction to EDK and its Features

Business Process Modeling

Specify User Interface Layout

Generate Deliverables

Base Screen Extension

EDK Screens to Launch Reports

Requirement Script

Code Generation Using EDK Stub Generator

Deployment
What is EDK

Extensible Development Kit is a tool used for developing

 Business Process

 Components

 Activity

 User Interface.

To extend the screen functionality of already existing Base screen

What is EDK

This tool can be used by

 Customer

 Users at customers site

 Implementation team.

 Pre-Sales team
Features of EDK

Develop user defined Components

Extend the functionality of Base Screens

Transfer data

 From one Interface to another User Interface

 From UI to Base Screens

 From Base Screens to User Interface.

Design Reports for the User Interface.

Model Driven Application Development

Uses a model based approach to capture the specification

corresponding to life cycle phases

Information stored is captured in the Model Database.

Databases Used

EDK Model Database – Development time

Application Database – Application Component information

Deployment Database – Context and Security Information

Business Process

A Business Process is modeled as a set of Business functions

It could be a specific process followed in a particular industry.

 Example

HRM

Purchase

Finance
Process Driven

Human Resources
Management

Recruitment Payroll

Leave Management Training

Appraisal
Component

The technical implementation of a business function is a

component

 Examples

Leave Management

Leave Master Setup

Leave Maintenance

Leave Encashment
Activity

A basic unit of work within an organisation

The work of the component is delegated to small units

called activity.

 Activities are user entry points into the system

 Example

Leave Maintenance(Component)

Leave Application

Leave Authorization
User Interface

An activity is implemented as one or more User Interfaces

The flow across User Interfaces establishes traversal and

Information Assistance.

Each User interface is provided with the unique UI name,UI type

and a description, which is used as the screen title.
Workflow

Business Process

Component

Activity

User Interface(UI)
Actions (Tasks)

Actions are steps performed by a user on a User Interface to

complete the activity.

User Action
Action Patterns

Task-Action When is this generated

pattern
One per User Interface to populate all the
combo controls available
Initialize
A Fetch task is generated per UI for all the
combo controls available and for all the other
Fetch Controls

A UI task for every UI combo type of control

with “On Select” event support and edit
UI control with “On Enter” event support
Action Patterns

Task-Action When is this generated

pattern

For each button Control, a Trans task is

generated which can subsequently be mapped
Trans to the respective sections on the screen

One for every Link type of control and data

hyperlink control
Link

A help task for every help control

Help
Business Term

Business Term (BT) and BT Synonym

The Business Terms are identified from the Business document

structures or various Concepts or the problem domain under
consideration

A Business Term may be referred to by various names or aliases

(BT Synonyms)for higher relevance to an activity

The aliases will be used for Visual representation of Business

Terms (BT)
User Interface Layout Specification

Define UI Configuration

Define Pages (Optional)

Define Sections

Define Controls

Define Control Layout

Define Grid Contents (Optional)

Define Radio Buttons (Optional)

User Interface Layout Specification

Define Hidden Views (Optional)

Define Hidden Columns (Optional)

Define Static Enumerated Values (Optional)

Specify Data Transfer (Optional)

Specify Combo Re-load (Optional)

Generate Services
Generate Deliverables

The deliverables are

 HTML

 JavaScript

 XML

 .CS (For Report Definition).

 aspx (For Report Definition)

 .ttx (For Report Definition if service is yes)

Base Screen Extension

We can extend the functionality of already existing screen

through Base Screen.

Base Screens are generally taken from RVW 2.0 Model database,

To Get the Base Screen, we need to run the Requirement Script

exe

We need to provide the RVW 2.0 model database information in

order to get the component deployed.

The exe will generate the SQL Scripts.

Run the Scripts in Model Database.

EDK Screens to Launch Reports

Once the Service is generated,Report definition should be done.

Specify the Report name and specify the fields required to be
visible in the report.
Sample Report Screen
Stub Generator

Stub Generator exe will generate the following Scripts

 UDD
 Precision
 Stored Procedures
Steps in Deployment

Type the URL http://ServerName / rvw in IE

 Login as admin user

UserID AdminUser
Password admin

 Map the component to a particular OU

 Identify the RM Server for the Component

 Identify the Application Server for the Component

Steps in Deployment

Map the Component, and the required activity to a particular

role, OU

Create a Business Process Chain

Run the Config Generator exe.

THANK YOU