Azure Automation and Actions

Automations in Azure DevOps are designed to streamline processes and enhance efficiency by automating repetitive tasks. They save time by automatically executing predefined actions based on specific triggers or conditions.

Create Automations To create an Automation, go to the Project Settings tab under Peeklogic Setup, select Project, Work Item Type, and click Automation Integration.

1. Click New

• Click New Automation.

2. Enter basic information

• Process Name: Enter a name for the automation configuration.
• Select Salesforce Object: Select the Salesforce object that will be used as the source (for example, Case).
• Record Type (optional)
• Description (optional): Enter a short description of the configuration.

3. Save

• Click Save

After saving, the configuration opens and the Fields Mapping section becomes available.

Configure Fields Mapping

Field mapping is a way to set up how data is passed from Salesforce to ServiceNow.

• A field can be given a fixed value (Default Value).
• Or it can be linked to another field (Field Reference) so that the data is filled in automatically. Only fields with a matching type will be available for mapping.
  

👉 Picklists: when using Field Reference with picklists, each value must be mapped manually. You choose a value from the ServiceNow picklist and assign the corresponding value from the Salesforce picklist.

Click Add Mapping to add additional rows.

Click Save All Changes to save the mappings

Enable / Disable Automation

• This toggle is used to set whether the automation process is Active or Inactive.
• When set to Active, the automation can be used by the integration flow to create/populate items automatically.
• When set to Inactive, the configuration remains saved but is not used for automated creation.

Additional actions

• Return to Process List: navigates back to the list of configurations.
• Delete Process: deletes the current automation configuration.

Flow Actions

Flows are simple instructions that trigger automated actions.

They define when automation should start (for example, when a record is created or a field is updated). You decide what happens next.

👉 This way, Flows help you tailor processes to your needs and make your work more convenient and efficient.

Custom Apex Flow Actions are tailored components that automate specific tasks within Salesforce, designed to meet unique business needs. In our setup, we use two custom actions to create and edit work items.

Peeklogic Create Work Item

Purpose: Automatically creates Azure DevOps work item(s) for a specific Salesforce record using a selected Automated Process Configuration.

Behavior: When invoked, it takes the provided sObjectId, applies the mapping from automatedProcessId (or automatedProcessIds), and queues the creation job (sync or async based on executeAsynchronously). The created work item(s) are then linked back to the Salesforce record (according to your process configuration).

Input Variables:

• sObjectId: This is the unique identifier of the record that you want to process.
• automatedProcessId: You would typically use Automated Process Id
• automatedProcessIds: You would typically use List  Automated Process Ids
• executeAsynchronously: This flag determines the execution timing

Peeklogic Edit Work Item

Purpose: Automatically updates existing Azure DevOps work item(s) that are already linked to a Salesforce record, using the selected Automated Process Configuration.

Behavior: When invoked, it takes the provided sObjectId, applies the mapping from automatedProcessId, and queues the update job (sync or async based on executeAsynchronously).

If workItemIds is provided, the action is applied only to those target work item(s); otherwise, it updates the relevant linked work item(s) defined by the process configuration.

Input Variables:

• sObjectId: This is the unique identifier of the record that you want to process.
• automatedProcessId: You would typically use Automated Process Id
• executeAsynchronously: This flag determines the execution timing
• workItemIds: The purpose of this input is to specify the target Work Item(s) on which the component should perform its action.

Manual Process Configuration

Manual Process Configuration allows you to predefine certain fields when creating a work item. This means that when you open the form to create a new work item, some fields will already be filled out based on the configurations you’ve set up.

How to Set Up Manual Process Configuration

Step 1: Navigate to Manual Process Configurations

• Go to the Project Settings tab under Peeklogic Setup
• Select Project, Work Item Type
• Select Manual Create

Step 2: Create New Configuration:

• Click “New Automation” button
• Fill in the basic details:
• Process Name: Give your configuration a name
• Active: Check this box to activate the configuration (only one can be active at a time)
• Select Salesforce Object: Choose which Salesforce object this applies to
• Select Record Type: Choose a specific record type (optional)
• Description: Add a description of what this configuration does

Step 3: Save Basic Configuration

• Click “Save” to proceed to field mapping

Step 4: Set Up Field Mapping(similarly to the setup for automation)

• Map Azure DevOps fields to either:
• Default Value: Set a fixed value that will always appear
• Field Reference: Link to a Salesforce field to pull data automatically
• For picklist fields: Map each Azure value to the corresponding Salesforce value

Step 5: Save and Activate

• Click “Save All Changes” to finalize your configuration
• The configuration is now ready to pre-fill work item forms

This setup ensures that when users open the Create a new work item form, the configured fields will be automatically populated based on your settings.