Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- - Handling of data that is displayed based on language (records in STR table). In ADF we can switch between languages, translated field values get auto-updated based on the STR_ID + Language. Are we going to keep this or go for another approach?
- - Are translations (adding translations through the UI in real-time -> in STR table) considered, and if they are, how should we handle them?
- - Structure in the REST section. Should it be admin -> work-code or just work-code on the same level as the others e.g. vehicle/person/object etc.;
- - Filtering based on WORK_CODE_STD_TYPE and WORK_CODE_STD_CATEGORY should be based on checkboxes, right? Users should be able to select which categories/types they want to see. Any place I can look that up?
- - In ADF we have a global boolean that stores if the user is an admin and is being used in several cases, one being in filters such as the one we discussed about - list of accessible vehicle owners. We have something like this in the app? (select * from vehicle_owner WHERE 'true' = ? --< boolean var
- OR vo.vehicle_owner_id IN
- (SELECT gvo.vehicle_owner_id
- FROM gu_vehicle_owner gvo
- WHERE gvo.gui_user_id = :gui_user_id))
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement