Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.drpn.ai/llms.txt

Use this file to discover all available pages before exploring further.

Darpan backend calls use Moqui JSON-RPC through /rpc/json. The method name is a Moqui service name, for example: 
facade.ReconciliationFacadeServices.list#SavedRuns

​
Layering

LayerRole
Facade servicesPublic JSON-RPC contracts used by the UI. They validate inputs, enforce access, normalize parameters, and shape responses.
Core servicesInternal services that perform reconciliation, schema, rule, and file-processing work.
Entity servicesMoqui entity operations and XML actions that persist product records.
Helper codeGroovy or Java methods for dense logic such as Spark processing, JSON parsing, and rule execution.

​
Facade services

Facade services are the app integration point. The active facade files include:
  • service/facade/AuthFacadeServices.xml
  • service/facade/SettingsFacadeServices.xml
  • service/facade/JsonSchemaFacadeServices.xml
  • service/facade/ReconciliationFacadeServices.xml
  • service/facade/SearchFacadeServices.xml
ReconciliationFacadeServices.xml includes product-level operations such as:
  • create#CsvRun
  • create#RuleSetRun
  • list#SavedRuns
  • save#SavedRunName
  • delete#SavedRun
  • run#SavedRunDiff
  • run#GenericDiff
  • list#GeneratedOutputs
  • get#GeneratedOutput
  • delete#GeneratedOutput
  • list#Mappings
  • create#Mapping
  • save#Mapping

​
Core reconciliation services

Core reconciliation services live under service/reconciliation/**.
Service filePurpose
ReconciliationCoreServices.xmlSpark-backed core compare services, RuleSet compare-scope preparation, base diff generation, and legacy mapping execution.
ReconciliationGenericServices.xmlGeneric reconciliation entrypoints that accept uploaded or text payloads and route to RuleSet or mapping execution.
ReconciliationRuleEngineServices.xmlRuleSet, Rule, Drools compile, execution, and cache operations.
ReconciliationInventoryServices.xmlInventory-specific reconciliation support.

​
XML-first rule

XML services own validation, authorization, entity mutation, service calls, and response shaping. Groovy and Java helpers handle processing-heavy code such as Spark preparation, rule execution, JSON normalization, and schema inference.

​
API shape

Darpan APIs are exposed through verified facade service names and the Moqui JSON-RPC envelope. Service references document required parameters, auth expectations, side effects, and response fields for those facade contracts.