Description of reusable components description-of-reusable-components
AEM Forms workspace is composed of reusable components which are organized in a specific folder structure in CRX™. Each component has model, view, and template file at location specified in the folder structure, JavaScript™ dependencies on other component files, events listened by the component and JavaScript objects which trigger these events in AEM Forms workspace. The complete list of reusable components with constituent filenames and dependencies is given here.
TaskList tasklist
NOTE
This component can be used independently of AEM Forms workspace, provided you trigger filterSelected event for this component from your custom application.
Task task
NOTE
Workspace calls fetchTasks function of TaskList model to create Task models for this component.
FilterList filterlist
Filter filter
TeamQueues teamqueues
TeamFilter teamfilter
NOTE
TeamFilter gets the event indicating which task has been selected from TaskList component. Although these components share the model class, there is no other dependency.
TaskDetails taskdetails
CategoryList categorylist
NOTE
This component uses model classes of some other components like StartPointList, StartPoint, and Task. Besides this dependency, CategoryList can be used independently.
Category category
StartPointList startpointlist
NOTE
StartPointList and CategoryList components share the model class, hence the former depends on the latter. CategoryList accesses the information about which category’s start points are shown. To use StartPointList independently, simulate the event trigger from CategoryList.
StartPoint startpoint
StartProcess startprocess
NOTE
StartProcess and StartPointList components share the model class. This component becomes relevant you select a startpoint from StartPointList.
ProcessNameList processnamelist
NOTE
ProcessNameList does not depend on other components. However, internally it depends on ProcessInstanceList model class that in turn depends on other components. Hence, ProcessNameList uses many model classes like ProcessInstanceList, ProcessInstance, TaskList, Teamtask, and Task. Besides these dependencies, ProcessNameList can be used independently.
ProcessName processname
ProcessInstanceList processinstancelist
NOTE
ProcessInstanceList expects an event from ProcessNameList indicating the process name for fetching and displaying instances. To use ProcessInstanceList independently, simulate the event trigger separately.
ProcessInstance processinstance
ProcessInstanceHistory processinstancehistory
NOTE
ProcessInstanceHistory expects an event from ProcessInstanceList indicating which process instance’s history is to be shown. Besides this dependency the component can be used independently.
OutofOffice outofoffice
NOTE
OutofOffice can be used independently.
ShareQueue sharequeue
NOTE
ShareQueue can be used independently.
UISettings uisettings
NOTE
UISettings can be used independently.
AppNavigation appnavigation
NOTE
AppNavigation can be used independently.
UserInfo userinfo
NOTE
UserInfo can be used independently.
WSError wserror
UserSearch usersearch
SearchTemplate searchtemplate
SearchTemplateList searchtemplatelist
SearchTemplateDetails searchtemplatedetails
recommendation-more-help
19ffd973-7af2-44d0-84b5-d547b0dffee2