Workflow: Form Entry Action - Creating Additional Blank Person Record

[noblemosby]

Description

When submitting a workflow with the Form Entry Action from the Workflow Entry block via the External Website, the person record is created but also an additional person record is created with blank information.

CORRECT PERSON RECORD & HISTORY

BLANK PERSON RECORD & HISTORY

Actual Behavior

When submitting a workflow with the Form Entry Action from the Workflow Entry block via the External Website, the person record is created but also an additional person record is created with blank information.

When submitting the same workflow internally from the internal site, the additional blank person record is NOT created.

Also, when submitting the workflow on the external site when the user is logged in does not create the additional blank person record.

The issue doesn't seem to be related to any other action inside the workflow. Once the Form Entry action is completed, even without the workflow completing, both records are created, complete record and blank record.

Expected Behavior

The expected behaviour is that no additional blank person record would be created.

Steps to Reproduce

Go to Settings -> Workflow Configuration.

• Create a simple workflow that includes the Form Entry & Workflow Complete Actions.
• Add Workflow Attributes for 'Person' (Person Attribute) and 'Family' (Group Attribute)

In the Form Entry Action Settings:

• Enable Person Entry: Checked
• Gender, Email Address, Mobile Phone: Required
• Person Attribute: Person Workflow Attribute
• Family Attribute: Family Workflow Attribute

Go to Settings -> Pages.

• Add the Workflow Entry block to a page on the External Webpage.
• Select the newly created workflow and save.

Go to the External Website.

• Log Out or Open a Private/Incognito browser.
• Go to the page where the form is located.
• Fill out and submit the form.

Go to the Internal Website.

• Check the workflow history to see the entry has been created.
• Search for the newly created person profile record.
• You should see the blank profile record created in the family of the newly created person.

To test Internally (which does not create the blank record)

• Go to Tools -> Workflows
• Fill out the form and submit.
• Check the workflow log.
• Search for the newly created person. You should not see an additional blank record created.

Issue Confirmation

• Perform a search on the Github Issues to see if your bug is already reported.
• Reproduced the problem on a fresh install or on the demo site.

Rock Version

Rock McKinley 17.3 (17.3.1)

Client Culture Setting

en-US

[chead4]

@noblemosby Hi Noble - Can you let us know if this issue is happening with the new Obsidian Workflow Entry block or on the Webforms block?

[noblemosby]

Obsidian Workflow Entry block

…

On Aug 25, 2025, at 10:13 AM, Colleen Head ***@***.***> wrote: Obsidian Workflow Entry block

[bpvan24]

We're having the same issue in v17.2. I think the issue stems from a change made recently affecting v17+.
When the block fires the "GetNextInteractiveForm" block action, it processes our user entry form which runs the WorkflowPersonEntryProcessor's SetFormPersonEntryValues method.
I think the issue is either from changes made in this commit a month ago: 99ed508
Or this other commit from four months ago: 8dffa3c

The tests for the WorkflowPersonEntryProcessor all have the "Spouse" field included, which misses the cases where the "Spouse" fields would be blank/missing. Now, I'm not confident of this but I think these lines:

Rock/Rock/Workflow/WorkflowPersonEntryProcessor.cs

Lines 433 to 436 in 164dbcf

	if ( personEntryValues.Spouse != null )
	{
	var personEntryPersonSpouse = CreateOrUpdatePersonFromEntryValues( form, existingSpouse, primaryFamily, personEntryValues.Spouse );
	if ( personEntryPersonSpouse.Id == 0 )

are thinking the personEntryValues.Spouse is not null (the First/Last name properties are blank though). So, existingSpouse is missing but it will create a new Person anyways in the family.

When this gets processed in PersonMatchQuery that sets First and Last Name to string.Empty

Rock/Rock/Model/CRM/Person/PersonService.cs

Lines 533 to 542 in 164dbcf

	public PersonMatchQuery( string firstName, string lastName, string email, string mobilePhone )
	{
	FirstName = firstName.IsNotNullOrWhiteSpace() ? firstName.Trim() : string.Empty;
	LastName = lastName.IsNotNullOrWhiteSpace() ? lastName.Trim() : string.Empty;
	Email = email.IsNotNullOrWhiteSpace() ? email.Trim() : string.Empty;
	MobilePhone = mobilePhone.IsNotNullOrWhiteSpace() ? PhoneNumber.CleanNumber( mobilePhone ) : string.Empty;
	Gender = null;
	BirthDate = null;
	SuffixValueId = null;
	}

Just wondering if that is the cause of this. At the very least it affects us at v17.2