---
title: "Workflow customization for Cloud"
canonical: "https://support.appfire.com/space/CSOT/68753674/Workflow%20customization%20for%20Cloud"
format: markdown
---
> Macro (aura-html)

What **workflow designers** need to know about workflow customization using **Cloud add-ons** implemented with Atlassian Connect architecture. 

| Topic | Cloud Implications | Discussion |
| --- | --- | --- |
| Conditions | - Not currently supported for connect add-ons |  |
| Validators | - Not currently supported for connect add-ons | Request to Atlassian to add support<br>- Workflow designer option to add validator
- Validator with timeout
- Not validated if timeout exceeded |
| Post functions | - Supported for connect add-ons |  |
| Process flow | - Post functions are started in the order indicated in the configuration (same as server workflow)
- Built-in (Atlassian) post functions complete before the next post function is started (same as server workflow)
- Connect post functions are **asynchronous** once started (key difference with server) | Request to Atlassian to add support<br>- Workflow designer option - defaults to asynchronous
- Allow synchronous with timeout
- Timeout exceeded, processing continues asynchronously |
| Create issue transition | - This is a unique transition situation even for server that requires some care in post functions and configuration
- There are currently significant differences for connect post functions as they run too early |  |
| Issue data | - Connect post functions access issue data external to the transition operation
- The issue data may or may not have been updated based on other transition activity following the point the connect post function was initiated
- The issue data changed by connect post functions may collide (not deterministic) | Atlassian needs to ensure that external changes to issue can be intermixed the internal transition changes. |
| Transition properties | - Not supported for connect add-ons |  |
| Issue view | - View of issue shown to user after the transition may or may not include results of connect post functions that change issue data | View of issue should at least re-read from database |
| Concurrency | - Concurrency issues for updates are more likely as connect post functions run concurrently |  |