ServicePlus

Service Definer Guide

(SDG V5.2)

Jun, 2018
Table of Contents
1. General Details.......................................................................................................... 4
2. Coverage ................................................................................................................... 5
3. Service Definer’s Address ........................................................................................ 5
4. Beneficiary Profile .................................................................................................... 6
5. Submission Mode...................................................................................................... 7
6. Service charge ........................................................................................................... 8
7. Payment Configuration Details ................................................................................. 9
8. Additional Configuration ........................................................................................ 11
9. Application Form .................................................................................................... 12
10. Process Flow ........................................................................................................... 13
11. Deliverable (Documents) ........................................................................................ 14
12. Privileges & actions of officials .............................................................................. 15
13. MVEL Functions .................................................................................................... 17
14. Notification Designer .............................................................................................. 18
ANNEXURE..................................................................................................................... 19
I. Forms to be submitted by Applicant........................................................................... 19
II. Please provide sample and details of the following for each form that the applicant
needs to submit at different point of time: ........................................................................ 19
III. Please provide any reference service(s) document. ................................................ 19
IV. Integration with Government Undertaken 3rd Party System(s) –............................ 19
V. Process Flow  ...................................................................................................... 19
VI. Please give details of the business rule applicable on Service Charge with sample
scenario(s). ........................................................................................................................ 21
VII. Please provide the details of Payment Gateway(s) as below: ............................. 21
EXAMPLES/DESCRIPTIONS ........................................................................................ 21
A. Category of Service(s) ............................................................................................ 21
B. Types of Service ..................................................................................................... 21
C. Standard Field ......................................................................................................... 22
D. Special Field............................................................................................................ 22
E. Validations & Function ........................................................................................... 22
F. WebService Registration ........................................................................................ 22
G. Handling of Process Flow with the help of Gateways ............................................ 22
Special Requirement ......................................................................................................... 24
1) Applicant eSign (based on Aadhaar verification) ................................................... 24
Note: All the fields are mandatory to be updated

1. General Details

1.1 Please provide the name of the service along with a brief description about the service and a
short abbreviation. You can provide these details in multiple languages.

Service Name Service Description Service Name Abbreviation

(Provide the name, description and Abbreviation of the service here. The abbreviation should be 5
characters in length. The abbreviation will be used as a prefix in the application reference number.)

1.1 Is your service a Primary Service, Derived Service or a Legacy Service? (A Service can be
configured in as a Primary, Derived or Legacy. Refer Annexure for description. )

1.2 To which Standard Service Group does your service belong?

(Standard Service Groups are the classifications of services defined in eTaal. E.g. ‘Birth and Death
Certificate’ group covers ‘Birth Certificate’ and ‘Death Certificate’ services. List of Standard Service
Groups is given in Annexure –I)

1.3 From where can your service be applied? (From State, India or Outside India)
(A service may accept applications from applicants residing within the State, within India or even from
Outside India.)

1.4 Is the service available for registered applicants only? – (Yes or No)
(If your service requires that only registered applicants can apply, then say “Yes”. In this case, when the
applicant clicks on the Apply button, it will ask the user to register/login (if he is not already
registered/logged in))

1.5 Please specify URL from where more information about the service is available. (In case you want
to provide any description/summary for the service selected, URL can be captured here. For e.g.: In
case if it Departmental/ State specific service)

1.6 Under which category does your service fall? – (G2B, G2C, G2E, G2G)

1.7 What is the type of your service? – (Consumer Utility, Developmental, Regulatory or Statutory)
(Services can be of four types: Consumer Utility, Developmental, Regulatory or Statutory. Refer
Annexure for description)

1.8 Is your service covered under the State Service Delivery Act?
(There are certain States (e.g.: Tripura) enacted the State Service Delivery Act. As per the Act, if the
service is not as per the defined service level or in case the applicant is not satisfied, then he/she can lodge
a grievance which will be redressed through a proper workflow. A state has to deliver its service(s) as per
the Service Level defined under this Act.)
1.9 What is the Service Level of your service?
(Service level is a duration within which the officials shall deliver the applied service to the respective
applicant. You can mention the Service Level and its Unit in (Day/Week).)

1.10 Do you want the applications to be processed in FIFO mode? (Yes or No)
(First In First Out (FIFO) mode ensures that the applications that have been received first will be
processed first; if FIFO mode is not adopted, then the applications can be processed in any order)

2. Coverage
(Coverage defines the set of Service Unit(s) (Department officials) who are responsible to deliver the
applied service(s). A Service Unit can be an urban local government (such as municipality), a rural local
government (such as a gram panchayat) or the field office of a Line Department such as Circle Office.
These detail(s) are being picked from LGD Data base only.)

2.1 What type of Area(s) of the State the service is defined for?
(The service getting defined may be specific to area(s) (e.g.: Rural, Urban etc...) for which the Department
Official (DO) shall be assigned)

2.2 Who are responsible for providing the service in the selected area?
(All the department(s) & its hierarchy responsible for delivering the service is selected under “Service
Provided By”. These DOs will have tasks in their inbox for action(s) like reject/ approve/ deliver etc.)

3. Service Definer’s Address

3.1 Please provide contact details of the Service Definer who can be contacted by an
applicant for any query regarding the service?
1. Contact Person Name -
2. Address -
3. Postal Code -
4. District -
5. Email-Id -
6. Contact Number -

(Service Definer is the role played by the official of the Department owning the service. Service Definer’s
contact details can be used for future reference related to a service.)
4. Beneficiary Profile

4.1 What is the type of beneficiary who will receive the benefit - (Individual, Family, Group or
Institution)

4.2 If beneficiary is a Group, what is the min. and max. size of the group?

4.3 Please specify the parameters, if any, and their allowed values which define the profile of the
beneficiary

Profile Parameter Allowed Values

(Profile parameters narrow down the beneficiary group. For e.g., a service may be exclusively for SC and
ST. In this case, Caste would be the profile parameter and SC and ST would be the allowed values which
this parameter can take. The beneficiary can be applicable to additional categories as well, i.e. definer can
add as many beneficiary criteria as required.)
 5. Submission Mode

5.1 What are the different modes through which the applicant can apply for the service?
(Online, Kiosk, By Post and In Person, are the available options and more than one option can be selected.
For Legacy services, the only mode of submission available shall be Data Entry Operator)

5.2 Do you want Acknowledgement slip to be generated without uploading the required documents
(Yes or No);

(When the applicant is submitting the application, there are possibilities due to poor
connectivity or no information on pre-requisites the applicant is not able to scan and upload
the required enclosures/documents. ServicePlus facilitates to provide acknowledgement slip
to the applicant without uploading the required enclosures.)

5.3 Please specify the address where the application has to be submitted in “In Person” or “Through
Post” mode. (Centrally Submitted or Service Unit Wise)
 Address-
 Postal Code-
 District
(In centrally Submitted mode, there need to an address where the application has to be submitted. If it is
service unit wise, then the address of each service unit where the service is available shall be captured at
the time service activation on DO’s task(s).)

5.4 Are there any enclosures to be uploaded by the applicant while applying for a service? - (Yes or
No)
a. If enclosures are mandatory to be provided by the applicant, what would be the type of
enclosures? Please provide the details in the following format:

Enclosure
Type of Max
Mandatory Allowed File Type Documents Recommended
Enclosure Size
(Yes/No)
Yes Residential <5 MB JPG,ZIP,DWG,JPEG,PNG,PD Trade License,
Proof F,KML,KMZ,GIF AADHAAR Card,
Income Tax Payment Receipts

5.5 Is there any additional document required with the application? (Yes or No)

5.6 Is the applicant required to fill in any document in a pre-defined format and attach with the
application? If yes, please provide the below details:
a) Title – “Name of the document”
b) Browse to Upload: (Supported file format: pdf, doc, docx - upto 1MB)
c) Is it Mandatory?- (Yes or No)
6. Service charge
(There may or may not be any service charge associated with a service. If there is a service charge related
payment/refund to be made by/to the applicant at any stage of the entire application processing life cycle,
the respective details are captured here. Also, payment may be made multiple times through different
payment modes. Depending upon number of charge/refund possibilities, the following details need to be
captured.)

6.1 Weather it will be used at the time of application submission?

6.2 Is refund allowed for this Service?

6.3 Will the charge be defined centrally or service unit wise?

6.4 If the charge is service-unit wise, then is there any default charge which is applicable for all
service units? (Yes/No)

