---
title: "Workflow - Post Function"
canonical: "https://docs.getxporter.app/space/XPORTERCLOUD/460608/Workflow%20-%20Post%20Function"
format: markdown
---
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> > Macro (toc)
## Getting Started
[Xporter](https://marketplace.atlassian.com/apps/891368/xporter-export-issues-from-jira?tab=overview&hosting=cloud) provides the Multi-Action Post Function, a [Workflow Post function](https://confluence.atlassian.com/adminjiraserver073/advanced-workflow-configuration-861253591.html#Advancedworkflowconfiguration-Postfunctions) that allows administrators to define multiple actions that will be performed during transitions in [Jira workflows](https://www.atlassian.com/software/jira/guides/workflows/overview#what-is-a-jira-workflow).
> ℹ️ "A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle, typically representing a process within your organization" (Atlassian, 2024).
## Adding a Workflow
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> In your Jira Cloud instance, click the *Settings*/gear icon on the top right of the screen (Figure 1 - 1).
>
> 
>
> Then, select the *Issues* option (Figure 1 - 2). The *Issues* menu will open on the left side of the screen (Figure 2 - 1).
>
> > Macro (rw-step)
>
> Click *Workflows* (Figure 2 - 7).
>
> 
>
> Here, you can:
>
> - See the list of existing Workflows (Figure 2 - 1).
> - Use the search bar to find existing Workflows (Figure 2 - 2).
> - Add a Workflow (Figure 2 - 3):
> - Create a new Workflow (Figure 2 - 4; a modal will open for you to enter the name and Workflow's description).
> - Import a Workflow from the marketplace (Figure 2 - 5; a screen will open for you to select a Workflow from the marketplace).
> - Click the *Actions*/ellipsis button (Figure 2 - 6) to view/edit/copy an existing Workflow.
## Multi-Action Post Function Configuration
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> ### Accessing the Workflows Menu
>
> 1.1 - In your Jira Cloud instance, click the *Settings*/gear icon on the top right of the screen (Figure 1 - 1).
>
> Then, select the *Issues* option (Figure 1 - 2).
>
> 1.2 - The *Issues* menu will open on the left side of the screen (Figure 2 - 1).
>
> 
>
> 1.3 - Click *Workflows* (Figure 2 - 2). Here you will see the list of active and inactive workflows (Figure 3 - 3).
>
> > ℹ️ Go [here](https://confluence.atlassian.com/adminjiraserver073/advanced-workflow-configuration-861253591.html#Advancedworkflowconfiguration-postfunctions) to see the full post functions configuration documentation.
>
> > Macro (rw-step)
>
> ### Adding the Xporter Multi-Action to the Transition
>
> Select the Xporter Multi-Action option (Figure 4 - 1) and then click the *Add* button (Figure 4 - 2).
>
> 
>
> > Macro (rw-step)
>
> ### Adding Parameters to the Function
>
> 
>
> Here, you can:
>
> - Select the template to use (Figure 5 - 1).
> - Choose the output format (Figure 5 - 2).
> - Provide the name of the file you want to generate (Figure 5 - 3; mandatory field).
> - Configure a new post action (Figure 5 - 4). If you click the *Configure* button, a modal will open (Figure 6).
>
> Once you're finished, click the *Add* button (Figure 5 - 5).
>
> > Macro (rw-step)
>
> ### Configuring an Action
>
> - The Xporter Post Function provides different actions and each of them will have its specification (learn more about each action below).
> - 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.
> - The filename can be modified on each action and it can be specified as 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
>
> Select this option (Figure 6) if you want the document generated to be attached to the issue that performed the transition.
>
> 
>
> Here, you can:
>
> - Choose one of the different actions. In this case, it is *Attach File* (Figure 6 - 1; mandatory field).
> - Use the toggle to have the default filename enabled or disabled (Figure 6 - 2). The filename configuration has a size limit of 50 characters (but the exported file name doesn't have a limit).
> - Enter a file name for the file that will be attached to the issue (Figure 6 - 3; mandatory field).
>
> Once you're done, click the *Confirm* button (Figure 6 - 4).
>
> #### Upload File
>
> Choose this option (Figure 7) if you want to upload the generated document to a file server. Just 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).
>
> 
>
> Here, you can:
>
> - Select one of the different actions. In this case, it is *Upload File* (Figure 7 - 1; mandatory field).
> - Choose the *Select file server* option (Figure 7 - 2; mandatory field).
> - Use the toggle to have the default filename enabled or disabled (Figure 7 - 3). The filename configuration has a size limit of 50 characters (but the exported file name doesn't have a limit).
> - Enter a file name for the file that will be attached to the issue (Figure 7 - 4; mandatory field).
>
> Once you're done, click the *Confirm* button (Figure 7 - 5).
>
> #### Send Email
>
> Select this option (Figure 8) if you want to send reports by email with a custom body message.
>
> 
>
> Here, you can:
>
> - Choose one of the different actions. In this case, it is *Send Email* (Figure 8 - 1; mandatory field).
> - Insert the recipient's email address (Figure 8 - 2; mandatory field).
> - Enter the email subject (Figure 8 - 3; optional field).
> - Write the email's message (Figure 8 - 4; optional field).
>
> Once you're done, click the *Confirm* button (Figure 8 - 5).
>
> > Macro (rw-step)
>
> Actions Overview
>
> After choosing all the actions that will be performed, Xporter will give you an overview of each action (Figure 9 - 1) with a description (Figure 9 - 2) and the filename (Figure 9 - 3). The filename configuration has a size limit of 50 characters (but the exported file name doesn't have a limit).
>
> 
>
>
> Here you can also edit (Figure 9 - 4) and/or delete (Figure 8 - 5) the actions based on your requirements.
>
> You can also add a new action (Figure 9 - 6).
>
> > Macro (rw-step)
>
> ### Configuration Concluded
>
> After the configuration process is finished, the post functions of the transition will look like the screenshot below (Figure 10).
>
> 
>
> Here, you can:
>
> - Publish the draft (Figure 10 - 1), discard the draft (Figure 10 - 2), and/or view the original issue (Figure 10 - 3).
> - Edit (Figure 10 - 4) and/or view the transition's properties (Figure 10 - 5).
> - Add a post function (Figure 10 - 6).
> ℹ️ The mappings that you can include are identical to the [mappings used](https://docs.getxporter.app/space/XPORTERCLOUD/558575/Mappings)[ inside the templates](https://docs.getxporter.app/space/XPORTERCLOUD/558575/Mappings) with the same notation.
> ℹ️
> ℹ️ You can also use these Xporter format functions:
> ℹ️
> ℹ️ - [Fields with HTML](https://docs.getxporter.app/space/XPORTERCLOUD/527053/Wiki+Markup%2C+HTML+and+Links)
> ℹ️ - [Formatting Date Fields](https://docs.getxporter.app/space/XPORTERCLOUD/460547/JavaScript)
> ℹ️ - [Formatting Number Field](https://docs.getxporter.app/space/XPORTERCLOUD/558535/Formatting+Fields)
> ℹ️ - [Formatting User Picker Fields](https://docs.getxporter.app/space/XPORTERCLOUD/558535/Formatting+Fields)
> ℹ️ - [Escaping fields](https://docs.getxporter.app/space/XPORTERCLOUD/558535/Formatting+Fields)
> ℹ️
> ℹ️ **You can't use JavaScript with these mappings.**
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/XPORTERCLOUD/18251779/In-App+Chat+Support).