Subversion Repositories SmartDukaan

Rev

Show changed files | Directory listing | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
37864 1 d 5 h ranu /trunk/profitmandi-fofo/src/main/ rbm performance view will consider all partners not taregted only  
37846 2 d 6 h amit /trunk/profitmandi-fofo/src/main/ feat(warehouse): dashboards list ACTIVE warehouses only, warehouse-team screens ACTIVE+SUSPENDED (from BillingWarehouseService, WAREHOUSE_MAP gone); global $warehouseNames for labels of data rows in any state; Sellers & Warehouses screen: all-warehouse overview with status tabs, 3-state status, rename, stock/unshipped orders/stores/mapping usage, send stock alert; partner zone offers active warehouses only; brand stock 'All' = active warehouses (replaces r37838 loop); jsVersion 442  
37839 2 d 13 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/monitors/ drr view dashboard commit  
37775 13 d 6 h ranu /trunk/ aging po approval process  
37761 13 d 12 h ranu /trunk/ aging po approval process  
37750 14 d 6 h ranu /trunk/ aging sku purchasing need to approval of niranjan kala sir  
37748 14 d 9 h ranu /trunk/profitmandi-fofo/src/main/ today po rbm view showing only for l7 and above  
37747 14 d 10 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/monitors/ today po rbm view showing only for l7 and above  
37745 14 d 10 h ranu /trunk/profitmandi-fofo/src/main/ today po rbm view showing only for l7 and above  
37720 19 d 9 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/monitors/ today po rbm view showing only for l7 and above  
37717 19 d 10 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/monitors/ today po rbm view showing only for l7 and above  
37716 19 d 12 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/monitors/ today po rbm view showing only for l7 and above  
37685 20 d 7 h amit /trunk/profitmandi-fofo/ Remove selenium from the fofo portal entirely

No browser starts in this WAR any more, and the selenium-java and
webdrivermanager dependencies are gone with it. Verified: no source reference to
selenium/WebDriver/ChromeDriver anywhere in the module, and zero selenium
artifacts on the runtime classpath.

Three pieces:

1. The insights schedule and its pull move to profitmandi-cron (r37684) and dao
(r37683). This service keeps only the READ paths -- redis, then in-memory,
then cs.agent_daily_insight -- plus refreshInsights(), which now asks the dao
sync service to run once and re-reads what it wrote. The portal therefore
holds no credentials at all: KNOWLARITY_USERNAME/PASSWORD are deleted from
this source, along with INSIGHTS_PAGE_URL and the 200-character CSS selector
the scrape depended on.

2. KnowlarityScraperService deleted. It was dead, not merely idle: zero
references anywhere, both @Scheduled annotations commented out, and its
@PostConstruct selenium block commented out with the note 'DISABLED - Live
status now comes from WebSocket via profitmandi-cron'. SVN backs that up --
r36057/r36058 (25-Mar) moved agent status to the websocket and r36072/r36075
(26-Mar) created KnowlarityBreakLogService in dao, but nobody removed the
corpse. It kept selenium in this WAR for six months after nothing used it.
The data agrees: 'On Break - <reason>' rows in cs.rbm_break_log stop on
25-27 March and plain 'Break' takes over, which is exactly that handover.

⚠ Consequence worth knowing: break-REASON granularity (lunch/meeting/sick)
was lost at that migration and is not coming back from the websocket feed.

3. setTokens() and POST /indent/set_knowlarity_tokens removed -- the method had
already been reduced to a log line, and the pull now authenticates itself per
run. Also retired the orphan knowlarity.scraper.enabled property (nothing read
it; it was still 'true' in prod), and corrected a stale section header and a
doc comment that promised 'current tokens' which no longer exist.

Not touched, deliberately: POST update_agent_status / bulk_update_agent_status /
update_status_by_name still exist and still write cs.rbm_break_log through
AgentLiveStatusService. They are orphaned -- the deleted scraper was their only
feeder and no view or script in the deployed WAR calls them -- but they are
public HTTP surface, so proving there is no INTERNAL caller is not the same as
proving no external one. Left for a separate decision.
 
37586 26 d 9 h ranu /trunk/ drr view modification  
37533 34 d 0 h ranu /trunk/ loi process added, revival and code changes process  
37519 35 d 6 h ranu /trunk/ rbm drr dashboard position wise data  
37505 36 d 7 h ranu /trunk/ rbm drr dashboard , all today po rbm view maped  
37497 36 d 9 h ranu /trunk/ rbm drr dashboard , all today po rbm view maped  
37487 37 d 6 h ranu /trunk/ rbm drr dashboard , all today po rbm view maped  
37460 39 d 9 h ranu /trunk/ rbm drr dashboard new ui looks  

Show All