Please enable JavaScript.
Coggle requires JavaScript to display documents.
IROC
cartographie (BBUS
(Tech)
tech features necessary to support…
IROC
cartographie
-
SalesForce
-
UI
:check: SEARCH, READ, UPDATE voucher IR
- access all data
- link with relevant case
- update is limited to status change
:question:REPORTS generation on IR vouchers
- check Béatrice docs for sample reports
Tech
:question: generate & link CASE with relevant data extracted from voucher IR creation
- was OK in UAT at some point, confirm status today
- beware case taxonomy handling is specific to each market
-
Dashboard
Business requirements
permission management (75%) :red_cross:
who can perform IR or OC related actions
requirements are pretty advanced but fully dynamic management of permissions needs more work (currently handle by IT team)
-
generate voucher OC :red_cross:
- for a customer with accountability and perimissions
- limited with quota for an hotel
- tracked by service for HQ users
-
-
SEARCH & READ voucher OC based on :red_cross:
- user hotel perimeter (hotelier)
- user service perimeter (HQ user)
UI
-
-
SEARCH VOUCHER IR :check:
- permission handling (visibility is based on user role and hotel perimeter)
- ui evol still necessary for ease of use
-
-
-
-
Voucher IR Permission management
- handle who can generate IR vouchers :check:
- filter voucher visibility based on hotel perimeter :check:
- change available options for each hotels (responsibility company or hotel, ...) :red_cross:
- custom UI for letting an HQ user manage dynamically those rights easily (50%) :red_cross:
-
-
Tech
-
-
-
Service context handling (OC vouchers for HQ users) :red_cross:
- switch from service to hotel perspective (50%)
- permission model refactor to handle service perimeter (50%)
-
-
-
PMS (Lean)
Tech & UI
-
Voucher Loyalty :question: :check:
If this one is ok others are ok too (same actions just the code to be used changes)
-
-