DIGIT Public Finance Management
PlatformDomainsAcademyDesign SystemFeedback
v2.0
v2.0
  • Introducing Public Finance Management (iFIX)
  • Platform
    • Release Notes
      • iFIX Core Release Notes
        • iFIX Core Build Updates
        • iFIX Core Test Cases
      • iFIX Adaptor Release Notes
        • iFIX Adaptor Build Update
        • iFIX Adaptor Test Cases
    • Specification
      • Functional Specifications
      • Technical Specification
        • Information Model
        • APIs
    • Architecture
      • Technology
    • Services
    • Setup
      • iFIX Service Setup
      • Infrastructure Setup
        • Quickstart/Local Setup
        • On AWS
        • On Azure
      • Deploy Services
        • Deploy from your local machine
        • CI/CD
      • API Access Key
    • Configuration
      • Core Service Documents
        • Master Data Setup
          • Domain Services
            • iFIX Core Master Data Service
            • iFIX Core Fiscal Event Service
            • iFIX Core Fiscal Event Post-Processor
        • iFIX Core Data Cleanup
        • iFix Department Entity Service
        • iFix Client Management Service
          • Keycloak Setup
      • Configuring Master Data
      • Promotion Docs
        • Master Data Service Promotion Doc
        • mGramSeva iFIX Adapter
        • Department Entity Service Promotion
        • Fiscal Event And Fiscal Event Post-processor Service Promotion
        • MongoDB Migration
  • Products
    • Use Cases
      • Leveraging iFIX To Enable Timely Payments To Frontline Health Workers
    • Works Module
    • mGramSeva
    • iFIX Adapter
      • Adapter Service Documents
        • iFIX Adapter Master Data Setup
        • mGramSeva iFIX Adapter Service
        • iFIX Adapter Master Data Service
        • iFix Adapter Services
      • Source Code
      • Installation
        • Local Setup
        • CI/CD
    • iFIX Dashboard
      • Features
      • Architecture
        • Technology
      • Source Code
      • Installation
        • Local Setup
        • CI/CD
      • Documents
        • iFIX Reference Dashboard
          • iFIX Fiscal Event Aggregator
  • Community
    • Ecosystem
      • News and Events
    • Roadmap
    • PFM Blogs
      • Why PFM Needs Fiscal Information Exchange Standards
    • Source Code
    • Discussions
    • Issues
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page

Was this helpful?

  1. Platform
  2. Configuration

Configuring Master Data

ADMIN ONLY

Before the iFIX platform can be used, the master data must be configured directly into the respective collections in MongoDB. Associated APIs for configuring Master Data will be made available in the next version.

  • Add Government - Insert into MongoDB collection

  • Add Department

  • Add Department Hierarchy - It defines the hierarchy definition for the department

    • department id: It is master department id (UUID)

    • level: It defines the depth of hierarchy of department level

      • Root level department hierarchy will not contain any parent value and level value will be zero

      • Level value incrementation rule:

        • When parent id is having any value then we search parent in department hierarchy record for hierarchy level evaluation

        • Get level value from parent department hierarchy and increment current department hierarchy level value by one

    • parent: It provides details about department parent (UUID)

  • Add Department Entity - It contains department entity information along with its hierarchy level and also attaches master department information (department id - UUID). Here we keep all children information list at every department node (department record). Leaf level department will not have any children info. Children list contains department entity id list, which makes current department entity parent of all children list (department id list), that's how it maintains department entity level. Entities can be created by

    • First defining the hierarchy level top to bottom because it has parent's reference

    • Then we can start adding department entities, bottom-to-top because it has child's reference.

Note:

  • The root department hierarchy will have the label "Department", and the root department entity will be the department itself

  • When we have to update the existing children list of Department Entity then update the existing children list using mongodb command like below:

    • Find the department entity parent where the new children need to be added. Do search by name and hierarchy level db.departmentEntity.find({"name" : "<current_department_entity's_name>","hierarchyLevel": <Current_department_entity_hierarchy_level>});

    • Append the department entity id at the end of the current department entity children's list. So first find the length of the current array and then set it as "children.n": "" (where n is the length of the array.)db.departmentEntity.update({"_id": ""},{$set: {"children.n": "", "children.n+1": ""} })

  • Add Chart of Accounts - Insert manually into MongoDB collection

  • Add Expenditure - Insert manually into MongoDB collection.

PreviousKeycloak SetupNextPromotion Docs

Last updated 3 years ago

Was this helpful?

All content on this page by is licensed under a .

​
eGov Foundation
Creative Commons Attribution 4.0 International License
Creative Commons License