Create Aliased existing records, DeepInsert service support for Business Process Flow

[JanLosenicky]

Prerequisites

Branch is based on this PR: #182

Purpose

Having already existing aliased records

Specify '@key' in .json data file to reference already existing record in database.

Enabling creation of records in specific Business Process Flow stage

Specify '@bpf' as an object with '@logicalName' and '@activestageid' to be able to move record to desired bpf stage.

Adding step binging [Given(@"'(.*)' exists")]

Added this binding which will call the same logic as the [Given(@"I have created '(.*)'")] so the human language makes more sense while having an existing record or record in specific bpf stage.

Example:

#Entity
@talxis_opportunityheader

Feature: Open Opportunity

Background:
	Given I am logged in to the 'TALXIS Sales' app as 'a salesman'
	And 'an existing account' exists
	And 'an opportunity in won stage' exists
	And I have opened 'the opportunity in won stage'
Scenario: Open Opportunity In Won Stage
	Given I have opened 'the opportunity in won stage'

an existing accounts.json

{
  "@logicalName": "account",
  "@alias": "the existing account",
  "@key": "126caa2c-9133-ef11-a316-7c1e5235b61b"
}

an opportunity.json

{
  "@logicalName": "talxis_opportunityheader",
  "@alias": "the opportunity",
  "talxis_name": "Test Opportunity",
  "talxis_accountid@alias.bind": "the existing account"
}

an opportunity in won stage.json

{
  "@extends":  "../an opportunity",
  "@logicalName": "talxis_opportunityheader",
  "@alias": "the opportunity in won stage",
  "@bpf": {
    "@logicalName": "talxis_opportunitybusinessprocessflow",
    "@activestageid": "b573544e-8c04-4b6d-ac3d-84d810d92ac1"
  }
}

Approach

• adding [Given(@"'(.*)' exists")] binding
• introducing RecordService with function to get existing record
• update of dataManager to prevent cleanup of already existing records
• update of deepInsertService to be able to work with '@bpf'
• modifying and creating related tests

TODOs

• Automated test coverage for new code
• Documentation updated (if required)
• Build and tests successful

[ewingjm]

Hi @JanLosenicky. Thanks for the contributions. Could you please document the new features and, if possible, split them into separate pull requests?

[JanLosenicky]

Hi @JanLosenicky. Thanks for the contributions. Could you please document the new features and, if possible, split them into separate pull requests?

Hello @ewingjm, I have separeted feature for creating records in specific BPF stage there: #184. I will create separete PR for aliased exsiting records soon.

Also this #182 needs to be merged first, lmk if there's anything blocking it.