ce570c4d-2ad4-4da7-b7da-603ff2be6641.PNG

RPA Developer

a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

This template can be used as a starting point for automating processes where the input data comes from an email account. The code here works with a normal email account, but it can work also with a shared email account if correctly configured.

  

**Prerequisite:**

The user should create in the email account a **folder** where the successfully processed emails are moved and configure the ProcessedEmailsMailFolder parameter in the Config.xlsx file.

  

**Description:**

This ReFramework can be used when processing a list of emails. The **datatype** of the **TransactionItem** is **MailMessage** and the datatype of the **TransactionData** is **List**. By default, this uses Exhange Server for retrieving the emails, but you can use also other providers and adapt the framework to it. 

  

The main issue that is adjusted is the fact that the list of emails is not marked as read in the **Init** step, but in the **EndProcess** step.

The other main adjustment by this is that if the robot crashes in the middle of the **process** then, if the robot is ran again it will still find the unread emails that were not processed yet.

  

**Init**: Inside the **'**GetInitialData.xaml' workflow the 'GetEmails.xaml' workflow is invoked. All the unread emails are added to a list, but they are not marked as read.

\* Inside the GetEmails.xaml, 'GetAppCredentials.xaml' is invoked. This is used for the Exchange server authentication. If you are working with Integrated Outlook, you don't need that.

  

**Process**: Beside the code that any developer can add, the last step is to invoke 'MoveProcessedEmail.xaml' which moves the just processed transaction item into the folder for the processed emails (the one that was previously created and configured in the ProcessedEmailsMailFolder parameter in the Config.xlsx file) only if the transaction was successful.

  

**End Process**: Before the invoke of 'CloseAllApplications.xaml', the workflow 'MarkAsReadAllEmails.xaml' is invoked and all the emails existing in the folder created prior by the user for the processed emails to be moved and then they are marked as read.

This adjusted ReFramework can work both for a **normal email accoun**t and also for **shared email accounts**, but for the shared email, the developer must add the required information in the Exchange activities used for reading the email, moving the mail and mark as read the messages.

The Robotic Enterprise Framework configured and optimized to get the input data from a list of emails. This is an adapted framework version of the Generic ReFramework.

**This package consists in one Scope Activity and 10 Activities that can be used for the basic operations in ActiveDirectory:**

1.  Active Directory Scope
2.  Add User To Group
3.  Change User Password
4.  Check User
5.  Create User
6.  Delete User
7.  Disable User
8.  Enable User
9.  EnableExpirePasswordNow
10.  Find User
11.  Remove User From Group

This is a Custom Activities package that provides an integration between UiPath and Active Directory connector that permits the usage of the key functionalities of Active Directory

The package contains a set of activities which can be used independently or in a flow of multiple combined activities respecting the business logic of the flow in Salesforce. These activities can also be used together with any other activity.

  

All the activities have mandatory and (sometimes) optional inputs based on the logic provided.

  

Each activity has a mandatory property called UiElement as input/output. Any activity should be included in a Use Application/Browser resource activity manually indicating the Salesforce application page needed (this can be the Home page, for example). In the Use Application/Browser activity the user should Save For Later Use the Output of the Use Application/Browser and then use this value as an input for each Salesforce activity included inside the resource in the UiElement property.

  

All the activities have a Default property named “Selector Timeout” with value 5 (seconds) which can be modified, if needed. This is the amount of time awaited for all the selectors inside the activity before erroring out.

  

Each activity should have a logical starting point mentioned also in each description bellow.

  

Activities inside the package:

*   Account GetOpportunities
*   Account NavigateToAccount
*   Case NavigateToCase
*   General

ChangeApp

NavigateToDetails

NavigateToMenu

NavigateToRecord

ReadAllDetailsFields

ReadCheckbox

ReadFieldValue

UpdateCheckbox

UpdateLookupField

UpdatePickListField

UpdatePickListMultiSelectField

UpdateTextareaField

UpdateTextNumberPercentageDateField

*   Opportunity NavigateToOpportunity

This package includes a set of activities that interact with the Lightning User Interface of Salesforce. The activities included in the package are meant to be used by Citizen Developers.

About me