Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AndrewKeys123
Community profile AndrewKeys123 Level 1
Job title here
Location here
3 BADGES
Level 1

Level 1

Learn more
Joined the community 28-10-2020 11:26:20 AM
Offline
Top badges earned by AndrewKeys123
Customize the badges you want to showcase on your profile
Re: Render XFA as HTML- Issues with Texfield Validation
Avatar
Validate 1
Level 1
AndrewKeys123
Level 1

Like

1 like

Total Posts

5 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
AndrewKeys123
- Adobe LiveCycle
I communicated with Adobe on this topic and have enough information to give a correct reply. I summarize below the information I was given:-Not everything that is supported in a PDF rendering is supported in an HTML rendering. One needs to test with HTML build to see what is supported. With designer interface validation, in the event of a failed validation, the PDF rendering supports both a change in border color as well as the display of an error message when exiting the field. However, with th...

Views

163

Likes

0

Replies

0
Re: XFA Rendered as HTML - Designer Scripting Affect on S...
Avatar
Validate 1
Level 1
AndrewKeys123
Level 1

Like

1 like

Total Posts

5 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
AndrewKeys123
- Adobe Experience Manager Forms
I communicated with Adobe on this topic and have enough information to provide a correct answer. I summarize below the information I was given:-This is a subjective topic that depends on the build.-Server resources are used during the rendering of the HTML form. the AEM Server performs the rendering an XFA form as HTML, and the "heavier" the form, the more resources are used. By "heavier", we mean the number of pages, fields, objects, borders, interface validation, scripts (as well as size of sc...

Views

237

Like

1

Replies

0
XFA Rendered as HTML - Designer Scripting Affect on Server Performance
Avatar
Validate 1
Level 1
AndrewKeys123
Level 1

Like

1 like

Total Posts

5 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
AndrewKeys123
- Adobe Experience Manager Forms
I am working on a project where AEM Server (6.5) is used to render XFA forms as HTML. There is a list of form links on the website. The user clicks the XFA form link, the form is rendered as HTML, and then the user then has an option to click a button which will generate a flattened PDF including their typed in data. The intent is for large scale use of this. We need to make a decision on how much forms scripting to use in the XFA forms. The forms scripting will be Client scripts. Even though th...

Views

350

Likes

0

Replies

2
Re: Render XFA as HTML- Issues with Texfield Validation
Avatar
Validate 1
Level 1
AndrewKeys123
Level 1

Like

1 like

Total Posts

5 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
AndrewKeys123
- Adobe LiveCycle
AEM Server version is 6.5.4.0. Adobe Designer version is 6.5.0.201903203.935878

Views

244

Likes

0

Replies

0
Render XFA as HTML- Issues with Texfield Validation
Avatar
Validate 1
Level 1
AndrewKeys123
Level 1

Like

1 like

Total Posts

5 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
AndrewKeys123
- Adobe LiveCycle
I am working on an AEM project where the XFA form is rendered as HTML and am having an issue with validation of an textfield. I have a textfield where the user is supposed to enter a phone number. I set up the validation as follows: Object/Value - Validation Pattern - I set Validation, Edit, Display as a phone number. I check off both Validation Pattern Message and Validation Script Message and wrote in an error message in both. When the user types in non-numerals, and exits the field, if it is ...

Views

264

Likes

0

Replies

3
Likes from