While Atlas is inherently a no-code platform, there are certain areas of it that require a bit more technical know how to get the most out of. Function Tasks are one of these areas. You can do a lot with them but you'll also need a bit of help from the Atlas Support staff to achieve some of the more complex outcomes they offer.

What is a Function Task?

A Function Task allows developers to integrate natively with the Atlas Workflow Process Engine, the engine that keeps Atlas purring in such innovative ways. That means that custom code can be developed and executed, allowing for pretty powerful results.

What does Async mean?

Whether a Function Task is async, or asynchronous, or not determines whether the Process the Function Task is part of should wait for the Function Task to complete before continuing.

If it is async, then the Process can continue while the Function Task continues to complete. This might be useful if the contents of the Function Task are particularly time intensive, or if the outcome isn't something the rest of the Process depends on. If it is not async, the Process will have to wait until the Function Task is complete.

What can you do with a Function Task?

Right now, the main baked in functions we've enabled with the Function Tasks are sending emails and copying processes.

You can read all about that in their respective articles:

The opportunities with Function Tasks are potentially limitless. Obviously the functionality you can add in depends on the coding expertise you have access to, but if there's something outside of the Atlas toolset that you'd like to integrate, you can probably give it a try with a Function Task.

Due to the extra level of competency needed to make the most out of Function Tasks, we suggest your first port of call is Atlas Support. Use the Intercom chat function to get in touch with one of our experts who will be able to guide you through the process of utilising Function Tasks.

Did this answer your question?