6.5 If yes, how much is the default charge?

6.6 Is the same service charge applicable to all applicants or it is based on the profile of the
beneficiary?

6.7 If the charge is based on input provided by the applicant, please give details of the business rule.

6.8 What is the mode of payment through which the applicant can pay the charge?
(Cash |Cheque | DD | Bill Desk | SBI ePay | CSC e-wallet | Respective State(s) Treasury etc…)
7. Payment Configuration Details
(In case of Online payment mode, there are certain details required for ensuring security (Checksum,
Security ID) as well as part unique identification based on State/department (Merchant ID) and other
details depending on business rules to charge an applicant. These details are specific to an individual
payment gateway among which Merchant Id and checksum are 2 mandatory fields.)

7.1 Will the payment mode details be provided ‘Centrally’ or ‘Service Unit Wise’?
(In case the Payment Gateways are to be used ‘Service Unit Wise’, ‘Designated officer’ has to provide the
above details for each Service Unit before activating the service.)

7.1.1 Bill Desk

 Merchant ID-
 Security ID-
 Checksum key-

7.1.2 CSC e-Wallet

 Merchant ID-
 Checksum Key-
 MtrxID Pattern-
 SMER Normal-
 SMER Additional-

7.1.3 SBI e-Pay

 Merchant ID-
 Checksum Key-

7.1.4 e-Treasury (Applicable only to Kerala)

 Department code-
 Payment type-
 Treasury code-
 Office code-
 Period-
 Major Head-
 Head of Account (HOA1)-
 HOA2-
 HOA3-
 HOA4-
 Date From-
 Date To-
 Tax ID-
 PAN-
 Party name-
 Address 1-
  Address 2-
 Address 3-
 PIN No.-
 Mobile No.-
 Service Dept. code-
 Sub system-

7.1.5 eGras (Haryana/Kerala)

 DTO –
 STO –
 DDO –
 Dept. Code –
 Scheme Name –
 CSC Amount –
 City Name –
 Bank Code –
8. Additional Configuration
(This section allows you to capture details related to integrated Government undertaken third party
system(s) and require to be captured by the applicant.)
Following are pre-integrated 3rd Party System(s) and respective details which need to be captured as
part of Application processing:

8.1 Rapid Assessment System (RAS)

 State ID (mandatory) -
 Department ID (mandatory) -
 Service ID (mandatory) -
 Contact Details to be taken from (mandatory) -
 Trigger Point (mandatory) -

8.2 DigiLocker Issuer Model

 Issuer ID (mandatory) -
 Doc ID (mandatory) -
 API Key (mandatory) -

8.3 Aadhaar Integration

 AUA Code (mandatory) -
 Sub AUA Code (mandatory) -
 License Key (mandatory) -

8.4 eSign Integration

 ASP ID(mandatory) -
9. Application Form
(A section where you can define: An Application Form – For Requesting a Service & An Action Form –
For Task Officials to capture details/documents while performing actions)

9.1 What will be the name of Template to be defined?

9.2 Is this Application Form / Action Form?

9.3 Do you want to add Form Header?

9.4 Do you want to add Form Footer?

9.5 Do you want to add Declaration?

9.6 Do you want to have 3D Display effect in Form?

9.7 Do you want to add Help message?

(In case Help message is required, either capture URL of the help document or upload the help document
you want to be displayed at the time of capturing Form (online))
9.7.1 Standard Fields
Any field which you need specific to the service can be defined with the help of drag & drop field Type and
to which you can define data type length etc. Refer Annexure for example

9.7.2 Special Fields

All the generic fields are available with drag and drop feature functionality. On right click of the dropped
field; you can select specific features to it. Refer Annexure for example
9.7.3 Beneficiary Fields
(Applicable in case beneficiary details are being filled and the fields are generated on the basis on criteria
selected in Beneficiary tab (Section 4).)

9.8 Validation & Function (via Service specific javascript functions)

There are scenarios where you need to add may be just 1 more fields/value to the existing
Application form or need to link 2 fields available on the form. This feature functionality of
binding javascript can be applied to Application form at any stage of defining to its launched
status as well. Refer Annexure for Steps to be Followed.

9.9 Webservice mapping (via Webservice Registration by DA)

