• Re-investigated Activiti's actual integration after the user asked
    how it's used. Substantive findings:
    
    State on this dev DB: engine wired, never used.
    - The Activiti 6.0 engine bootstraps with xlyEntry. activiti-spring-
      boot-starter-rest-api:6.0.0 declared in xlyFlow/build.gradle pulls
      ProcessEngineAutoConfiguration. xlyEntry's
      EntryApplicationBoot only excludes Activiti's
      REST-security autoconfig, not the engine. xlyFlow is consumed as
      api project(':xlyFlow') in xlyEntry, so all xlyFlow controllers
      serve at xlyEntry's context-path.
    - ActivitiConfig.java is a real @Configuration that wires Chinese
      fonts and a custom ICustomProcessDiagramGenerator into the engine.
    - Real call sites confirmed:
      * runtimeService.startProcessInstanceByKey(...) at
        ProcessServiceImpl.java:107
      * taskService / repositoryService used across CurrencyFlowController,
        ModelerController, ProcessDefinitionController,
        ProcessActController, BizTodoItemServiceImpl, etc.
      * Modeler endpoints: /modeler/model/{id}/save, /modeler/editor/
        stencilset, /modeler/create, /modeler/deploy/{id}.
    - Empirical state: every workflow table is 0 rows in this dev DB —
      act_re_model, act_re_procdef, act_ru_task, act_hi_procinst,
      gdsmoduleflow, biz_flow, biz_todo_item, plus 0 gdsmodule rows
      with bCheck=1. Engine running, plumbing hot, no traffic.
    
    CheckFlowController correction:
    - The class file is 22 lines with ZERO handler methods. Just
      @RestController @RequestMapping("/checkflow") shell. The wiki
      previously described it as "Activiti workflow surface (approve/
      reject/view)" — this was wrong. /checkflow/* returns 404.
    - Real workflow URLs live in xlyFlow's CurrencyFlowController:
      /complete/{taskId}/{sBrandsId}/{sSubsidiaryId}/{sUserId},
      /completeerp/{...}, plus /modeler/* for BPMN authoring.
    - Fixed in runtime.md (load-bearing-controllers row),
      internal.md (specialised-runtime row), with cross-link to
      activiti.md.
    
    activiti.md rewritten:
    - Reframed from "deferred for full coverage" to "engine wired,
      never used in this dev DB" — the engine state is concrete and
      documentable; only the flow content is empty.
    - Added "Activiti is wired — engine ON" section with the
      bootstrap chain.
    - Added a concrete table of Activiti API call sites (file:line
      + which Activiti service is invoked).
    - Added URLs-the-modeler-exposes section listing the real
      workflow URLs served via xlyEntry.
    - Added the act_* schema state table with the live 0-row counts.
    - Added "What would make it move" — the 6-step path from drawing
      a BPMN to seeing a flowing approval.
    - Added "Why xly bothered with Activiti at all" — the
      architectural rationale.
    - Documented xlyApi/xlyPersist 5.17 declarations as vestigial
      (only IdGen.java's User import; type signature works under 6.0
      too — safe to remove).
    zichun authored
     
    Browse Code »
  • Investigated the FROUNT home-page card titled `KPI监控` to determine
    whether it's Activiti-driven (it isn't).
    
    Findings:
    - Endpoint: POST /xlyEntry/modelCenter/getModelCenter →
      BusinessModelCenterController.getModelCenter (xlyEntry,
      web/businessweb/) → BusinessModelCenterServiceImpl.getKPIModelList
      (thin wrapper) → BusinessModelKpiServiceImpl.getKPIModelList
      (xlyBusinessService).
    - Internal name: "KPI Work Center" (Javadoc 初次获取KPI工作中心).
    - Data source: gdsmodule rows where bUnTask=1, partitioned by sUnType
      ∈ {Pending, PendingCheck, MyWarning}. No KPI math; just open-task
      aggregation.
    - Categorisation in UI: by role (sftlogininfojurisdictiongroup ⋈
      sisjurisdictionclassify) and by business flow (gdsmodule parent-
      child tree; "01/04, 02/04…" is the iOrder within a flow parent).
    - Cache: @Cacheable(value="getKpiModelByUser") evicted by
      getModelCenterCalculation and gdsmodule-changing paths.
    - Empirical proof of independence from Activiti: in this dev DB,
      biz_todo_item and biz_flow are both 0 rows, yet the KPI Work
      Center still shows non-zero counts. Activiti's task surface
      flows through CheckFlowController instead.
    
    Updates:
    - runtime.md: add BusinessModelCenterController row to the load-
      bearing-controllers table; new "The KPI Work Center" subsection
      with full architecture, data source, cache behaviour, and the
      why-not-Activiti contrast.
    - internal.md: add /modelCenter/* row to the runtime endpoints
      table with cross-link.
    zichun authored
     
    Browse Code »
  • Audit every concrete claim in the 41 hand-written en pages against the
    three primary sources (DB, source on cleanup branch, source-tree
    inventory). Fix divergent claims in place; preserve framing where
    verified.
    
    Substantive corrections:
    
    - request-lifecycle / runtime / slice 01: the metadata read sources from
      five tables/families (gdsconfigformmaster + overlays, gdsformconst,
      sysjurisdiction, sysbillnosettings, sysreport), not four. The map key
      `gdsjurisdiction` is misleading — the per-user grant read queries
      `sysjurisdiction`; `gdsjurisdiction` is the builder-side action
      catalogue. `gdsformconst`, `gdsconfigformmaster`, `gdsconfigformslave`
      are NOT tenant-scoped; they filter by form-id only.
    - multi-tenancy: four metadata tables (gdsformconst, gdsmodule,
      gdsconfigformmaster, gdsconfigformslave) are an explicit exception to
      the "every table tenant-scoped" promise — `sTableNameList` strips
      sBrandsId/sSubsidiaryId from writes against them.
    - sSaveProName / sSaveProNameBefore are pre/post-save HOOKS on top of
      the always-running base path (BusinessBaseServiceImpl.add/update),
      not either/or branches. Default add/update path is in
      BusinessBaseServiceImpl, not AddDelUpdCommonServiceImpl.
    - cache-invalidation: redis cache is cleared synchronously in BACK via
      @CacheEvict on CleanRedisServiceImpl during save. The JMS
      CHANGE_GDS_MODULE queue triggers PRO_ERPMERGEBASEGDSMODULE (base-data
      merge), NOT cache invalidation despite the name. Cross-node
      coherence open question (no custom CacheManager bean configured).
    - messaging: enumerate all 24 P2pQueue destinations grouped by intent;
      fix CHANGE_GDS_MODULE description; clarify single Consumer.java with
      24 @JmsListener methods (not 24 listener classes).
    - API paths: /checkflow lowercase (mapping value, not class name);
      /procedureCall/doGenericProcedureCall (not /business/genericProcedureCall*).
    - tech-stack: Druid 6 java imports + 16 yml mentions (was 25 conflated);
      fastjson per-module xlyInterface 9 (was 10); commons-lang3 39 (was 41);
      @Document classes 20 PLAT_* + 2 DIKE_TEST* (was "all PLAT_*"); xlyPersist
      activiti hit is IdGen.java (was BaseDao.java); add Springfox to
      declared-but-no-imports table; reconcile module list to 11 framework
      core + xlyPlc plugin + xlyPlatConstant utility.
    - index.md: clarify xlyFace as "in build, not documented"; add xlyErpTask
      / xlyPlatTask scheduler bullet; correct MongoDB framing (caller is in
      xlyPersist with no consumers, not xlyPlat*); add xlyPlc note; extend
      backup-table OOS to cover *_copy1 / *_history / *YYYYMMDD[HHMMSS].
    - deployment.md: split deployable Boot apps from library modules;
      enumerate 12 commented-out includes (was 3); remove xlyPlatConstant from
      out-of-scope Plat* list; split profile permutations by service.
    - activiti.md: add xlyApi to 5.17 dependency list; replace speculative
      BPMN path hint with verified state; name actual ActivitiConfig.java;
      note act_id_* are views projecting xly users into Activiti shapes.
    - api-reference/external.md: fix bearer-token validation flow (sysapibrand
      via AES-decrypted corpid, not sysapithirdtoken); /online/* are page
      renders not API execution; /pro/* mostly returns Thymeleaf views; mark
      sysapidbtodb as xlyFlow-owned; /token/getToken accepts GET and POST.
    - api-reference/webhooks.md: add Swagger Docket caveat (UI shell ships but
      no Docket bean → /v2/api-docs effectively empty); flag /send/sendQw as
      stub (returns "ok").
    - slices/03-report.md: fix dir path xlyEntry/com/xly/report/ →
      xlyEntry/com/xly/web/report/; reframe PrintReportControllerOld as dead
      source (file body fully commented out).
    - concepts/modules-forms-vtables.md: add 22-prefix glossary table
      (gds/sys/sis/sft/ele/mft/sal/quo/acc/pur/ops/cah/sgd/ept/mit/pit/qly/
      kpi/udf/viw_/plat_/ai_/act_/qrtz_) so a maintainer can enumerate
      business-data domains at a glance.
    - concepts/master-slave.md: disambiguate document-row pattern from
      DataSource master/slave (different concept, name overlap).
    - proc-dispatch.md: add proc-name molds (Sp_*_BeforeSave/AfterSave/
      SaveReturn, sp_btn_*, PRO_ERPMERGE*) + function-layer paragraph
      (Fun_*/Fn_*/get_*; SQL-called, not Java-dispatched).
    - concepts/index.md: schema label MySQL\nxlyweberp → xlyweberp_*.
    
    Pass E (live behavioural traces) deferred — source/DB-side audit was
    thorough; live traces best done as a follow-up sweep against a running
    instance.
    zichun authored
     
    Browse Code »

  • zichun authored
     
    Browse Code »
  • Documents the xly (小羚羊) printing-industry ERP framework. Built with
    MkDocs Material; CJK search via jieba; 3,076 auto-generated catalog
    pages from recon/*.tsv plus hand-written prose for the framework's
    core mental model and end-to-end vertical slices.
    
    Phase 0 recon: stack, schema shape, framework metadata layer, scope.
    Phase 1 wiki: scaffold + auto-catalog + Slices 1-6 (Slice 7 deferred).
    
    Slice coverage:
      1. CRUD module (Hello World) — observed network + cited source
      2. Multi-tenancy & product editions — sBrandsId/sSubsidiaryId/sVersionFlowId
      3. View-backed module (read-only report)
      4. Custom field overlay (gdsconfigformcustomslave)
      5. Per-customer SQL override (script/客户/<customer>/)
      6. Hardware integration (xlyPlc, optional)
      7. Workflow (deferred — Activiti tables empty in dev DB)
    
    Concepts: thesis, modules-forms-vtables, master/slave, semantic-FK,
    customization channels & layers, multi-tenancy, request lifecycle.
    
    Reference (Builder): define-form, define-vtable, permissions,
    attach-workflow (deferred).
    
    Reference (Maintainer): runtime, proc-dispatch, cache-invalidation,
    sql-templates, deployment, activiti.
    reporkey authored
     
    Browse Code »