Cloning a SharePoint Site Collection and running the K2 registration wizard results in an error stating: "A Site Collection with the title [SharePoint Site Collection name] has already been registered". This error occurs at the final step of the wizard.

None

A group provider is still pointing to the old SharePoint Site Collection name and needs to be deleted.

Delete the duplicate old group provider pointing to the old SharePoint Site Collection name and run the K2 registration wizard again. This will register the new group provider for the new SharePoint Site Collection.

New properties added to SharePoint List or Library based SmartObjects not showing in Forms or Views.

1. Were the properties added to the SmartObject in K2 Designer?
2. Was the SmartObject edited by adding columns in the SharePoint List or Library itself?

The SmartObject was edited via the K2 Designer which causes the SmartObject in the K2 App to be out of sync.

It is recommended to add columns directly in the SharePoint List or Library and then regenerate the SmartObject, Views and Forms. If this was not the case we recommend that you edit the SharePoint List or Library with the new columns or remove the necessary columns and regenerate the SmartObject, Views and Forms. Manually adding the fields to the Views will only add these fields to the Views and Forms and the SmartObject will still be out of sync. It is important however that if you remove columns to run through the Forms, Views and Workflows making use of these columns and ensure that these items are updated as well.

Unable to start a workflow after editing SharePoint List or Library and regenerating SmartObjects. An error occurs stating: "An unexpected error has occurred while trying to resolve a value for Resolver ID: 106C5886-18B1-4c09-BEB3-6F7342669D18.Logged : True".

1. Was the SmartObjectt edited in K2 Designer?
2. Was the SmartObject edited by editing the SharePoint List or Library itself?
3. How many SmartObjects are involved?
4. Was there any associations on the SmartObjects?
5. Which SharePoint List or Library is the primary list or library where the Workflow exists?
6. Are there lookup columns involved?

Associations created on SmartObjects were orphaned after editing the SharePoint List. A SmartObject was auto generated for the SharePoint List which contained a lookup column to reference another list. A SmartObject for the list being referenced in the lookup column was also generated with associations between the two SmartObjects. After editing the list being referenced, these associations were orphaned causing the error when starting a workflow. Another reason could be when using a column of a SharePoint list as the workflow folio, and at a later stage removing the column from the list and regenerating the SmartObject.

1. If these associations are no longer required, delete them from the associations tab in the SmartObjects in K2 Designer and save the SmartObject. Run through the Start wizard of the Workflow to refresh the association options.
2. If these associations are still required, they need to be remapped from the associations tab in the SmartObjects in K2 Designer.
3. If it was related to the removed column being used as the workflow folio, run through the Start wizard of the workflow to edit the Folio value.

Using a Rule on a Form to start a workflow successfully starts the workflow but no parameters are passed into the workflow.

Is the SharePoint List or Library SmartObject correctly used as a reference on the Form?

When starting a workflow using a Form rule, the SharePoint List or Library SmartObject needs to be passed into the reference's field to give the workflow context to the instance of the list or library item from which the instance has been initiated.

Ensure that the Item Reference property is configured with the correct SmartObject in the Workflow Start wizard. This is configured automatically, but if a user changes these settings they need to ensure to use the correct SmartObject.

1. Edit the workflow and open the Start Wizard.
2. Expand the "Specify the Form that will start the workflow" section.
3. Ensure the Item Reference property is referencing the correct SmartObject.

Opening a worklist item results in an error stating: "Action not found".

What is the Rule structure for actioning worklist items on a Form?

The following Rule structure is incorrect as it is trying to action a worklist item when the Form is initializing and has no context of the action yet as the action was configured to be selected either using a radio button or dropdown list or similar controls: When the Form is initializing > If current Workflow activity is…. >>Then action worklist item.

Edit the Form related to the specific workflow step and edit the "When a Form is initializing" rule for the state that was selected in the workflow step. Ensure the Rule structure is configured to first open the worklist item to get context of the configured actions. Only after opening the worklist item can the item be actioned. These rules are automatically created in the correct order when creating a K2 Application, but can be edited by the user.

Form not saving after clicking the Submit button.

1. Are there any extra validtions occurring on the Form?
2. Are there hidden fields on the Form?
3. Were any of the fields removed from the Form?

When extra validations were added on a Form and changes were made to fields, ensure that these extra validations are still required or that the field is not referencing a field on the Form that was removed.

1. Remove any references to fields that were removed from the Form in these extra validations, or
2. Remove the extra validations if they are no longer required due to fields removed from the Form.

After adding a new Data Label control on a Display Form, other fields are empty at runtime.

This issue can be reproduced using the following steps:

1. Create a custom list and appify the list.
2. Edit the Display Form.
3. Add a new Data Label.
4. Assign a Field to the Data Label using the properties panel and save the Form.
5. Run the Form.
6. Notice that only the new Data Label is populated.

Output mappings are empty by default, this means that SmartForms will automatically resolve them at runtime. As soon as you specify one output mapping, auto resolve is stopped. When adding a Data Label and setting an action to populate the Data Label, an output mapping was created only for this Data Label. When specifiying one mapping, you have to specify a mapping for all the fields due to the auto resolve that is stopped if manual mappings are specified for a control.

1. Edit the Form and go to the Rules tab.
2. Edit the "When the view executed initialize" Rule.
3. Configure the "then execute the Get List Item By ID method" action.
4. Map the Form ID parameter to the Input Properties ID field.
5. Go to the Output Mappings and click Auto Map.
6. Save and finish the Form.