Transactional snippets are built on several repository item descriptors:
TransactionFragment– the snippet itemTransactionFragmentParameter– input parameters for the snippetTransactionFragmentParameterListValue– for parameters that are of type list, these are the possible values in the list
Creating transactional snippets
Use the following steps to create a transactional snippet:
Create a JSP file containing the JSP code you want to display in the transactional snippet. Store this file in the Web-app directory of the appropriate Service extensions directory. See Configuration File Locations for details about directory locations.
In the ACC, create a global component of class
atg.svc.fragment.in the ATG Registry under
TransactionalFragment/atg/registry/. Edit its properties with appropriate information and save the component.
TransactionalFragmentsSee Properties of Transactional Snippets for details on available configuration properties.
In the ACC, create an
atg.svc.repository.beans.repository item in the ServiceRepository for each parameter you need to use in your transactional snippet (number, string, date, Boolean, or list; list parameters will appear as dropdowns in the user interface).
TransactionalFragmentParameterFor each parameter of type
list, create anatg.svc.repository.beans.repository item.
TransactionalFragmentParameterListValueSee Properties of Transactional Snippets for information on parameter repository items.
To use this snippet in Knowledge Manager and Self Service, go to Service Administration and create a new
FieldDefinitionof typeTransactionalFragmentType, then add thatFieldDefinitionto a new or existing solution class.