It is helpful in case you need data transactions with 3rd party system. There are basically 2 types
of Calls “Calling” & “Callback” and depending upon the flow of data you can map the registered
web-services at Form level via “Validation & Function” and can create web-service Task(s) and
map the web-service. Refer Annexure Webservice Registration
10. Process Flow

10.1 Does the service involve Auto Approval Process?- (Yes or No)
(Sometimes, the service (ex: Mark-sheet) may not have any workflow. In such cases, the applicant’s request
is usually approved or rejected based on some verification/validation rule.)

10.2 If yes, please provide the details of the business rule based on which the service request will be
approved or rejected.

10.3 In case, there is a proper workflow involved in processing the application, please provide the
details of the task(s) involved in the processing of the application:
(Tasks can be of four types: Official, Applicant, Web Service and Timer. Application Submission is always
the first task which is performed by the applicant {online applicant, data entry operator or kiosk}. Official
task is a task which is carried out by officials belonging to Government Departments who are involved in
processing the application. Applicant task is a task which is to be performed by the applicant. A web
service task is a task which is performed by a web service exposed by an external application.)

10.4 Please define the process flow for the service by providing the mapping between the tasks:
(In order to define the process flow, it is required to indicate the order in which the tasks will be executed.
Start with Application Submission task (which is always the first task) and name the tasks which succeed
each task. If the application moves to multiple tasks from a task (the flow is diverging), then specify all the
tasks to which it is going in the “To Task” column. If the application is received from multiple tasks (the
flow is converging), then specify all the tasks from which it is converging in the “From Task column). In
case there is a conditional divergence or convergence, then specify the conditions in the Conditions
column. Refer Annexure for Example)

10.5 Which field in the application form determines to which office the application has to be
submitted?
Application form field Service Unit type

(An application is usually routed to the appropriate office (service unit) based on some information
provided by the applicant. For e.g., if the application given the name of the village in his residential
address, then the village will determine to which Gram Panchayat or Circle Office the application will be
sent)

10.6 Please provide the details of the ‘Designated Officer’ who will activate the service at different
locations:
Service Unit Type Department/Local Body Designation
 (A Designated Officer is an official who will be responsible for activating a service in a service unit. Here,
provide the name of the line department or local government (panchayat, municipality etc.) and the
designation which would be assigned this responsibility.)

10.7 Process Flow Gateways (Forking & Merging of Tasks by Divergent & Convergent Gateway respectively)
Many a times in a process flow we have TASK with 1 or more conditions associated, these conditions
determine the flow of task to/from 1 or more task(s). Such scenarios are addressed by extending the task
mapping with the help of gateways.
Forking & Merging: Whenever we need forking on specific conditions we must imply Divergent Gateways
and in case of merging we address the same with Convergent gateways.

11. Deliverable (Documents)

(One or more documents may be delivered to the applicant at different stages of the processing. These
could be Output, Rejection, Intermediate and Acknowledgement).

11.1 Please provide the details of the documents/certificates to be given to the citizen at different
stages of application processing and the details associated with it:
 Name of the document
 Name of the task at which it is generated
 Type of document (Output, Rejection, Intermediate, Acknowledgement)
 Is 2D Bar Code required? (Y/N)
 Mode of delivery of the document (Online, In-Person, By Post):
 Whether the document is to be digitally signed
 Provide a copy of the document
12. Privileges & actions of officials
Please provide details of privileges, responsibilities that should be assigned to officials, forms to be filled in
and actions that they have to take to complete a task. Give the following details for each official task:

12.1 Name of the task

12.2 The Office and designation of the official who will be carrying out the task
(If the task has to be performed by an official, then you need to specify the office and the designation of the
official who will do the task. In turn, Department Admin (DA) will assign Official(s) to the Designations
responsible to complete the task(s) )

