2022.2

l
Directory: Enter the directory to which the job files are to be uploaded. If you leave this box
empty, the job files are sent to the root directory of the FTP server.
l
File name: Enter the name under which the output job file will be saved. Consider using a
dynamic name, since if you use a static name every new file will overwrite the previous one.
l
Connection mode group
l
Active: Select to prompt PlanetPress Workflow to use the active mode when sending files
to the FTP server.
l
Passive: Select to prompt PlanetPress Workflow to use the passive mode when sending
files to the FTP server.
Miscellaneous Tab
The Miscellaneous tab is common to all tasks.
Check the option Use as step description to display the text next to the icon of the plugin in the Pro-
cess area.
Microsoft 365 Email Output
The Microsoft 365 Email Output task can send emails on behalf of any user in an organization's
Microsoft 365 accounts, without having to specify that user's credentials. This way privacy is main-
tained while allowing a process to send email messages and attachments on behalf of any user. The
task communicates through HTTPS. However, the real protection scheme (like certificates) is con-
figured in Azure Active Directory by the IT administrators.
Note that this task doesn't merge data records with a PlanetPress Connect template, like the "Create
Email Content" on page502 task does.
This task uses the Microsoft Graph API.
For this task to function correctly, Workflow needs to be granted application permissions for Microsoft
Graph in the organization’s Azure instance.
It needs read access to the Users category (User.Read.All) so that the task can identify the users in
the organization.
In addition, to send emails on any user’s behalf, the Mail.Send permission is required.
For more information on setting application permissions for Microsoft Graph, see https://-
docs.microsoft.com/en-us/graph/auth-v2-service.
Input
Any data file.
Page 548