Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Presence Property for standard Email Submit Button

Avatar

Level 2

Hi All,

Is it possible to hide the presence of the standard Email Submit Button in Livecycle Designer?

Example: User cannot access EmailSubmitButton1 until a valid date has been entered in to DateTime1 field.

I have tried the presence property, with both a change event and exit event with no luck. I am assuming that since the standard Email Submit Button does not have a "click" event available, this task cannot be accomplished.

Any assistance is welcome

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Everything looks fine as foar as I can tell ....if you email the form to LIveCycle8@gmail.com I can have a look and see what is wrong. Please include a description of the issue in your email.

paul

View solution in original post

4 Replies

Avatar

Former Community Member

Yes you can change the presence of that button. First make sure that the form is saved as dynamic ....the change in presence will be ignored unless the form is dynamic. The code shoudl be on the exit of the Date field so the click event on the email button has no berring on this operation.

Hope that helps.

paul

Avatar

Level 2

Hi Paul,

Thank you for your response. I have saved the form as a  "Dynamic XML Form", but have had no luck with the exit event you suggested. I assumed that I would need an event to initially hide the presence of button and another event, that when validated, would show the button.

I used the code below, based on your suggestion:

form1.#subform[0].currendate[1]::exit - (JavaScript, client)

if

(this.rawValue != null)

{

Button1.presence

= "hidden";

}

else

{

Button1.presence

= "visible";

}

Any Ideas?

Jeff

Avatar

Correct answer by
Former Community Member

Everything looks fine as foar as I can tell ....if you email the form to LIveCycle8@gmail.com I can have a look and see what is wrong. Please include a description of the issue in your email.

paul

Avatar

Level 2

Hi Paul,

You were correct, the mistake was on my part. I replaced the Button1 value in the script with the correct value "SubmitButton1".

Thanks again for your assistance.

Best Regards

Jeff

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----