---
title: "Workflow Post Function"
canonical: "https://docs.getxporter.app/space/XPORTER/1412596/Workflow%20Post%20Function"
format: markdown
---
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> > Macro (toc)
## Introduction
[Xporter](https://marketplace.atlassian.com/apps/891368/xporter-export-issues-from-jira?tab=installation&hosting=datacenter) provides a [Workflow Post Function](https://confluence.atlassian.com/adminjiraserver/advanced-workflow-configuration-938847443.html) that allows administrators to define multiple actions that will be performed during transitions in Jira Workflows.
The Xporter Post Function allows you to generate a document during transitions in Jira Workflows and to define which actions you want to perform.
## Access
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On your Jira instance, click the Settings/gear icon (Figure 1 - 1), and select *Issues *(Figure 1 - 2)*.*
>
> 
>
> > Macro (rw-step)
>
> On the left side menu, click *Workflows* (Figure 2 - 1).
>
> 
>
> Here you can:
>
> - See the list of the active workflows (Figure 2 - 2).
> - Add a workflow (Figure 2 - 3).
> - Import a workflow (Figure 2 - 4).
> - View/edit/copy an existing Workflow (Figure 2 - 5).
## Operations
### Xporter Post Function Configuration
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> To [configure the Xporter Workflow Post Function](https://confluence.atlassian.com/adminjiraserver/advanced-workflow-configuration-938847443.html) you must:
>
> - Select the [Template](https://docs.getxporter.app/space/XPORTER/1409467) to use (Figure 3 - 1).
> - Select the output format (Figure 3 - 2).
> - Provide the name of the file you want to generate (Figure 3 - 3).
> - Select if the [Xporter Post Function should have a Javascript condition](https://confluence.getxray.app/display/public/XPORTER/Workflow+Post+Function#WorkflowPostFunction-WorkflowPostFunctions:JavaScriptconditions) to be evaluated when this Workflow function is executed (Figure 3 - 4).
>
> 
>
> > ℹ️ If the **Include Attachments** option is turned on, the file will be generated with the Issue's attachments.
>
> > ℹ️ The [mappings](https://docs.getxporter.app/space/XPORTER/1413922) that you can include are the same mappings that are used inside the Templates with the same notation.
> > ℹ️
> > ℹ️ You can also use the following Xporter format functions:
> > ℹ️
> > ℹ️ - [Fields with HTML](https://docs.getxporter.app/space/XPORTER/1413876)
> > ℹ️ - [Formatting Date Fields](https://docs.getxporter.app/space/XPORTER/1413867)
> > ℹ️ - [Formatting Number, Escaping and User Picker Fields](https://docs.getxporter.app/space/XPORTER/1413867)
> > ℹ️
> > ℹ️ You can't use JavaScript with these mappings.
>
> > Macro (rw-step)
>
> Once you're done, click the *Add* button (Figure 3 - 5).
### Actions Available on the Xporter Post Function
The Xporter Post Function provides four different actions and each of them will have its own specifications.
The administrator will have the possibility to have more than one action configured to different receivers or to upload the document generated into multiple [File Servers](https://docs.getxporter.app/space/XPORTER/1409479).
The filename can be modified on each action, and it can be specified a custom name. The filename configuration has a size limit of 50 characters (but the exported file name doesn't have a limit).
#### Attach File
The document generated can be attached to the Issue of who performed the transition (Figure 4).
#### Save on Jira Host
This action allows the administrators to save the report on the Jira machine.
> ℹ️ The path defined (Figure 6) will be accepted only if the SO user has permission to write on the respective folder.
####
Send Email
Another important action is sending emails with attached reports or rendering a Template in the body of the Post Function.
Enable the option to use the default body (Figure 6 - 1) and your Post Function will have the Template rendered.
#### Upload File
Choose this action if you want to upload the generated document to a File Server.
Pick the Server to which the exported file will be saved and after this, the administrator will have the opportunity to define the path on the filename. The filename configuration has a size limit of 50 characters (but the exported file name doesn't have a limit).
### Xporter Post Function Overview
After choosing all the actions that will be performed, Xporter will give you an overview of each action with a description and the filename. The filename configuration has a size limit of 50 characters (but the exported file name doesn't have a limit).
You'll be able to edit (Figure 8 - 1) and/or remove (Figure 8 - 2) the existing actions according to your expectations.
After the configuration process, the post functions of the transition will look like the screenshot below (Figure 9).
### Workflow Post Functions: JavaScript Conditions
#### Overview
Xporter supports the evaluation of JavaScript conditions to check if the Workflow Post Function should be executed on that specific Jira transaction.
> ❌ Be careful with dangerous JavaScript expressions. For example, watch out for infinite loops or high-computation expressions. This will make Jira take up a lot of your CPU and you might have to restart it.
> ❌
> ❌ This feature is currently only available in Xporter Server version.
#### Configuration
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Activate the Condition option (Figure 10 - 1) in both Post Functions.
>
> 
>
> > Macro (rw-step)
>
> Write your JavaScript condition in the text box (Figure 10 - 2). If you activate this option, your Post Function will only be executed if the JavaScript expression is evaluated to be a *True* statement.
>
> > Macro (rw-step)
>
> Use the Mappings the same way you use them in Xporter Templates.
>
> 
>
> For this example, every time you make Status transaction on an Issue, Xporter will check if the Issue Key is "TEST-1" and if it is, it will execute this Post Function.
Support/Troubleshooting
If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://docs.getxporter.app/space/XPORTER/23102936).