Onboard to AEM Forms as a Cloud Service overview
Decide personas personas-aem-forms-project
-
User Experience (UX) Designer: A User Experience (UX) Designer defines style, layout, and branding for AEM Forms assets.
-
Forms practitioner: A Forms practitioner creates Adaptive Forms, themes, and templates as per the style, layout, and branding provided by the UX Designer. The practitioner also creates and integrates Adaptive Form with a Form Data Model (FDM) and AEM Workflows. A Forms Practitioner typically undertakes front-end related tasks.
-
Forms developer: A Forms developer develops a custom forms solution. A Forms developer typically undertakes backend development like developing custom components, AEM Workflows, pre-fill services and more.
-
AEM administrator: An AEM administrator helps with overall configuration like setting up users, hardening the environment, configuring data sources, configuring email, and third-party software. AEM administrator also helps with integrations like integrating with Adobe Analytics, Adobe Target, and Adobe Sign.
-
End user: A user interacts with and submits the published form, signs submitted forms, tracks submitted applications through a web portal, and receives personalized communications.
Onboard to the service onboarding
You can use Forms as a Cloud Service to create an adaptive form (Digital Enrollment) or generate a customer communication. After completing Onboarding to the Adobe Experience Manager as a Cloud Service, perform the following actions to enable Forms - Digital Enrollment or Customer Communications features. :
-
Log in to Cloud Manager and open your AEM Forms as a Cloud Service Instance.
-
Open the Edit Program option, go to the Solutions & Add-ons tab:
-
If you have a production environment, select Forms - Communications option to enable Forms - Digital Enrollment and Forms - Communications Add-On.
-
If you have a sandbox environment, select Forms to enable Forms - Digital Enrollment and Forms - Communications Add-On.
-
-
Click Update.
-
Run the build pipeline. After the build pipeline succeeds, selected solution is enabled for your environment.
# Allow Forms Doc Generation requests
/0062 { /type "allow" /method "POST" /url "/adobe/forms/assembler/*" }
Configure users config-users
After you complete onboarding to the service, login to your AEM Forms as a Cloud Service environment, open Author and Publish instances, and add users to Forms-specific AEM groups, based on their persona. The following table lists Forms-specific AEM groups, available out of the box, and corresponding user types. The table also provides AEM instance type for each user type:
- forms-users
- template-author
- workflow-users
- workflow-editors
- fdm-authors
- forms-users
- template-author
- aem-administrators,
- fd-administrators
- When a user must log in to view and submit an Adaptive Form, add such users to the forms-users group.
- When no user authentication is required to access Adaptive Forms, do not assign any group to such users.
For more information about Forms-specific AEM groups and corresponding permissions, see Groups and permissions.
Next step next-steps
Set up a local development environment. You can use a local development environment to create an Adaptive Form and related assets (Themes, Templates, custom Submit Actions, pre-fill service and more). And, convert PDF forms to Adaptive Forms without logging in to a cloud development environment.