mwokasch

Disregard. I think I figured this out. (The “submit” does appear on the last page).

click the field, then conditions, then options based on a condition.

i don’t believe so.

The way forms are built is similar, but different. I recreated my forms and am pretty happy with the way AIO works compared to smartforms.

I appreciate the repeater part.

For the computed fields, I guess that sort of makes sense except that those calculated fields tend to be read-only and so they’re not change-able in the editor. If I increase the number of adults, family size can’t change either.

Same thing happens for a form field that is the calculated number of days between two dates. Changes in the edit screen will put that computed field out of synch.

Bringing this one back to the top.

The approval workflow email part still remains an issue. There’s no option to pick the entry status in the conditions and there’s no way to link the approval workflow in the email.

For those wanting to do the other portions, you can change the “Entry Status” on the entries page by clicking the little ??</img> next to the status on the “Edit” screen. And then click the ??</img> button (but see the Error issue on another topic)

It’s sort of magical because I’m not sure what language is actually going on in the background,b ut you can do that using:

[date_field_1]+2*86400

Where 2 is the number of days.

You can do that by clicking the little calculator button on the Minimum Date of the second date field.

Repeater values aren’t exported, but I can get the other data, now.

Checking back in on this issue. Having access to the CSV export is pretty important requirement to make this new version work.

The example is from the BODY of the email. Not the subject.

For example:

Results in:

I guess the question then is, how am I supposed to use those fields? Right now they’re not end user presentable and they look different depending on which part of the tool I’m using.

For now, it’d be okay if the Email use of the tag presented it like it does in the fieldsummary template (i.e., a table format). That’s at least somewhat acceptable.

Yes I do.

Confirmed. This works as expected now.

This might be a bug or a CSS conflict somewhere in something. I can make the year picker appear by adding the following to the custom CSS section:

.flatpickr-current-month input, .flatpickr-current-month select  { display: inline-block !important; }

On the Entries Screen. One other weird thing I noticed. It seems like the HTML field is getting reported on the “entries” screen as if they’re user input. Where I’m using the HTML element for explanatory purposes, this is clogging up the entries screen.

Could we add some way to exclude it from those reporting functions?

These are my AIO plugins.