Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1
BSNL SOUTHERN TELECOM REGION
Location Manager
User Manual
Location Manager
User Manual
Note
This manual is intended as a guide to the users of Location Manager module of Transnet in
the groups such as User, Master Data Support, Data Test Coordination and Module
Administrators. Hence assuming that the reader is one among the above, this manual answers
most of the How to / Do I questions and explains procedures and techniques involved.
For the concept of Location Manager, definitions, design, code, implementation and
complete technical details (details not covered under this manual) please refer the Code
Reference Manual.
Document Status
Property
Tracking Period
Volume Revision
Formats
Size
Released
Authors
Editor
Editor
Value
From: 1/6/2014
1 3
.pdf [, .doc ]
67 Pages
To: 12/12/9999
Document Conventions
Convention
Description
Arial
Example usage
LM is the base module for all other
modules in Transnet
Table of Contents
INTRODUCTION
THE
CONCEPT
THE
DESI GN
ORGANISA TION
5.1 Hierarchy
3
THE
CONTROL
5.2 Designation
5.2.1 Basic Data
LOCATI ON
4.1 Circle
5.3 Officer
4.2 SSA
5.4 Privileges
4.3 SDCA
4.3.1 Create SDCA
REPORTS
Consolidated
4.4 Place
Details
Tree View
7 IMPLEMENTATION &
MAINTENANCE
SUMMARI ES
DEFINITIONS
I N T R O D U C T I O N
Introduction
What is Location Manager?
Location Manager (LM) is a module of Transnet software application which helps
in managing the network of locations in which assets of BSNL are available. To
provide the telecommunication facility, BSNL has set up a number of units of various
categories. The administration of this huge asset base is being done by dividing the
operational area into various circles according to the geography as well as
operational complexity. Out of these circles some are grouped under the territorial
circle categories which are the face of BSNL to its customers. They are purely
divided based on the service area as in national numbering plan and identify the same
boundary as the states in many of the cases. The other categories of circles enhance
the operational activities of the territorial circles by suitably supporting them on
technical and organizational front. The territorial circles are divided into SSA and
SDCA in line with LDCA and SDCA area as in national numbering plan.
LM helps in identifying all units of BSNL geographically as in the territorial
circle, SSA and SDCA boundaries. After identifying units geographically LM groups
them under various circles as per its administrative control. Then it connects the
officers to manage the assets in these units. It holds the data of organisation
structure of all the circles.
I N T R O D U C T I O N
GM / DGM, specific officers in administration and planning are only expected to have
the privileges in LM. All users will be able to view the data available in LM.
Chapter
1
THE CONCEPT
Applies to: ALL users.
Details about: circles, units, designations, locations, officers.
The assets in BSNL are distributed over various units. Units are
geographically located within the boundaries of territorial circle, SSA and SDCA.
To identify a unit in a SDCA, Place and buildings in a place are added as two
extra levels in between. Units have the latitude and longitude property to plot
on a map. Various types of units are identified by their category property.
The designation
can
be
of
controlling or
supporting
type.
The
designation name is a structured one made out of cadre and functional area. The
functional area defines the area of operation of a designation. It is the
concatenation of a synonym string and a location.
Officers personal data are collected in LM. The HR number of the officer is
the unique identification, which is the user id for logging into the Transnet.
All officers are created against a circle and cadre level is also collected upon
creation. Each officer should have a designation to work with all the modules in
Transnet. The designation is linked with the circle and cadre of the officer.
Transfer In module takes care of attachment of officers with the designations.
Designations which are attached with an officer will only be available for unit
attachment with the designation. After attaching with a designation, the officer
will have the presence in the units to which the designation is linked. Further,
the officer becomes a part of the hierarchy reporting structure of the circle.
Chapter
2
THE DESIGN
Applies to: ALL users.
Details about: design, navigation, actions, menu, filter.
All the pages in the LM module are following the following design.
have the actions particular to the selected data upon clicking on it. A
particular action can be clicked and it will lead to the action form.
The data in the data table will have the link to its corresponding pages
and users can seamlessly travel to any page in LM module without using the menu /
submenu navigation. Clicking on the data table head will sort the contents in an
order. The search field at the bottom of the data table searches the entire table
and shows the data searched for. The table can be navigated page wise by clicking
on the buttons at the at the bottom right side.
Chapter
3
THE CONTROL
Applies to: ALL users.
Details about: previleges.
The structure, design and codes as well as the data of Location Manager 3
are controlled by assigning privileges to authorized persons. The roles which is
also named as individual privileges are defined within the package and the
facility to group the roles is also provided. Users are privileged either when
directly assigned with individual privileges or grouped privileges or when
including in a user group of assigned privileges. (Refer section 5.4 for more
details of privileges.)
USER GROUP
PRVILEGE GROUP
Individual Privilege / Role
Individual Privilege / Role
User tagged to HR No
User tagged to
Designation
User
Chapter
4
LOCATION
Applies to: ALL users.
Details about: Circle, SSA, SDCA, Place, Units
Theis menu groups all the pages which are related with geographical
location.
4.1 Circle
Circles are categorised as territorial and non-territorial circles. The
non-territorial circles are further classified into various sub categories as per
the operations they conduct to enhance the productivity of territorial circles.
Non-territorial
circle
boundaries
span
more
than
one
territorial
boundaries.
Circle Type
Category
Territorial
Overseas
Non Territorial
Maintenance Region
Project Circle
Quality Assurance
Remarks
circle
Inspection Circle
Production Units
Training Institution
Data Network
NCES
Railway Electrical
Telecom Civil
Telecom Electrical
Telecom Stores
All circles will have organisation hierarchy. The hierarchy levels and their
default reporting structure can be defined in the hierarchy sub menu for a
circle. All units will be created against a circle. All designations will be
created against a circle. All officers will be created against a circle.
Circles will have a code and for territorial circles the length of the code
will be of 2 characters. When a circle is selected using the select filter the
boundary list and the subsequent boundaries are listed in a data table. In case
of territorial circles the data table headings will be SSA and SDCA. In case of
non-territorial circles it will be territorial circles and the SSA. By clicking
on the territorial circle / SSA / SDCA the page will be redirected to the
appropriate page showing further data of the clicked data.
The actions available in circle sub menu are,
Some foreign countries are created as overseas circles which are the
international gateway terminating locations.
The MTNL service area at Mumbai and New Delhi are also created as
territorial circles as a special case, so that the units of BSNL
available at these locations can be properly mapped.
To create a new circle the circle name, circle type and circle code
mandatory fields are to be filled in a form as shown below which will
be displayed upon clicking the create button on the page.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.1.2 Relocate SSA
The circles / SSAs which are not part of a circle can be selected
from the left side multiple select box and the target circle can be
selected from the right side select box.
By clicking the move button will make the changes in the boundary.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.1.3 Change Circle Name
The
privilege for this action is restricted and is available to the users of Policy
Maker User Group.
4.1.4 Update CDR Code
While creating the circles the CDR code was optional and using this
menu the CDR can be added or edited.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.2 SSA
This page will show the boundary details of a selected SSA. The selected
SSA name will be available in the Select SSA search filter box.
The circle in
which the SSA belongs will be shown next to it and on clicking that the page will
be redirected to the circle page. The data table will have the SDCA and Places in
the SDCA. Clicking on them will redirect to the appropriate pages. The search
filter will show the list of ssa as and when the 3 or more characters are being
typed and upon selecting them will redirect to the correct SSA page selected.
The actions available in SSA submenu are,
This action can be used if any SSA is found missing in any of the
territorial circle.
Multiple SSA of a circle can be added with the same page by using the
Add another SSA link, which will show another text box to enter the
next SSA name.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.2.2 Relocate SDCA
This action can be used to relocate the wrongly created SDCA in a SSA
to its correct SSA.
First select the wrongly created SDCA/s and then type the correct ssa
in the choose target SSA search filter.
Select the correct ssa from the dropdown and confirm. The SDCA/s will
be shifted then.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.2.3 Change SSA Name
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.3 SDCA
The page will show the places in the SDCA with the summary of buildings,
Units and Route Joints at the Places. The other details are similar to that of
SSA page.
The actions available in SDCA submenu are,
Each SDCA is uniquely identified with a short code within the circle.
This short code will be used as the prefix for the places in the
SDCA.
This will avoid the confusion that may arise for same places
available in different SSA.
For places with the same name as the SDCA, the short code will be
omitted.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.3.2 Change SDCA Code
Usually this action is used to add a short code for an SDCA, if not
given while creation in the earlier versions of LM.
Changing
an
existing
short
code
of
an
SDCA
will
make
the
corresponding changes in the Place names and unit names in that SDCA.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
4.4 Place
The page shows the Buildings and the functional units in the place. The
other details like Taluk, Pin code etc... Of a place can be viewed by clicking on
the Details link. Along with the functional units the category and administering
circle also will be shown. The buildings can be renamed or moved to another place
using the action buttons etched with the building name.
The actions available in Place sub menu are,
The privilege for this action is restricted and is available to the users of
Circle Administrator User Group.
4.4.2 Move Building
The privilege for this action is restricted and is available to the users
of Circle Administrator User Group.
4.4.3 Create Place
The selected SDCA short code will be prefixed with the place name
while creation.
More than one place can be created for an SDCA in the same page.
The privilege for this action is restricted and is available to the users
of Circle Administrator User Group.
4.4.4 Update Details
The privilege for this action is restricted and is available to the users of
Circle Administrator User Group.
Main Category
Transmission
Category
LDCC
Sub
Category
DTS
Renarks
LDCC Treansmission centres of
Maintenance Regions
(Normally they are the big stations
co-located with Level I/II Tax)
TXC
SDCC
DTS
Maintenance Regions
(They are available at the SDCA head
quarters)
TXC
TXC
OFC
Outdoor
OD
Mobile TXC
The privilege for this action is restricted and is available to the users of
Circle Administrator User Group.
the
supporting
controlling
designation
and
designation
the
will
existing
become
the
controlling
By
attaching
with
designation
the
unit
comes
under
the
This tab shows the list officers responsible for the maintenance of
the assets attached with the unit. The responsibility of an officer
in a functional unit is of two types,
Controlling / Adl. Charge : This officer will be the overall in
charge of the functional unit. In normal case it will be the
senior most officer working in the unit.
Supporting : All other officers working in the unit for supporting
the maintenance activities.
This tab shows the other names of the functional unit and can be
updated by any officer responsible with the functional unit.
After Place selection the already created buildings in the place will
be listed in a select box with last option as to Add Builsing.
If you choose to add building the new building name will be asked.
If the latitude and longitude of the unit is known that also can be
entered.
Use the Rewind button to go back and correct the data if required.
P1 stands for identifying the type of circle for which the functional
unit is going to be created. This value will be fetched when the
circle to which the functional unit is attached is selected. For
territorial circle the P1 value will be C.
Click the forward button to go to the next step where the unit name
framed with the values selected from this step will be shown for
confirmation.
In this step whatever selected through the first and second steps
will be givetepn for confirmation along with the framed functional
unit name.
Use the Rewind button to go back and correct the data if required.
The privilege for creation of functional unit is given to all the users,
whereas it will be effective upon approving by the users of circle administrators
group only.
4.6.7 Rename Functional Unit
Renaming a functional unit is just like the creation process without the
first step i.e. Selecting the geographical position. There are two steps in
renaming the functional unit,
Step 1 : Re-frame Functional Unit Name
You might have noticed that this page will help in changing the
category of the functional unit also.
The privilege for this action is restricted and is available to the users
of Circle Administrator User Group.
4.7 Customer
The OF cables may be terminated at customer premises for providing
bandwidth and BSNL may have transmission equipments installed at these premises.
These locations are grouped in the customer page according to the geographical
position.
This page shows the customer details SSA wise. The SSA can be selected
using the Select SSA filter and the customers created in the SSA will be listed
out SDCA wise in that SSA.
Each row of the customer in an SDCA will show the customer name attached
with the circle and the customer location name framed using the P1 through P5
part values. The customer location name will be used in all the modules of the
Transnet for identifying a customer at the location.
To make things more clear, let us take the example of State Bank of India
as the customer of BSNL. As circles are the business units of BSNL which are
collecting the revenue out of the bandwidth sale with customers, State Bank of
India has to be created as the customer of those circles wherever the bandwidth
is provided. This linking of customers with circles is called as the circlecustomer master data link. While creating this master data link, the short form
of the customer is also collected to be used while creating the customer location
name, like SBI in the case of Stae Bank of India.
P1 and P3 parts are not used for customers. P2 part for all customers will
be LL. P4 will be the place name prefixed with the SDCA code & P5 will be the
customer short form.
The Edit and Remove buttons are available in each row of the customer
location name which can be used to edit the customer name or remove it.
The privilege for these actions is restricted and is available to the users
of Circle Administrator User Group.
The create button on the page can be used to create a customer location
name or customer in a circle.
The circle, customer name and customer short name can be entered in
this form and click the create button to create the circle-customer
link.
In the customer location name option you have to select the circle,
ssa,sdca and the customer from the select boxes which will fill up
the P2,P5 and SDCA prefix for the P4 parts.
The place name only need to be entered in the Customer Location text
box and click on the create button to create the customer location
name.
This page lists out the route joints in a SSA. The SSA can be selected
using the Select SSA filter and the route joints created in the SSA will be
listed out SDCA wise in that SSA.
Each row of the route joints in an SDCA will show the route joint name
under the appropriate columns. The route joint name is framed using the P1
through P5 part values.
P1, P3 and P5 parts are not used for route joints. P2 part for
fiber
tappings will be BJC and for virtual units will be VST. P4 will be the place name
prefixed with the SDCA code.
The Edit, Remove and convert to virtual unit / fiber tapping buttons are
available in each row of the route joint which can be used to edit, remove and
convert the route joint respectively.
The privilege for these actions is restricted and is available to the users
of Circle Administrator User Group.
The create button on the page can be used to create a route joint.
Select the route joint type from the create route joint form and continue
selecting circle, ssa & SDCA where the route joint to be created. Finally enter
the place name and click the create button to create the route joint.
Chapter
5
ORGANISATION
Applies to: ALL users.
Details about: Officer,Designation,Hierarchy
This menu groups all the pages which are related with hierarchy structure
and controls.
5.1 Hierarchy
This master page defines the default functional hierarchy reporting of a
circle.
Three types of Hierarchy are defined at present. They are,
1.
Technical Hierarchy
2.
Accounts Hierarchy
3.
ISO Hierarchy
Each of the hierarchy types above are constitute of Cadres. The cadre list
in each hierarchy type is given below,
Hierarchy Type
Technical
Cadre Name
Cadre Code
CGM
PGM
Sr GM
Accounts
ISO Hierarchy
General Manager
GM
TDM
Adl GM
DGM
AGM
Divisional Engineer
DE
SDE
JTO
TTA
Telecom Mechanic
TM
GM F
DGM F
CAO
Accounts Officer
AO
JAO
CEO
Management Representative
MR
DMR
circle. The represent column shows the default administrative area of the cadre
in the circle.
It is possible to change the default reporting cadre and represent columns
of any cadre and after changing it is must to click the change button to make it
in effect.
The privilege for these actions is restricted and is available to the users
of Circle Administrator User Group.
This page has provision for creating a Cadre name by clicking on the create
button.
The privilege for this action is restricted and is available to the users
of Policy Maker User Group.
5.2 Designation
This page will show the data of a designation in accordion tabs which will
be revealed upon clicking on it.
The accordion tabs in the designation display page are,
This tab shows the basic details of the designation like cadre, hierarchy
type, designation type, cadre progression of the designation, Represents and
Reporting higher designation.
Designations can be created of two types,
is
supporting
the
controlling
officer
of
that
unit
for the
Choose the Hierarchy type, circle and designation type from the
respective select boxes.
While entering the place name the possible options may be listed out.
You can either select from the options or keep on typing a place name
which is not available in the list.
The privilege for these actions is restricted and is available to the users
of Circle Administrator User Group.
5.2.5 Edit designation
The privilege for these actions is restricted and is available to the users
of Circle Administrator User Group.
5.3 Officer
This is the landing page of any user accessing the LM module and shows the
logged in officers profile. In line editing is provided to change the personal
data like mobile number, phone number, email and DOB. The officer can change his
password also by clicking on the Change Password button. The photo of the officer
can be uploaded in this profile tab.
The responsible location tab will list out the units in which the officer
has the presence.
The next form will be shown depending upon the details available with
the system for the hr number provided.
If all the details are known about the officer that details will be
shown.
The privilege for these actions is restricted and is available to the users
of Circle HR User Group.
5.3.2 Edit Officer Details
It is also possible to edit the details like Name, Mobile Number and
Gender of any officer by clicking on the Edit button.
The privilege for these actions is restricted and is available to the users
of Circle HR User Group.
5.3.3 Transfer In an officer
The details asked in the transfer in form has to be completed and the
submit button has to be clicked to effect the transfer.
wherein
the
officer
will
keep
her
present
The privilege for these actions is restricted and is available to the users
of Circle HR User Group.
5.4 Privileges
The Privilege Menu and Process Flow menu are designed to handle various
roles and privileges of different users to access different utilities of
different packages/apps and process flow mechanism. Since the packages are going
to implement in pan-India basis, Circles also come into picture. This part of LM3 should manage and take care of lot of things in respect of verticals and
horizontals, permutations and combinations, access and denials etc... There are
policies underlying to decide the flexibility and restrictions. Those things will
vary from time to time area to area, and hence these should be manageable from
within it.
The Edit/View window has 4 accordion tabs and they are arranged in the
following order
1. Application and Privilege(Role)
2. User
3. User Group
4. Privilege Group
Application and Privilege (Role) : View and Edit facility for the master
data of application is made available here. The eligible circles for each
application can be set.
The privileges can be viewed and edited by clicking on the link provided.
Here the description of Role, the Code for developers and weight Index can
be edited. The status of each privilege can be activated or de-activated.
Privilege Group:
can be
viewed and edited here. For a custom defined group, the programmer code , index
etc. can be changed here.
2. The master data of Roles can be created by using the option Create
Privilege(Role) Master. A role is created for an application. Description, role
code for programmerss use, weight index and status are the input fileds. The
default value of weight index is 1.000.
3. The master data of privilege group can be made with using the option
Create
Custom
Privilege
Group
Master,
for
circle
and
application.
Description, privilege group code for programmer and weight index are the input
fileds.
4. A user group can be created by using the option Create User Group
Master and Form Group by adding HR/Desig./FU. By clicking on the radio button
Create User Group Master , a user group can be created for a circle and
application where description and weight index and status are input. After
creating a user group , members can be included into the group by clicking on the
radio
button
User
group
formation
by
adding
HR/Designation/FU.
After
selecting a user group, the type of member has to be selected. The available
options are Specific User with HR Number , User with Specific Designation
, Users in a Functional Unit and Cadre with Synon. After selecting the
type, an HR , designation , functional unit or cadre with category(synon) can be
picked by from autocomplete drop down.
Actions available in create drop down are Create Flow Master and Create Process
Flow Path.
1. Creation of the master data of Process flow can be done by selecting the
option Create Flow Master. Description of the process and code for developers
are the input fields. Status also can be set.
2. By selecting the option Create Process Flow Path, the parameters for next
level of a selected process can be set. Suppose there are already 2 levels are
set for a particular process and one can define the parameters for only the 3rd
level by selecting this option. After the selection of circle and application ,
the process can be selected. When the process is selected, the next level is
shown in the level field in red colour. The field is disabled so that the user is
not able to change the level. After inputting the name and short description of
the particular level, recipient type can be selected. The options available are
HR, Designation, User Group, Functional unit, Hierarchy Link
Cadre. According to the type, the autocomplete field for recipient will
populate with options. The option Hierarchy Link Cadre is meant for
hierarchical progression of flow. Suppose SDE DTS wants to submit a form to his
reporting officer to DE TM, then this option can be selected. Other things
available are action table and condition table. These are optional additional
facilities provided to programmers who want to store the actions and conditions
of the flow to be performed or checked at a particular level.
Chapter
6
REPORTS
Applies to: ALL users.
This menu groups all the pages which are related with reports and views.
1. Reports
2. Tree View
1. Reports: Reports are grouped into 3 sub-titles
1. Questions and Answers
2. Consolidated
3. Detailed
Q&A portion useful to find out individuals as designations or staff , the
information at the extremes etc. There are lot of mouse over capture
points which presents tips and cards for details.
Consolidated Reports give count of various parameters in tables as well as
diagrams
Detailed reports are also available.
Some screen shots:
Chapter
7
Implementation & Maintenance
Applies to: ALL users.
8. The officers in the circle dealing with the transmission wing are to be
created.
9. The officers has to be attached to the controlling designations using the
Transfer In procedure (Initial Attachment option).
10.The functional units are to be attached to the designations in the operation
hierarchy tab of each of the functional units.
11.View the organisation tree diagram to see that all the data are linked in
order.
Chapter
8
Summaries
Applies to: ALL users.
1. Creation of a user
Every user of the package is to be created in the LM module. A new user can be
added by clicking on the create button on the Organization -> officer page.
In the officer text box enter the HR number of the user and click on check button
If all the details are known about the officer that details will be shown.
If additional details are required for the HR number it will be asked for.
The privilege for these actions is restricted and is available to the users of Circle HR User Group.
Now the created user has to be attached to a specific designation. If the designation for the user is
not available in the system, go the Process 7.
If the designation is already created in the system, go to Process 2.
For initial attachment, select Type of transfer as Initial attachment. Select the required cadre,
Circle and Designation for the user and submit. Now if you go to profile page of the user the
designation of the user will also appear in the same line of the name and HR Number.
If some mandatory data is missing for the user, activate/ remove button also will appear on
the same line. Then the user is to be activated before initial attachment. The user without any
designation/ Functional unit attachment can be removed using remove button. Removal is required
to be done when the user is no more a user of the package, may be due to retirement/ death/
transferred out of the jurisdiction of the package.
After initial attachment of the user to a designation, check whether the designation is attached to
some Functional Unit or not. If the designation is not attached to any of the Functional Unit,
continue with Process 6.
3. Transfer in of a user
All the transfer and promotion/ demotion processes are clubbed into this single process. Go to
Organization->officer (the profile page of the user to be transferred in) by inputting/ selecting
either name or HR number of the user in the select officer text box.
In the profile page of the user, the present designation, if any, of the user will be available. By
transfer In process, the user is being attached to the new designation to which he is transferred.
During this process the user, if any, is in the transferred designation will be transferred out and all his
controlling responsibilities will be attached to the incoming user. Also the controlling responsibilities
of the transferred in user will automatically be assigned to his reporting officer. The additional
responsibilities, if any, attached to the transferred in user have to be relinquished before
implementing the transfer in process. But this condition is not compulsory in the case when the
additional charge designation and the transferred in designation are the same.
Click on the Transfer In button.
Fill all the required fields and click on Submit. If the process is successful, the background
changes due to transfer in process will be displayed in the Transfer In Result screen. The transferred
out user will now be without any designation and all the controlling/ supporting responsibilities of
the transferred out userr is now assigned to the transferred In user. This can again be verified by
Process 10.
to be done when the user is no more a user of the package, may be due to retirement/ death/
transferred out of the jurisdiction of the package.
Operational Hierarchy tab shows the linkage of a functional unit with designations.
The user bearing the designation will be responsible for the maintenance activities on
the assets attached with this functional unit.
A unit can be attached with any number of designations, out of which one will be of
controlling nature.
In case a unit is attached with more than one designations, the supporting
designations may have two options,
Remove : By clicking on the button with label Remove, the linkage of the unit with
the supporting designation will be removed.
Make Controlling : By clicking on the button with label Make Controlling, the
supporting designation will become the controlling designation and the existing
controlling designation will become the supporting designation.
If the functional unit is not attached with any of the designation, there will be an
option for choosing the controlling designation.
By attaching with a designation the unit comes under the administrative control of a
circle.
All the processes in this tab are collectively called as the delegation of charge and
the privilege is given to all the officers of DE and above cadre in Technical hierarchy
type and CAO and above cadre in Accounts hierarchy type.
Choose the Hierarchy type, circle and designation type from the respective select
boxes.
Choose the cadre, synonym and identifier and place to frame the designation.
While entering the place name the possible options may be listed out. You can either
select from the options or keep on typing a place name which is not available in the
list.
Select the reporting designation to which the user is supposed to report to. Enter
few characters of the reporting designation in the filter box and select from the
dropdown list.
Designations have to be created from the top to bottom levels of reporting structure
for a circle.
The privilege for these actions is restricted and is available to the users of Circle
Administrator User Group.
By editing the designation we can even change its reporting designation also.
The privilege for these actions is restricted and is available to the users of Circle
Administrator User Group.
Definitions