737 Engine Change

0 views

Skip to first unread message

Veronica Hernandez

unread,

Aug 5, 2024, 3:25:28 AM8/5/24

to unmaldefu

Iunderstand the server documentation (I think) and the options available for each server node. What I am failing to find out is what controls the choice of engine for each workflow and how that may, or may not, change with the upgrade i.e. which engine will be chosen for any particular workflow.

Previously I don't /think/ that we had any workflows that needed the AMP engine, so initially I selected Original only for our 2022.1 UAT system, however I am now being asked to switch AMP on because of a specific requirement for Exchange online tools.

If a workflow ran on the Original engine before the upgrade will it definitely continue to run on the Original engine afterwards i.e. do we need to do anything to ensure that workflows continue to run as they have previously using the Original engine?

If we have a workflow running in Production (on 2020.4) which is running on the Original engine and a developer publishes a copy fresh to our UAT (on 2022.1) do they need to do something to force it to run on the Original engine i.e. in order to make the test run on the same engine as currently in Prod? Nothing additional is needed, the workflow will always run respecting the Engine setting specified in the workflow. Before 2022.1 the "Use AMP Engine" checkbox was not checked by default, so if a user went in and checked that and saved the workflow they could have AMP enabled.

For Server it will attempt to run with AMP, but if the Server does not support AMP then users will receive an error and either the workflow needs to be saved without AMP enabled or the Server Admin needs to enable AMP on the Server Instance.

If you are going to migrate workflows that were previously built using the original Engine to AMP Engine, you may find the Engine Compatibility Mode helpful - this maintains the record order of the original Engine by using the same sort method. There is a slight performance cost, but AMP should still perform faster than the original Engine.

AMP is now the default Engine for any new workflows you create. However, you can still choose the engine for your workflows via the workflow-level setting. Go to the Workflow - Configuration pane in Designer and select the Runtime tab. Next, enable or disable the Use AMP Engine check box to make your engine selection.

Alteryx Multi-threaded Processing (AMP) is a new architecture of Alteryx Engine, designed to work with larger volumes of data at a higher velocity. To learn more about the AMP Engine, as well as the differences between the original engine and AMP, visit these resources:

One thing that I missed originally that I'll call out is that as well as setting "Engine:" in Engine > General to "Both Engines" you do need to also check the "Engine: Enable AMP Engine" box in Controller > General

Is there a way to turn off the new fluid engine business? There are a number of issues with it:

- (biggest issue) cannot drag blogs between sections anymore. This was the only way to duplicate a block previously (duplicate a section, then drag the blog from new copy into the original, because we SILL cannot duplicate a block)

- the dragging and resizing is extremely unresponsive, at least in Chrome

- the options to change layout between desktop and mobile aren't great, because they don't apply to everything. For example grid spacing is unified between desktop and mobile, which makes it difficult to make things look good on both

Overall, this feels like a beta version, and can I please turn it off somehow and not be a guinea pig?

Agree. If fluid engine could also be responsive in drag/drop this would work (for example, when it is in mobile view...which should be for pads and phones). But as it stands now, I lost several hours of work because the site is now not visually aligned for mobile devices:(

I logged on this morning to make it, and found that... everything has changed? I'm referring, I gather, to "Fluid Engine". I had already been adept at using 7.1, but suddenly lots of stuff looks different, and making anything is hard.

I'm sure that once I get used to it it'll be wonderful blah blah blah... but in the meantime I'd really just like to make a quick new website, and not have to re-teach myself the fundamentals of Squarespace.

Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.

Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)

I tried again yesterday to come to terms with FE, spending several hours trying to (re) create classic and basic SS styles using FE + an open mind, and ended up on the verge of leaving Squarespace -EVERYTHING to do with image blocks is gone; image styles (poster, overlap, etc.) animations, the option to add a caption, just trying to get text and buttons to align properly ... and then do the whole thing again anywhere I want that layout. (And then edit for mobile)

And the mobile rendering? ? Yes, it's nice to eliminate or change a section on mobile view without CSS, but to have to check and edit/redesign the entire site as you go because with FE mobile now renders based on timeline (when you added the sections/blocks!)

It's all over the place ...

Who are the people FE was tested on that determined it was faster and more intuitive?? For sure not the general DIY population who are the backbone of SS, and not designers ...

There are advanced designers who are loving the flexibility and can use advanced CSS, HTML and Java to make it work for them, but many of us do not fall into that category. I dare say, the majority of SS users do not.

Maybe Im the only one, but I actually really like the option of spacer blocks. I use them to set up my own even grid, and serve many purposes ...they are a fundamental tool.

As are image block options ...please give us the OPTION to use FE

This forced "migration" to FE is going to be disastrous for many long time loyal SS customers.

Are you reading these threads??

PLEASE make FE a CHOICE! And keep classic not just for a few months, but forever. Just as you have with 7.0 and 7.1 -proving that it's possible.

The really critical issue for me with FE is that the blue + "insertion points" available in the classic editor are gone in FE. This means there's no way to insert images or other blocks on the same "layer" as text and then to flow the text around them. This seems like a huge oversight, and makes design much, much more difficult. It's a shame, as the regular, classic editor (still usable on blog posts) is fast and intuitive, and it feels like FE is a step back from that.

I haven't had an opportunity to try it yet, but it all seems to be rolling out VERY quickly. Does it just turn up automatically for some people? I'm pretty happy it hasn't appeared in any of my sites yet, but I would definitely like to try it out.

Completely agree! I had a client site almost completely finished in the old editor, and now being forced to use Fluid Engine is making the design inconsistent! We need a way to turn it off until we're ready to use it!

@tinabee - I just had the same issue but when I spoke to support found out that you can still use the old editor but it's not obvious at first. When you go to add a section make sure you scroll all the way to the bottom till you see: The above sections use the new Fluid Engine editor. Looking for sections built with our Classic Editor?

So the order on mobile is based on the order you created the block. If you create a new block and even if its on top it will be last on mobile since you made it last. If you accidentally use the first block on the second item you will have to redo the entire page. Either by deleting all blocks and doing it in order or if they all the same blocks move the content to the correct order of blocks created.

Oh thank heavens! Scroll down to the bottom of the add section sidebar on the left. At the bottom there will be a link (in small grey text) to add a section with Classic Editor! The Fluid engine doesn't handle things very well responsively. On mobile things are not in order and get jumbled up. I think the Fluid Engine looks really great and would be a VERY cool custom section for the few times you really need to do a fancy, layered, dynamic layout like a magazine spread, but it's not good for predictable web design.

What a shame. One of the best things about Squarespace has always been it's more "rigid" column layout that always created predictably great looking sites/pages on any screen. This seems like things will get far less nice looking.

Please make the Fluid Engine optional.

I'm ready to launch a site today, doing last minute edits, and fluid engine is forced on the site now. (Yes, I can scroll all the way to the bottom when adding a block and click "Looking for sections built with our Classic Editor?" but it's extra steps and time-consuming.