Lesson 1Validation strategy: required fields, email validation, value ranges, conditional visibility, real-time feedbackImplement a robust validation strategy fi request data. Yuh wi combine required fields, pattern checks, ranges, an conditional visibility wid real-time feedback fi prevent errors widout frustratin users.
Configurin required an optional fieldsEmail an pattern-based input validationNumeric ranges an allowed value setsConditional visibility an dynamic rulesInline error messages an success cuesLesson 2Request Details screen: full metadata, history/timeline, comments, attachments, status change actionsDesign di Request Details screen fi show full context. Yuh wi surface metadata, history, comments, attachments, an status actions in a clear layout dat support auditin an collaboration.
Structurin key metadata an fieldsDisplayin history an status timelineComments an internal collaborationManagin attachments an versionsStatus change an approval actionsLesson 3Admin Dashboard: assignment queue, workload views, SLA breaches, configuration pages fi request types an prioritiesBuild an Admin Dashboard dat surface operational insights. Yuh wi design assignment queues, workload views, SLA breach indicators, an configuration screens fi request types, priorities, an routin rules.
Designin assignment an triage queuesWorkload an capacity overview viewsHighlightin SLA breaches an risksConfigurin request types an prioritiesAdmin-only configuration an securityLesson 4Formula an delegation patterns: patch vs submitform, LookUp/Filter delegation, use of collections, error handlin an retriesApply reliable formula an delegation patterns. Yuh wi compare Patch an SubmitForm, design delegable filters an lookups, use collections safely, an implement error handlin wid retries fi resilient apps.
Choosin Patch versus SubmitFormDesignin delegable Filter an LookUpUsin collections widout data lossHandlin errors an user notificationsRetry logic fi transient failuresLesson 5Home/Dashboard design: widgets, filters, counts by status, SLA alerts, search an quick actionsCreate a Home Dashboard dat summarize key metrics an actions. Yuh wi design widgets, filters, status counts, SLA alerts, search, an quick actions fi guide users to di most important tasks first.
Designin KPI tiles an summary widgetsGlobal filters fi status an ownershipSLA alerts an overdue indicatorsSearch across requests an metadataQuick actions fi frequent user tasksLesson 6Screen structure an navigation: Home/Dashboard, New Request, My Requests, Request Details, Admin DashboardDefine a clear screen map an navigation model. Yuh wi connect Home, New Request, My Requests, Request Details, an Admin Dashboard usin consistent menus, deep links, an back navigation patterns.
Mappin core app screens an journeysTop navigation, side menu, or tabsUsin context variables fi navigationDeep linkin to specific request recordsBack navigation an cancel behaviorsLesson 7Selectin app type: Canvas vs Model-driven wid justification an trade-offsCompare Canvas an Model-driven apps fi request solutions. Yuh wi evaluate data complexity, UX needs, governance, an ALM, den justify yuh choice wid clear trade-offs fi performance, extensibility, an maintenance.
When fi favor a Canvas app experienceWhen fi favor a Model-driven appHybrid patterns usin both app typesImpact on security, ALM, an governanceLicensin an environment considerationsLesson 8My Requests an Team Views: list galleries, sortin, filterin, inline actions (edit, comment, escalate)Design My Requests an Team Views fi efficient triage. Yuh wi configure galleries, sortin, filterin, an inline actions so users can quickly find, update, comment on, or escalate requests from a single screen.
Designin list galleries an layoutsSortin an filterin by key fieldsInline edit, comment, an escalate actionsVisual indicators fi status an priorityPerformance tips fi large request listsLesson 9New Request screen: form layout, required fields, attachments, request type picker, auto-populated fieldsDesign di New Request screen fi capture data accurately an quickly. Yuh wi define layout, required fields, request types, attachments, an auto-filled values dat reduce user effort while enforcin data quality an governance rules.
Choosin single vs multi-column form layoutsConfigurin required an optional fieldsDesignin di request type picker controlManagin file attachments an size limitsImplementin auto-populated default valuesLesson 10Accessibility, responsive layout fi tablet/desktop, an mobile considerationsDesign layouts dat adapt to tablets, desktops, an phones. Yuh wi use containers, breakpoints, an relative sizin fi keep forms usable, accessible, an readable across orientations, resolutions, an input methods.
Usin containers an flexible height controlsConfigurin breakpoints fi device sizesDesignin fi touch, mouse, an keyboardColor contrast an readable typographyScreen reader an focus order support