12.3 Details of the information, if any, which the official needs to provide while processing the task:
(While doing the task, sometimes, the official may need to submit some information. If there is any such
information to be provided, you may provide the details of the information as requested along with the
format of the form for capturing the information (if such a form is available). Also, please specify if any
fields included in this form to be linked with some other form attributes.

12.4 If any format is available in which this information is to be captured, pl. provide the details as
follows:
 Name of the form
 Format/Layout of the form (pl. provide a printed/pdf/doc form)
 Business rules/validations to be applied in the form

12.5 Can the official reject any enclosure/document submitted by the applicant (Yes/No)?
(Sometimes the enclosures provided by the applicant may not very clear or the official may have some
doubt with respect to the document. In such cases, the official may be required to reject the enclosures
provided by the applicant and ask for fresh copies of the same enclosures to be uploaded by the applicant)

12.6 Can the official ask for additional enclosures from the applicant (Yes/No)?

12.7 If yes, please specify the name and type of the enclosure(s) which the official can ask for a new
enclosure?
(Sometimes the official may need the privilege to ask the applicant for additional enclosures as supporting
documentation. If this is the appropriate task, then privilege may be given to the official for asking for
additional documents.)

12.8 Is the official required to take payment from the applicant in the task (Yes/No)?

12.9 If yes, in what mode will the payment be accepted?

12.10 Is the official responsible for generating any document (Yes/No)?

(If the official is required to generate an intermediate document in this task, then the same may be
mentioned here)
12.11 If Yes, please specify the name(s) of the documents to be generated:

12.12 Is the official required to upload any document (Yes/No)?

12.13 If Yes, please specify the name(s) of the documents that the official is required to upload:

12.14 Please provide the following information about the documents that the official will be dealing
with in this document:

Document to be Documents to be uploaded Is it mandatory to The task(s) to which

generated and merged with the digitally sign the these documents have
generated document document? to be sent?

12.15 If there are multiple users in the next task(s), does the official have the privilege to select the
user(s) to which the application should be sent?

12.16 In case there are multiple tasks after the current task, does the official have the privilege to select
the tasks where the application should go (Yes/No)?

12.17 Should the official be allowed to take decisions on multiple applications in one go (bilk
application processing) (Yes/No)?

12.18 What action can the official take to complete the task? (forward /recommend /non-recommend
/deliver /reject /partially deliver and partially reject)

12.19 Can the official be allowed to Callback a forwarded application?

 13. MVEL Functions
Theses business rules are MVEL driven; which are generally applied post Application/Action form
submission and also, eligible to handle exceptional scenarios. For this MVEL Function needs to defined
and captured as per required scenario. This MVEL function thereafter is available for selection in the
MVEL Function Tab.

13.1 Where do you want the MVEL Function to be triggered?

13.2 Which Function (MVEL defined logics) you want to be invoked at the selected trigger point?
If yes, please provide the following details:

Business Rule (in words) Trigger point at which this rule should be executed (select any one)

After Form Submission, Before Loading Enclosures, Before making payment,

Business rule 1 After making Payment, Before executing a task, After Executing a task, On a
Gateway

After Form Submission, Before Loading Enclosures, Before making payment,

Business Rule 2 After making Payment, Before executing a task, After Executing a task, On a
Gateway
14. Notification Designer

14.1 Do you want to send any notification to the applicant/work flow player during application
processing? (Yes or No)

14.2 Please provide the following details for each SMS and email notification:

14.3 In case of SMS notification, please provide the following details for sending SMS:
 To whom SMS will be sent?
 What would be the trigger point? (Application form submission, Application pull, Callback,
Reminder time, Task completion and Task mapping)
 What will be the content of the SMS?

14.4 In case of Email notification, please provide the following details for sending the mail:
 Who will send the mail?
 To whom mail will be sent?
 Anyone to be marked in ‘CC’?
 What would be the trigger point? (Application form submission, Application pull,
Callback, Reminder time, Task completion and Task mapping)

 What will be the subject of the email?

 What will be the content (body) of the email?
ANNEXURE

I. Forms to be submitted by Applicant

Please provide a Sample Application Form for each of the Service(s).

II. Please provide sample and details of the following for each form that the
applicant needs to submit at different point of time:
 Name of the form
 The step at which the applicant needs to submit the form
 Format/Layout of the form
 Business Rules/Validations to be applied in the form

III. Please provide any reference service(s) document.

IV. Integration with Government Undertaken 3rd Party System(s) –

 Applicant Impacted 3rd Party System: -

o To be Integrated 3rd Party System(s) –
o Business Rule(s) applicable on Charge with sample scenario(s) –
o Copy of Integration document –

 Non-Applicant Impacted 3rd Party System: -

o Currently Integrated 3rd Party System(s) –
 eTaal:
o eTaal Id with appropriate Service Name
 CAS:
o To be Integrated 3rd Party System(s) –
o Business Rule(s) applicable on Charge with sample scenario(s) –
o Copy of Integration document –

V. Process Flow 

 Please provide any reference to Application Process Flow for each of the
Service(s).
 Process Flow  Please Provide Task details as below: (Red one will generate
notification)
Task(T) Task Name Performing Allowed
Designation  Actions: (only one at a time
 Document(s): Enclosure/Annexure/Certificates
 Forward to Task: Conditional Business Rules

Application submission  Applicant  Application submitted by an applicant with

-
 DEO attached Enclosures
 Kiosk  T1 – Verification Task with Acknowledgement
slip
Application Verification  SO  Forward to Task 2 with SO Official Form*
T1
 CA  Documents: Action Form
 Return to Applicant for Enclosures with an
alert notification
Verification by  CA  Forward to Task 3 with CA Official Form*
T2
Competent Authority  Documents:
 Reject Service with Non Candidature Letter*
rejection certificate to applicant
Appointment Letter  AS  Forward to Task 4
T3
forwarding by AS or by JS  JS & LA  Forward to Task 5
and LA or by CA  CA
Final approval action by  AS  Forward to task 5
T4
AS or by JS and LA or by  JS & LA  Deliver Service with Certificate of Practice*
CA  CA output certificate to applicant
Approval by Law minister  Min  Deliver Service with Certificate with DSC/eSign.
T5
 DSC output certificate to applicant
Dispatch  Clerk  Dispatch of letters
-

 List of applicable officials:

 Department Admin (DA) –
 Department Designation(s) and associated Official(s) –

Mobile
Email ID
S. No. Department Admin Designation Officials Number
(Mandatory)
(Optional)
1 SCO1
2 SC1 SCO2
3 SCO3
4 DA1 SCO4
5 SCO5
SC2
6 SCO6
VI. Please give details of the business rule applicable on Service Charge
with sample scenario(s).

VII. Please provide the details of Payment Gateway(s) as below:

 Planned integration of Payment GW(s) (If Any) –
o Merchant ID –
o Checksum Key –
o Security ID –

 Business Rule(s) applicable on Charge with sample scenario(s) –

 Copy of Integration document with the payment Gateway(s) –

EXAMPLES/DESCRIPTIONS

A. Category of Service(s)
Definition
 Primary Service – A Primary Service is the main service for which the applicant originally
applies. For e.g., Issuance of Passport is a Primary Service.
 Derived Service - Derived Services are those services which are based on the Primary service.
They can only be given if the applicant has already availed the Primary Service. For e.g.,
Change of address in Passport would be a derived service of “Issuance of Passport” service.
 Legacy Service- Legacy services are those services which are used to digitize old data. A legacy
service may be linked to a Primary or Derived Service. This service can be applied through Data
entry operator only. It is by default set as G2G service. Hence, Legacy services are not visible to
general public and kiosk operators.
 If your service is ‘Derived’ then you can mention the Primary Service and if your service is
‘Legacy’ then you can mention the Primary and derived Service. In case if legacy service is
selected, you just need to provide the service category and type of service.
o Single Window- Single window services are also known as umbrella service. Such services
require NOC(s) from various respective departments and SP provides Ease of Doing Business
(EODB) for such services via providing Single window service Option. For e.g.: Setting up a
factory.)

B. Types of Service
Definition
 Consumer Utility Service- Service which covers need and want of consumer(s) fall in this type,
e.g.: Telephone (MTNL) bill payment, electricity bill payment etc.
 Developmental- Services which Supports development of People and the Society, e.g.: NREGS,
IAY, Old age Pension etc.
  Regulatory- Service that can be restricted according to rules or principles, e.g.: trade license,
permit for construction of a building etc.
 Statutory- Services which cannot be denied by the providing agency as denial of that service is
punishable under a statute, e.g.: Issuance of birth/death certificate)

