Map a Template to a Model

   Journey Manager (JM) Previously known as Transact Manager (TM). |   System Manager / DevOps |  5.1 & Higher This feature is related to 5.1 and higher.

Manager allows you to map a template to a model

The following table lists the model variable names and types for each page.

  • Java type names are not fully-qualified unless clarity is needed. For example, class String is the normal java.lang.String unless otherwise noted.
  • Java types marked as an Entity are in the package com.avoka.fc.core.entity unless otherwise noted.
  • Model classes that "inherit from" other model classes inherit the variables of those classes. For example, the model for ErrorPage not only includes the variables listed for it, but also all of the variables for BorderPage.
  • The fact that the model can include a given variable does not mean that the variable is non-null at runtime.
Page Model Class Variable Name Java Type Inherits From
(global)

PortalUtils-Form

This is not a Model class, but a utility method used by Model classes to set certain properties in the Model from the Form
PortalUtils.addFormAndVersionProperties(Page, Form)

form (Entity) Form
formProperties Map<String, String>
BorderPage headerPath String
serverBuild String
portal (Entity) Portal
detectJavaScriptTimeout int
disableUserProfileEdit boolean
allowUserCreation boolean
permissionSet Set<String>
error.htm ErrorPage entityId String BorderPage
errorLog (Entity) ErrorLog
errorContext String
showDetails Boolean
messageKey String
errorMessage String
errorTitle String
submission-cancelled.htm SubmissionCancelledPage formRenderUrl String BorderPage
PortalUtils-Form
formCode String
submission-saved.htm SubmissionSavedPage submission (Entity) Submission BorderPage
PortalUtils-Form
isAnonymous boolean
formUrl String
userAccount (Entity) UserAccount
userName String
logoutMsg String
todoCount int
evaluatedPage String

Next, learn how to configure a form space email template.