C. Standard Field
Example: Service is only valid for Late Defense Officers only, following are simple step:
 drop-down field will be dropped on the form
 Click on the drop-down 
o Click on “Field Property”, edit the
 field name = “Salutation”
 Parent = “Defense” *//shall be in edit mode when an option of field is selected as
“Defense” *//
 Is this a mandatory field? = Check
o Click on “Add Choices”, edit
 Option 1 = “Lt.”
 Option 2 = “Late”
 Option 3= “Deputation”
 Option 4 = “…”
o Help = any help message

D. Special Field
Examples:
 Name field will always have alphabets in text area.
 Form is applicable only for citizen above 18 years- Date picker need to have years before year 2000 this
month today’s date.

E. Validations & Function

Following needs to be done: -
 Service specific javascript functions  write & save Java script function
 Validation & Function tab  Modify the saved application/action form click on “validation &
function” tab  map the event to the form field with the help of Java script saved in “Service
specific javascript functions” )

F. WebService Registration
The Service plus capture the Webservice details require for registration call types calling or
call back. Webservice registration can get or post data depending upon the request or
response type which involve parsing of parameter from one data type to other.
Please refer user manual specific to WebService Registration.

G. Handling of Process Flow with the help of Gateways

S. Gateways Name & Mapping Scenarios/E.g. Description

No. Official Task (OFC Task)
 Applicant task (App Task)

1. 1. OFC Task to either App Task or Forking scenarios: forward to only 1

OFC Task task(1:1out of N)
2. Either to OFC Task1 or OFC
SD  Action Form: Action & Task
Task2
attributes must be dropped. Also,
check the check boxes of the task(s)
to which Task needs to forwarded

2. 1. either to App Task or OFC Task1 Forking scenarios: forward to 1 or

2. to App Task as well as OFC Task more at a time (1:1or >1)
3. either to OFC Task1 or OFC
Generally handled through MVEL
Task2
i.e.
4. to OFC Task1 and OFC Task 2
 what condition shall be applied
 which task to be associated
 Whom shall it be assigned

3. OFC Task to more than 1 OFC Forking Scenario: forward to all at

Tasks at a time. a time (1:N)

Merging Scenario: forward from

4. 1. Either from App Task or OFC
only 1 task
Task
(1out of N :1)
2. Either from OFC task1 or OFC
Task2

Merging Scenario: forward from

5. 1. either from App Task or OFC
Task1
more than 1 task (1or>1:1)
2. from App Task as well as OFC Handled through MVEL i.e.
Task1  what condition shall be applied
3. either from OFC Task1 or OFC  which task to be associated
Task2
 Whom shall it be assigned
4. from OFC Task1 and OFC task2
Merging Scenario: forward from
6. OFC Task from more than 1 OFC
Tasks at the same time.
all tasks at the same time (N:1)
Unless and until response from all
task are received it will not be
forwarded to next task.
Special Requirement

1) Applicant eSign (based on Aadhaar verification)

a) Prerequisite:
i) eSign Configuration based on
ii) ASP ID

b) Aadhaar Configuration based on :

i) AUA
ii) SUBAUA
iii) LK

b) Impacted Placeholders in ServicePlus (SP) :

c) Service Definer (SD):
i) Form Designer :
(1) Check in case Applicant’s e-Sign is desired on the Application/document(s). Also, check the
check-boxes of the options (Application Form & Annexure), wherever applicant’s e-Sign is
desired.
(2) Drag & drop Aadhaar field & check in case it will be used for eSign.
(3) Ensure only 1 Aadhaar field is checked for e-Sign, to avoid jeopardize the e-Office to fetch e-
Sign.

ii) Additional Configuration:

(1) eSign Configuration require following:
(a) ASPID
(2) Aadhaar Configuration require following:
(a) AUA
 (b) SUBAUA
(c) LK
iii) Service Status Change(Freeze) : (Condition & Validation; in case of multiple i(2&3) & ii )

d) Citizen Login:
i) View All Services  View Service List  Apply eSign configured Service:
(1) Enter valid Aadhaar Field; check the Aadhaar Consent wrt e-Sign.
(2) When the applicant clicks “eSign & Submit” which is available any time before “Make
Payment”; the applicant’s e-Signed document is stored in SP. To view the eSign Application
navigate to Citizen  View My Application  Track My Application

e) Work Flow Player(View of Applicant’s e-Signed Application Form):

i) Message Box  Inbox  Pull  Action  View Processing History  Click on Application
Submission (completion Status)

25